Chapter 1. Release summary
B.1 APAR II12431
This APAR documents defining data and index components for data sets after conversion to R1E0.
B.1.1 Error description
This APAR is intended to provide information to the user about the removal of IMBED and REPLICATE in DFSMS R1E0. This is a supplement, but not a replacement, for the AMS Reference for Integrated Catalog Facility Guide (SC26490600), the Managing Catalogs Guide (SC26491400) and/or the Enhanced Catalog Sharing and Management Redbook (SG24-5594). Please refer to these manuals first.
IMBED and REPLICATE are ignored on a DEFINE of a new data set under DFSMS R1E0 and above. This was done because, with the faster DASD and the improved Cache Controllers and procedures, IMBED no longer provides value for performance. Also, IMBED and REPLICATE are not supported for RLS or for extended format or compressed data sets. For compatibility reasons, IMBED and REPLICATE are still supported for the IMPORT and DFSMSdss RESTORE functions. When Catalog ignores the IMBED parameter, it means that the allocation size for the index component now has to accommodate both the sequence set index records as well as the high level records. Before, with IMBED, the sequence set was stored with the data and the index allocation only needed to contain the high level index records, which are relatively few. For this reason, data sets with a small index allocation size or ones with a zero
secondary space, can have space problems once IMBED is removed. For these data sets, the user will need to make provisions to increase the Index size. There are no good formulas to calculate the amount of space required for the index component because the number of index records depends on the size of the data set, the size of the data CA and the size of the index records
themselves. The AMS Reference for Integrated Catalog Facility states that space can be allocated at the Cluster or Data component level and Catalog will figure out what the Index component will need.
1. If space is provided for the cluster, the system will divide the space between the data and index components.
2. If space is provided only for the data component, the system will determine how much more space is needed for the index component.
Appendix B. Maintenance information 173
One recommendation is to make the primary space allocation of the Index component (in tracks) equal to the number of cylinders the data set uses. This means that, for a data set using 200 cylinders, the Index component should have a primary allocation of 200 tracks. Also, secondary space should always be defined. Large data sets could be defined with an Index component space allocation of 2 cylinders with a smaller secondary space allocation.
PLEASE NOTE: REPLICATE is not ignored in the base code of DFSMS R150. OW44442 corrects this omission and should be applied as soon as possible so IMBED and REPLICATE are treated together. Without OW44442, the
IMBED/REPLICATE option will be treated as NOIMBED/REPLICATE which requires more index space than either IMBED/REPLICATE or
NOIMBED/NOREPLICATE.
For R1F0, after applying the PTF of APAR OW41955, the new return code IEC161I RC254 will be generated when OPEN for OUTPUT is done against a VSAM IMBED/REPLICATE/KEYRANGE data set. The associated sfi code means IMBED (001), KEYRANGE (002), and REPLICATE (003).
The new RC254 with SFI 1, 2 and 3 are informational only and do not require any immediate action. It is intended as an aid to customers to identify data sets currently defined with IMBED, REPLICATE or KEYRANGE.
If the message IEC161I rc254 is created 00000000 will be returned in REG15, and no ACBERFLG value will be returned.
PLEASE NOTE: After converting (migrating) to R1F0 — When a DEFINE CLUSTER contains the IMBED and/or REPLICATE keywords they will be ignored and the CLUSTER will be defined as NOIMBED and/or NOREPLICATE. Thus, msgIEC161i rc254 message will no longer be generated after the
CLUSTER is re-DEFINEd under R1F0.
PLEASE NOTE: For further information regarding KEYRANGE data sets please see II12896, and WSC Flash10072 which may be found at:
http://www-1.ibm.com/servlet/support/manager?rs=0&rt=0&org=ats &doc=F9AD8FC0B58E4A6A852569F5004ADC21
You may also find this Web site by: 1. Go to http://www.ibm.com 2. Select ’Support & downloads’
3. Type ’Flash10072’ (without the quotes) in the field ’Search for technical support by keyword(s):’
4. Double-click on the title ’KEYRANGE Specification to be Ignored in Future Release of DFSMS’
B.2 APAR II12896
This APAR documents DFSMShsm support for KEYRANGE data sets.
B.2.1 Problem conclusion
The value of keyranges as a feature of VSAM key-sequenced data sets has diminished significantly over the last few years with the introduction of new DASD cached controllers, improved SMS DASD performance parameters, and VSAM data striping. Because of this, it is IBM's intent to ignore the KEYRANGE specification on the IDCAMS DEFINE and IMPORT commands for any new data sets beginning in the z/OS V1R3 release of DFSMS. In accordance with this, DFSMShsm customers should be aware of the following:
DFSMShsm control data sets
For those customers that currently use keyrange data sets for their DFSMShsm control data sets (CDSes), it is strongly recommended that they begin planning to convert their CDSes to be multi-cluster non-keyrange. Chapter 3 of the DFSMShsm Implementation and Customization Guide SH21-1078 contains information on multi-cluster non-keyrange control data sets.
A good time to convert the CDSes to be non-keyrange is during a planned reorganization of the CDSes. To do the conversion, simply remove the
KEYRANGE keyword from the IDCAMS DEFINE statements used to define the multi-cluster CDSes. Then follow, your normal reorganization process. When DFSMShsm is restarted, since the VSAM keyranges are not present,
DFSMShsm will dynamically calculate the key boundaries of each cluster. Use the QUERY CONTROLDATASETS command to view both the low and high keys that DFSMShsm calculated for each cluster.
If the keyranged multi-cluster CDSes are not converted to be non-keyranged before migrating to z/OS v1R3 release of DFSMS, then UPDATEC must be used in CDS recovery situations.
The Enhanced CDS Recovery procedure will not perform properly in z/OS v1R3 DFSMS if the CDSes still contain VSAM keyranges.
Datamover selection
DFSMShsm can use either DFSMSdss or DFSMShsm as the datamover when performing either space or availability management. DFSMSdss has been the default data mover since the introduction of DFSMS/MVS V1R1 and is being used in most DFSMShsm installations.
Appendix B. Maintenance information 175
When DFSMShsm is the datamover, IDCAMS is invoked to manage VSAM data sets. Because of this, beginning with the next release of DFSMS, VSAM data sets with keyranges will have their keyranges removed during Recall and Recovery operations.
To verify that your installation is not using DFSMShsm as the datamover, examine your DFSMShsm startup parmlib member for a patch to the Datamover Selection Table (DMVST). If this patch is being used, then DFSMShsm is being selected as the datamover.
IBM recommends that only DFSMSdss be used as the datamover.
Migration
Attempts to migrate VSAM keyrange data sets with the DFSMShsm datamover will be failed. VSAM keyrange data sets must be migrated using the DFSMSdss datamover.
Recall
VSAM keyrange data sets that were previously migrated with the DFSMShsm datamover will be recalled, but the keyranges will be removed. A warning message will be issued to indicate this.
If possible, the data set should be recalled on a lower level system. VSAM keyrange data sets that were previously migrated with the DFSMSdss datamover will be recalled with the keyranges intact.
Backup
Attempts to backup VSAM keyrange data sets with the DFSMShsm datamover will be allowed, but a warning message will be issued. The warning message will indicate that the keyranges will be removed if the data set is recovered.
Recovery
VSAM keyrange data sets that were previously backed up with the DFSMShsm datamover will be recovered, but the keyranges will be removed. A warning message will be issued to indicate this. If possible, the data set should be recovered on a lower level system.
VSAM keyrange data sets that were previously backed up with the DFSMShsm datamover will be recovered, but the keyranges will be removed. A warning message will be issued to indicate this.
VSAM keyrange data sets that were previously backed up with the DFSMSdss datamover will be recovered with the keyranges intact.
Other DFSMShsm functions remain unchanged.
B.3 APAR OW53834
This APAR documents that update under HDZ11G0 of a GDG created prior to JDP2230 or OZ97150 can corrupt the catalog GDG base record.
B.3.1 Error description
GDG bases defined prior to the installation of JDP2230 or OZ97150 (Y2K support) did not account for a century indicator in the base record. If a GDG base of this type is altered by adding a GDS or rolling off a GDS under HDZ11G0 the catalog record for the GDG base will become corrupted.
A DIAGNOSE of a catalog will indicate this corruption by the following messages:
IDC21363I THE FOLLOWING ENTRIES HAD ERRORS:
gdgbasename (B) - REASON CODE: 2 gdgbasename.G0001V00 (H) - REASON CODE: 28
The errors seen during processing of this GDG base are unpredictable, but may include MSGIGD07001I with RC14 RSN0 module IGG0CLED, or MSGIDC3009I RC24 RSN12.
There is a method to help detect whether or not you have any GDGs susceptible to this problem, and a step you can take to correct those old-format GDGs to avoid the problem entirely:
1. If you know the date when JDP2230 or OZ97150 was installed on your system, you may run a LISTCAT CREATE(xxxx) GDG ALL where 'xxxx' is the number of days that have passed since that date. This LISTCAT will only show those GDG bases that were defined prior to that date. If you have none, then this problem should not occur in your environment.
2. If you issue an IDCAMS ALTER of the expiration date of: a. All of your GDG bases, or
b. Only those that are listed in step 1 above, the old record format will automatically be upgraded to the new format, and you will not be susceptible to this problem. The IDCAMS ALTER must be successful for this to occur. You may alter the expiration date to its current value — it is not necessary to alter it to a new date for this to correct the down level record.
Appendix B. Maintenance information 177
Note: You cannot alter GDG expiration dates in HDZ11G0, as that support has been removed. You must do the ALTER from a prior level system.
Problem summary
USERS AFFECTED: All releases using GDGs
Problem description:
Use of a GDG under HDZ11G0 may break the GDG catalog record, if the GDG base was created prior to installation of Y2K support (product FMID JDP2230 or APAR OZ97150 added support to Catalog, approximate date of ship was 5/86).
Recommendation
GDG catalog records can be corrupted if they were created prior to installation of JDP2230 or OZ97150 on the system, and those GDGs are accessed by a HDZ11G0 system. Also, changes are necessary on lower-level releases to ensure that expiration dates are no longer accepted or modified for GDG bases (HDZ11G0 removed support for expiration dates for GDGs, and this APAR includes toleration support for that change for other releases). Note that failure to install the PTFs on lower-level releases will not result in any catalog corruption, however the dates shown under HDZ11G0 for a GDG “last alter date” will be incorrect. This data is not currently used by any catalog functions but is made available for customer use. Incorrect dates in this field will not affect catalog operation, but any new user programs that extract and take action based on last alter dates of the GDG may make incorrect decisions if lower-level releases do not have this fix installed and they are used to alter the expiration dates of GDGs.
Problem conclusion
For the HDZ11G0 APAR, if a down-level (e.g. pre-Y2K) format GDG base record is encountered when adding or deleting a GDS, the old format cell will be upgraded to the new format as part of the update. This will prevent any breakage of the catalog record. For the other releases, this APAR fix prevents users from altering or setting the expiration of GDG bases, which is incompatible with the change in HDZ11G0. Beginning with HDZ11G0, expiration dates are no longer supported for GDG bases. Without this fix for the releases before HDZ11G0, users can alter the expiration date of a GDG, and it will incorrectly show up as the last alteration date if the GDG base is listed under HDZ11G0. If you attempt to alter the expiration date of a GDG base under HDZ11G0, it will fail with MSGIDC3009I RC60 RSN30. After installing this fix on releases prior to HDZ11G0, an attempt to alter the expiration date of a GDG base will fail for the same reason.
© Copyright IBM Corp. 2002 179
Glossary
Your glossary term, acronym or abbreviation. Term definition.
A
ABARS. Aggregate backup and recovery support.
ABR. Aggregate backup and recovery record.
access method services. A multifunction service program that manages VSAM and non-VSAM data sets, as well as integrated catalog facility (ICF). Access method services provides the following functions:
Defines and allocates space for data sets and catalogs
Converts indexed-sequential data sets to key-sequenced data sets
Modifies data set attributes in the catalog Reorganizes data sets
Facilitates data portability among operating systems
Creates backup copies of data sets Assists in making inaccessible data sets
accessible
Lists the records of data sets and catalogs Defines and builds alternate indexes Converts CVOLs to ICF catalogs
accompany data set. In aggregate backup and recovery processing, a data set that is physically transported from the backup site to the recovery site instead of being copied to the aggregate data tape. It is cataloged during recovery.
accompany list. An optional list in the selection data set that identifies the accompany data sets.
ACDS. Active control data set.
ACS. Automatic class selection.
active control data set (ACDS). A VSAM linear data set that contains an SCDS that has been activated to control the storage
management policy for the installation. When activating an SCDS, you determine which ACDS will hold the active configuration (if you have defined more than one ACDS). The ACS is shared by each system that is using the same SMS configuration to manage storage.
active data. Data that is frequently accessed by users and that resides on level 0 volumes.
activity log. In DFSMShsm, a SYSOUT or data set on disk used to record activity and errors that occurred during DFSMShsm processing.
AG. Aggregate group.
aggregate backup. The process of copying the data sets and control information of a user-defined group of data sets so that they may be recovered later as an entity by an aggregate recovery process.
aggregate data sets. In aggregate backup and recovery processing, data sets that have been defined in an aggregate group as being related.
aggregate group. A Storage Management Subsystem construct that defines control information and identifies the data sets to be backed up by a specific aggregate backup.
aggregate recovery. The process of recovering a user-defined group of data sets that were backed up by aggregate backup.
ATL. Automated tape library.
audit. A DFSMShsm process that detects discrepancies between data set information in the VTOCs, the computing system catalog, the MCDS, BCDS, and OCDS.
authorized user. In DFSMShsm, the person or persons who are authorized through the DFSMShsm AUTH command to issue DFSMShsm system programmer, storage administrator, and operator commands.
automated tape library. A device consisting of robotic components, cartridge storage frames, tape subsystems, and controlling hardware and software, together with the set of volumes which reside in the library and may be mounted on the library tape drives.
automatic backup. In DFSMShsm, the process of automatically copying eligible data sets from DFSMShsm-managed volumes or migration volumes to backup volumes during a specified backup cycle.
automatic class selection (ACS) routine.
A procedural set of ACS language statements. Based on a set of input variables, the ACS language statements generate the name of a predefined SMS class, or a list of names of predefined storage groups, for a data set.
automatic class selection (ACS). A mechanism for assigning SMS classes and storage groups.
automatic dump. In DFSMShsm, the process of using DFSMSdss to automatically do a full volume dump of all allocated space on DFSMShsm-managed volumes to designated tape dump volumes.
automatic interval migration. In
DFSMShsm, automatic migration that occurs periodically when a threshold level of
occupancy is reached or exceeded on a DFSMShsm-managed volume during a specified time interval. Data sets are moved from the volume, largest eligible data set first, until the low threshold of occupancy is reached.
automatic primary space management. In DFSMShsm, the process of automatically deleting expired data sets, deleting temporary data sets, releasing unused overallocated space, and migrating data sets from DFSMShsm-managed volumes.
automatic secondary space
management. In DFSMShsm, the process of automatically deleting expired migrated data sets from the migration volumes, deleting expired records from the migration control data set, and migrating eligible data sets from level 1 volumes to level 2 volumes.
automatic space management. In DFSMShsm, includes automatic volume space management, automatic secondary space management, and automatic recall.
automatic volume space management. In DFSMShsm, includes automatic primary space management and automatic interval migration.
availability management. In DFSMShsm, the process of ensuring that a current version (backup copy) of the installation’s data sets resides con tape or disk.
Glossary 181 B
backup control data set (BCDS). A VSAM, key-sequenced data set that contains
information about backup versions of data sets, backup volumes, dump volumes, and volumes under control of the backup and dump functions of DFSMShsm.
backup copy. In DFSMShsm, a copy of a data set that is kept for reference in case the original data set is destroyed.
backup cycle. In DFSMShsm, a period of days for within a pattern is used to specify the days in the cycle on which automatic backup is scheduled to take place.
backup frequency. In DFSMShsm, the number of days that must elapse since the last backup version of a data set was made until a changed data set is again eligible for backup.
backup version. Synonym for backup copy.
backup volume. A volume managed by DFSMShsm to which backup versions of data sets are written.
backup. In DFSMShsm, the process of copying a data set residing on a level 0 volume, a level 1 volume, or a volume not managed by DFSMShsm to a backup volume.
base configuration. The part of an SMS configuration that contains general storage management attributes., such as the default management class, default unit, and default device geometry. It also identifies the systems or system groups that an SMS configuration manages.
base sysplex. A base (or basic) sysplex is the set of one or more MVS systems that is