An AutoSys command job, without a std_in_file, runs to FAILURE with an exit code of 121.

Document ID : KB000050422
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

An AutoSys command job, without a std_in_file, runs to FAILURE with exit code of 121.
<Could not open Input File:>

Sample JIL:

insert_job: w3 job_type: c
command: c\:\progra~1\ca\unicen~3\autosys\bin\autoflags -a
machine: a142b225w2k
owner: administrator@a142b225w2k

Except from event_demon.$AUTOSERV log:

[05/26/2011 03:23:06] CAUAJM_I_40245 EVENT: STARTJOB JOB: w3   
[05/26/2011 03:23:06] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: STARTING      JOB: w3 MACHINE: a142b225w2k   
[05/26/2011 03:23:07] CAUAJM_I_10082 [a142b225w2k connected for w3 68582.223.1]   
[05/26/2011 03:23:07] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: RUNNING       JOB: w3 MACHINE: a142b225w2k   
[05/26/2011 03:23:08] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: FAILURE       JOB: w3 MACHINE: a142b225w2k EXITCODE: 121   
[05/26/2011 03:23:08] <Could not open Input File:>   
[05/26/2011 03:23:08] CAUAJM_I_40245 EVENT: ALARM ALARM: JOBFAILURE             JOB: w3 MACHINE: a142b225w2k   
[05/26/2011 03:24:00] ----------------------------------------  

Solution:

This can be caused by the NULL plug and play device not being active on the remote agent machine.

Right mouse click My computer -> Manage
Expand out computer Management (Local) -> System Tool -> Device Manager
Expand out <hostname> -> Non-Plug and Play Drivers -> Null
Null must be enabled and started.
To change the state and setting a system reboot is required.