Version Control in DataStage

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

There is an option in the Administrator client to set the ability for operators to view all jobs. Open the Project properties and you will find on the Permissions tab a check box called DataStage Operator can view full log.

Export/import is the only available way to move jobs that have not been released from one project to another. If the export includes compiled code (there's a check box for this in the export dialogue) there is no need to re-compile.

You solve the re-naming problem in one of two ways. Either you re-write your scripts so they recognize the highest-numbered released job name, or you re-write your DataStage to use DSGetJobInfo() with DSJ.JOBNAME as the InfoType argument, which returns the actual name. DSAttachJob() automatically uses the highest-numbered released job if the unreleased job name is not present.


Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
Post Reply