PH64152: CONVERT TO EXTERNAL FORMAT OR COMPARE REPORT IN EXTERNAL FORMAT INCORRECT ALLOCATIONS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1. Customer is performing LOAD or CONVERT to EXTERNAL format
  processing in BATCH.
  When the order of tables in the used Table Map (TM) does not
  match the order of the DD statements for the EXTERNAL converted
  files, the converted data may end up in the incorrect data set.
  
  A TM with tables' order, which does not match the tables'
  processing order, may be generated by Optim when using EXTRACT,
  or ARCHIVE, files located on TAPE. Or the generated JCL may have
  been manually modified by the user.
  
  2. Customer is performing COMPARE processing using the option to
  produce a COMPARE REPORT in EXTERNAL format in BATCH.
  When the order of the tables in the used TM does not match the
  order of the DD statements for the EXTERNAL REPORT files, or
  some of the reports use dedicated data sets and some use the
  default report data set, then the report output may be directed
  to the incorrect data sets.
  
  3. When processing an EXTRACT, or ARCHIVE, data sets located on
  TAPE, and using a TM, Optim may create one where the order of
  tables is different (alphabetical) than when such data sets were
  located on DISK (matching the original Access Definition).
  While the actual processing order of tables is based on
  relational dependencies, and irrespective of the order of
  tables in the TM, it may affect the produced BATCH JCL,
  especially with LOAD processing. This may be confusing for the
  users.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1. Optim users working with EXTRACT, or      *
  *                 ARCHIVE, files located on TAPE.              *
  *                 2. Optim users performing CONVERT, or        *
  *                 COMPARE, with data sets in EXTERNAL format.  *
  ****************************************************************
  1. Optim is incorrectly matching the tables to be processed with
  the respective definitions of the EXTERNAL data sets to be used.
  2. The tables in the generated TMs are being ordered
  alphabetically, instead of retaining their original order.
  

Problem conclusion

• Optim processing will be corrected and enhanced as follows:
  
  The Optim LOAD processing will now offer a new option on the
  "Specify LOAD Parameters and Execute". The new option of
  "Generate Disk/Tape compatible JCL" will only affect processing
  of the input EXTRACT, or ARCHIVE, files located on TAPE.
  With the option set to N(o), default:
  The generated JCL will be compatible with JCL generated with
  Optim code in releases prior to 11.7 and prior to APAR PH64152.
  When the EXTRACT, or ARCHIVE, file resides on tape then the
  generated JCL may differ from the JCL generated when such data
  set resides on disk. The order of tables listed in the TM and
  the order of the load steps, as well as the order of the
  associated DD statements, may differ. With this default, the
  generated JCL may be sensitive to type of media on which the
  input EXTRACT, or ARCHIVE, file resides.
  
  With the option set to Y(es):
  The generated JCL will be identical irrespective of the media on
  which the input EXTRACT, or ARCHIVE, file resides. Note that
  the generated JCL will contain the DISKTAPE_COMPAT YES control
  keyword reflecting the option's value. Such JCL may not be
  executed with Optim code at the PTF level prior to APAR PH64152.
  

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

• FOP2RRSQ FOP9APIM FOPCFPMN FOPHSTM  FOPK00   FOPMADDE FOPMAIN
  FOPMAMAI FOPMCMAI FOPMCOLP FOPMDBMN FOPMDPRC FOPMDXTR FOPMECMN
  FOPMEMAI FOPMMCMR FOPMMJBS FOPMMUNU FOPMMUTL FOPMUXIM FOPOMN
  FOPRS10  FOPRS9   FOPT02T  FOPT29K  FOPTLPRA FOPUMCBT FOPZFMMN
  FOPZSUB
  

Fix information

• Fixed component name

  OPTIM MOVE FOR

• Fixed component ID

  5655V0700

Applicable component levels

• RB70 PSY UI99443

     UP24/12/17 P F412

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.