Error_Extract Error Log Information (ASB, ATB7) Messages
The Error_Extract service can return one of the messages described in this section when a partner system or TP finds an error in the most recently completed call to another APPC TP conversation service or CPI Communications (CPI-C) call. These messages appear on the Error_log_information parameter on return from Error_Extract.
Error_Extract also returns error messages when APPC/MVS finds an error in a call to an APPC conversation service. For descriptions of those messages, see Error_Extract (ATB8) Messages.
- ASB70000I
Abend occurred in APPC/MVS transaction scheduler while processing inbound allocate request. - ASB70001I
APPC/MVS transaction scheduler cannot obtain storage for its internal data area. - ASB70002I
APPC/MVS cannot schedule inbound TP. Scheduler class class_name is not active. - ASB70003I
Scheduler class class_name is not defined to the APPC/MVS transaction scheduler. - ASB70004I
APPC/MVS transaction scheduler is terminating. - ASB70005I
APPC/MVS transaction scheduler cannot schedule an inbound TP. Internal error code: error_code - ASB70006I
APPC/MVS transaction scheduler class not specified in TP Profile, and no default class name is defined. - ASB70007I
APPC/MVS transaction scheduler cannot schedule inbound allocate request. Error codes from IXCMSGI macro: Return code return_code, reason code reason_code. - ASB70008I
APPC/MVS transaction scheduler cannot schedule inbound allocate request. An internal error occurred. - ASB70009I
APPC/MVS transaction scheduler cannot schedule inbound allocate request. Scheduler class class_name was deleted. - ASB70010I
APPC/MVS transaction scheduler could not associate a TP with an initiator. - ASB70011I
ASCH initiator could not create security environment for TP. - ASB70012I
An internal failure occurred in the APPC/MVS transaction scheduler. Detection code is: error_data - ASB70013I
ASCH initiator was unable to determine the SYSOUT and accounting information for the TP. - ASB70014I
ASCH initiator could not schedule a TP. TP account number rejected by IEFUAV installation exit. - ASB70015I
ASCH initiator cannot schedule the OpenEdition MVS fork TP. OpenEdition MVS job initiation processing return code is: error_data. - ATB70001I
TP name specified on inbound allocate request is not valid. Length of TP name is zero. - ATB70002I
TP name specified on inbound allocate request is not valid. Name contains all blank characters. - ATB70003I
TP name tp_name specified on inbound allocate request is not valid. It is the name of a SNA service TP that APPC/MVS does not support. - ATB70005I
TP name tp_name is not valid. An inbound allocate request specified a TP name with an incorrect character. If the TP is a SNA service TP, the first character is incorrect. - ATB70006I
TP name tp_name specified on the inbound allocate request is not valid. A request to allocate a SNA service TP specified an incorrect TP name. - ATB70007I
TP name tp_name specified on the inbound allocate request is not valid. The system could not find the associated TP profile. - ATB70008I
TP security violation. Signed-on-from and signed-on-to lists are not synchronized. - ATB70009I
TP security violation. Inbound request to attach SIGNON SNA service TP specified a security_type that was not security_none. - ATB70010I
TP security violation. Inbound allocate request specified a password, profile, or both, but did not specify a user ID. - ATB70011I
TP security violation. Allocate request specified a user ID but did not specify a password. - ATB70012I
TP security violation. Inbound allocate request specified persistent verification security level, but did not specify a user ID. - ATB70013I
TP security violation. Inbound allocate request specified 'already verified' security level, but did not specify a user ID. - ATB70014I
TP security violation. User ID userid is longer than the maximum number of characters allowed on MVS. - ATB70015I
TP security violation. Password is longer than the maximum number of characters allowed on MVS. - ATB70016I
TP security violation. Profile name is longer than the maximum number of characters allowed on MVS. - ATB70017I
TP security violation. Partner LU plu_name rejected the allocate request because authorization checks failed. - ATB70018I
TP security violation. Password specified for user userid has expired. - ATB70020I
TP security violation. User userid not authorized to access TP tp_name. - ATB70021I
TP security violation. User not authorized to test TP tp_name. - ATB70022I
TP security violation. User userid not authorized to run TP tp_name, which is served by an APPC/MVS server. - ATB70023I
APPC/MVS cannot process allocate request. PIP data is specified but is not supported by APPC/MVS. - ATB70024I
APPC/MVS cannot process allocate request. Value in FMH-5 command field is not supported by APPC/MVS. - ATB70025I
APPC/MVS cannot schedule an allocate request. LU LU_name, where the request arrived, is a NOSCHED LU. - ATB70026I
APPC/MVS cannot schedule an allocate request. Scheduler sched_name, associated with LU LU_name where the request arrived, is not active. - ATB70027I
APPC/MVS cannot schedule allocate request. LU LU_name is not in active state. - ATB70028I
APPC/MVS cannot process allocate request. LU LU_name is not defined to APPC/MVS. - ATB70030I
APPC/MVS cannot schedule TP tp_name. The TP profile is not active. - ATB70031I
APPC/MVS cannot schedule allocate request. TP profile for requested TP is an alias of another TP profile, which is an alias of a third TP profile. A TP profile cannot be an alias of another alias TP profile. - ATB70032I
APPC/MVS cannot schedule an allocate request. A syntax error was found in the TP profile. - ATB70033I
APPC/MVS cannot schedule an allocate request. Scheduler sched_name, associated with LU LU_name where the request arrived, is not a member of the APPC XCF group. The scheduler can not be notified about the inbound allocate request. - ATB70034I
APPC/MVS cannot schedule an allocate request. Scheduler sched_name, associated with LU LU_name where the request arrived, did not specify a valid XCF message user routine. The scheduler can not be notified about the inbound allocate request. - ATB70034I
APPC/MVS cannot schedule an allocate request. Scheduler sched_name, associated with LU LU_name where the request arrived, did not specify a valid XCF message user routine. The scheduler can not be notified about the inbound allocate request. - ATB70035I
APPC/MVS cannot schedule an allocate request. XCF Signalling Services could not deliver an inbound allocate request message to a scheduler XCF message user routine due to the unavailability of message buffers. - ATB70036I
APPC/MVS cannot schedule an allocate request. XCF Signalling Services could not deliver an inbound allocate request message to a scheduler XCF message user routine. XCF IXCMSGO Return Code: xxxxxxxx XCF IXCMSGO Reason Code: yyyyyyyy - ATB70040I
APPC/MVS cannot schedule allocate request. Log name for LU lu_name is unknown. - ATB70041I
APPC/MVS cannot schedule allocate request. LU lu_name is not syncpt capable. - ATB70042I
APPC/MVS cannot schedule allocate request. LU lu_name cannot process syncpt conversations. - ATB70043I
APPC/MVS cannot process allocate request. Sync_level specified for a RESYNC TP is not CONFIRM. - ATB70044I
APPC/MVS cannot process allocate request. Conversation type specified for a RESYNC TP is not BASIC. - ATB70050I
Receive allocate request failed: Return code: return_code - ATB70051I
APPC/MVS detected a protocol violation during an Exchange Log Name processing. Reason Code: reason_code - ATB70052I
APPC/MVS detected a warm/cold log status mismatch during an Exchange Log Name processing. - ATB70053I
APPC/MVS detected a log name mismatch during an Exchange Log Name processing. - ATB70054I
Conversation was terminated because a protocol violation was detected by LU partner_lu during a syncpoint processing. Reason code = rsncode intrsncode. - ATB70055I
Conversation was terminated due to a break-tree condition or a terminating syncpoint situation. - ATB70056I
APPC/MVS detected a protocol violation during a Resynchronization Exchange. Reason Code: rsncode. - ATB70057I
APPC/MVS detected an error during Purge Log Name TP processing. Reason Code: rsncode. - ATB70058I
APPC/MVS cannot process allocate request. Syncpoint conversations are not supported when the partner LU session capabilities are single session. - ATB70059I
APPC/MVS cannot process allocate request. Syncpoint conversations are not supported on the SNASVCMG session. - ATB70061I
APPC/MVS cannot process allocate request. Conversation type specified for a PLNA TP is not BASIC. - ATB70999I
An APPC/MVS internal error occurred: Reason code: reason_code.
Parent topic: Error_Extract Reason Codes and Messages