IBM Support

OA45876: ERROR MESSAGE IKJ56221I WITH RETURN CODE 0218 ISSUED AFTER THE APPLY OF APARS OA42679 AND OA43330

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After the Apply of IDCAMS APAR OA42679 and TSO/E APAR OA43330,
    DAIRFAIL message IKJ56221I with RC0218 may be issued from a
    address space running IDCAMS.  The RC0218 dynamic allocation
    error code states the caller does not have volume mount
    authority. This error can only occur if the allocation requires
    that a volume be mounted in order to satisfy the request.
    .
    In APAR OA42679, IDCAMS changed the way it invokes TSO/E to
    issue an IDCAMS ALLOCATE command. Under OA42679 IDCAMS now uses
    the TSO/E Service Facility (TSF) to invoke ALLOCATE, rather than
    running the ALLOCATE under the TSO/E TMP.  TSO/E APAR OA43330
    was taken to permit the authorized IDCAMS caller to use TSF.
    (Prior to this APAR, no authorized APF authorized caller could
    use TSF.)  However, by default, users of TSF do not get "volume
    mount authority".
    .
    So if either an IDCAMS ALLOCATE, or some subsequent SVC99
    dynamic allocation request within the IDCAMS address space
    were to need "volume mount authority" to satisfy its request,
    that allocation would fail with RC0218, unless the SVC99
    caller explicitly allows "volume mount authority" by setting
    the S99MOUNT flag to '1'B in the S99RB prior to the SVC99 call.
    .
    Additional Keywords: MSGIKJ56221I SVC99 RC0218 RC218
    
    ------------------------------------------------------------
    Verification Steps:
    1. ALLOCATION fails with RC0218 and/or message IKJ56221I.
    2. In the failing address space, JSCBPSCB is non-0 pointing
       to a PSCB with PSCB+x'10' bit x'10' OFF.
    3. ASXBLWA is non-0 pointing to an LWA with LWA+x'260' bit
       x'80' ON and LWA+x'10B' bit x'40' ON.
    .
    CATKEYS: IDC2014 IDCALLOC
    

Local fix

  • ++APAR AA45876 is available for z/OS V1R12 (HTE7770),
    z/OS V1R13 (HTE7780), and z/OS V2R1 (HTE7790) for any
    customer experiencing this problem. Contact TSO/E L2
    to request the ++APAR service.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All job running PGM IDCAMS that              *
    *                 subsequently issues an IDCAMS ALLOCATE       *
    *                 command.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: After APARS OA42679 and OA43330, any    *
    *                      job using IDCAMS to invoke an ALLOCATE  *
    *                      now uses the TSO/E Service Facility.    *
    *                      Subsequently, any program running in    *
    *                      that IDCAMS address space and issuing   *
    *                      SVC99 for an allocation which requires  *
    *                      a device or volume mount will fail      *
    *                      with SVC99 retcode x'0218' and/or       *
    *                      message IKJ56221I, because the TSO/E    *
    *                      Service Facility, by default, does not  *
    *                      grant volume mount authority.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After the Apply of IDCAMS APAR OA42679 and TSO/E APAR OA43330,
    DAIRFAIL message IKJ56221I and/or RC0218 is being issued from
    an SVC99 request that requires that a volume or device be
    mounted. If issued, the message might look something like the
    following:
      IKJ56221I DATA SET userid.TEMP.TAPE NOT ALLOCATED, VOLUME
                NOT AVAILABLE+
      IKJ56221I VOLUME  NECESSARY TO SATISFY YOUR REQUEST NOT ON
                SYSTEM, AND CANNOT BE MOUNTED
    .
    Historically, any program using the TSO/E Service Facility
    would not have volume mount authority, as a default.
    The RC0218 indicates that the SVC99 requestor does not have
    volume mount authority. (Note that the SVC99 requestor could
    specifically request volume mount authority on the SVC99 call
    by setting the S99MOUNT bit ON in the S99RB prior to issuing
    the SVC. This would override any "no mount authority" default.)
    .
    In APAR OA42679, IDCAMS changed the way it invokes TSO/E.
    IDCAMS now uses the TSO/E Service Facility. It previously
    attached the TSO/E TMP (Terminal Monitor Program) IKJEFT01.
    For its part, TSO/E under APAR OA43330 makes it possible
    for the APF Authorized IDCAMS to be able to setup and use
    a TSO/E Service Facility Environment. However, the mount
    authority default in such a TSO Service Facility Environment
    is, and always has been, no volume mount authority.
    .
    So what now happens is that the first time an IDCAMS ALLOCATE
    command is issued, IDCAMS creates the TSO Service Facility
    environment. This creates a PSCB control block which contains
    the default mount authority - "no mount authority". From
    this point forward, any SVC99 request in the address space
    that does not specifically request "mount authority", will
    be subject to the default. And dynamic allocation always
    uses the mount authority default from the PSCB, if a PSCB
    exists. Hence SVC99 requests that need a volume mounted
    might now fail.
    .
    Additional Keywords: MSGIKJ56221I SVC99 RC0218 RC218
    .
    Verification Steps:
    1. ALLOCATION fails with RC0218 and/or message IKJ56221I.
    2. In the failing address space, JSCBPSCB is non-0 pointing
       to a PSCB with PSCB+x'10' bit x'10' OFF.
    3. ASXBLWA is non-0 pointing to an LWA with LWA+x'260' bit
       x'80' ON and LWA+x'10B' bit x'40' ON.
    

Problem conclusion

  • This APAR extends the support previously provided by
    OA43330 when used together with OA42679. With this support,
    the special TSO Service Facility environment started for
    IDCAMS will default to "volume mount authority allowed".
    
    So any SVC99 alloc (DYNALLOC) request from an IDCAMS
    environment which had previously established a TSO/E Service
    Facility environment will have "volume mount authority
    allowed" as its default.
    

Temporary fix

  • *********
    * HIPER *
    *********
    ++APAR AA45876 IS AVAILABLE FOR Z/OS V1R12 (HTE7770),
    Z/OS V1R13 (HTE7780), AND Z/OS V2R1 (HTE7790) FOR ANY
    CUSTOMER EXPERIENCING THIS PROBLEM. CONTACT TSO/E L2
    TO REQUEST THIS ++APAR SERVICE.
    

Comments

APAR Information

  • APAR number

    OA45876

  • Reported component name

    TSO/E SCHEDULAR

  • Reported component ID

    566528502

  • Reported release

    780

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-20

  • Closed date

    2014-09-17

  • Last modified date

    2014-10-02

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

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

    UA74850 UA74851 UA74852

Modules/Macros

  • IKJPCENV
    

Fix information

  • Fixed component name

    TSO/E SCHEDULAR

  • Fixed component ID

    566528502

Applicable component levels

  • R770 PSY UA74850

       UP14/10/01 P F409 Ž

  • R780 PSY UA74851

       UP14/10/01 P F409 Ž

  • R790 PSY UA74852

       UP14/10/01 P F409 Ž

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 October 2014