ADAMTS Utility Messages

#### Search Results

Search

# ADAMTS Utility Messages

### Overview of Messages

`ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-128 | ERROR-129 | ERROR-130 | ERROR-131 | ERROR-132 | ERROR-133 | ERROR-134 | ERROR-135 | ERROR-136`

ERROR-121 | Parameter MTYPE must be set to ETBROKER or MQSERIES
Explanation | An invalid value was specified for the MTYPE parameter of the ADAMTS utility.
Action | Check the parameter input, correct the error, and rerun the job.

ERROR-122 | Parameter ETBROKERID must be specified when MTYPE=ETBROKER Parameter ETBSERVICE must be specified when MTYPE=ETBROKER Parameter ETBSERVICENAME must be specified when TYPE=ETBROKER Parameter ETBSERVICECLASS must be specified when MTYPE=ETBROKER Parameter MQQNAME must be specified when MTYPE=MQSERIES Parameter MQQMGRNAME must be specified when MTYPE=MQSERIES
Explanation | The listed, required parameters are missing for the selected MTYPE.
Action | Check the parameter input, correct the error, and rerun the job.

ERROR-123 | ETBROKER parameters may not be specified when MTYPE=MQSERIES MQSeries parameters may not be specified when MTYPE=ETBROKER
Explanation | Improper parameters have been specified for the selected MTYPE.
Action | Check the parameter input, correct the error, and rerun the job.

ERROR-124 | Open failed for file MTSIN
Explanation | The file allocated by the MTSIN DD statement could not be opened.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-125 | Load failed for {ADAETB|ADAMQS}
Explanation | The module listed could not be loaded by the job.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-126 | INIT call failed. Return code rcrc, Reason code reason
Explanation | The INIT call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-127 | CONNECT call failed “Return-code” “reason-code” “messaging-system-return-code” “messaging-system-reason-code”
Explanation | The CONNECT call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-128 | OPEN call failed. “Return-code” “reason-code” “messaging-system-return-code” “messaging-system-reason-code”
Explanation | The OPEN call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-129 | SEND call failed. “Return-code” “reason-code” “messaging-system-return-code” “messaging-system-reason-code”
Explanation | The SEND call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-130 | CLOSE call failed. “Return-code” “reason-code” “messaging-system-return-code” “messaging-system-reason-code”
Explanation | The CLOSE call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-131 | DISCONNECT call failed. “Return-code” “reason-code” “messaging-system-return-code” “messaging-system-reason-code”
Explanation | The DISCONNECT call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-132 | TERM call failed. Return code xxxxxxxx Reason code xxxxxxxx
Explanation | The TERM call failed for the selected MTYPE.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-133 | Read of MTSIN failed
Explanation | A problem occurred while attempting to read MTSIN. The cause is probably a JCL error.
Action | Check the job output or JCL, correct the error, and rerun the job.

ERROR-134 | Parameter ETBSCONV must be set to YES or NO
Explanation | An invalid value was specified for the ETBSCONV parameter of the ADAMTS utility.
Action | Check the parameter input, correct the error, and rerun the job.

ERROR-135 | Parameters ETBTOKEN and/or ETBUSERID are only allowed when parameter ETBSCONV=YES
Explanation | A value was specified for the ETBTOKEN and/or ETBUSERID parameters when ETBSCONV was set to NO.
Action | Check the parameter input, correct the error, and rerun the job.

ERROR-136 | ETBBROKER Service has multi conversation mode data waiting to be consumed, switch to single conversation mode not allowed
Explanation | This error occurs whenever the parameter ETBSCONV is set to YES and there are multi conversation mode messages waiting to be consumed from the last session. Switching to single conversation mode is not allowed until the pending multi conversation mode messages are consumed.
Action | Run ADAMTR with ETBSCONV set to NO and consume the pending multi conversation mode messages.