A fix is available
APAR status
Closed as program error.
Error description
DB2's RUNLIB is currently allocated ( internally / dynamically ) as part of a group of DB2 load libraries needed during the execution of a DB2 Log Analysis job. The RUNLIB could be specified during initial installation, or as part of menu option 'Setup' at any time thereafter for any given DB2 subsystem. But the grouping of RUNLIB as a DB2 load library does not include it in any generated JCL DD STEPLIB allocation list, where it may be needed. Additionally, RUNLIB, if not authorized (which it must be if it is actually needed during a run, for example, if edit or field procedures are present), will prevent any libraries within the allocation list from being APF authorized. . This change will remove RUNLIB from the group of allocated DB2 load libraries, so it will not affect APF authorization of the dynamically allocated DB2 load library list. . Note that if edit or field procedures are present in any tracked tables, RUNLIB must be specified as a non-DB2 loadlib during control file install or 'Setup', and it must be APF authorized. Also note, that this change affects only the process of installation or 'Setup', if RUNLIB is currently in your DB2 load library list in the control file, it may be removed (if not needed for edit or field procedures), or added to your non-DB2 Load library list (if needed for edit or field procedures), but in either case, it MUST be APF authorized.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of ALA 350 * **************************************************************** * PROBLEM DESCRIPTION: *********PI79636*********************** * * While processing distributed type log * * records * * (participant/coordinator), a S0C4 * * abend may occur if the log * * record spans two logs. The abend * * occurs in load module ALASUBG, * * csect ALAUDDF because the spanned * * components of distributed * * type log records are not being handled * * properly. * * *************************************** * * *********PI79335*********************** * * DB2's RUNLIB is currently allocated * * ( internally / dynamically ) * * as part of a group of DB2 load librarie * * needed during the * * execution of a DB2 Log Analysis job. * * The RUNLIB could be specified during * * initial installation, or as * * part of menu option 'Setup' at any time * * thereafter for any given * * DB2 subsystem. But the grouping of * * RUNLIB as a DB2 load library * * does not include it in any generated * * JCL DD STEPLIB allocation * * list, where it may be needed. * * Additionally, RUNLIB, if not * * authorized (which it must be if it is * * actually needed during a * * run, for example, if edit or field * * procedures are present), will * * prevent any libraries within the * * allocation list from being APF * * authorized. * * . * * This change will remove RUNLIB from the * * group of allocated DB2 * * load libraries, so it will not affect * * APF authorization of the * * dynamically allocated DB2 load library * * list. * * . * * Note that if edit or field procedures * * are present in any tracked * * tables, RUNLIB must be specified as a * * non-DB2 loadlib during * * control file install or 'Setup', and it * * must be APF authorized. * * Also note, that this change affects * * only the process of * * installation or 'Setup', if RUNLIB is * * currently in your DB2 load * * library list in the control file, it * * may be removed (if not * * needed for edit or field procedures), * * or added to your non-DB2 * * Load library list (if needed for edit * * or field procedures), but * * in either case, it MUST be APF * * authorized. * * *************************************** * * * * * * * **************************************************************** * RECOMMENDATION: APPLY the PTF * ****************************************************************
Problem conclusion
APPLY the PTF
Temporary fix
Comments
APAR Information
APAR number
PI79335
Reported component name
DB2 LOG ANALYSI
Reported component ID
5655E6601
Reported release
350
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-04
Closed date
2017-05-01
Last modified date
2017-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI46866
Modules/Macros
ALAGEN1 ALAHLP1 ALALF1 ALALOAD1 ALAMSP ALAREC ALASUBG ALAUDDF H237350J
Fix information
Fixed component name
DB2 LOG ANALYSI
Fixed component ID
5655E6601
Applicable component levels
R350 PSY UI46866
UP17/05/12 P F705
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":"3.5.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 June 2017