z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Error_Extract (ATB8) Messages

z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
SA23-1397-00

The Error_Extract service can return one of the messages described in this section when APPC/MVS finds an error in the most recently completed call to another APPC TP conversation service or CPI-C call. These messages appear on the Message_text parameter on return from Error_Extract.

Error_Extract also returns error log information messages when a partner system or TP finds an error in a call to an APPC TP conversation service or CPI-C call. For descriptions of those error log information messages, see Error_Extract Error Log Information (ASB, ATB7) Messages.    

  • ATB80003I
    APPC data structures for the TP are in use by another process.
  • ATB80004I
    System cannot process a call. A Cleanup_TP request is in progress.
  • ATB80005I
    APPC/MVS could not retrieve side information.
  • ATB80006I
    Error retrieving security information.
  • ATB80008I
    Address space cannot use the system base LU.
  • ATB80009I
    No base LU defined for scheduler.
  • ATB80010I
    Scheduler extract exit could not identify active TP.
  • ATB80011I
    Storage not available for APPC internal structures.
  • ATB80014I
    Service interrupted by call to Cleanup_TP service.
  • ATB80016I
    An internal error occurred in APPC processing.
  • ATB80020I
    Information about local LU was not available to APPC/MVS.
  • ATB80023I
    Processing for service interrupted by Deallocate_abend.
  • ATB80025I
    A previous error left the conversation in an undefined state.
  • ATB80026I
    An unexpected resource failure occurred.
  • ATB80033I
    Address space in which TP is running cannot use system base LU.
  • ATB80034I
    No system base LU defined to APPC/MVS.
  • ATB80036I
    Buffer storage not available for Receive processing.
  • ATB80037I
    Value specified on Conversation_type parameter is not valid.
  • ATB80038I
    Value specified on Sync_level parameter is not valid.
  • ATB80039I
    Value specified on Security_type parameter is not valid.
  • ATB80040I
    Value specified on TP_name_length parameter is not valid.
  • ATB80041I
    TP name length is zero, but no symbolic destination name is specified.
  • ATB80042I
    Caller is not authorized to specify User_token or TP_ID parameters.
  • ATB80043I
    Calling program did not specify both a user ID and a password and/or surrogate authorization check failed.
  • ATB80044I
    Value symdestname specified on Sym_dest_name parameter is not defined in active side information data set.
  • ATB80045I
    Mode name SNASVCMG is not valid.
  • ATB80046I
    An allocate request for an SNA service TP name beginning with X'06' is allowed only for programs running in supervisor state or with PSW key 0-7.
  • ATB80047I
    Value specified on User_token parameter is not valid.
  • ATB80048I
    Value specified on Local_LU_name parameter is not valid.
  • ATB80049I
    Value specified on Local_LU_name parameter is not the name of the system base LU or the name of a NOSCHED LU.
  • ATB80050I
    Allocate request specified system base LU name on Local_LU_name parameter. Alternate scheduler cannot use that LU name.
  • ATB80051I
    Allocate request for SNA service TP is not valid when Conversation_type is mapped.
  • ATB80052I
    LU specified on Local_LU_name parameter is not defined to APPC/MVS.
  • ATB80053I
    Value specified on TP_ID parameter is not valid.
  • ATB80054I
    Value specified on Timeout_Value_Minutes parameter is not valid.
  • ATB80055I
    APPC/MVS could not create required internal data structures.
  • ATB80058I
    An abend occurred in APPC/MVS.
  • ATB80059I
    Value plu_name specified on Partner_LU_name parameter is not valid.
  • ATB80060I
    Value specified on the Return_control parameter is not valid.
  • ATB80061I
    Session for mode name mode_name is not available. Partner LU: plu_name, local LU: loclu_name.
  • ATB80062I
    Local LU LU_name is terminating. The system cannot establish a session.
  • ATB80063I
    No default mode name is available to establish a session.
  • ATB80064I
    Local LU LU_name is not active. APPC/MVS cannot establish a session.
  • ATB80065I
    Partner LU plu_name is not active. APPC/MVS cannot establish a session.
  • ATB80066I
    The Local LU unregistered as a resource manager causing the conversation to terminate.
  • ATB80067I
    The Local LU unregistered as a resource manager causing the allocate request to fail.
  • ATB80068I
    Value specified on Notify_type parameter is not valid.
  • ATB80069I
    Confirm processing not allowed when Sync_level is None.
  • ATB80070I
    Value specified on Deallocate_type parameter is not valid.
  • ATB80071I
    Scheduler extract exit is not specified.
  • ATB80073I
    TP cannot call the service_name service while in current_state state.
  • ATB80074I
    Call to previous service did not finish sending logical record. TP must specify more data to send.
  • ATB80075I
    Partner ended session for LU=LOCAL conversation.
  • ATB80076I
    No data immediately available to receive for Receive_Immediate service.
  • ATB80077I
    Value specified on Error_Direction parameter is not valid.
  • ATB80078I
    No inbound conversations available, no active TPs in the address space.
  • ATB80079I
    No inbound conversation available for the TP to receive.
  • ATB80082I
    A TP called Accept_Conversation or Get_Conversation out of sequence.
  • ATB80083I
    Side information data set not defined.
  • ATB80084I
    From VTAM macro APPCCMD: General Return Code: genrc, Recovery Action Return Code: recrc
  • ATB80085I
    Conversation_type of CM_mapped_conversation is not valid when Fill characteristic is CM_fill_buffer.
  • ATB80086I
    Conversation_type of CM_mapped_conversation is not valid when log_data characteristic is specified.
  • ATB80087I
    Fill of CM_fill_buffer is not valid when conversation_type characteristic is CM_mapped_conversation.
  • ATB80088I
    Value specified on Prepare_to_receive_type parameter is not valid.
  • ATB80089I
    Value specified on log_data_length parameter is not valid.
  • ATB80090I
    Set_Log_Data service not valid for a mapped conversation.
  • ATB80091I
    Value specified on Mode_name_length parameter is not valid.
  • ATB80092I
    Value specified on partner_lu_name_length parameter is not valid.
  • ATB80093I
    Deallocate_type of CM_deallocate_confirm is not valid when sync_level characteristic is CM_none.
  • ATB80094I
    Prepare_to_receive_type of CM_prep_to_receive_confirm is not valid when sync_level characteristic is CM_none.
  • ATB80095I
    Value specified on Receive_type parameter is not valid.
  • ATB80096I
    Deallocate_type of deallocate_confirm or deallocate_flush is not valid when sync_level characteristic is Syncpoint.
  • ATB80097I
    Value specified on send_type parameter is not valid.
  • ATB80098I
    Send_type of CM_send_and_confirm is not valid when sync_level characteristic is CM_none.
  • ATB80099I
    The APPCCMD command detected that the ACB is no longer active for the local LU.
  • ATB80100I
    From VTAM macro APPCCMD: Primary error return code: prim_code, secondary error return code: sec_code, sense code: sense_code.
  • ATB80101I
    LU=LOCAL conversation received sense code sense_code from partner TP.
  • ATB80102I
    Sync_level of CM_none is not valid when send_type, prepare_to_receive_type or deallocate_type characteristic indicates confirm processing.
  • ATB80103I
    Sync_level of CM_syncpt is not valid when deallocate_type characteristic is either deallocate_flush or deallocate_confirm.
  • ATB80104I
    Value specified on Locks parameter is not valid.
  • ATB80105I
    Value specified on Fill parameter is not valid.
  • ATB80106I
    Value specified on Access_token parameter is not valid.
  • ATB80107I
    Value specified on Requested_length parameter is not valid.
  • ATB80108I
    Value specified on Receive_length parameter is not valid.
  • ATB80109I
    Value specified on Send_length parameter is not valid.
  • ATB80110I
    Value specified on Buffer parameter is not valid for a basic conversation.
  • ATB80111I
    Post_On_Receipt service not valid for a mapped conversation.
  • ATB80112I
    Protocol Violation: APPC/MVS received deallocation status on a conversation with Sync_Level of Syncpt, but not during a two-phase commit exchange.
  • ATB80114I
    Protocol violation: A conversation with a Sync_Level of None was established, but APPC/MVS received confirm status.
  • ATB80115I
    Protocol violation: Partner system specified an incorrect GDS variable format for error log data.
  • ATB80116I
    Protocol violation: APPC/MVS failed to receive expected error log data.
  • ATB80117I
    Protocol violation: Partner system did not send complete error log data in GDS variable.
  • ATB80119I
    An OpenEdition MVS exit failed when a TP tried to allocate a conversation with the OpenEdition MVS fork TP.
  • ATB80120I
    The conversation is not owned by the home address space of the caller of the service.
  • ATB80121I
    The local LU does not support the synchronization level specified.
  • ATB80122I
    System cannot process a call. A Syncpoint or Backout verb is running.
  • ATB80123I
    System cannot process a call. The conversation is in backout required state.
  • ATB80124I
    The local LU cannot process syncpt requests at the present time.
  • ATB80125I
    Log name exchange failed during syncpt processing.
  • ATB80126I
    Conversation was terminated during syncpt processing.
  • ATB80127I
    Conversation was terminated because APPC/MVS received unrecognized PS header.
  • ATB80128I
    APPC/MVS detected a protocol violation during an Exchange Log Name processing.
  • ATB80129I
    APPC/MVS detected a warm/cold log status mismatch during an Exchange Log Name processing.
  • ATB80130I
    APPC/MVS detected a log name mismatch during an Exchange Log Name processing.
  • ATB80131I
    Conversation was terminated due to a break-tree situation.
  • ATB80133I
    APPC data structures for the TP are in use because a Syncpoint or Backout verb is still running.
  • ATB80134I
    APPC/MVS detected a protocol violation during a syncpoint processing.
  • ATB80135I
    APPC/MVS detected a protocol violation during Resynchronization Processing.
  • ATB80136I
    Conversation was terminated because the unit of recovery was resolved by the installation before a syncpt decision was received from the syncpt initiator.
  • ATB80138I
    Sync_level of Syncpt is not valid when the partner LU only supports single sessions.
  • ATB80139I
    APPC/MVS detected an error during Purge Log Name processing.
  • ATB80140I
    From Resource Recovery Services (RRS/MVS) callable service: service_name. Error Return Code: rrs_error_rc
  • ATB80141I
    Retrieved incomplete UR that is in in-doubt state was not found in the APPC log.
  • ATB80142I
    APPC/MVS terminated the conversation because APPCCMD did not complete in the time-out limit specified by the caller.
  • ATB80143I
    Value specified on Timeout_Value_Seconds parameter is not valid.
  • ATB80144I
    The APPC Conversational Timer monitor is not available.
  • ATB80145I
    APPC/MVS did not permit this conversation to start because the maximum number of conversations has already been reached by this address space.
Parent topic: Error_Extract Reason Codes and Messages

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014