OA07204: NEW FUNCTION - MSGISPI025 TSO/E ROUTINE IRXINIT SEVERE ERROR RAS ENHANCEMENT REQUIRED

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • ISPF message "ISPI025 TSO routine IRXINIT severe error - REXX
    environment could not be initialized" occurs when invoking ISPF.
    IRXINIT returns a return code 20 (RC20) and reason code 21
    (RSN21).
    Per the z/OS TSO/E REXX Reference manual, RSN21 indicates that a
    module could not be loaded into storage.
    Additional documentation needs to be captured to aid in
    determining which module could not be loaded.
    -
    ADDITIONAL SYMPTOMS:
    At Netview initialization the following message may be seen:
     MSGCNM416I REXX INTERPRETER ENVIRONMENT INITIALIZATION FAILED
     FOR TASK, RETURN CODE = 20, REASON CODE = 21."
    Executing REXX execs result in:
     "Unable to initialize a REXX environment.  IRXINIT Return
     Code = 00000020 Reason Code = 00000021."
    -
    At TSO/E LOGON, the following may be seen:
    ABEND66D in IKJEFT0I where REG15 at the time of the abend
    contains x'00140014' indicating IRXINIT RC20.
    -
    In an HSM environment the following may be seen:
     *ARC0031E TSO/E AND REXX LANGUAGE ENVIRONMENT INITIALIZATION
     DID NOT COMPLETE, RC= 8, REASON= 80, REASON2= 21
    -
    See also HSM APAR OA03081.
    

Local fix

  • SLIP SET,IF,ID=xxxx,J=yyyyyyy,LPAMOD=(IRXINIT,zzzzz),A=SYNCSVCD,
               SDATA=(LPA,CSA,RGN,TRT,LSQA,SQA,PSA,SUM),END
           where xxxx is any 4-character unique SLIP identifier,
           where yyyyyyy is the jobname or userid,
           where zzzzz is calculated by:
             obtaining an AMBLIST for LMOD IRXINIT (in LPA).  Find
             the entry point address for IRXITPA.  Add x'21EA' to
             the address (for level HTE7706).
             The total will be the zzzzz in the slip.
             .
             The offset x'21EA' is valid for level HTE7706, which
             ships in the base of HTE7706 through HTE7760. It is
             also valid for base HTE7770, and for all PTF levels
             representing the fix for APAR OA23837 (namely, UA47422
             (HTE7730), UA47423 (HTE7740), UA47424 (HTE7750), and
             UA47425 (HTE7760)).
    .
    After setting the SLIP, recreate the problem to obtain a dump.
    Initialize the dump under IPCS and issue IPCS command
    STATUS REGS to obtain the registers.
    .
    The address computed by adding Reg9 (at the time of the dump)
    +x'460' will point to the 8-byte area containing the module
    name for which LOAD failed.  (If the PTF for APAR OA23837 has
    been installed or for level HTE7770, Reg9+x'468' will contain
    the module name address.)
    .
    This module name address can also be obtained from the
    SYSTRACE entry for the failing LOAD (SVC 8).  The Reg0 address
    at the time of the LOAD, as recorded in the UNIQUE-2 field of
    the SVC 8 SYSTRACE entry, points to the module name.
    For Example:
                                          UNIQUE-1 UNIQUE-2 UNIQUE-3
    00597700  SVC    8 478D1000 847DAD5A  00000000 198DE400 80000000
    00597700  SVCR   8 478D1000 847DAD5A  00000004 7FFFBF30 00000800
    ... SVCR 8, in the UNIQUE-1 field is R15=4 showing this load
        failed. The R0 value from the UNIQUE-2 field of the SVC 8
        points to the module name address for the load that failed.
    .
    Once the module name is found, the user needs to determine
    where it resides, where it SHOULD reside, and if it's
    authorization is correct.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS TSO/E or z/OS REXX.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When IRXINIT is invoked to initialize   *
    *                      a new REXX environment, and the init    *
    *                      fails, a return code 20 reason code     *
    *                      nn is returned to help describe the     *
    *                      error. (Currently, nn may range from    *
    *                      1 to 27.) However, this information     *
    *                      may not always be externalized to the   *
    *                      user. Often a SLIP trap must be set to  *
    *                      obtain additional IRXINIT return code,  *
    *                      reason code, and/or other diagnostic    *
    *                      information.                            *
    *                      .                                       *
    *                      This information should be made more    *
    *                      readily available.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When IRXINIT is invoked to initialize a new REXX environment,
    and the IRXINIT call fails, a return code 20 reason code nn
    (where n is a reason code currently in the range 1 to 27)
    is returned to help describe the error. However, this is often
    not externalized to the user. Often a SLIP trap must be set
    to obtain the additional IRXINIT return code / reason code
    or other diagnostic information.
    .
    For example, the following are some of the typical errors seen:
    -ISPF message "ISPI025 TSO routine IRXINIT severe error - REXX
     environment could not be initialized" occurs when invoking
     ISPF. IRXINIT returns a return code 20 (RC20) and reason
     code 21 (RSN21).
     .
     Per the z/OS TSO/E REXX Reference manual, RC20 RSN21 indicates
     that a module could not be loaded into storage.  Additional
     documentation then needs to be captured to aid in determining
     which module could not be loaded. The module name is typically
     not externalized, and it would usually require the user to set
     a SLIP trap in order to obtain the module name informaton.
    .
    Other similar errors seen:
    -At Netview initialization following message may be seen:
     "MSGCNM416I REXX INTERPRETER ENVIRONMENT INITIALIZATION FAILED
     FOR TASK, RETURN CODE = 20, REASON CODE = 21."
     .
     Executing REXX execs result in:
     "Unable to initialize a REXX environment.  IRXINIT return
     Code = 00000020 Reason Code = 00000021."
    .
    -At TSO/E LOGON, the following may be seen:
     ABEND66D in IKJEFT0I where REG15 at the time of abend contains
     x'00140014' indicating IRXINIT RC20.
    .
    Additional RAS support should be added to help better diagnose
    REXX initialization failures, including errors that can occur
    when creating the REXX TMP environment during LOGON to TSO/E.
    

Problem conclusion

Temporary fix

Comments

  • With this REXX RAS APAR, REXX Initialization errors are easier
    to diagnose and correct. If an error return code 20 occurs when
    IRXINIT is called, new message IRX0900E or IRX0901E will be
    issued to provide the IRXINIT return code / reason code.  If the
    IRXINIT error is for return code 20, reason code 21 (indicating
    some module could not be loaded), the name of the module is
    included in message IRX0901E.
    .
    In addition, the ABEND66D reason code information is enhanced
    for errors that can occur when trying to create the TSO/E TMP
    REXX environment.
    .
    Additional Search Keywords:  MSGIRX0900E MSGIRX0901E
    .
                    PUB changes for OA07204
                  ============================
    The following publications are updated for this APAR:
     o "z/OS V1R11.0 MVS System Codes (SA22-7626-21)"
     o "z/OS V1R11.0 TSO/E REXX Reference" (SA22-7790-08)
     o "z/OS V1R11.0 TSO/E Messages"  (SA22-7786-09)
    All changes shown are flagged by the change bar (|).
    
    =============================================
    Pub Changes for "z/OS V1R11 MVS System Codes"
    =============================================
    (1) Update description of ABEND66D as documented in "z/OS MVS
        System Codes" within "Chapter 2.0 System Completion Codes".
    
        The "Note" under "Explanation" below has been changed.
        (a) There are now 2 separate notes, "1" and "2", now
            clearly labeled.
        (b) The second paragraph of the first note should also have
            been indented to clearly show it is part of note 1.
        (c) After note 1, added multi-paragraph note 2.
    
    === Start of Pub Update ========================================
     o 66D
    
     Explanation: This abend may be issued from three different
        areas in TSO/E: I/O services, REXX, and CLIST processing.
             :       :  (* Rest of explanation, and note 1 *)
    | Notes:
    |  1.  The reason code appears on the user's terminal as a
           four-byte field. The rightmost two bytes contain the
           abend reason code. If these two bytes are between
           X'000D' and X'0013', then the leftmost two bytes (if
           they are non-zero) contain the return code of the
           function called by the module that issued the abend.
    
    |      For example, if the reason code is X'0008000D', the
    |      abend reason code is X'000D' and the return code of the
    |      function called by the module is X'0008'.
    |
    |  2.  If the reason code is of the form X'zzzz0014',
    |      X'zzzz0064', X'zzzz0068', or x'zzzz006C', this indicates
    |      a failure in IRXINIT while trying to initialize the TSO/E
    |      TMP REXX environment.  If the rightmost two bytes contain
    |      X'0014' then the leftmost two bytes will contain the
    |      IRXINIT reason code associated with IRXINIT return code
    |      20, as documented in the "TSO/E REXX Reference" under
    |      IRXINIT.
    |
    |      If the rightmost two bytes contain X'0064' or X'0068',
    |      indicating a system or user abend occurred in IRXINIT,
    |      then the leftmost two bytes contain the system abend
    |      code or user abend code respectively of the abend
    |      experienced by IRXINIT.
    |
    |      If the rightmost two bytes contain x'006C', the leftmost
    |      two bytes contain the unexpected IRXINIT return code.
    |      Refer to codes X'14', X'64', X'68', and x'6C' below
    
     Code  Explanation
     ====  ===================
            :           :         :
            :(codes 01 through 13):
            :           :         :
    |14    IRXINIT failed with return code 20 while trying to
    |      create the TSO/E TMP REXX environment.
            :           :         :
            :(codes 15 through 62):
            :           :         :
    |64    IRXINIT failed with return code 100 while trying to
    |      create the TSO/E TMP REXX environment.
    |
    |68    IRXINIT failed with return code 104 while trying to
    |      create the TSO/E TMP REXX environment.
    |
    |6C    IRXINIT failed with an unexpected return code while
    |      trying to create the TSO/E TMP REXX environment.
    
     Note: If you are not able to locate the abend reason code in
     the above table, see the note at the beginning of the ABEND66D
     description section.
    
    System Action: The action of the system varies depending on
       ...    (*rest of system action text *)
    
     Code   System Action
    
     02-0B  An SVC dump is not taken for the abend.
    
    |0D-13  See note 1 at the beginning of the ABEND66D description
      section.  An SVC dump is not taken for the abend.
    
    |14-19, 64, 68, 6C  See note 2 at the beginning of the ABEND66D
    | description section for more information about codes 14, 64,
    | 68, and 6C.  An SVC dump is not taken for the abend.
    
     Application Programmer Response: Try rerunning the REXX exec or
        re-invoking the TSO/E function...
           (*rest of Application Programmer Response text*)
    
     Code Response
     ==== ====================================================
            :           :         :
            :(codes 2 through 0B) :
            :           :         :
    |14  IRXINIT failed with return code 20 (X'14') while trying
    |    to initialize the TSO/E TMP REXX environment. The complete
    |    4-byte reason code is of the form X'zzzz0014'.  zzzz is
    |    the IRXINIT reason code, as documented in the "TSO/E REXX
    |    Reference" under IRXINIT.  It further describes the
    |    meaning of IRXINIT return code 20.  The REXX environment
    |    is not initialized.
    |
    |    This error will usually be accompanied by a message
    |    IRX0900E or IRX0901E issued to the console.
    |
    |    If your installation has replaced a parameters module,
    |    verify that the correct module was called during REXX
    |    initialization.
    |
    |    Examples:
    |     00150014 - IRXINIT completed with return code X'14',
    |                reason code X'15'. A module could not be
    |                loaded.  Look for message IRX0901E issued to
    |                the console for the name of the module.
    |
    |     001B0014 - IRXINIT completed with return code X'14',
    |                reason code X'1B'. Wrong number of parameters.
    |                Message IRX0900E might also be issued.
            :           :         :
            :(codes 15 through 4D):
            :           :         :
    |64  IRXINIT failed with return code 100 (X'64') while trying to
    |    initialize the TSO/E TMP REXX environment. This indicates
    |    that IRXINIT abended with a system abend.  The complete
    |    4-byte reason code is in the form X'zzzz0064', where zzzz
    |    is the hexadecimal abend code of the system abend in
    |    IRXINIT.
    |
    |    If needed, use a SLIP COMP=zzz to get a dump for the system
    |    abend zzz in IRXINIT, where zzz represents the rightmost
    |    three hex digits of the system abend code.
    |
    |68  IRXINIT failed with return code 104 (X'68') while trying
    |    to initialize the TSO/E TMP REXX environment. This
    |    indicates that IRXINIT abended with a user abend.  The
    |    complete 4-byte reason code is in the form X'zzzz0068',
    |    where zzzz is the hexadecimal abend code of the user abend
    |    in IRXINIT.
    |
    |    If needed, use a SLIP COMP=Udddd to get a dump for the user
    |    abend in IRXINIT, where dddd are the decimal digits of the
    |    user abend code. (That is, hex code zzzz converted to
    |    decimal dddd.)
    |
    |6C  IRXINIT failed with an invalid non-zero return code while
    |    trying to initialize the TSO/E TMP REXX environment. The
    |    complete 4-byte reason code is in the form X'zzzz006C',
    |    where zzzz is the unexpected IRXINIT return code in hex.
    |
    |    If needed, use a SLIP COMP=66D to get a dump for this
    |    abend.
    
     System programmer response:  If no fix exists, contact the
         IBM Support Center.
    
     Source: Time Sharing Option Extensions (TSO/E)
    === End   of Pub Update ========================================
    
    ================================================================
    Pub Change for "z/OS V1R11.0 TSO/E REXX Reference"
    ================================================================
    (2a) Update Chapter 15 "Initialization and Termination
         Routines", within the section "Initialization Routine -
         IRXINIT" and under the subsection entitled "Parameters".
    
         Under the subsection "Parameters", in paragraph 2, second
         sentence, change the sentence to now read as follows:
     --Start of update ---------------
     "If IRXINIT does not find the high-order bit set on in either
    | the address for parameter 7 or in the address of one of the
    | optional parameters from 8 to 11, IRXINIT does not initialize
      the environment and returns with a return code of 20 and a
      reason code of 27."
     --End   of update ---------------
    
    (2b) Under the subsection "Parameters", update Table 66.
         "Parameters to IRXINIT" to add new optional parm11:
    === Start of Pub Update ========================================
               No. of
      Parameter Bytes Description
      ========= ===== ==============================================
      Param 10    4   Parameter 10 ... existing description ...
           :                :         :
    | --------------------------------------------------------------
    | Param 11    4   Parameter 11 is an optional parameter that is
    |                 the address of a message buffer (MSGBUF) in
    |                 which IRXINIT can return an error message if
    |                 IRXINIT completes with return code 20.
    |
    |                 The MSGBUF consists of a fullword length
    |                 header field (MSGHDR) followed by the message
    |                 text return area (MSGTEXT). The MSGHDR word is
    |                 divided into two halfword length fields:
    |                 - The first halfword, MSGTLEN, is used by the
    |                   caller to pass the length of the MSGTEXT
    |                   area, excluding the length of the 4-byte
    |                   header. This value is not changed by
    |                   IRXINIT.
    |                 - The second halfword, MSGRLEN, is used by
    |                   IRXINIT to indicate the actual length of the
    |                   message text returned in the MSGTEXT area,
    |                   or 0 if none. (The caller should initialize
    |                   this halfword to 0 before calling IRXINIT.)
    |
    |                 If a message buffer address is passed and
    |                 IRXINIT encounters an error for which a
    |                 message is returned, no message is issued by
    |                 IRXINIT. Instead, IRXINIT just returns the
    |                 message.
    |
    |                 If parm11 is 0, or if this parameter is not
    |                 passed because fewer than 11 parameters are
    |                 passed, and if IRXINIT completes with return
    |                 code 20, a message will be issued to the TSO/E
    |                 user and/or to the CONSOLE containing
    |                 information about the error. (This is default
    |                 for callers not using this parameter.)
    |
    |                 If the caller of IRXINIT does not want IRXINIT
    |                 to issue an error message nor return a message
    |                 when an error occurs, specify parm11 pointing
    |                 to a buffer with a length header word of
    |                 X'00000000'.  This indicates a buffer of
    |                 length 0 is passed, so no message will be
    |                 returned and no message will be issued if an
    |                 error should occur.
    |
    |                 If a MSGBUF buffer is passed, the MSGTEXT area
    |                 should at least 124 bytes long. If the message
    |                 being returned is longer than the message
    |                 buffer space provided, it will be truncated
    |                 to the size of the buffer provided.
    |
    |                 Messages issued or returned by IRXINIT are not
    |                 translated by MMS message processing.
    | --------------------------------------------------------------
    === End   of Pub Update ========================================
    
    (2c) Figure 28 must be updated to now show 11 parameters
    === Start of Pub Update ========================================
      +- R1
      |
      v                                  fullword    fullword
      +----------+ +---> +------------+    +----------+-----------+
      | parm1 ptr| |     |Extended    |--->| Storage  | Len of    |
      +----------+ |     |Parmlist_ptr|  +-| workarae@| storage   |
      | parm2 ptr| |     +------------+  | +----------------------+
      +----------+ |                     | |   FFFFFFFFFFFFFFFF   |
      / :   :    / |                     | +----------------------+
      +----------+ |                     v
      | parm8 ptr|-+                     +------------------+
      +----------+                       | Storage workarea |
      / :   :    /                       +------------------+
    | +----------+    +----------+
    | |*parm11ptr|--> |MsgBuf ptr| -+
    | +----------+    +----------+  |
    |* high order bit on            |
    |                               |
    | +-----------------------------+
    | | On Entry to IRXINIT, if parm11 is passed it looks like this
    | |     MSGBUF     MSGTEXT
    | +---> +---------+----------------/../------------------------+
    |       |007C|0000|  msgtext...return area                     |
    |       +---------+----------------/../------------------------+
    |         |    |  |<------------------ X'7c' ----------------->|
    |         |    |
    |         |    +--- MSGRLEN:  Init return len to 0.
    |      MSGTLEN: halfword len of buffer text area passed,
    |               excluding the 4-byte length header word.
    | /
    | |  On Exit from IRXINIT when rc=20, parm11 may return a msg
    | +---> +---------+----------------/../------------------------+
    |       |007C|00nn|IRX090nE message text data ... to end.      |
    |       +---------+----------------/../------------------------+
    |         |    |  |<--------- X'nn' ------------------->|
    |         |    |  |<------------------ X'7c' ----------------->|
    |         |    |
    |         |  MSGRLEN:  halfword that returns the length
    |         |            X'nn' of msg text being returned in
    |         |            the MSGTEXT area, or 0 if none.
    |      MSGTLEN: halfword len of msg buffer (unchanged)
    |
    | Note:
    |   To prevent IRXINIT from issuing a message or returning a
    |   message, code X'00000000' in the length header word of the
    |   MSGBUF passed to IRXINIT. The first halfword (MSGTLEN) is
    |   X'0000', which indicates that the length of the MSGTEXT
    |   return area is 0, so if an error does occur resulting in
    |   return code 20, no message will be returned, and no message
    |   will be issued.
    |
    |   To allow IRXINIT to issue an error message if it is unable
    |   to initialize a new REXX environment and would otherwise
    |   return a return code 20, simply end the parameter list
    |   before parm11, or pass parm11 with an address of 0 (no
    |   buffer).
    === End   of Pub Update ========================================
    
    (2d) Under the IRXINIT subsection entitled  "Output Parameters",
        between the paragraph that describes Parameter 7 as an
        output parameter and "Table 68. Reason codes for IRXINIT
        processing", add a paragraph describing output parameter 11.
    === Start of Pub Update ========================================
          :       :       :
      Parameter 7 contains a reason code for IRXINIT processing.
      The reason code indicates whether IRXINIT completed
      successfully.  If IRXINIT processing was not successful, the
      reason code indicates the error.  Table 68 describes the
      reason codes IRXINIT returns. Note that these reason codes
      are not the same as the reason codes that are returned
      because of a system or user abend. A system or user abend
      results in a return code of 100 or 104 and an abend code and
      abend reason code in register 0. See Return codes on page
      426 for a description of return codes 100 and 104.
    
    | If parameter 11 is specified and IRXINIT is returning with
    | return code 20, the message buffer pointed to by parameter 11
    | will return a message associated with the error, usually
    | containing the return code and reason code. If parameter 11
    | is not passed when IRXINIT completes with return code 20, the
    | message is issued to the TSO/E user and/or to the CONSOLE.
    | The caller of IRXINIT can set parm11 to point to a buffer
    | with length header word X'00000000' to prevent IRXINIT from
    | either issuing or returning a message when the IRXINIT return
    | code is 20.
    
      Table 68. Reason codes for IRXINIT processing
     +------------------------------------------------
     |  ... rest of Table 68 ...                     |
          :       :       :
    === End   of Pub Update ========================================
    
    (2e) Under the IRXINIT subsection entitled  "Output Parameters",
         within "Table 68. Reason codes for IRXINIT processing,
         update the description for reason code 21, as shown:
    === Start of Pub Update ========================================
    Reason Code  Description
    -----------  ---------------------------------------------------
    |  21        Unsuccessful processing. A module could not be
    |            loaded into storage. Refer to message IRX0901E for
    |            the name of this module. This message may be issued
    |            or returned to the caller of IRXINIT in parm 11.
    === End   of Pub Update ========================================
    
    =========================================
    Pub Changes for z/OS V1R11 TSO/E Messages
    =========================================
    (3) Update "z/OS TSO/E Messages" under Chapter 8, "TSO/E
        Terminal Messages" by adding new msgs IRX0900E and IRX0901E.
    === Start of Pub Update ========================================
    | IRX0900E REXX INITIALIZATION FAILED WITH RETURN CODE <retcode>
    |          AND REASON CODE <reascode>.
    |
    | Explanation:  The IRXINIT REXX initialization routine failed
    |    with the return code and reason code specified in the
    |    message.  Refer to the "TSO/E REXX Reference" under the
    |    description of IRXINIT for more information about the
    |    meaning of the specified return code and reason code.
    |
    | System Action: IRXINIT terminates unsuccessfully.
    |
    | User Response: After referring to the return code and reason
    |    code information, correct the call to IRXINIT. You may need
    |    to contact your system programmer for assistance.
    |
    | Audience: REXX user or system programmer.  This message
    |    usually goes to a TSO user, but it may also be issued to
    |    the system CONSOLE during an unsuccessful TSO/E user LOGON.
    |
    | Detected by: IRXINIT or IRXITPA
    | --------------------------------------------------------------
    | IRX0901E REXX INITIALIZATION FAILED WITH RETURN CODE <retcode>
    |          AND REASON CODE <reascode>. MODULE <modname> COULD
    |          NOT BE LOADED.
    |
    | Explanation:  The IRXINIT REXX initialization routine failed
    |    with the return code 20 and reason code 21 as specified in
    |    the message.  Refer to the "TSO/E REXX Reference" under
    |    the description of IRXINIT for more information about the
    |    meaning of the specified return code and reason code.
    |
    |    The error occurred because the specified module could not
    |    be loaded.  If you recently changed this module make sure
    |    it is linked correctly and is available in a load library
    |    accessible to IRXINIT.
    |
    |    This error sometimes occurs when the name of a new function
    |    package routine (or other routine) is added to some REXX
    |    parameter module, but the specified load module is not made
    |    available in one of the accessible load libraries.
    |
    |      * A REXX parameter module is a non-executable module
    |        that is passed to IRXINIT during REXX environment
    |        initialization to describe and control the attributes
    |        of the REXX environment being initialized. (Examples
    |        of REXX parameter modules include IRXPARMS, IRXTSPRM,
    |        IRXISPRM.)
    |
    | System Action: IRXINIT terminates unsuccessfully.
    |
    | User Response: After referring to the return code and reason
    |      code information and missing module information, make the
    |      specified load module available. You may want to place
    |      the module in a STEPLIB or in a system load library. You
    |      may need to contact your system programmer for
    |      assistance.
    |
    | Audience: REXX user or system programmer.  This message
    |    usually goes to a TSO user, but it may also be issued to
    |    the system CONSOLE during an unsuccessful TSO/E user LOGON.
    |
    | Detected by: IRXINIT or IRXITPA
    === End   of Pub Update ========================================
    

APAR Information

  • APAR number

    OA07204

  • Reported component name

    TSO REXX

  • Reported component ID

    566528508

  • Reported release

    706

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Serviceability

  • Submitted date

    2004-04-07

  • Closed date

    2010-07-22

  • Last modified date

    2010-09-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA55798 UA55799 UA55800 UA55801

Modules/Macros

  •    IKJEFT0I IRXINIT  IRXITERM IRXITPA  IRXRECOV
    IRXTMSGS RXREPL
    

Publications Referenced
SA22762621 SA22779008 SA22778609    

Fix information

  • Fixed component name

    TSO REXX

  • Fixed component ID

    566528508

Applicable component levels

  • R740 PSY UA55798

       UP10/08/18 P F008

  • R750 PSY UA55799

       UP10/08/18 P F008

  • R760 PSY UA55800

       UP10/08/18 P F008

  • R770 PSY UA55801

       UP10/08/18 P F008

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information


More support for:

z/OS family

Software version:

706

Operating system(s):

MVS, z/OS

Reference #:

OA07204

Modified date:

2010-09-01

Translate my page

Content navigation