z/OS MVS System Messages, Vol 3 (ASB-BPX)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ATB messages

z/OS MVS System Messages, Vol 3 (ASB-BPX)
SA38-0670-00

Note

This topic does not contain explanations for the following types of messages:
  • ASB7xxxxI messages - Error log information messages that the APPC transaction scheduler or an alternate scheduler returns to an APPC transaction program (TP).
  • ATB6xxxxI messages - Error messages that the application program interface (API) trace facility returns to the issuer of an ATBTRACE request, or writes to the trace data set.
  • ATB7xxxxI messages - Error log information messages that the Error_Extract service returns to an APPC TP.
  • ATB8xxxxI messages - Error messages that the Error_Extract service returns to an APPC TP.

See z/OS MVS Programming: Writing Transaction Programs for APPC/MVS for descriptions of those types of messages.

  • ATB001I
    APPC IS INITIALIZING.
  • ATB002I
    APPC HAS TERMINATED.
  • ATB003I
    START APPC SYNTAX IS INCORRECT. COMMAND IGNORED.
  • ATB004I
    APPC ALREADY STARTED. SUBSEQUENT REQUEST WAS IGNORED.
  • ATB005I
    APPC IS RESTARTING. FAILURE CODE = reason-code
  • ATB006I
    APPC IS TERMINATING. RESTART CRITERIA NOT MET. FAILURE CODE = return-code
  • ATB007I
    APPC IS ACTIVE.
  • ATB008E
    APPC SYSTEM INITIALIZATION FAILED
  • ATB009I
    SUB=MSTR NOT SPECIFIED ON START APPC. COMMAND IGNORED.
  • ATB010I
    APPC IS TERMINATING DUE TO OPERATOR CANCEL
  • ATB011I
    APPC NOT STARTED DUE TO INITIALIZATION FAILURE
  • ATB012I
    APPC IS TERMINATING DUE TO OPERATOR FORCE OR DUE TO CRITICAL ERROR
  • ATB013E
    SYNTAX ERROR IN APPC INITIALIZATION INPUT PARAMETERS. START APPC COMMAND IGNORED.
  • ATB014I
    THE BUFFER STORAGE LIMIT HAS BEEN SET TO number MEGABYTES
  • ATB015I
    APPC IS STARTING AFTER A FAILED RESTART. SPECIFIED PARMLIB MEMBER(S) ARE IGNORED.
  • ATB016I
    THE AMOUNT OF BUFFER STORAGE AVAILABLE TO ONE CONVERSATION IS number KILOBYTES.
  • ATB017I
    CONVBUFF PARAMETER VALUE EXCEEDS BUFFER STORAGE LIMIT. DEFAULTING TO BUFFER STORAGE LIMIT.
  • ATB018E
    CRITICAL APPC/MVS ERROR. APPC SHOULD BE CANCELLED AND RESTARTED TO RESUME NORMAL INCOMING APPC WORK.
  • ATB019I
    THE APPC ACTIVE CONVERSATION THRESHOLD FOR ONE ADDRESS SPACE IS number
  • ATB020E
    THE NUMBER OF APPC ACTIVE CONVERSATIONS FOR ASID num1 HAS CROSSED THE PRE-ESTABLISHED THRESHOLD. NUMBER OF ACTIVE CONVERSATIONS: num2; APPC ACTIVE CONVERSATION THRESHOLD: num3.
  • ATB021I
    APPC/MVS ENCOUNTERED INTERNAL ERRORS WHILE PROCESSING TIMED CONVERSATIONS. ALL CONVERSATIONAL SERVICES WILL NOT BE TIMED HEREAFTER.
  • ATB022I
    APPC COULD NOT INITIALIZE DUE TO XCF NOTIFICATION FAILURE. APPC HAS RECEIVED RETURN CODE=xxxxxxxx, REASON CODE=yyyyyyyy FROM THE servname SERVICE.
  • ATB023I
    FAILED TO JOIN the APPC/XCF GROUP. IXCJOIN RETURN CODE = xxxxxxxx, REASON CODE = yyyyyyyy.
  • ATB024I
    INITIALIZATION OF APPC/XCF GROUP NAME FAILED: IXCQUERY RETURN CODE = xxxxxxxx REASON CODE = yyyyyyyy.
  • ATB025I
    INCORRECT CHARACTERS SPECIFIED FOR APPC PARMLIB MEMBER VALUE.
  • ATB026I
    APPCPMxx IGNORED. MEMBER IS EMPTY.
  • ATB027I
    APPCPMxx: LINE num1 - num2 IGNORED. UNBALANCED COMMENT DETECTED.
  • ATB028I
    APPCPMxx: LINE num statement STATEMENT IGNORED. STATEMENT TYPE NOT RECOGNIZED.
  • ATB029I
    APPCPMxx: LINE num statement STATEMENT IGNORED. NO OPERANDS SPECIFIED.
  • ATB030I
    APPCPMxx: LINE num statement STATEMENT IGNORED. NO keyword KEYWORD SPECIFIED.
  • ATB031I
    APPCPMxx: LINE num statement STATEMENT IGNORED. DUPLICATE KEYWORD keyword SPECIFIED.
  • ATB032I
    APPCPMxx: LINE num statement STATEMENT IGNORED. VALUE SPECIFIED FOR KEYWORD keyword IS NOT VALID.
  • ATB033I
    APPCPMxx: LINE num statement STATEMENT IGNORED. UNRECOGNIZED KEYWORD: keyword.
  • ATB034I
    APPCPMxx: LINE num statement STATEMENT IGNORED. MISSING RIGHT PARENTHESIS FOR A KEYWORD VALUE SPECIFIED IN THE STATEMENT.
  • ATB035I
    APPCPMxx: LINE num statement STATEMENT IGNORED. NO VALUE SPECIFIED FOR KEYWORD keyword.
  • ATB036I
    APPCPMxx: STARTING LINE num MEMBER IGNORED. statement STATEMENT TEXT EXCEEDS 4096 CHARACTERS.
  • ATB038I
    APPCPMxx: stmtrec
  • ATB039I
    SET APPC COMMAND IGNORED. APPC NOT ACTIVE.
  • ATB040I
    SYSTEM ERROR ENCOUNTERED IN APPC PARMLIB PROCESSING.
  • ATB041I
    APPCPMxx: LINE num statement STATEMENT IGNORED. keyword1 AND keyword2 ARE MUTUALLY EXCLUSIVE.
  • ATB042I
    APPCPMxx: LINE num statement STATEMENT IGNORED. STATEMENT TYPE NO LONGER SUPPORTED.
  • ATB043I
    APPCPMxx: LINE num statement STATEMENT IGNORED. GENERIC RESOURCE NAME grname IS THE SAME AS THE LOGICAL UNIT NAME.
  • ATB044I
    THE APPC LOGGING OPTION IS keyword
  • ATB047I
    THE APPC ACTIVE CONVERSATION THRESHOLD ACTION IS value.
  • ATB048E
    THE MAXIMUM NUMBER OF APPC ACTIVE CONVERSATIONS FOR ASID num1 HAS BEEN REACHED. APPC ACTIVE CONVERSATION THRESHOLD: num2.
  • ATB050I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname HAS BEEN ADDED TO THE APPC CONFIGURATION.
  • ATB051I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname HAS BEEN DELETED FROM THE APPC CONFIGURATION.
  • ATB052E
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname NOT ACTIVATED IN THE APPC CONFIGURATION. REASON CODE = error-field-value.
  • ATB053I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname NOT ADDED. IT ALREADY EXISTS IN THE APPC CONFIGURATION.
  • ATB054I
    LOGICAL UNIT luname NOT DELETED. IT DOES NOT EXIST IN THE APPC CONFIGURATION.
  • ATB055I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname HAS BEEN TERMINATED DUE TO SYSTEM ERROR. REASON CODE=xx.
  • ATB056I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname NOT ADDED DUE TO A SYSTEM ERROR. REASON CODE = reason-code.
  • ATB057I
    LOGICAL UNIT luname NOT DELETED DUE TO A SYSTEM ERROR. REASON CODE = reason-code.
  • ATB058I
    SESSION VALUES NOT DEFINED FOR LOGICAL UNIT luname.
  • ATB059I
    SESSION VALUES NOT DELETED FOR LOGICAL UNIT luname.
  • ATB060I
    SESSION VALUES NOT PROCESSED FOR LOGICAL UNIT luname DUE TO A SYSTEM ERROR.
  • ATB061I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname WAS NOT COMPLETELY MODIFIED. REASON CODE = reason-code
  • ATB062I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname HAS BEEN TERMINATED DUE TO ALTERNATE APPLICATION TAKEOVER.
  • ATB063I
    PSTIMER PARAMETER REQUIRES VTAM PERSISTENT SESSIONS SUPPORT.
  • ATB064I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER NOT ACTIVE. REASON CODE=reason-code.
  • ATB065I
    GRNAME PARAMETER FOR LOGICAL UNIT luname IS IGNORED. APPC/MVS GENERIC RESOURCE SUPPORT REQUIRES VTAM V4R4.
  • ATB066I
    LOGICAL UNIT luname NOT ACTIVATED. FAILURE IN REGISTERING LOGICAL UNIT WITH GENERIC RESOURCE NAME grname. VTAM RETURN CODE:vtam-return-code, FDB2:fdb2
  • ATB067I
    LOGICAL UNIT luname NOT ACTIVATED. FAILURE IN REGISTERING LOGICAL UNIT WITH GENERIC RESOURCE NAME grname. VTAM RETURN CODE:vtam-return-code, FDB2:fdb2
  • ATB068I
    NQN PARAMETER FOR LOGICAL UNIT luname IS IGNORED. APPC/MVS NETWORK-QUALIFIED NAME SUPPORT REQUIRES VTAM V4R4.
  • ATB069I
    PROTECTED CONVERSATIONS FOR LOGICAL UNIT luname IS NOT AVAILABLE. APPC/MVS PROTECTED CONVERSATIONS SUPPORT REQUIRES VTAM V4R4.
  • ATB070I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname IS TERMINATING DUE TO XCF NOTIFICATION FAILURE. APPC HAS RECEIVED RETURN CODE=xxxxxxxx, REASON CODE=yyyyyyyy FROM THE servname SERVICE.
  • ATB071I
    PERSIST PARAMETER ON LUDEL FOR LOGICAL UNIT luname IS IGNORED. THE LU WAS NOT ENABLED FOR PERSISTENT SESSIONS.
  • ATB072I
    LOGICAL UNIT luname NOT ADDED TO THE APPC CONFIGURATION BECAUSE THE MAXIMUM NUMBER OF SCHEDULER-BASED LOCAL LUS HAS BEEN REACHED.
  • ATB073I
    LOGICAL UNIT luname NOT ADDED TO THE APPC CONFIGURATION BECAUSE THE MAXIMUM NUMBER OF TOTAL LOCAL LUS HAS BEEN REACHED.
  • ATB075I
    APPC COMPONENT TRACE IS UNAVAILABLE. REASON= xxxxxxxx.
  • ATB076I
    option IS NOT A VALID TRACE OPTION.
  • ATB077I
    APPC COMPONENT TRACE CANNOT START YET.
  • ATB078I
    THE DUMP FOR APPC COMPONENT TRACE FAILED. REASON=xxxxxxxx.
  • ATB079I
    APPC COMPONENT TRACE START OR STOP FAILED. REASON= xxxxxxxx.
  • ATB080I
    SYNTAX ERROR WITH THE OPTION USERID.
  • ATB082I
    A USERID SPECIFIED IS NOT VALID.
  • ATB083I
    THE NUMBER OF USERIDS SPECIFIED EXCEEDS THE MAXIMUM OF 9.
  • ATB100I
    hh.mm.ss APPC DISPLAY [id]
  • ATB101I
    hh.mm.ss APPC DISPLAY [id]
  • ATB102I
    hh.mm.ss APPC DISPLAY [id]
  • ATB103I
    hh.mm.ss APPC DISPLAY [id]
  • ATB104I
    hh.mm.ss APPC DISPLAY [id]
  • ATB105I
    DISPLAY APPC SYNTAX ERROR. UNEXPECTED END OF COMMAND: error
  • ATB106I
    DISPLAY APPC SYNTAX ERROR. INVALID PARAMETER: error
  • ATB107I
    DISPLAY APPC SYNTAX ERROR. INVALID DELIMITER AFTER PARAMETER: error
  • ATB108I
    DISPLAY APPC SYNTAX ERROR. DUPLICATE KEYWORD PARAMETER: error
  • ATB109I
    DISPLAY APPC SYNTAX ERROR. INVALID KEYWORD VALUE: error
  • ATB110I
    DISPLAY APPC UNAVAILABLE. APPC IS NOT ACTIVE.
  • ATB111I
    DISPLAY APPC UNAVAILABLE. APPC IS STARTING.
  • ATB112I
    DISPLAY APPC UNAVAILABLE. APPC IS TERMINATING AND WILL AUTOMATICALLY RESTART.
  • ATB113I
    DISPLAY APPC UNAVAILABLE. APPC IS TERMINATING.
  • ATB121I
    hh.mm.ss APPC DISPLAY [id]
  • ATB122I
    hh.mm.ss APPC DISPLAY [id]
  • ATB175I
    APPC COMPONENT TRACE IS UNAVAILABLE. REASON= xxxxxxxx. DATA= kkkkkkkkjjjjjjjj.
  • ATB178I
    THE DUMP FOR APPC COMPONENT TRACE FAILED. REASON=xxxxxxxx. DATA=kkkkkkkk.
  • ATB179I
    APPC COMPONENT TRACE START OR STOP FAILED. REASON=xxxxxxxx. DATA=kkkkkkkkjjjjjjjj.
  • ATB200I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname IS ACTIVE, BUT WILL REJECT ALL PROTECTED CONVERSATIONS UNTIL RRS/MVS IS ACTIVE.
  • ATB201I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname NOW ACCEPTS PROTECTED CONVERSATIONS.
  • ATB202I
    LOGICAL UNIT luname IS RESTARTING. BECAUSE HARDENED DATA WAS LOST, INCOMPLETE UNITS OF RECOVERY MIGHT NOT BE RESOLVED TO A CONSISTENT STATE.
  • ATB203I
    LOGICAL UNIT luname ENCOUNTERED AN INSTALLATION ERROR FOR LOGSTREAM: logstream_name. SYSTEM LOGGER RETURN CODE: return-code, REASON CODE: rsncode FOR THE IXGCONN SERVICE.
  • ATB204I
    LOGICAL UNIT OF WORK luwid WITH CONVERSATION CORRELATOR convcorr IS outcome AT LU partner_lu BECAUSE OF RESYNCHRONIZATION BETWEEN LU local_lu AND LU partner_lu.
  • ATB205I
    RESYNCHRONIZATION FOR LOGICAL UNIT OF WORK luwid WITH CONVERSATION CORRELATOR convcorr HAS COMPLETED, BUT RESOURCES FOR LOCAL LU local_lu AND PARTNER LU partner_lu HAVE NOT BEEN BROUGHT TO A CONSISTENT STATE.
  • ATB206E
    LU luname1 DETECTED A PROTOCOL VIOLATION MADE BY LU luname2 DURING RESYNCHRONIZATION. THE RESYNCHRONIZATION HAS FAILED. SOME LOGICAL UNITS OF WORK MIGHT NOT BE AUTOMATICALLY RESOLVED BY RESYNCHRONIZATION AND NO NEW PROTECTED CONVERSATIONS MAY BE ALLOCATED BETWEEN THE TWO LOGICAL UNITS UNTIL THE PROBLEM IS RESOLVED. REASON: description-of-protocol-violation
  • ATB207I
    EXCHANGE LOG NAME PROCESSING HAS COMPLETED SUCCESSFULLY BETWEEN LOCAL LU luname AND PARTNER LU pluname LOCAL LOG: local-log PARTNER LOG: partner-log
  • ATB208I
    LOGICAL UNIT luname FOR TRANSACTION SCHEDULER schedname WILL REJECT ALL PROTECTED CONVERSATIONS. THE RESOURCE MANAGER EXITS HAVE BEEN UNSET. NOTIFICATION EXIT REASON=rsncode.
  • ATB209I
    LOGICAL UNIT lu_name DETECTED A MAXBUFSIZE VALUE THAT IS TOO SMALL FOR THE APPC/MVS LOG STREAM logstream_name. APPC/MVS EXPECTS A BUFFER SIZE OF AT LEAST 65276 BYTES.
  • ATB210E
    A LOG NAME EXCHANGE INITIATED BY LU luname1 WITH LU luname2 HAS FAILED. LU luname3 DETECTED A WARM/COLD MISMATCH. AS A RESULT, SOME LOGICAL UNITS OF WORK MIGHT NOT BE AUTOMATICALLY RESOLVED BY RESYNCHRONIZATION AND NO NEW PROTECTED CONVERSATIONS MAY BE ALLOCATED BETWEEN THE TWO LOGICAL UNITS UNTIL THE MISMATCH IS RESOLVED. REASON: reason
  • ATB211E
    A LOG NAME EXCHANGE INITIATED BY LU luname1 WITH LU luname2 HAS FAILED. LU luname3 DETECTED A LOG NAME MISMATCH. AS A RESULT, SOME LOGICAL UNITS OF WORK MIGHT NOT BE AUTOMATICALLY RESOLVED BY RESYNCHRONIZATION AND NO NEW PROTECTED CONVERSATIONS MAY BE ALLOCATED BETWEEN THE TWO LOGICAL UNITS UNTIL THE MISMATCH IS RESOLVED. REASON: reason
  • ATB212E
    LU luname1 DETECTED A PROTOCOL VIOLATION IN THE EXCHANGE LOG NAME DATA SENT BY LU luname2. SOME LOGICAL UNITS OF WORK MIGHT NOT BE AUTOMATICALLY RESOLVED BY RESYNCHRONIZATION AND NO NEW PROTECTED CONVERSATIONS MAY BE ALLOCATED BETWEEN THE TWO LOGICAL UNITS UNTIL THE PROBLEM IS RESOLVED.
  • ATB213I
    LOGICAL UNIT OF WORK luwid WITH CONVERSATION CORRELATOR convcorr REQUIRED RESYNCHRONIZATION ON mm/dd/yyyy AT resynctime. TO RESOLVE THE LOGICAL UNIT OF WORK, RESYNCHRONIZATION HAS STARTED BETWEEN LOCAL LU luname AND PARTNER LU pluname.
  • ATB214I
    THE RESYNCHRONIZATION OF LOGICAL UNIT OF WORK luwid WITH CONVERSATION CORRELATOR convcorr IS BEING SUSPENDED ON mm/dd/yyyy AT resynctime. RESYNCHRONIZATION WAS STARTED BY LOCAL LU luname ON mm/dd/yyyy AT resynctime FOR THE LOGICAL UNIT OF WORK. THE LOCAL LU WILL TRY AGAIN TO RESYNCHRONIZE WITH LU pluname TO RESOLVE THE LOGICAL UNIT OF WORK.
  • ATB215E
    LOGICAL UNIT pluname HAS ISSUED A DEALLOCATE OF TYPE DEALLOCATE_ABEND TO ABNORMALLY TERMINATE THE RESYNCHRONIZATION TRANSACTION EXCHANGE.
  • ATB216E
    PROTOCOL VIOLATION DETECTED IN THE RESYNCHRONIZATION OF LOGICAL UNIT OF WORK luwid WITH CONVERSATION CORRELATOR convcorr. LOGICAL UNIT OF WORK STATE SENT WAS state AND LOGICAL UNIT OF WORK STATE RECEIVED FROM LU luname WAS state.
  • ATB217I
    EXCHANGE LOG NAME PROCESSING INITIATED BY LU luname1 WITH LU luname2 HAS FAILED ON mm/dd/yyyy AT resynctime. THE LOCAL LU WILL TRY AGAIN TO COMPLETE A SUCCESSFUL EXCHANGE LOG NAME WITH LU pluname. SOME LOGICAL UNITS OF WORK MIGHT NOT BE AUTOMATICALLY RESOLVED BY RESYNCHRONIZATION AND NO NEW PROTECTED CONVERSATIONS MAY BE ALLOCATED BETWEEN THE TWO LOGICAL UNITS UNTIL AN EXCHANGE LOG NAME TRANSACTION COMPLETES.
  • ATB218E
    PROTOCOL VIOLATION DETECTED IN THE gds-variable-name DATA SENT BY LU luname. THE RESYNCHRONIZATION HAS FAILED.
  • ATB219E
    APPC/MVS, AS INITIATOR OF A RESYNCHRONIZATION, HAS RECEIVED AN ERROR REPLY IN THE COMPARE STATES DATA FROM LU luname. THE RESYNCHRONIZATION HAS FAILED.
  • ATB220I
    PROTOCOL VIOLATION MADE BY LU luname1 WAS DETECTED BY LU luname2 IN THE SYNCPOINT PROCESSING OF LUWID luwid WITH CONVERSATION CORRELATOR convcorr. syncpoint-message-in-error. THE SYNCPOINT PROCESSING WAS TERMINATED.
  • ATB221I
    AN ATRSUSI CALL ISSUED TO SET side_information HAS FAILED. INTERNAL REASON CODE = rsncode.
  • ATB222I
    LOGICAL UNIT luname ATTEMPTED A SYSTEM LOGGER SERVICE FOR A LOGSTREAM THAT HAS NOT BEEN DEFINED. THE LOGSTREAM NAME IS: logstream_name.
  • ATB223I
    APPC/MVS ENCOUNTERED INTERNAL ERRORS WHILE ISSUING A LOGGING SERVICE. LOGGING SERVICES ARE NOT AVAILABLE.
  • ATB224I
    BECAUSE OF AN INTERNAL ERROR, LOGICAL UNIT luname IS ACTIVE, BUT WILL REJECT ALL PROTECTED CONVERSATIONS.
  • ATB225I
    LOGICAL UNIT luname IS ACTIVE, BUT WILL REJECT ALL PROTECTED CONVERSATIONS BECAUSE OF A FAILURE RETURN CODE FROM THE service SERVICE. RETURN CODE IS retcode.
  • ATB226I
    LOGICAL UNIT luname IS ACTIVE, BUT WILL REJECT ALL PROTECTED CONVERSATIONS UNTIL RRS/MVS NOTIFIES APPC/MVS ABOUT THE STATUS OF RESOURCE MANAGER EXITS.
  • ATB227I
    LOCAL LU luname IS log-status AS A RESOURCE MANAGER WITH RRS/MVS. LOCAL LOG: logname
  • ATB229E
    APPC/MVS WAS NOT ABLE TO RESYNCHRONIZE THE INCOMPLETE UNIT OF RECOVERY urid IN IN-DOUBT STATE. MANUAL INTERVENTION IS REQUIRED TO RESOLVE THIS UR.
  • ATB275I
    SIDEINFO KEYWORD WAS NOT PROCESSED DUE TO SYSTEM ERROR. REASON CODE=reason-code
  • ATB277E
    SIDEINFO KEYWORD IGNORED. DATA SET WAS NOT OPENED SUCCESSFULLY.
  • ATB278E
    LOGICAL UNIT unitname NOT ADDED. TP PROFILE DATA SET WAS NOT OPENED SUCCESSFULLY.
  • ATB279I
    SIDEINFO KEYWORD IGNORED. DATA SET SPECIFIED IS ALREADY THE ACTIVE SIDEINFO DATA SET.
  • ATB280E
    SIDEINFO KEYWORD IGNORED. SIDEINFO DATA SET WAS NOT ALLOCATED. REASON CODE=reason-code
  • ATB281E
    LOGICAL UNIT unitname NOT ADDED. TP PROFILE DATA SET WAS NOT ALLOCATED. REASON CODE=reason-code
  • ATB300E
    Message msgid not found.
  • ATB301I
    data
  • ATB302I
    Request request syntax checked successfully - no warning message(s) issued.
  • ATB303I
    APPC administration utility has begun.
  • ATB304I
    APPC not present. TPADD and TPMODIFY syntax checked only.
  • ATB305I
    APPC not present. JCL of TPADD and TPMODIFY requests not checked.
  • ATB306I
    Only syntax checking will be performed on request(s).
  • ATB307I
    APPC administration utility processing completed - one or more requests failed.
  • ATB308I
    APPC admin. utility processing terminated - a severe error was encountered.
  • ATB309I
    Request request completed successfully.
  • ATB310I
    Request completed successfully - warning message(s) issued.
  • ATB311I
    Request request failed.
  • ATB312I
    Severe error processing request request.
  • ATB313I
    APPC administration utility processing completed successfully.
  • ATB314I
    APPC administration utility processing completed - warning message(s) issued.
  • ATB317I
    Start of statement image records.
  • ATB318I
    End of statement image records.
  • ATB319I
    No JCL error messages encountered by APPC administration utility.
  • ATB322I
    No output returned by APPC administration utility for request.
  • ATB323I
    Processing of request request has begun.
  • ATB324I
    Request request syntax checked successfully - warning message(s) issued.
  • ATB326I
    Request request syntax checking failed.
  • ATB327I
    Error freeing APPC administration utility storage - Freemain RC: return-code.
  • ATB328I
    Request not performed due to TYPRUN=APPC and APPC not present.
  • ATB330I
    Error deleting load module module - Delete RC: return-code
  • ATB332I
    APPC administration utility failed to free storage.
  • ATB333I
    Error closing file ddname - Close RC: return-code.
  • ATB335I
    Warning - GENERIC_ID ignored.
  • ATB336I
    Warning - ")" expected following keyword value:
  • ATB337I
    Warning - Extra data on request line ignored:
  • ATB338I
    Warning - No requests to process.
  • ATB339I
    Warning - No match found for the following TPSCHED_DELIMITER value:
  • ATB340I
    Warning - Data following last ")" on line is ignored:
  • ATB341I
    Syntax checking of request begun.
  • ATB342I
    Start of JCL messages.
  • ATB343I
    End of JCL messages.
  • ATB345I
    keyword keyword must not be entered as part of Scheduler Data.
  • ATB346I
    Error - GENERIC_ID required when TPSCHED_TYPE is MULTI-TRANS.
  • ATB347I
    Error - SYSTEM, USERID and GROUPID keywords are mutually exclusive.
  • ATB348I
    Required keyword(s) missing from request request.
  • ATB349I
    Unrecognized line encountered:
  • ATB350I
    Unrecognized keyword on request line:
  • ATB351I
    Operation expected - unrecognized line encountered:
  • ATB352I
    keyword keyword must be entered as part of Scheduler Data.
  • ATB353I
    Maximum length allowed for keyword is length.
  • ATB354I
    Minimum length allowed for keyword is length.
  • ATB355I
    Keyword value is not valid for keyword keyword:
  • ATB356I
    Duplicate entry found for keyword keyword.
  • ATB357I
    Keyword not recognized for request request:
  • ATB358I
    keyword keyword may not have an associated parameter:
  • ATB360I
    Failed to locate Alternate Transaction Scheduler Exit: module
  • ATB361I
    Alternate Transaction Scheduler Exit is not authorized: module.
  • ATB362I
    TP ALIAS already exists.
  • ATB363I
    Severe error returned from APPC administration utility.
  • ATB364I
    TP profile already exists.
  • ATB365I
    Side information already exists.
  • ATB366I
    Syntax error in TP profile JCL.
  • ATB367I
    TP profile not added, dataset full.
  • ATB368I
    Side information not added, dataset full.
  • ATB369I
    Insufficient authority to perform request.
  • ATB370I
    Second TP profile name specified is an alias.
  • ATB371I
    Specified TP profile not found.
  • ATB372I
    Specified side information not found.
  • ATB374I
    The TP profile is registered for test.
  • ATB375I
    TPMODIFY of an alias TP profile is not allowed.
  • ATB376I
    SCHED_EXIT may not be changed from non-ASCH to ASCH.
  • ATB378E
    Error getting APPC administration utility storage - Getmain RC: return-code.
  • ATB380E
    APPC admin. utility error - Keyword table contains unknown type for keyword.
  • ATB381E
    No match found for the following delimiter_type value:
  • ATB383E
    Unknown error from APPC administration utility for request : RC = return-code.
  • ATB384E
    APPC admin. utility error - unexpected output returned for keyword keyword.
  • ATB386E
    APPC administration utility error - keyword not recognized:
  • ATB389E
    Error opening ddname file.
  • ATB390E
    Required ddname file is not allocated.
  • ATB391E
    Allocation for SYSSDLIB failed. Reason Code = return-code.
  • ATB392E
    Error reading record from dataset: ddname.
  • ATB393E
    Error writing to dataset: ddname.
  • ATB394E
    APPC administration utility error - I/O action requested is not valid: action.
  • ATB396E
    Error loading module - Module Load RC: return-code.
  • ATB397E
    ATBSDFMU input PARM not recognized: TYPRUN.
  • ATB400I
    APPC/MVS TEST SERVICES UNAVAILABLE. REASON= xxxxxxxx.
  • ATB498I
    API TRACES STARTED WITH THE DATA SET dsname IN USE BY user WERE STOPPED BECAUSE OF A SEVERE INTERNAL ERROR
  • ATB499I
    APPC/MVS TRACE ROUTINE IS NOT AVAILABLE BECAUSE OF AN APPC/MVS INTERNAL ERROR. ANY ACTIVE API TRACES WERE STOPPED.
  • ATB500E
    APPC INTERNAL ERROR. REASON CODE=return-code

Go to the previous page Go to the next page

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



Copyright IBM Corporation 1990, 2014