Issue with Multiple instance job seq

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
akarsh
Participant
Posts: 51
Joined: Fri May 09, 2008 4:03 am
Location: Pune

Issue with Multiple instance job seq

Post by akarsh »

Hi,

I have to process four file with same meta data. i have created one px and one seq job with multiple instance feature to perform this.

i am calling this multiple ins seq by four diff script as there some more checks on the same file needs to be performed.

My issue is when these scripts calls the seq it loading the data without job is giving any error but script is giving below error

=======================================

[2013-04-30 07:29:40] - Starting to verify for the feed files availability ...
Finished waiting for job

Status code = 0
./ABC.ksh: Scv XYZSeq has failed on Tue Apr 30 07:29:51 PDT 2013

=======================================


I am just checking the multiple ins property in seq and passing the inv id in dsjob command as seq_name.inv_id.

Please suggest how to get rid off from this error.
Thanks,
Akarsh Kapoor
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not sure how anyone could help - without you posting your script we'd just be guessing.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Use the -jobstatus option instead of the -wait option in your dsjob command.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Of course, Ray is generally a pretty good guesser. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
akarsh
Participant
Posts: 51
Joined: Fri May 09, 2008 4:03 am
Location: Pune

Post by akarsh »

I got the issue.
After running the job was checking the job status as
STATUS=`dsjob -jobinfo $ds_project $ds_seq
checking with the value 1 or 2, while it will be always 99.

i updated the script as

STATUS=`dsjob -jobinfo $ds_project $ds_seq.$Inv_Id

which worked fine.
Thanks,
Akarsh Kapoor
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

:?

Peoples, that's not a "workaround" that's a RESOLUTION. Changed.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply