DSXchange

Will do. Thanks, Vincent!

In case anyone is interested, I tried to compile some of my jobs using the command line interface instead of the V8.0.1 GUI and the performance is actually a little slower (at least in my experience).

We will be opening a ticket with IBM about the performance issues we are having as they make development almost untenable.

Hi,
In the site I'm in they built a .NET application that uses the APIs to move and compile jobs between environments as well as retrieve MF definitions directly to DS and migrate JCL and cobol code to MF from DS
But as I understand version 8 doesn't support those APIs
routines are moved manually here.

IHTH (I Hope This Helps),

In our shop, we have to protect and unprotect the projects in STAGE and PROD in order to get the compiles in those environments complete.

Unfortunately, we have 120+ projects over multiple installations and this can be a bit of a pain as we have to leave the project unprotected for up to 24 hours for the project source deployment systems to actually move the code from source control to DataStage server.

Building the process to allow the following steps in line would allow for a safer project protection strategy:

Unprotect the project
Deploy the code
Compile the code
Protect the project

Are there any tips or tricks people have come up with to either script the project/unprotect process?

The administrator user (typically dsadm) can compile in a Protected project using the Multiple Job Compiler.

That is what we use today but we need to move towards a more secure methodology. This is especially true when one team does software deployment and it not part of the DataStage admin team.

Ideally, the project admin ID would have this functionality and then not need the DataStage admin.