PQ67957: ENHANCE PSSR TO VALIDATE SEGMENTS THAT ARE EDITED BY A SEGMENT/EDIT COMPRESSION EXIT ROUTINE WITH A PAD PARAMETER.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• A fifth parameter of 'PAD' has been added to the
  COMPRTN keyword of the SEGM macro by PQ34603 and PQ34604.
  PSSR newly supports the PAD parameter.
  If the fixed length segment is edited by a segment
  edit/compression exit routine and the PAD is defined,
  PSSR adjusts the maximum segment length to the pad value.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM IMS High Performance        *
  *                 Load for OS/390 Release 1 (FMID=H1IM110)     *
  *                 who use Physical Sequence Sort for Reload    *
  *                 (PSSR).                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: (1)Enhances PSSR to validate segments   *
  *                         that are edited by a Segment Edit    *
  *                         /Compression exit routine with a     *
  *                         PAD parameter.                       *
  *                      (2)When the fixed length segment is     *
  *                         edited by a Segment Edit/Compression *
  *                         exit and it's length is made         *
  *                         increased, PSSR could sort unload    *
  *                         records in incorrect order.          *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  (1)The fifth parameter PAD has been added to the COMPRTN keyword
     of the SEGM macro by PQ34603 of IMS/ESA V6 and PQ34604 of IMS
     V7. PSSR newly supports the PAD parameter.If the fixed length
     segment is edited by a Segment Edit/Compression exit routine
     and the PAD is defined, PSSR adjusts the maximum segment
     length to the pad value.
  (2)PSSR could sort unload records in incorrect order when all of
     the following conditions are satisfied:
     - The fixed length segment edited by the Segment Edit
       /Compression exit has the largest value of BYTES keyword in
       the DBD.
     - The length of segment increases during editing by the
       Segment Edit/Compression exit.
     - A user exit returns with return code 4 for the segment.
     Additionally, for HIDAM, PSSR could incorrectly convert the
     *CS header.
     The reason of this problem is an internal work area is broken
     in increasing the segment length by the Segment Edit
     /Compression exit.
  

Problem conclusion

Temporary fix

Comments

• (1)The modules FABSRT15, FABSPE15 and FABSCMPR have been
     modified to validate segments edited by a Segment Edit/
     Compression exit routine with a PAD parameter.
  (2)The modules FABSRT15 and FABSPE15 have been modified not to
     override the work area.
  ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS High Performance Load User's Guide (SC27093800) should be
  changed as follows:
  ------------------------------------------------------------
  Part 3. Physical Sequence Sort for Reload.
  3.2  Chapter 8.  Operating Instructions
  3.2.5  Output
  3.2.5.11 PR8 Data Set
  
  3.2.5.11.6  Record Sizes Report
  
    This report (see Figure 28) contains a printed list of the
    sizes of all database records.
  | If the PAD operand of COMPRTN= parameter in DBDGEN SEGM
  | statement is defined, and the length of the fixed length
  | segment is shorten than the PAD value by the Segment Edit
  | /Compression exit, the PAD value is used to calculate the size
  | of the database records instead of the segment length.
  | This report also contains the total number of root segments
    and the total number of dependent segments that were processed
    Ten record sizes are printed on each line.
    Therefore,the number of printed lines on this report is about
    one tenth of the number of root segments in your database.
    If your database is large, this report will also be fairly
    large. You may want o suppress this report by using a blank in
    column 65 of your control statement (see "CTL Data Set (Used
    by FABSPSSR)" in topic 3.2.4.4 or "CTL Data Set (Used by
    FABSPSSI)" in topic 3.2.4.7).
  
  3.2.5.11.8 Record Size Distribution Report
  
    This report (see Figure 30) contains a printed histogram of
    the sizes of all database records.
  | If the PAD operand of COMPRTN= parameter in DBDGEN SEGM
  | statement is defined, and the length of the fixed length
  | segment is shorten than the PAD value by the Segment Edit
  | /Compression exit, the PAD value is used to calculate the size
  | of the database records instead of the segment length.
    You can specify the width of the histogram classes in column
    58 of your control statement (see "CTL Data Set (Used by
    FABSPSSR)" in topic 3.2.4.4 or "CTL Data Set (Used by
    FABSPSSI)" in topic 3.2.4.7). For databases with a large
    number of database records, this report is much more useful
    than the Record Sizes Report.
  

APAR Information

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

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

  UQ72199

Modules/Macros

•    FABSCMPR FABSPE15 FABSRT15
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R110 PSY UQ72199

     UP02/12/04 P F212

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.