.net

lstacks · Post by **lstacks** » Mon Jul 31, 2006 8:03 am

If a job is designed in DataStage, which may or may not utilize custom routines, is there an interface / conversion process to .net?

ArndW · Post by **ArndW** » Mon Jul 31, 2006 9:28 am

I wish I understood the question. The normal custom routines in DS server are written in DS/BASIC and are internal to the package, so .net doesn't play a role. External routines can (with some difficulty) be bound into the package, but they too are unaffected by .net.
Are you referring to custom written stages?

lstacks · Post by **lstacks** » Mon Jul 31, 2006 9:45 am

I threw in the question about the routine as a side bar. They specific question is, "If you have a DataStage job that runs cleanly in the server environment, can that job be executed from a .net connection?"

ArndW wrote:I wish I understood the question. The normal custom routines in DS server are written in DS/BASIC and are internal to the package, so .net doesn't play a role. External routines can (with some difficu ...

ArndW · Post by **ArndW** » Mon Jul 31, 2006 10:20 am

Jobs are initiated from the DataStage server machine using the "dsjob" command. If you can issue this command then you can run a job. The .NET doesn't come into it at all.

ray.wurlod · Post by **ray.wurlod** » Mon Jul 31, 2006 11:38 am

No. .NET is a Windows-only phenomenon. You have specified running DataStage on UNIX. Therefore you can not use any .NET programming.

DataStage on Windows platforms can invoke functions exposed via COM objects, but I do not believe there is anything more flexible than that to take any advantage of the .NET framework (even though to run the clients you must have version 1.1 of the .NET framework installed).