Job Return Code 127

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
rager
Participant
Posts: 27
Joined: Tue Jul 17, 2007 11:23 pm
Location: UK

Job Return Code 127

Post by rager »

Hi,
Please could you tell me what does the dsjob return code 127 stand for?


Thanks,
Rager
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

You really shouldn't see anything over 99 but occasionally we do. Under what circumstances are you seeing this?
-craig

"You can never have too many knives" -- Logan Nine Fingers
rager
Participant
Posts: 27
Joined: Tue Jul 17, 2007 11:23 pm
Location: UK

Post by rager »

We are trying to run a sequence from shell script. It seems to be running fine from development environment but in UAT, the script is exiting with the return code 127.

I have never seen this before and not sure what this means. I think it is an issue with wrong parameters but was curious what the errorcode meant.

Thanks,
Rager
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

I've never seen it either and it's not a dcumented status code. Hold on, clarify something for me - does your script use "-jobstatus" or "-wait" to run the job?
-craig

"You can never have too many knives" -- Logan Nine Fingers
rager
Participant
Posts: 27
Joined: Tue Jul 17, 2007 11:23 pm
Location: UK

Post by rager »

It uses both...
dsjob -run -jobstatus -wait ...
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

You don't use both, you use one or the other. Perhaps that's contributing to it. Try removing the "-wait" and see, as the "-jobstatus" also waits.
-craig

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