PM51927: OPTION TO USE DISPLAY LINES FOR PAGE LIMIT IN REPORT EXITS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Per PMRs
  - 75946,999,000
  
  - 75950,999,000
  
  ================================================================
  PMR75946,999,000 -  Option to use DISPLAY lines for page limit
                      in report exits
  
  Date reported: 11/01/2011
  
  Pre-req: APAR PM50166
  
  
  Severity: medium
  
  Users Affected:
   All IMU users
  
  Problem Description:
   IMU always uses value coded for PAGESIZE on report statement,
   or the PAGESIZE default in EASYDTAB. Thus, the page overflow
   does not match that of EZT Plus.
  Also, the following problems are being addressed with this
  APAR:
  - blank lines cannot be seen when viewing reports on INFOPAC.
  - The MOVE from variable length field and ASSIGN from variable
    length field is moving data from position 3 instead of
    position 1.
  
  Problem Summation
   IMU's logic has been working like this since day 1.
  
  Problem Conclusion:
   RXITOVF=NATIVE/EASYT was added to correct the overflow the
   test.
  
   RXITOVF=NATIVE
      Use PAGE= value in the GENERATQ macro for page overflow in
      report exits. This limit
      is enforced when REXOVCK macro is in use (the IMU way).
  
   RXITOVF=EASYT
      Use DISPLAY= value in the  GENERATQ macro for page overflow
      in report exits.  When this optin is in use, REXOVCK is
      automatically turned on, therefore the %REXOVCK ON is not
      required.
  
  The following macros in SFSYFJCC have been changed:
  
   EASYTRAN - existing macro
   EASYOVRD - existing macro
   EASYT007 - existing macro
   GENERATQ - existing macro
  
  Note: this issue was reported by the Swedbank
  ================================================================
  
  
  ================================================================
  PMR 75950,999,000 - 1st detail line spacing is not correct when
                      BEFORE-LINE exit is used
  
  Date reported: 11/01/2011
  
  Pre-req: APAR PM50166
  
  
  Severity: Low
  
  Users Affected:
   All IMU users
  
  Problem Description:
  
   IMU is not honoring double space before 1st detail on each page
   when BEFORE-LINE exit is used.
  
  Problem Summation
   IMU's logic has been working like this since day 1.
  
  Problem Conclusion:
  
   LXITDTL=NATIVE/EASYT option to correct print CC on the 1st
   detail line when BEFORE-LINE exit is used.
  
   LXITDTL=NATIVE
     DO not double space when BEFORE-LINE exit is used (the IMU's
     way)
  
   LXITDTL=EASYT
     Double space when BEFORE-LINE exit is used (the EZT Plus
     way).
  
  The following macros in SFSYFJCC have been changed:
  
   EASYTRAN - existing macro
   EASYOVRD - existing macro
   EASYT007 - existing macro
   GENERATQ - existing macro
  
  Note: this issue was reported by the Swedbank
  ================================================================
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMU v3.2 users.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: IMU always uses value coded for         *
  *                      PAGESIZE on report statement, or the    *
  *                      PAGESIZE default in EASYDTAB. Thus,     *
  *                      the page overflow does not match that   *
  *                      of EZT Plus.                            *
  *                                                              *
  *                      Also, the following problems are being  *
  *                      addressed with this fix:                *
  *                                                              *
  *                      - blank lines cannot be seen when       *
  *                        viewing reports on INFOPAC.           *
  *                                                              *
  *                      - The MOVE from variable length field   *
  *                        and ASSIGN from variable length       *
  *                        field is moving data from position    *
  *                        3 instead of position 1.              *
  ****************************************************************
  * RECOMMENDATION: Apply PTF.                                   *
  ****************************************************************
  

Problem conclusion

• RXITOVF=NATIVE/EASYT was added to correct the overflow the
  test.
  
  RXITOVF=NATIVE
     Use PAGE= value in the GENERATQ macro for page overflow in
     report exits. This limit
     is enforced when REXOVCK macro is in use (the IMU way).
  
  RXITOVF=EASYT
     Use DISPLAY= value in the GENERATQ macro for page overflow
     in report exits.  When this optin is in use, REXOVCK is
     automatically turned on, therefore the %REXOVCK ON is not
     required.
  

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:

Modules/Macros

•    FSYESORD FSYETRAN FSYET007 FSYGRATQ
  

Fix information

• Fixed component name

  MIGRATION UTILI

• Fixed component ID

  5697N4400

Applicable component levels

• R320 PSY UK74557

     UP11/12/09 I 1000

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.