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 ( |
<> 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 ( |
4
|
Unsuccessful: Parameter error. |
8
|
Unsuccessful: Load for module failed. |
11
|
Unsuccessful: Dataset 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 dataset. |
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 dataspace was not defined. |
255
|
Unsuccessful: List was not found. |