IBM Support

OA66459: MSGIEF336I JOB CANCELLED BY ALLC_OFFLN INSTALLATION EXIT WITH JES3 AND TS7700 AND JES3 ALLOCATION ASSIST ENABLED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Any JES3 users with TS7700 and JES3 Allocation Assist function
    specified in DEVSUPxx parmlib member JES3_ALLOC_ASSIST=YES where
    their clusters being used do not start with cluster 0 or if
    their clusters being used start with cluster 0 but there are
    gaps, for example, clusters 0, 1, 4, 5, 6, 7 allocations may
    fail with MSGIEF336I JOB CANCELLED BY ALLC_OFFLN INSTALLATION
    EXIT or may go into allocation recovery IEF877I to vary a
    device online or may hang.
    Users Affected: users joining or unjoining clusters where
    the first cluster is not cluster0 or first one is cluster0
    but there are gaps, are running JES3 ONLY, with DEVSUPxx
    parameter JES3_ALLOC_ASSIST=YES
    

Local fix

  • BYPASS/CIRCUMVENTION:
    create a new DEVSUPNN parmlib member, copy current DEVSUPxx to
    the new one and add:
    JES3_ALLOC_ASSIST=NO
    Then issue SET DEVSUP=NN where NN is the new DEVSUPNN created
    
    RECOVERY ACTION:
    rerunning the job will normally run successfully
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of TS7700 Virtualization Engine        *
    *                 D/T3957 and D/T3948 and are running in JES3  *
    *                 environment only.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: In Jes3 environment with TS7700 and     *
    *                      JES3_ALLOC_ASSIST=YES is specified in   *
    *                      DEVSUPxx member of SYS1.PARMLIB, if the *
    *                      first cluster in the composite library  *
    *                      is not named cluster 0 or if the first  *
    *                      cluster is named cluster 0 but there    *
    *                      are gaps in the names, for example cl0, *
    *                      cl1,cl4,cl5, device services may return *
    *                      a list of libpool ids that include the  *
    *                      distributed libraries incorrectly.      *
    *                      This can cause JES3 to build LDXlibid,  *
    *                      LDElibid entries in the JES3 deck       *
    *                      incorrectly.  When this happens some    *
    *                      tape allocations may fail because these *
    *                      invalid library names are returned in   *
    *                      the device pool list to allocation.     *
    ****************************************************************
    

Problem conclusion

  • Code was updated in LIBSERV POOLIST request to correctly return
    a list of device pool ids with the correct associated
    distributed library names.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA66459

  • Reported component name

    DEV SUPPORT SER

  • Reported component ID

    5695DF113

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-26

  • Closed date

    2024-10-25

  • Last modified date

    2024-12-03

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

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

    UJ96218 UJ96219 UJ96220

Modules/Macros

  • IGX01044
    

Fix information

  • Fixed component name

    DEV SUPPORT SER

  • Fixed component ID

    5695DF113

Applicable component levels

  • R240 PSY UJ96220

       UP24/11/27 P F411 ¢

  • R250 PSY UJ96219

       UP24/11/27 P F411 ¢

  • R310 PSY UJ96218

       UP24/11/27 P F411 ¢

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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"310"}]

Document Information

Modified date:
03 December 2024