OA26104: NEW FUNCTION - WORK DEPENDENT ENCLAVES

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • New function -  Work Dependent Enclaves
    
    For SQL statements that are eligible for parallel query
    execution, DB2 creates additional independent enclaves.  These
    enclaves are created under subsystem DB2 (which the DBM1 space
    is connected to) and are classified according to the
    classification rules for subsystem DB2. In order for these
    enclaves to be classified correctly, the classification rules
    for subsystem DB2 must be updated to replicate existing
    classification rules for every subsystem that may cause a stored
    procedure to run that exploits CPU parallelism.
    Furthermore, these additional independent enclaves are regarded
    as new transactions.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS 1.8 (HBB7730) and          *
    *                 above.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: For SQL statements that are eligible    *
    *                      for parallel query execution, DB2       *
    *                      creates additional independent          *
    *                      enclaves.  These enclaves are created   *
    *                      under subsystem DB2 (which the DBM1     *
    *                      space is connected to) and are          *
    *                      classified according to the             *
    *                      classification rules for subsystem DB2. *
    *                      In order for these enclaves to be       *
    *                      classified correctly, the               *
    *                      classification rules for subsystem DB2  *
    *                      must be updated to replicate existing   *
    *                      classification rules for every          *
    *                      subsystem that may cause a stored       *
    *                      procedure to run that exploits CPU      *
    *                      parallelism. Furthermore, these         *
    *                      additional independent enclaves are     *
    *                      regarded as new transactions.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See problem description.
    

Problem conclusion

Temporary fix

Comments

  • A new type of enclave, work-dependent, has been introduced to
    extend an existing independent enclave's transaction.
    WLM service IWM4ECRE has been updated to add a new TYPE keyword
    (TYPE=WORKDEPENDENT).
    With TYPE=WORKDEPENDENT specified on IWM4ECRE, the resulting
    enclave's type and certain attributes depend on the caller's
    execution environment:
    
    If the caller has joined or is scheduled into an enclave of type
    independent, the resulting enclave will be a new type of enclave
    called work-dependent. It is regarded as an extension of the
    independent enclave's transaction. Classification and owner
    address space is adopted from the independent enclave. Service
    consumed in a work-dependent enclave is accounted for as if it
    was consumed by the owning independent enclave, i.e., a period
    switch happens if the total service consumed by the independent
    and all associated work-dependent enclaves exceeds the duration
    of their current period.
    
    If the caller has joined or is scheduled into an enclave of
    type work-dependent, the resulting enclave will be of type
    work-dependent, as well. It is considered a part of the
    underlying independent enclave's transaction and inherits owner
    address space and classification from that independent enclave.
    
    If the caller has joined or is scheduled into a dependent
    enclave, the resulting enclave will be of type dependent.
    
    Finally, if no enclave has been joined when the service is
    called, the resulting enclave will be as if the service had been
    invoked with TYPE=DEPENDENT specified. Note that it is not
    allowed to invoke this service with TYPE=WORKDEPENDENT specified
    while running in a foreign enclave.
    
    
    Documentation updates :
    +--- Documentation to be updated ------------------------------+
    | z/OS 1.8: SA22-7619-14                                       |
    |     MVS Programming: Workload Managment Services             |
    | z/OS 1.9: SA22-7619-16                                       |
    |     MVS Programming: Workload Managment Services             |
    | z/OS 1.10: SA22-7619-17                                      |
    |     MVS Programming: Workload Managment Services             |
    | z/OS 1.8: SA22-7612-08                                       |
    |     MVS Programming: Authorized Assembler                    |
    |     Services Reference Vol 4 (SETFRR-WTOR)                   |
    | z/OS 1.9: SA22-7612-09                                       |
    |     MVS Programming: Authorized Assembler                    |
    |     Services Reference Vol 4 (SETFRR-WTOR)                   |
    | z/OS 1.10: SA22-7612-10                                      |
    |     MVS Programming: Authorized Assembler                    |
    |     Services Reference Vol 4 (SETFRR-WTOR)                   |
    | z/OS 1.8: GA22-7582-11                                       |
    |     MVS Data Areas, Volume 2 (DCCB - ITZYRETC)               |
    | z/OS 1.9: GA22-7582-12                                       |
    |     MVS Data Areas, Volume 2 (DCCB - ITZYRETC)               |
    | z/OS 1.10: n/a                                               |
    |     MVS Data Areas, Volume 3 (IEFDORC-ISGYQCBP)              |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Workload Managment Services               |
    |   SA22-7619-14 / SA22-7619-16 / SA22-7619-17                 |
    |   Chapter 3. Creating and Using Enclaves                     |
    +--------------------------------------------------------------|
    |   Section "Why Would You Use an Enclave":                    |
    |   (...) Each independent enclave starts in period 1 of its   |
    |   service class and switches periods based on the service    |
    |   consumed by the dispatchable units belonging to the        |
    |   enclave.                                                   |
    |   A work-dependent enclave represents a continuation of an   |
    |   existing independent enclave's transaction. It inherits    |
    |   its classification and performance goals from the          |
    |   independent enclave. Service consumed by a work-dependent  |
    |   enclave is treated as if it was consumed by the            |
    |   independent enclave, and can cause the independent enclave |
    |   (including all associated work-dependent enclaves) to      |
    |   switch into later periods.                                 |
    |   A dependent enclave represents (...)                       |
    |                                                              |
    |   Section "Creating an Enclave":                             |
    |   A subsystem creates an enclave using the IWM4ECRE service. |
    |   You can define independent, work-dependent, or dependent   |
    |   enclaves.                                                  |
    |   Comparison between Independent, Dependent and              |
    |   Work-dependent Enclaves:                                   |
    |   Independent Enclaves (...)                                 |
    |   Dependent Enclaves                                         |
    |       (...) Use a dependent enclave when you have an existing|
    |       address space defined with its own performance goal    |
    |       that you wish to extend to programs running under      |
    |       dispatchable units in other address spaces. For a      |
    |       dependent enclave that is created with TYPE=DEPENDENT  |
    |       specified on IWM4ECRE, the owner will become the home  |
    |       address space at the time the service is invoked. The  |
    |       owner address space of a dependent enclave, resulting  |
    |       from IWM4ECRE with TYPE=WORKDEPENDENT specified, will  |
    |       be the creating enclave's (i.e., the enclave the       |
    |       TCB/SRB was running in when it called IWM4ECRE) owner. |
    |       A dependent enclave derives (...)                      |
    |   Work-dependent Enclaves                                    |
    |       Use a work-dependent enclave to extend an existing     |
    |       independent enclave's transaction. A work-dependent    |
    |       enclave inherits its classification and its owner      |
    |       address space from the independent enclave it extends. |
    |       CPU service consumed by the enclave is accumulated in  |
    |       the SMF 30 record of the owning address space and the  |
    |       SMF72 record of the enclave's service class.           |
    |                                                              |
    |   Section "Multisystem Enclaves":                            |
    |   (...) A multisystem enclave begins as either an independent|
    |   or dependent enclave on a single system. This enclave is   |
    |   called the original enclave. Note that WLM does not allow  |
    |   you to export work-dependent enclaves. If the work manager |
    |   decides to involve other systems in the processing of the  |
    |   work unit, (...)                                           |
    |                                                              |
    |   Section "Performance Management of Address Spaces          |
    |               with Enclaves":                                |
    |   How workload management manages an address space where an  |
    |   enclave (dependent, work-dependent or independent) is      |
    |   running depends on the characteristics of the enclave.(...)|
    |                                                              |
    |   Section "Enclave Resource Accounting":                     |
    |   The accounting for resources consumed by an enclave        |
    |   depends on whether it is an independent, work-dependent,   |
    |   dependent, or a foreign enclave. (...)                     |
    |   For an independent enclave and work-dependent enclaves,    |
    |   CPU service is included in the SMF 30 record of the owning |
    |   address space, and in the SMF 72 record for the enclave    |
    |   service class or performance group period. MSO service is  |
    |   not calculated for either kind of enclave.                 |
    |   For dependent, work-dependent, and independent enclaves,   |
    |   IOC service is included in the SMF 30 and 72 records       |
    |   associated with the address space where the enclave work   |
    |   is executing. SRB service for enclaves is always zero.(...)|
    |   Table "Enclave Characteristics and Resource Accounting"    |
    |     ** NOTE: if a cell is omitted here, it's content hasn't  |
    |           changed  **                                        |
    |     Dispatchable unit type:                                  |
    |       Work-dependent enclave: SRBs and/or tasks              |
    |     New transaction:                                         |
    |       Work-dependent enclave: no                             |
    |     Owner:                                                   |
    |       Dependent enclave:                                     |
    |         Depends on the TYPE parameter passed to IWM4ECRE:    |
    |         If TYPE=DEPENDENT, the home a.s. at the time the     |
    |         service was issued.                                  |
    |         If TYPE=WORKDEPENDENT, the creating (dependent)      |
    |         enclave's home a.s.                                  |
    |         If TYPE=MONENV, the a.s. associated with the         |
    |          monitoring environment - see note 1                 |
    |       Work-dependent enclave:                                |
    |         owner a.s. of the creating independent enclave       |
    |     Server:                                                  |
    |         a.s. where enclave work is dispatched                |
    |     Service class/report class:                              |
    |       Work-dependent enclave:                                |
    |         same as owning independent enclave's                 |
    |     CPU time:                                                |
    |       Independent enclave:                                   |
    |         owner's SMF30Cpt (total)                             |
    |         owner's SMF30Enc (independent and work-dependent     |
    |         only)                                                |
    |       Work-dependent enclave:                                |
    |         owner's SMF30Cpt (total) owner's SMF30Enc            |
    |         (independent and work-dependent only)                |
    |     CPU service by a.s.:                                     |
    |       Independent enclave:                                   |
    |         owner's SMF30Csu (total)                             |
    |         owner's SMF30Esu (independent and work-dependent     |
    |         only)                                                |
    |       Work-dependent enclave:                                |
    |         owner's SMF30Csu (total)                             |
    |         owner's SMF30Esu (independent and work-dependent     |
    |         only)                                                |
    |     CPU service by period:                                   |
    |       Independent enclave:    enclave's R723Ccpu             |
    |       Dependent enclave:      owner's R723Ccpu               |
    |       Foreign enclave:        enclave's R723Ccpu             |
    |       Work-dependent enclave: enclave's R723Ccpu             |
    |     DASD I/O connect time by a.s. (see note 3)               |
    |       Independent enclave:    owner's SMF30Eic               |
    |         (independent and work-dependent only)                |
    |       Dependent enclave:      owner's R723Ccpu               |
    |       Foreign enclave:        enclave's R723Ccpu             |
    |       Work-dependent enclave:                                |
    |         owner's SMF30Eic (independent and work-dependent     |
    |         only)                                                |
    |     DASD I/O connect time by period (see note 3)             |
    |       Independent enclave:    enclave's R723Cict             |
    |       Dependent enclave:      owner's R723Cict               |
    |       Foreign enclave:        enclave's R723Cict             |
    |       Work-dependent enclave: enclave's R723Cict             |
    |     DASD I/O counts by a.s:                                  |
    |       Independent enclave:    owner's SMF30Eis               |
    |         (independent and work-dependent only)                |
    |       Work-dependent enclave: owner's SMF30Eis               |
    |         (independent and work-dependent only)                |
    |     DASD I/O counts by period:                               |
    |       Independent enclave:    enclave's R723Circ             |
    |       Dependent enclave:      owner's R723Circ               |
    |       Foreign enclave:        enclave's R723Circ             |
    |       Work-dependent enclave: enclave's R723Circ             |
    |     Page delay samples, with storage mgt. (see note 4)       |
    |       Work-dependent enclave: enclave's R723Cspv             |
    |     Page delay samples, without starage mgt. (see note 4)    |
    |       Work-dependent enclave: enclave's R723Caxm             |
    |     IOC service:                                             |
    |       Work-dependent enclave:                                |
    |         server's SMF 30 and 72 records                       |
    |     SRB service:                                             |
    |       Work-dependent enclave: n/a                            |
    |     MSO service:                                             |
    |       Work-dependent enclave: n/a                            |
    |                                                              |
    |   Section "Managing the Performance of Work in Enclaves":    |
    |   This section describes how to classify the work running    |
    |   in enclaves. It is broken into three topics:               |
    |       Using Independent Enclaves                             |
    |       Using Dependent Enclaves                               |
    |       Using Work-dependent Enclaves                          |
    |   Using Independent Enclaves (...)                           |
    |   Using Dependent Enclaves (...)                             |
    |   Using Work-dependent Enclaves                              |
    |       Work-dependent enclaves inherit their classification   |
    |       from the owning independent enclave and are thus       |
    |       managed to the independent enclave's performance goal. |
    |                                                              |
    |   Section "Deleting an Enclave": (...)                       |
    |   A foreign enclave is deleted using the IWMUIMPT macro.     |
    |   Work-dependent enclaves are implicitly deleted when the    |
    |   owning independent enclaves gets deleted. (...)            |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Workload Managment Services               |
    |   SA22-7619-14 / SA22-7619-16 / SA22-7619-17                 |
    |   Chapter 71. IWM4ECRE - Creating an Enclave                 |
    +--------------------------------------------------------------|
    |   DESCRIPTION:                                               |
    |      (...) Work-dependent enclaves are implicitly deleted    |
    |      when the owning independent enclave is deleted. (...)   |
    |   PROGRAMMING REQUIREMENTS:                                  |
    |      (...) Prior to release z/OS V1.11, the caller has to    |
    |      assure that work-dependent enclave support is           |
    |      available on the system before calling this macro with  |
    |      TYPE=WORKDEPENDENT. A flag (SRMSTWDP) in macro IRASRMST |
    |      (which is returned by sysevent REQSRMST) indicates      |
    |      whether or not work-dependent enclaves can be created.  |
    |      (...)                                                   |
    |   SYNTAX:                                                    |
    |      label  IWM4ECRE     TYPE=INDEPENDENT                    |
    |                       |     ,CLSFY=xclsfy                    |
    |                       |     (...)                            |
    |                       |     ,ESTRT=NEVER                     |
    |                         ,TYPE=DEPENDENT                      |
    |                         ,TYPE=WORKDEPENDENT                  |
    |                         ,TYPE=MONENV                         |
    |                             ,MONTKN=xmontkn                  |
    |                             ,ACCESS=PRIMARY                  |
    |                             ,ACCESS=HOME                     |
    |                         ,ETOKEN=xetoken                      |
    |                         ,RETCODE=xretcode]                   |
    |                         ,RSNCODE=xrsncode]                   |
    |                         ,PLISTVER=xplistver|IMPLIED_VERSION  |
    |                         ,MF=S                                |
    |                         ,MF=(L,xmfctrl,xmfattr|0D)           |
    |                         ,MF=(E,xmfctrl,COMPLETE)             |
    |   PARAMETERS:                                                |
    |     TYPE=WORKDEPENDENT                                       |
    |       Indicates that the enclave represents a continuation   |
    |       of the creating unit of work's (TCB or SRB)            |
    |       transaction The resulting enclave's type depends on    |
    |       the caller's execution environment:                    |
    |       If the caller has joined or is scheduled into an       |
    |       enclave of type independent, the resulting enclave     |
    |       will be of type work-dependent and is regarded as an   |
    |       extension of the independent enclave's transaction.    |
    |       Classification and owner address space is adopted      |
    |       from the independent enclave.                          |
    |       If the caller has joined or is scheduled into an       |
    |       enclave of type work-dependent, the resulting enclave  |
    |       will be of type work-dependent, as well. It is         |
    |       considered a part of the underlying independent        |
    |       enclave's transaction and inherits owner address space |
    |       and classification from that independent enclave.      |
    |       If the caller has joined or is scheduled into a        |
    |       dependent enclave, the resulting enclave will be of    |
    |       type dependent. The new enclave is considered part of  |
    |       the creating enclave's (i.e., the enclave the caller   |
    |       is running in) owner address space's transaction and   |
    |       inherits its classification. The creating enclave's    |
    |       owner address space will become the owner of the new   |
    |       enclave.                                               |
    |       Finally, if no enclave has been joined when            |
    |       the service is called, the resulting enclave will be   |
    |       as if the service had been invoked with TYPE=DEPENDENT |
    |       specified.  Note that it is not allowed to invoke this |
    |       service with TYPE=WORKDEPENDENT specified while        |
    |       running in a foreign enclave.                          |
    |   RETURN AND REASON CODES:                                   |
    |     Return Code/Reason Code 8/xxxx0872                       |
    |       Symbol: IwmRsnCodeForeignEnclave                       |
    |       Meaning: It is not allowed to create an enclave of     |
    |           type work-dependent from out of a foreign enclave. |
    |       Action: Make sure not to have joined a forein enclave  |
    |           prior to calling IWM4ECRE with TYPE=WORKDEPENDENT. |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Workload Managment Services               |
    |   SA22-7619-14 / SA22-7619-16 / SA22-7619-17                 |
    |   Chapter 25. IWM4EDEL - Deleting an Enclave                 |
    +--------------------------------------------------------------|
    |   RETURN CODES:                                              |
    |     Return Code/Reason Code 4/xxxx0449                       |
    |       Symbol: IwmRsnCodeWDEDeleted                           |
    |       Meaning: Enclave was deleted and one or several        |
    |           associated work-dependent enclaves were            |
    |           physically deleted.                                |
    |       Action: None required.                                 |
    |     Return Code/Reason Code 4/xxxx044A                       |
    |       Symbol: IwmRsnCodeActiveWDEDeleted                     |
    |       Meaning: Enclave was deleted while it had one or       |
    |           several TCBs joined or SRBs scheduled/running.     |
    |           Additionally, one or several associated            |
    |           work-dependent enclaves were physically deleted.   |
    |       Action: None required.                                 |
    |     Return Code/Reason Code 4/xxxx044B                       |
    |       Symbol: IwmRsnCodeAWDEDeleted                          |
    |       Meaning: Enclave was deleted and one or several        |
    |           associated work-dependent enclaves were physically |
    |           deleted. One or several physically deleted         |
    |           work-dependent enclaves had TCBs joined or SRBs    |
    |           scheduled/running.                                 |
    |       Action: None required.                                 |
    |     Return Code/Reason Code 4/xxxx044C                       |
    |       Symbol: IwmRsnCodeActiveAWDEDeleted                    |
    |       Meaning: Enclave was deleted and one or several        |
    |           associated work-dependent enclaves were physically |
    |           deleted. The enclave itself and one or several     |
    |           physically deleted work-dependent enclaves had     |
    |           TCBs joined or SRBs scheduled/running.             |
    |       Action: None required.                                 |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Workload Managment Services               |
    |   SA22-7619-14 / SA22-7619-16 / SA22-7619-17                 |
    |   Chapter 25. IWMERES - Changing an Enclave                  |
    +--------------------------------------------------------------|
    |   RESTRICTIONS:                                              |
    |      (...) The caller cannot reset a work-dependent enclave. |
    |      Such an enclave can only be reset by resetting the      |
    |      owning independent enclave. (...)                       |
    |   RETURN CODES:                                              |
    |     Return Code/Reason Code 8/xxxx08B7                       |
    |       Symbol: IwmRsnCodeWorkDepEnclave                       |
    |       Meaning: The requested service is not supported for a  |
    |           'work-dependent' enclave.                          |
    |       Action: A 'work-dependent' enclave cannot be reset     |
    |           directly. It can only be reset by resetting its    |
    |           owning independent enclave.                        |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Workload Managment Services               |
    |   SA22-7619-14 / SA22-7619-16 / SA22-7619-17                 |
    |   Chapter 25. IWMEXPT - Exporting a WLM Enclave              |
    +--------------------------------------------------------------|
    |   RESTRICTIONS:                                              |
    |      (...) It is not allowed to export work-dependent        |
    |      enclaves. (...)                                         |
    |   RETURN CODES:                                              |
    |     Return Code/Reason Code 8/xxxx08B7                       |
    |       Symbol: IwmRsnCodeWorkDepEnclave                       |
    |       Meaning: The requested service is not supported for a  |
    |           'work-dependent' enclave.                          |
    |       Action: Do not try to export work-dependent enclaves.  |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Data Areas                                             |
    |   GA22-7582-11 / GA22-7582-12 / n/a                          |
    |   IWMWRQAA Programming Interface information, RQAD           |
    |   Enclave Descriptive Entry                                  |
    +--------------------------------------------------------------+
    |    Offset     Type/Value  Len   Name                         |
    |  Dec    Hex                                                  |
    |                           (...)                              |
    |  14     (E)   BITSTRING         RQADFLAGS_BYTE1              |
    |               1... ....                                      |
    |                 (...)                                        |
    |               .... ..1.         RQADWorkDependent            |
    |                           (...)                              |
    |  124    (7C)  CHARACTER   8     RQADOwnerETKN                |
    |  132    (84)  BITSTRING   8     RQADNumWDEncls               |
    |                           (...)                              |
    |  DESCRIPTION:                                                |
    |    RQADWorkDependent: enclave is of type work-dependent      |
    |    RQADOwnerETKN: enclave token of the owner of this         |
    |      'work-dependent' enclave. this field is invalid for non |
    |      'work-dependent' enclaves.                              |
    |    RQADNumWDEncls: number of 'work-dependent' enclaves which |
    |      are owned by this independent enclave. this field is    |
    |      invalid for non-independent enclaves.                   |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10                              |
    |   MVS Programming: Authorized Assembler                      |
    |   Services Reference Vol 4 (SETFRR-WTOR)                     |
    |   SA22-7612-08 / SA22-7612-09 / SA22-7612-10                 |
    |     SYSEVENT - System Event                                  |
    |         Set the State for an Enclave (ENCSTATE)              |
    +--------------------------------------------------------------|
    | An independent enclave must not be set idle as long as there |
    | are non-idle work-dependent enclaves associated with it.     |
    +--- Location in Publication ----------------------------------+
    | z/OS 1.8 / z/OS 1.9 / z/OS 1.10 MVS Data Areas               |
    |   GA22-7582-11 / GA22-7582-12 / n/a                          |
    |   IRASRMST Programming Interface information                 |
    +--------------------------------------------------------------|
    |    Offset     Type/Value  Len   Name      Description        |
    |  Dec    Hex                                                  |
    |                           (...)                              |
    |  6      (6)   BITSTRING   1     SRMSTFF2                     |
    |               1... ....                                      |
    |               .1.. ....         SRMSTWDP  work-dependent enc |
    |                                           lave support       |
    |                           (...)                              |
    +--------------------------------------------------------------|
    

APAR Information

  • APAR number

    OA26104

  • Reported component name

    5752 SYS RSRCE

  • Reported component ID

    5752SC1CX

  • Reported release

    730

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-08-19

  • Closed date

    2009-05-29

  • Last modified date

    2009-07-02

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

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

    UA47535 UA47536 UA47646 UA47647

Modules/Macros

  • IRAENCB  IRAENCLS IRAENJON IRAENLEV IRAENREG
    IRAENRES IRAENRST IRAENTRX IRAEVECR IRAEVEDL IRAEVERY IRAEVREQ
    IRAOPREF IRAOPRES IRARMER5 IRARMFME IRARMFMT IRARMSET IRARMST3
    IRARMWL2 IRASAACR IRASADIO IRASAISS IRASAMSU IRASAPRO IRASARCM
    IRASASAS IRASASRV IRASASTO IRASRMST IRATXCHP IRATXCH2 IRAWLMPL
    IRAWRENC IWMA3TRN IWMC3EXP IWMERES  IWMERESP IWMEXPT  IWMEXPTP
    IWMQ2SAM IWMWRQAA IWMW2CRE IWMW2DEL IWMW2ERE IWMW3MLD IWMW3QRY
    IWMYCON  IWM4ECRE IWM4ECRP IWM4EDEL IWM4EDEP
    

Publications Referenced
SA22761914 SA22761916 SA22761917 SA22761208 SA22761209
SA22761210 GA22758211 GA22758212    

Fix information

  • Fixed component name

    5752 SYS RSRCE

  • Fixed component ID

    5752SC1CX

Applicable component levels

  • R730 PSY UA47535

       UP09/06/17 P F906

  • R740 PSY UA47536

       UP09/06/17 P F906

  • R750 PSY UA47646

       UP09/06/17 P F906

  • R760 PSY UA47647

       UP09/06/17 P F906

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

730

Operating system(s):

MVS, z/OS

Reference #:

OA26104

Modified date:

2009-07-02

Translate my page

Machine Translation

Content navigation