Data sets cataloged with an esoteric device group name

When using HCD, data sets that were previously cataloged with an esoteric device group name (for example, SYSDA) by use of the DEFINE NONVSAM or IMPORT CONNECT command of the Integrated Catalog Facility, can cause unpredictable results if such a data set is accessed through the catalog. The reason is that the catalog entry contains the EDT-index pointing to the esoteric. The order of the esoteric in the EDT is no longer determined by the order in which the esoterics are defined, because HCD arranges the esoterics alphabetically.

To avoid this problem, you can do one of the following:

• Specify a token for the esoterics.

  The esoteric token is used by allocation to find the appropriate esoteric for a data set that has been cataloged using the esoteric. You no longer have to maintain a chronological order and may delete and add esoterics without getting access problems for data sets that are cataloged using esoterics. Tokens for system built esoterics (for example, SYSALLDA) are generated by allocation and always have the same value (for SYSALLDA 9999 decimal, for example). You cannot control the token for system built esoterics. To circumvent the problem, define a new user esoteric with a token that corresponds to the EDT index in the catalog entry and that contains the same device list as SYSALLDA.

  To get to the EDT index:

  • Use the LISTCAT command, or,
  • If you have your MVSCP deck, count the UNITNAME statements for esoterics up to the statement that defines the esoteric name to get to the number for the token.
• Re-catalog the data sets with a generic device type name (for example, 3380), before using HCD to migrate IOCP/MVSCP data.

To determine if you have any data sets that have been cataloged with an esoteric, use the scan utility that is provided in the SYS1.SAMPLIB member IEFESOJL. This utility scans a catalog and lists the data sets that were cataloged with esoteric device group names. The prologue of this SAMPLIB member contains information on the modifications you have to make to the JCL to run the job in your installation.