Compiling a job in a protected project

[wademoore]

I am using DataStage version 7.51A. Using the dsadm id I can migrate code into a production "protected" project, but I can't compile the job in a protected project. Does anyone know a way around this without having to unprotect the project?

[chulett]

Hmmm... have you tried as dsadm using the Multi-Job Compiler from the Manager against the protected project?

[wademoore]

Hmmm... have you tried as dsadm using the Multi-Job Compiler from the Manager against the protected project? ...

The Multi-Job compiler is not an option (grayed out) when the project is protected, but is an option when the project is unprotected.

[kumar_s]

Perhaps you will need to import the compiled code. (With executable). Ok in other words, you cant compile in Protected Project. Even Production Manager wont be having access.

[ray.wurlod]

That's pretty much it, Wade. Protected means what it says. It's the whole SDLC (software development lifecycle) thing - nothing changes in production. So your choices, it seems to me, are two:

• compile before exporting
  
  temporarily un-protect the production project

The second option may be the only one available, for example if you develop parallel jobs on one platform and your production environment uses a different operating system/incompatible C++ compiler.

[vyyuri]

1) Import Protected Jobs into Unprotected Project
2) Goto Manager Choose Multi Compile 3) You can able to comiple them

[lokeshreddy]

I am using DataStage version 7.51A. Using the dsadm id I can migrate code into a production "protected" project, but I can't compile the job in a protected project. Does anyone know a way around this without having to unprotect the project?

Hi,

1) Try to make the changes in the job in DEV Environement and then compile it and then promote the same job to the protected Project.

2) Export the job and set the flag of read only to "0" and then Import the job and try compilin it in Protected Project.

[ray.wurlod]

A protected project has higher precedence than the READONLY flag.