OA61648: AFTER OA58718, INCOMPLETE OR MISSING PRINT RECORDS 21/06/17 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A printer issues a GETREC request for a set of records.  Then,
  the printer issues a GETREC request for the very first record
  (again).  A timing window exists in which the IO to despool data
  to satisfy the original GETREC request may still be inflight.
  This causes the POINT operation associated with the second
  GETREC to fail.  In this, we are not properly positioned back to
  the first record and the subsequent GET will fail to read those
  records.  This results in missing print data.
  
  ANALYSIS:
  When the POINT was made for the second GETREC request, it is
  possible the RPL passed in was still marked as active
  RPLACTIV=FF.  This causes the POINT to fail.  Then the GET
  obtains the next records from the current location, without
  having repositioned to the first record.
  
  KNOWN IMPACT:
  Missing print records
  
  VERIFICATION STEPS:
  1) OA58718 / UJ03249 is installed
  2) Printer issues a GETREC requesting the first record and a
  GETREC request for additional sequential records
  3) Then printer issues a GETREC requesting the first record
  again
  4) Missing print output
  
  PE INFORMATION:
  USERS AFFECTED:
  All users of HJE77C0 with OA58718 applied that do FSS printing:
    FMID      PTF
    ----      ---
    HJE77C0   UJ03249
  
  USER IMPACT:
  APAR OA58718 introduced the new function of spool encryption as
  it describes, but introduced a new problem in which print
  records may be missing.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of HJE77C0 with OA58718                            *
  * applied and all users of HJE77D0.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * An FSS GETREC specific request may be                        *
  * treated as a normal GETREC due to a                          *
  * timing error.                                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Normal processing when an FSS application does a GETREC
  specific involves re-orienting the data set to the record
  requested (a POINT) followed by GETs of the records
  requested.  In the error case, the POINT fails due to a
  timing problem but the error return code is not detected.
  This results in the GETREC specific acting as a normal
  GETREC next.
  

Problem conclusion

• TYPE/RESTART (WARM) IPL/REQUIRED (YES) CLPA (YES)
  
  CLPA is needed only if HASCxxxx modules currently reside in
  the pageable link pack area (PLPA).
  
  A GETREC specific interrupts the normal read ahead that FSS
  processing does.  JES2 FSS processing needs to complete any
  pending requests for read ahead before repositioning.  This
  was not done.  Code was added to complete the pending
  requests before starting the read process at the specific
  record requested.
  
  APAR OA61648 prereq's (and sup's) for FMID HJE77C0:
  Pre's: CA58718 CA60486 CA60972
  
  APAR OA61648 prereq's (and sup's) for FMID HJE77D0:
  Pre's: DA60972
  

Temporary fix

Comments

APAR Information

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

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

  UJ06010 UJ06011

Modules/Macros

• HASPFSSM HASCPHAM HASCHAM
  

Fix information

• Fixed component name

  JES2

• Fixed component ID

  5752SC1BH

Applicable component levels

• R7C0 PSY UJ06010

     UP21/07/21 P F107 {

• R7D0 PSY UJ06011

     UP21/07/21 P F107 {

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.