PM44756: FIX DBRMLIB DSN TO CONTAIN MEMBER NAME

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The APAR is for these PMRs:
  ================================================================
  PMR 65152,999,000: Fix DBRMLIB DSN to contain member name
  
  Date reported: 07/01/2011
  
  Severity: low
  
  Users Affected:
   All IMU users of MU V3.2
  
  Problem Description:
   The BIND step in JCMUSQLP and JCMUSQLJ is failing.
  
  Problem Summation
   The data set name on DBRMLIB JCL statement does not include the
   translated program name.
  
  Problem Conclusion:
   The program/&MEMBER name was added to the DSN.
  
   Changed JCL/JOBS in SFSYJCLS
  
    JCMUSQLP - Existing JCL
    JCMUSQLJ - Existing JCL
  
  Note:
  This change does not impact the generated code.
  
  ================================================================
  PMR 65154,999,000: Page title field value is not correct
  
  Date reported: 07/01/2011
  
  Severity: High
  
  Users Affected:
   All IMU users of MU V3.2
  
  Problem Description:
   Field value shown on the Report Title is not correct.
  
  Problem Summation:
   Fields printed on report titles are printed from the values
   saved in the control break routines. If there are no control
   breaks, values are saved the 1st time thru the report logic.
   Therefore, the same first value is printed on all subsequent
   page titles.
  
  Problem Conclusion:
   The GENERATQ macro was changed to save fields, printed on
   report titles, in the detail logic before the detail lines
   are built. This makes sure that the most current value is
   used when multiple pages exist.
  
   Changed SFSYFJCC macros:
  
    GENERATQ - Existing macro
  
  Note:
  Programs that had Title issues must be re-translated (compiled)
  in order for this change to take effect.
  
  ==============================================================
  PMR 65159,999,000: Support for Easytrieve Plus Version 11.00
  
  Date reported: 07/24/2011
  
  Severity: High
  
  Users Affected:
   All IMU users of MU V3.2
  
  Problem Description:
  
   Easytrieve Plus Version 11.00 provides an option to use field
   values from the record before the record that caused the
   break.  This properly reflects the values associated with
   the control break. The older EZT Plus versions used values
   from the record that caused the break.
  
  Problem Summation
   IMU is compliant with the older version of EZT Plus. A special
   option is needed to generate code for EZT Plus 11.00.
  
  Problem Conclusion:
   EZVERS=STD/11.00  option was added to EASYTRAN/EZPARAMS table.
  
   The meaning is as follows:
  
    EZVERS=(STD)  - Generates code that uses values from the
    record that caused the break.
    EZVERS=(11.00)  - Generates code that uses values  from the
    record before the record that caused the break.
  
    The default is EZVERS=STD
  
    Changed macros in SFSYFJCC:
     EASYT007 - Existing macro
     EASYTRAN - Existing macro
     EASYOVRD - Existing macro
  
  Note: Users of EZT PLus version 11.00 or later must add
  EZVERS=(11.00) option to EZPARAMS table.
  ================================================================
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMU V3.2 users.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: A. The BIND step in JCMUSQLP and        *
  *                         JCMUSQLJ is failing.                 *
  *                                                              *
  *                      B. Field value shown on the Report      *
  *                         Title is not correct.                *
  *                                                              *
  *                      C. Easytrieve Plus Version 11.00        *
  *                         provides an option to use field      *
  *                         values from the record before the    *
  *                         record that caused the break. This   *
  *                         properly reflects the values         *
  *                         associated with the control break.   *
  *                         The older EZT Plus versions used     *
  *                         values from the record that caused   *
  *                         the break.                           *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  A. The data set name on DBRMLIB JCL statement does not include
     the translated program name.
  
  B. Fields printed on report titles are printed from the values
     saved in the control break routines. If there are no control
     breaks, values are saved the 1st time thru the report logic.
     Therefore, the same first value is printed on all subsequent
     page titles.
  
  C. IMU is compliant with the older version of EZT Plus. A
     special option is needed to generate code for EZT Plus 11.00.
  

Problem conclusion

• A. The program/&MEMBER name was added to the DSN.
  
  B. The GENERATQ macro was changed to save fields, printed on
     report titles, in the detail logic before the detail lines
     are built. This makes sure that the most current value is
     used when multiple pages exist.
  
  C. EZVERS=STD/11.00  option was added to EASYTRAN/EZPARAMS
     table.
  

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

•    FSYGRATQ FSYJCQLJ FSYJCQLP
  

Fix information

• Fixed component name

  MIGRATION UTILI

• Fixed component ID

  5697N4400

Applicable component levels

• R320 PSY UK70908

     UP11/08/19 P F108

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.