Hi All,
I have to deploy the project with 60 separate jobs into Test env.
Is there any way to use
'Multiple Job Compile' Datastage utility
through unix.
Thanks and regards,
Munish
Multiple Job Compile Utility
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Unless your test environment consists of protected projects there's nothing to stop you connecting to them with a client tool and effecting a multi-job compile that way. Of course, as others noted, you can obviate the requirement completely by exporting and importing the job and routine executables.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I guess you intention to automate the process of compiling the code as soon as it is promoted from Dev to Test. The other option available is, pass on the list of jobs that are promoted to 'dscc', a client executable, to compile the jobs.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Thanks Gentlemen,
I deployed them as Executable.
However, if someone could throw some more light on
1.
I deployed the jobs as Executable with Design Information,
When I open that DSX,
Some of the DSX have design information with binary information (0,1)
WHERE
as in others it is Design information with some OSH information.
What exactly happens when we create Executable with Design Information.
2.
All the Executables (With Design) have
ToolVersion "4"
ServerName "olbdev-o.in.telstra.com.au"
ToolInstanceID "TEG_R1-CBA-TRIAL3"
in the heading.
Will that make any difference when we export them to another environment.
I tried exporting them to New Project but on the same server.
and it worked fine.
Any comments!!!!
Thanks and regards,
Munish
I deployed them as Executable.
However, if someone could throw some more light on
1.
I deployed the jobs as Executable with Design Information,
When I open that DSX,
Some of the DSX have design information with binary information (0,1)
WHERE
as in others it is Design information with some OSH information.
What exactly happens when we create Executable with Design Information.
2.
All the Executables (With Design) have
ToolVersion "4"
ServerName "olbdev-o.in.telstra.com.au"
ToolInstanceID "TEG_R1-CBA-TRIAL3"
in the heading.
Will that make any difference when we export them to another environment.
I tried exporting them to New Project but on the same server.
and it worked fine.
Any comments!!!!
Thanks and regards,
Munish
MK
1. 'Binary' executable for the Transformer stages, OSH scripts for the rest.
2. Internal product gobbledygook. Don't lose any sleep over it. As long as the 'another environment' is properly setup and at least the same version, you'll be fine.
2. Internal product gobbledygook. Don't lose any sleep over it. As long as the 'another environment' is properly setup and at least the same version, you'll be fine.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers