UNIX 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
sambit
Participant
Posts: 52
Joined: Mon Sep 05, 2005 4:59 am

UNIX Return Code 127

Post by sambit »

Hi,
I am triggering a UNIX script from my sequencer using the execute command activity but it is failing with a return code of 127. But when I run this script manually from the command line it runs successfully. Any ideas why it is failing thru sequencer?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Can you post the complete log entry that shows the Execute Command stage running and what it returned?
-craig

"You can never have too many knives" -- Logan Nine Fingers
sambit
Participant
Posts: 52
Joined: Mon Sep 05, 2005 4:59 am

Post by sambit »

Sequencer Log
----------------
JobScr1..JobControl (@Execute_Command_31): Executed: /data/user/prod/script/run_j1.ksh
Reply=1
Output from command ====>

JobScr1..JobControl (@Execute_Command_31): Command /data/user/prod/script/run_j1.ksh did not finish OK, reply = '1'

Unix Log
----------
Function create inp_desc.cst - Failure. Return Code = 127
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

What is the exit status of the command from outside ?
sambit
Participant
Posts: 52
Joined: Mon Sep 05, 2005 4:59 am

Post by sambit »

the exit status is 1.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

An exit status of zero would indicate success.
-craig

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