IBM Support

PK02408: ABENDU3565 AND MSGFABA3565E OCCURS WHEN "//UOWCTL DD DUMMY" JCL STATEMENT IS SPECIFIED UNDER THE FABADA3 STEP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • When JCL statement //UOWCTL DD DUMMY is specified under the
    FABADA5 step, FABADA5 looks for a HISTORY2 DD (which is not
    coded) causing an ABENDU3565 and error message FABA3565E.
    Currently FABADA5 doesn't process a HISTORY2 DD if a UOWCTL DD
    statement is not provided.  But in this case when the statement
    is provided with a DUMMY DD, the abends occur.
    
    This is a forward fit of FPB V12 APAR PK02008.
    

Local fix

  • Remove the UOWCTL DD statement to alleviate the abend and
    allow processing to complete.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All FP Basic Tools Version 2 Release 1       *
    *                 users of DEDB Pointer Checker.               *
    *                 (FMID: H31A210)                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Forward Fit of APAR PK02008.            *
    *                      When JCL statement //UOWCTL DD DUMMY    *
    *                      is specified and HISTORY2 DD is not     *
    *                      specified, FABADA5 tries to process     *
    *                      a HISTORY2 DD and causes the error      *
    *                      message FABA3565E and ABENDU3565.       *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    When JCL statement //UOWCTL DD DUMMY is specified and HISTORY2
    DD is not provided, FABADA5 tries to process a HISTORY2 DD and
    causes the error message FABA3565E and ABENDU3565.
    Currently FABADA5 doesn't process a HISTORY2 DD if a UOWCTL DD
    statement is not provided.  But in this case when the statement
    is provided with a DUMMY, the abend occurs.
    

Problem conclusion

Temporary fix

Comments

  • FABADA5 is enhanced not to abend with U3565 when
    //UOWCTL DD DUMMY is specified and HISTORY2 DD is not provided.
    
    The macro DA5INIT0 has been modified that FABADA5 doesn't try
    to process a HISTORY2 DD in order to avoid the error message
    FABA3565E and ABENDU3565, when a UOWCTL DD is provided with a
    DUMMY and HISTORY2 DD is not provided.
    
    ========================
    = DOCUMENTATION CHANGE =
    ========================
    IMS High Performance Fast Path Utilities for z/OS
    User's Guide Volume 2: Fast Path Basic Tools Version 2 Release 1
    (SC18-9238-00)
    
    Part 2. DEDB Pointer Checker utility
     Chapter 3. Using DEDB Pointer Checker utility
      FABADA5 JCL
       UOWCTL DD
    
     UOWCTL DD statement should be changed as follows;
    
        This statement specifies the range of UOW of HISTORY2 file
        record. This data set can reside on a direct-access device,
        or it can be routed through the input stream. This DD
    |   statement is optional, but if it is specified, the HISTORY2
    |   DD statement is required. The HISTORY2 DD statement can
    |   be omitted when this DD statement is not specified, or
        specified as:
    
    |   //UOWCTL DD DUMMY
    
    
    Part 2. DEDB Pointer Checker utility
     Chapter 3. Using DEDB Pointer Checker utility
      FABADA5 JCL
       HISTORY2 DD
    
     HISTORY2 DD statement should be changed as follows;
    
    |  This statement defines the output HISTORY2 file data set.
       This data set can reside on either a direct-access device or
       a tape. This DD statement is optional.
    |  If UOWCTL DD is specified and it is not dummy, the HISTORY2
       DD statement is required. If only the UOWCTL DD is specified,
       and the HISTORY2 DD statement is not specified, FABADA5 ends
       with FABA3565E message and an abend code of 3565. When you
    |  use this feature, the HISTORY2 file should be preallocated
       with the following attributes:
    
           DSORG = PS
           RECFM = FB
           LRECL = 200
           BLKSIZE = user-specified
    
         The DD statement in the JOB stream should be specified as:
    
           //HISTORY2 DD DSN=TSS.DA.HISTORY2,
           // DISP=(MOD,KEEP,KEEP)
    
         The following syntax is also valid:
    
    |      //HISTORY2 DD DUMMY
    
    Part 2. DEDB Pointer Checker utility
     Chapter 3. Using DEDB Pointer Checker utility
      FABADA5 UOWCTL data set
       Format
    
       The following sentence should be added to the end of Format
       statement.
    
       If the UOWCTL data set is empty, all UOWs of the area are
       regarded as the target UOW range.
    

APAR Information

  • APAR number

    PK02408

  • Reported component name

    IMS HP FP UTILI

  • Reported component ID

    5655K9400

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-03-11

  • Closed date

    2005-03-14

  • Last modified date

    2005-04-01

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

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

    UK01445

Modules/Macros

  •    DA5INIT0 DA5MAIN0 FABADA5
    

Publications Referenced
SC18923800    

Fix information

  • Fixed component name

    IMS HP FP UTILI

  • Fixed component ID

    5655K9400

Applicable component levels

  • R210 PSY UK01445

       UP05/03/15 P F503

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89D","label":"IMS HP Fast Path Utilities"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
14 December 2020