IBM Support

PM38381: JCL GENERATED BY JCYMIG00 IS NOT CORRECT WHEN SYMBOL IS USED FOR DISP VALUE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PMR 56131,999,000
    
    JCYMIG00 symbolic DISP=&DISP and PDS/GDG issue
    
    ================================================================
    Date reported: 04/28/2011
    
    Severity: high
    
    Users Affected:
     New IMU users of JCYMIG00 utility
    
    Problem Description:
     1. JCL generated by JCYMIG00 is not correct when symbol is used
        for DISP value.
    
     2. Output PDS is being generated as a GDG.
    
    Problem Summation
     1. Utility does not provide symbolic replacement in the DISP=
        when determining the output file disposition.
    
     2. A flag from previous GDG was not reset, thus the PDS was
        wrongly generated as a GDG.
    
    Problem Conclusion:
     1. Utility was changed to replace symbolic variables before
        looking at DISP=&disp.
    
     2. The GDG flag was reset in FSYMIGS0 to force the correct
        handling of current file.
    
     Changed programs:
    
      FSYMIGS0
      FSYMIG00
    ================================================================
    
    ================================================================
    
    PMR 56149,999,000
    
    MNOTE when IF compares alpha fields of unequal length
    
    ===============================================================
    Date reported: 04/28/2011
    
    
    Severity: high
    
    
    Users Affected:
     All IMU users
    
    Problem Description:
     As per reference manual, the COBOL IF statement evaluates
     compare of alphanumeric fields by considering the length of
     both arguments, while EZT Plus uses the length of the first
     argument, causing a different
     outcome.
    
    Problem Summation
     As is now, it is difficult to locate such IF statements that
     could potentially cause a different outcome. The only way to
     tell is by a close inspection of the IF statements.
    
    Problem Conclusion:
     EASYT007 macro was changed to issue an MNOTE when alpha fields
     being compared are not of equal length.  This should help
     programmers to track the potential cause of differences on
     output files.
    
     Changed macros:
      EASYT007
    
     Impact on existing users
      Users should be aware of MNOTEs that will be issued if bad IF
      statements are encountered. The generated code is unchanged.
    ================================================================
    
    ===============================================================
    PMR 56151,999,000
    
    Purge JCL generated by FSYMIG20
    ==============================================================
    Date reported: 04/28/2011
    
    
    
    Severity: low
    
    Users Affected:
     All IMU users of the Automated Parallel Test utility
    
    Problem Description:
     The CLASS= on the JOB statement punched for purge JCL has to be
     changed manually.
    
    Problem Summation
     FSYMIG20 generates purge JCL with a hard coded CLASS=A.
    
    Problem Conclusion:
     An additional parameter was added to the PARM= on the EXEC of
     FSYMIG20 to provide one character CLASS to be used on the JOB
     card of Purge JCL.
    
     Note that, currently, FSYMIG20 accepts 8 parameters on the
     PARM. This additional parameter is optional. If not provided,
     FSYMIG20 will default to CLASS=A.
    
     Changed programs
      FSYMIG20
    
     Changed control file
      #FJICNTL
      #FJECNTL
    
     Impact on existing users
      If you are using the Automated Parallel Test utility, change
      the last value on the PARM= to whatever job class you need.
    
      Example:
    
    //         PARM=(PURGE,NOLET,NOEXIT,BYTE,EXPCC,64, X
    //         '&JOBACCT',                             X
    //         '&JOBUNAM',A)
    
    
    
     Caution: If you are using the Automated Parallel Test, make
              sure that you save your existing #FJICNTL and
              #FJECNTL if they are located in the SFSYEZTS library.
    ================================================================
    
    
    PMR 56137,999,000
    
    Files are not being reset/initialized the EZT Plus way when
    RESET is coded.
    ============================================================
    Date reported: 04/28/2011
    
    
    Severity: high
    
    
    Users Affected:
     All IMU users
    
    
    Problem Description:
     Files are not being reset/initialized the EZT Plus way when
     RESET is coded.
    
    
    Problem Summation
     EASYT007 macro never generates the required INITIALIZE
     statement for field to be RESET.
    
     The problem occurs for Synchronized file and SQL JOBS.
    
    
    Problem Conclusion:
     EASYT007 macro was changed to generate INITIALIZED as required.
    
    
     Changed macros:
      EASYT007
    
    
     Impact on existing users
      This fix should not impact the existing programs as such
      programs have been accepted free of errors. RESET fields,
      if any, would have caused processing issues that would have
      been discovered up front and corrected by programmers
      initially by clearing the relevant fields after the JOB
      statement.
    
      IF the existing programs contain RESET fields and potential
      problem was not realized, this change will correct the issue
      the next time program is compiled.
    ================================================================
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMU V3.2 users of JCYMIG00 Utility.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. JCL generated by JCYMIG00 is not     *
    *                         correct when symbol is used for      *
    *                         for DISP value.                      *
    *                                                              *
    *                      2. Output PDS is being generated as     *
    *                         a GDG.                               *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    *                                                              *
    *                 Users should be aware of MNOTEs that         *
    *                 will be issued if bad IF statements are      *
    *                 encountered. The generated code is           *
    *                 unchanged.                                   *
    ****************************************************************
    EASYT007 macro never generates the required INITIALIZE
    statement for field to be RESET.
    
    The problem occurs for Synchronized file and SQL JOBS.
    

Problem conclusion

  • EASYT007 macro was changed to generate INITIALIZED as required.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM38381

  • Reported component name

    MIGRATION UTILI

  • Reported component ID

    5697N4400

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-04

  • Closed date

    2011-06-15

  • Last modified date

    2011-07-05

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

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

    UK68805

Modules/Macros

  •    FSY#CNTL FSY#FCNT FSYMIGS0 FSYMIG00 FSYMIG20
    

Fix information

  • Fixed component name

    MIGRATION UTILI

  • Fixed component ID

    5697N4400

Applicable component levels

  • R320 PSY UK68805

       UP11/06/18 P F106

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSY4B9","label":"IBM Migration Utility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 October 2020