PM38384: JCL generated by JCYMIG00 is does not contain IDCAMS for copying VSAM files to a new dataset when DISP=OLD is specified.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR is for these following Internal PMRs:
  ==============================================================
  PMR 58199,999,000 - JCYMIG00 fix for cloning VSAM files for
                      DISP=OLD
  
  Date requested: 05/10/2011
  
  Severity: high
  
  Users Affected:
   New IMU users of JCYMIG00 utility who update VSAM files
  
  Problem Description:
   JCL generated by JCYMIG00 is does not contain IDCAMS for
   copying VSAM files to a new dataset when DISP=OLD is specified.
  
  Problem Summation
   There is a bug in FSYMIG0 program (called by FSYMIG00). The
   DISP=OLD is not recognized as a valid disposition for VSAM
   files accessed in I-O mode.
  
  Problem Conclusion:
   A change was made to FSYMIGS0 recognize DISP=OLD as a valid
   disposition for VSAM files in I-O mode.
  
   Changed programs:
    FSYMIGS0  - Logic was added to generate UNIT=&TAPE as per
    //TAPE-UNIT option.
  ================================================================
  ================================================================
  PMR 58203,999,000 - JCYMIG00 support for output tape files in
                      EZT Plus step
  
  Date requested: 05/10/2011
  
  Severity: high
  
  Users Affected:
   New IMU users of JCYMIG00 utility who create  tape files
  
  Problem Description:
   JCL generated by JCYMIG00 is directing output tape files in
   EZT Plus step to disk.
  
  Problem Summation
   Utility does not provide means of directing the output tape
   files to tape in EZT Plus step.
  
  Problem Conclusion:
   An option was added to #FJICNTL table to identify UNIT= coded
   on DD statements. All output files that match UNIT=&unit
   parameter provided in #FJICNTL via ??//TAPE-UNIT? are
   generated with such unit name, thus directing the file to tape.
  
  Changed programs:
   FSYMIGS0  - Logic was added to generate UNIT=&TAPE as per
               //TAPE-UNIT option.
  
   FSYMIG00 - Logic was added to capture //TAPE-UNIT option of
               #FJICNTL
  
  Changed control files:
   #FJICNTL  - //TAPE-UNIT was added.  See changes in the
               #FJICNTL.
  ================================================================
  
  ================================================================
  PMR 58206,999,000  - JCYMIG00 support for comparing output tape
                       files
  
  Date requested: 05/10/2011
  
  Severity: high
  
  Users Affected:
   New IMU users of JCYMIG00 utility who use the Automated
   Parallel Test utility with tape files
  
  Problem Description:
   The parallel test job is failing to allocate tape files that
   were created by the IMU step. This failure is occurring in
   the COMPARE step.
  
  Problem Summation
   IMU?s Dynamic Allocator module (FSYSVC99) cannot allocate tape
   files due to system restrictions.
  
  Problem Conclusion:
   Solution is to defer compare to a stand-alone compare. To do
   so, the FJCOMP0 file in the COMPARE step had to be copied to a
   permanent file for later use. This is accomplished as follows:
  
   1. New control files,  #FJICNT2 for Easytrieve Plus, and
      #FJECNT2 for EZT Classic,  were created to copy FJCOMP0 to a
      permanent file.  These files were created from #FJICNTL and
      #FJECNTL files. In these new control files, the COMPARE step
      was completely replaced by IEBGENER that copies the
      temporary FJCOMP0 to a permanent FJCOMP0 file.
   2.  An new stand-alone (JCYMIG21) job was created that reads
       in the FJCOMP0 data set file and generates the required JCL
       for stand-alone compare for all files in the FJCOMP0 data
       set.
       Note that JCYMIG21 generates the stand-alone compare and
       the purge JCL.  See comments in JCYMIG21 for details.
  
  Changed programs:
   FSYMIG21  - New program for generating compare and purge JCL.
               Used by JCYMIG21.
   FSYMIG20  - Program was changed to recognize stand-alone
               compare for files that were generated by the
               parallel test.
   FSYCNV20  - Program was changed to recognize stand-alone
               compare for files that were generated by the
               parallel test.
  
   FSYGTDCB - Support for Long Block Interface (LBI) was added
  
  New JCL:
   JCYMIG21  - generates the stand-alone compare and the purge
               JCL. See comments in JCYMIG21 for details.
  
  New control files:
   #FJICNT2  - Contains the new COMPARE step that saves the
               FJCOMP0 to a permanent file.
   #FJECNT2  - Contains the new COMPARE step that saves the
               FJCOMP0 to a permanent file.
  
  Special instructions for deferring the compare step:
   1. Make the necessary changes to #FJICNT2 and #FJECNT2 to
      reflect your own needs.
   2. Point FJICNTL=  in JCYMIG00 to use #FJICNT2 or #FJECNT2
      respectively
   3. Update JCYMIG21 JCL to use: (there are three (4) SET
      statements in the JCL.
      a)  FJCOMP0 saved by the COMPARE step of #FJICNT2 or
          #FJECNT2
      b)  FJICNTL that was used by JCYMIG00
      c)  The DSN for FJPURGE where purge JCL will be placed.
      d)  Change CLASS=A to whatever job class you wish on the
          generated compare and purge JCL.
      e)  Change PARM= options on the EXEC PGM=FSYMIG21 to suit
          your needs.
          Note that the 1st parameter cannot be changed.
   4. JCL for the parallel test is punched to FJCMP20 file.  As
      distributed, this file is punched into internal reader,
      therefore it is automatically run after the EOJ of JCYMIG21,
      of course, if the CLASS= is correct.
  ================================================================
  ================================================================
  PMR 58211,999,000 -  Add support for ALPHATEST=NATIVE/EASYT
  
  Date reported: 05/10/2011
  
  Severity: high
  
  Users Affected:
   All IMU users
  
  Problem Description:
   The COBOL ALPHABETIC test is not compatible with Easytrieve
   Plus.
  
  Problem Summation
   The default COBOL test is for upper and lower case, while
   Easytrieve Plus tests for upper case only.
  
  Problem Conclusion:
   ALPHATEST=NATIVE/EASYT  EZPARAMS/EASYTRAN  option  was added.
  
   Where:
    EASYT   Accepts ALPHABETIC as the only valid test. It is
    converted to  ALPHABETIC-UPPER for Easytrieve Plus
    compatibility.
  
  NATIVE   Accepts the following:
    ALPHABETIC
    ALPHABETIC-LOWER
    ALPHABETIC-UPPER
  
   The default is ALPHATEST=NATIVE.
  
   Changed macros:
    EASYTRAN
    EASYOVRD
    EASYT007
    EASYTCBW
  
   Impact on existing users
  
   The default option is ALPHATEST=NATIVE.
  
  When ALPHATEST=NATIVE is specified, the ALPHABETIC-LOWER and the
  ALPHABETIC-UPPER are recognized as valid tests. Prior to this
  change, ALPHABETIC-LOWER was translated by IMU as a valid field
  name, therefore, programs that contain ALPHABETIC-LOWER for a
  field name, might fail. The chance for this error is remote,
  however, be alert.
  
  This new feature provides for additional IF statement
  capabilities not available in Easytrieve Plus.
  ================================================================
  ================================================================
  PMR 58213,999,000 - Syntax issues with Easytrieve CLASSIC
  
  Date reported: 05/10/2011
  
  Severity: high
  
  Users Affected:
   All IMU users of Easytrieve Classic.
  
  Problem Description:
   1.  NF, NO, OF are not recognized a constant when used in IF
       post relational operator  without parentheses.
  2.   Unpaired parentheses error message when interpreting
       comments.
   3.  ?EASYTRAN ? in ?* EASYTRAN: ? test is failing.
   4.  When line is not specified for LABELS, IMU flags it as an
       error.
   5.  SPnn is not recognized as a valid control character on
       PRINT statement.
  
  Problem Summation
   1.  Logic in IMU never accounted for bit operators to be coded
       without parentheses
   2.  A bug in parsing logic
   3.  An original typo bug
   4.  IMU Logic is expecting line number
   5.  SP1, SP2, SP3 are the only recognized control characters
  
  Problem Conclusion:
   1.  Logic was changed to recognized NF, NO and OF as constants
       when coded post relational operator.
   2.  The error was corrected
   3.  The error was corrected
   4.  A default of 6 was added to to resolve deficiency.
   5.  A logic was put in to recognize ?SPnn?  As a valid control
       when coded as the 1st argument on the PRINT statement.
  
  Changed macros:
   EZTRV001
  
  Impact on existing users
   There is no impact on existing users because these conditions
   were handled as errors.
  ================================================================
  ================================================================
  PMR 58214,999,000  - Parentheses not printing on field
  titles/headings
  
  Date reported: 05/10/2011
  
  Severity: high
  
  Users Affected:
   All IMU users
  
  Problem Description:
   When parentheses are in the headings, the field titles do not
   mach to those produced by Easytrieve Plus
  
  Problem Summation
   EASYT007 macro strips parentheses for parsing when field
   headings are more than 3 rows deep.
   In the process it strips parentheses without handling quotes
   strings.
  
  Problem Conclusion:
   The logic was corrected to get rid of parentheses correctly.
  ================================================================
  ================================================================
  PMR 58263,999,000  - FSYGPCB0 trace feature
  
  Date reported: 05/18/2011
  
  Severity: n/a
  
  Users Affected:
   All IMU users of MU V3.2 DLI/IMS feature
  
  Problem Description:
   A trace of PCBs is needed when a DBD is not located in the PCB
   list passed to FSYGPCB0 by DFSRRC00 DLI program.
  
  Problem Summation
   A trace is needed when "FSY003E - FSYGPCB0: DBD XXXXXXXX PCB
   SEQ XXX CANNOT BE RESOLVED" message is issued due to undefined
   DBD received from DFSRRC00 DLI/IMS program.
  
  Problem Conclusion:
   A trace to display PCBs received from DLI was implemented.
  ================================================================
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMU users of JCYMIG00 utility who update     *
  *                 VSAM files.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: JCL generated by JCYMIG00 is does not   *
  *                      contain IDCAMS for copying VSAM files   *
  *                      to a new dataset when DISP=OLD is       *
  *                      specified.                              *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  A change was made to FSYMIGS0 recognize DISP=OLD as a valid
  disposition for VSAM files in I-O mode.
  

Problem conclusion

• A change was made to FSYMIGS0 recognize DISP=OLD as a valid
  disposition for VSAM files in I-O mode.
  

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

•    FSY#CNTL FSY#ECT2 FSY#FCNT FSY#ICT2 FSYCNV20
  FSYESCBW FSYESORD FSYETRAN FSYET001 FSYET007 FSYGPCB0 FSYGTDCB
  FSYJCG00 FSYJCG21 FSYMIGS0 FSYMIG00 FSYMIG10 FSYMIG20 FSYMIG21
  

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.