Page 1 of 1
How to migrate data stage jobs into production environment
Posted: Sat Feb 28, 2004 11:39 am
by iowajag
Hi,
Could anyone throw light briefly on how to migrate data stage jobs into production environment.
Thank you in advance.
iowaJAK
Re: How to migrate data stage jobs into production environme
Posted: Sat Feb 28, 2004 12:15 pm
by ogmios
iowajag wrote:Hi,
Could anyone throw light briefly on how to migrate data stage jobs into production environment.
Thank you in advance.
iowaJAK
1) Version Control that comes with the tool
2) Export jobs (in DataStage manager) from the development environment, import them in production and compile them with CompileAll (in version 7 use mass compile).
Ogmios
Posted: Sat Feb 28, 2004 3:15 pm
by chulett
Actually, there is a third method:
3) Release the jobs, create a 'Deployment Package' with the Packaging Wizard and then (after moving it to the target server, if needed) install the package using 'dspackinst'.
Me, I'd stick with #1.
Posted: Sat Feb 28, 2004 5:49 pm
by pedro.duran.silva
Hi ppl.
Release the jobs it's a good idea, but i've try to release a Job Sequencer and it's 2 inner jobs, but the association beetwen them has been lost.
The jobs called by the job sequencer are also released but the link is loss. The job sequencer is still with the link to the non released jobs.
Could anyone help?
thx
Posted: Sat Feb 28, 2004 9:12 pm
by chulett
pedro.duran.silva wrote:The job sequencer is still with the link to the non released jobs.
Shouldn't matter. You should always refer to the
unreleased Job Name in Sequencers or Job Control. Imagine the chaos if you had to constantly touch them every time you released a new version of a job they ran.
It's been a long time since I did anything with released jobs (preferring to use Version Control for job promotion once it became available) but from what I remember, DataStage will run the unreleased job if it can find it. If it can't (like in a Production project which only contains released jobs) it will find and run the
highest released version of the job in the Project.
Posted: Sun Feb 29, 2004 7:02 pm
by ray.wurlod
It doesn't matter.
DSAttachJob attaches the highest version-numbered released job if there are any present.
You can (should?) use DSGetJobInfo(hJob, DSJ.JOBNAME) to return the real name of the job being executed (for example MyJob%%rel20.2.1).
Posted: Mon Mar 01, 2004 3:06 pm
by pedro.duran.silva
thx for the tips :D
As always ... the ppl that help others are the best.
thx again.