Return Codes

Return codes are sent back to the initiator to report whether the transfer request is successful or not.

The following return codes are supported by the job step:

Return Code	Description
`0`	Successful: request was scheduled successfully (`WAIT=NO`). Successful: request was completed successfully (`WAIT=YES`).
`<> 0`	Unsuccessful

The following table lists the return codes that are set in message PGTB4142I when the Batch interface transfers are completed:

Return Code	Description
`0`	Successful: request was scheduled successfully (`WAIT=NO`). Successful: request was completed successfully (`WAIT=YES`).
`4`	Unsuccessful: parameter error.
`8`	Unsuccessful: load for module failed.
`11`	Unsuccessful: data set for file SEND was not cataloged.
`12`	Unsuccessful: abend occurred.
`14`	Unsuccessful: inconsistent EFFECT parameter.
`20`	Unsuccessful: server was not available.
`24`	Unsuccessful: security access was denied for local data set.
`21`	Unsuccessful: request timed out with no purge.
`22`	Unsuccessful: request timed out with purge.
`128`	Unsuccessful: network error occurred when scheduling request.
`252`	Unsuccessful: NODE definition was required by GLOBAL REQUIRE_NODE_DEFINITION.
`253`	Unsuccessful: user profile was not found.
`254`	Unsuccessful: profile data space was not defined.
`255`	Unsuccessful: list was not found.