Hi,
We have current jobs/sequences done in server 7.5.1. Planning to have 7.5.2 where we want to do the jobs in Parallel.
Can we have the Sequences used in the server intact?? i.e. We currently have routines/jobs build up to get the data from database and load as job parameters into the job activities (via User Activity).
Can we use the same routines/jobs to load job parameters into job activities (via User Activity).
As far as the sequences are concerned, will it matter if they r server jobs or parallel jobs?
Regards
Structure Server/Parallel
Moderators: chulett, rschirm, roy
Re: Structure Server/Parallel
Hi,
The sequences will be intact.
The sequences will be intact.
It took me fifteen years to discover I had no talent for ETL, but I couldn't give it up because by that time I was too famous.
-
- Participant
- Posts: 97
- Joined: Tue Feb 21, 2006 6:45 am
Hi,tostay2003 wrote:Sorry, by intact, i meant, can I use the same sequences, except that in job activities this time i will be calling parallel jobs
The point is there is no separate thing called server job sequence and parallel job sequence. Hence, it really does not matter which type of job you are about to call. It will always work.
It took me fifteen years to discover I had no talent for ETL, but I couldn't give it up because by that time I was too famous.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
However, unless you change the jobs referred to in the Job activities, they will still be the server jobs. There is no magic means by which jobs can automatically be migrated to parallel equivalents merely because you have installed Enterprise Edition.
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.
Exactly,ray.wurlod wrote:However, unless you change the jobs referred to in the Job activities, they will still be the server jobs. There is no magic means by which jobs can automatically be migrated to parallel equivalents merely because you have installed Enterprise Edition.
Infact, if you just change the jobs from server to parallel, keeping the same job name, u wont even have to recompile ur sequences. They will invoke the same jobs i.e., jobnames and it will end up invoking the new parallel jobs which have replaced the old server jobs. The parameters for the job obviously have to remain the same even for the parallel job for otherwise u will have to alter the sequence and pass the additional parameter values.
It took me fifteen years to discover I had no talent for ETL, but I couldn't give it up because by that time I was too famous.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Create parallel versions of each job you want to replace. Only replace your high volume and slow jobs, no reason to replace the smaller jobs. Use the copy parameters utility to copy the standard set of parameters into each of your parallel jobs. Give your jobs the same names as the server edition with a standard prefix or suffix.
With your sequence jobs export them, change the job name in the export file to have the new suffix/prefix and import them again. This will switch them across to the parallel jobs.
With your sequence jobs export them, change the job name in the export file to have the new suffix/prefix and import them again. This will switch them across to the parallel jobs.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn