Correct configuration file not getting generated

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
skathaitrooney
Participant
Posts: 103
Joined: Tue Jan 06, 2015 4:30 am

Correct configuration file not getting generated

Post by skathaitrooney »

Hi Everyone,

I have a sequence job calling the sequencer.sh with 2 parameters
(sequencer.sh -c2 -p2).
Instead of returning a config file with 2 nodes and 2 partitions, a config file is getting generated in the gridjobdir with only 1 node and 1 partition.

Can anyone suggest something on this??

Thanks!!
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Given that a config file is being generated, you have APT_GRID_ENABLED set to True. Now you have to look at APT_GRID_COMPUTENODE and APT_GRID_PARTITIONS to make sure that the values you are passing are the ones you expect. Depending on the version of your Grid ENablement Toolkit... a blank value might default to "1". Check what you are passing in, and look at the project level defaults.
lstsaur
Participant
Posts: 1139
Joined: Thu Oct 21, 2004 9:59 pm

Post by lstsaur »

How many jobs in your job sequence? In each job in the job sequence, you must set the $APT_GRID_ENABLE to NO. Did you specify the Compute Nodes and Partitions parameters in your Execute Command Activity stage? Then your downstream job activity stages using the expressing: Field(stagename.$CommandOutput," ", fieldnum) to access those passed parameters values?
Post Reply