IBM Support

PH60038: LONG TERM PLAN EXTEND JOB ABENDS WITH S0C7 (NAME=EQQLASEL)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the BL runs to directly update the AD file without passing
    through the controller, if there are errors about the number of
    versions for some of the application records (too many versions,
    as happened in the customer's scenario) , the change of a bit
    (from 1 to 0)  the process does not get completed and it results
    in a record corruption in the key. If it got completed, instead,
    a verify process would adjust all the records coherently.
    To overcome in case of corruption it is sufficient to insert at
    least one application via the same process, but for that
    application no error condition should occur.
    In fact, in this situation, the final verify in the code flow
    will adjust the keys of all the records in the AD, where needed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All WAz users who run with BL                *
    *                                                              *
    *                 FUNCTION=BATCH                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: AD record corruption might occur if you *
    *                      use BATCH LOADER without passing        *
    *                      through the controller and try to       *
    *                      create more than 4 versions of the      *
    *                      same AD record.                         *
    ****************************************************************
    AD record corruption might occur if you use BATCH LOADER
    without passing through the controller and try to create more
    than 4 versions of the same AD record.
    

Problem conclusion

  • The issue was caused by the change of a bit that, because of
    a base code bug, was done out of the needed control.
    The issue only occurred when using bl without the controller and
    at the same time trying to define more than 4 versions of
    the same AD record (the maximum number of allowed versions for
    an AD record is 4).
    Fixed by this apar.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH60038

  • Reported component name

    TIV WRKLD SCHD

  • Reported component ID

    5697WSZ01

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-02-27

  • Closed date

    2024-07-17

  • Last modified date

    2024-10-31

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

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

    UI97670 UI97671

Modules/Macros

  • EQQYFILE EQQYLSOS EQQYLTOP
    

Fix information

  • Fixed component name

    TIV WRKLD SCHD

  • Fixed component ID

    5697WSZ01

Applicable component levels

  • R952 PSY UI97670

       UP24/07/27 P F407

  • RA12 PSY UI97671

       UP24/07/27 P F407

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":"BU029","label":"Software"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950"}]

Document Information

Modified date:
31 October 2024