Parameter selection in Execute Command Activity stage

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
ratuldey
Participant
Posts: 33
Joined: Fri Jul 13, 2007 4:50 pm

Parameter selection in Execute Command Activity stage

Post by ratuldey »

DataStage Server Edn. 7.5.x2
OS : UNIX

Hi,

I have 2 questions regarding the usage of parameters in the ExecCommand tab of the Execute Command Activity stage of a Job sequence.

Suppose Job Stages names are "JobStageName1", "JobStageName2", "JobStageName3".
1.Through the Command field we specify the SH to be fired. In the Parameters field what is implication of specifying -

#JobStageName1.$JobName#=#JobStageName1.$JobStatus# #JobStageName2.$JobName#=#JobStageName2.$JobStatus# #JobStageName3.$JobName#=#JobStageName3.$JobStatus#

What is the meaning of such a parameter value?
Why do we have an equality sign between #JobStageName1.$JobName# and #JobStageName1.$JobStatus#?

2. Also in some cases we do have Parameters field with a single value "Exceptions Occured". What is meant by "Exceptions Occured" and how is it evaluated?

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

Post by ray.wurlod »

This is the example used in IBM's training class except that you have missed the most important part, namely the fact that SH is not the command they issue, but rather one that expects to get name=value pairs on its command line. $JobName and $JobStatus are "activity variables" whose purpose should be obvious from their names; however SH has no capacity to do anything sensible with them. Your example, as stated, could serve no useful purpose other than to generate a non-zero exit status from SH.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply