INIT.RECON command

The RECON data sets must first be created using the DFSMS command AMS DEFINE CLUSTER, and must be empty.

Subsections:

• Keywords
• Examples of initializing the RECON data set

Syntax

Keywords

ACCESS()

Optional keyword you use to disable or enable parallel RECON access.

SERIAL

Specifies access to a RECON data set in serial mode. Only one DBRC request can be processed at a time. Access to the RECON data set is serialized at the data set level using hardware reserve.

PARALLEL

Specifies access to a RECON data set in parallel mode. With parallel RECON access, DBRC requests from multiple IMS systems, batch jobs, and utility jobs can be processed concurrently. the RECON data set is accessed in transactional VSAM mode. Access is serialized at the VSAM record level using coupling facility locking.

To use parallel RECON access, the following conditions must be met:

• All three RECON data sets must be available.
• The DBRC instance processing the command must register with SCI (that is, an IMSplex name must be specified through the DBRC SCI Registration exit routine (DSPSCIX0) or the IMSPLEX execution keyword).

NOCATALG | CATALOG

Mutually exclusive, optional parameters that you use to indicate whether DBRC retrieves the database definitions from the IMS catalog or the DBDLIB data set when the following commands are run:

• CHANGE.DBDS
• CHANGE.PART
• INIT.DB
• INIT.DBDS
• INIT.PART
• NOTIFY.REORG

For databases that are defined using Database Definition Language (DDL), DBRC must access an IMS catalog.

NOCATALG

Specifies that the DBDLIB data set is used.

CATALOG(name)

Specifies that an IMS catalog is used.

name is an eight-character alphanumeric string that identifies an IMS catalog HALDB database that is registered in the RECON data set. Any catalog name that is less than eight-characters is padded with blanks.

The catalog name is not validated when the INIT.RECON command is run because the catalog cannot be defined in the RECON data set until after the RECON data set is initialized.

NOCATDS | CATDS

Mutually exclusive, optional keywords that you use to indicate whether image copy, change accumulation, and log data sets are cataloged.

NOCATDS

Specifies that these data sets, regardless of their cataloged status, are not to be treated as cataloged.

DBRC verifies that the volume serial and file sequence numbers that appear in the job file control block are the same as the information recorded in the RECON data set.

CATDS

Specifies that these data sets are cataloged or SMS-managed.

DBRC does not verify the volume serial and file sequence numbers for the data set.

In order for the CATDS option to be effective, the data set must be cataloged, and volume serial information for the data set must be omitted from the JCL. If the data set is cataloged, CATDS is specified, and volume serial information is included in the JCL, DBRC ignores CATDS and allocates the data set by the JCL. Normal volume serial and file sequence checking occurs.

If the data set is not cataloged, CATDS is not effective, and DBRC allocates the data set by the JCL, with volume serial and file sequence checking.

If log data sets are SMS-managed, select the CATDS option and remove the %LOGVOLS keyword from skeletal JCL member CAJCL.

Attention: The CATDS option affects restart of IMS from SLDS data sets. Because the CATDS option indicates the SLDSs are under the control of a catalog management system, the VOLSER is not passed back to IMS for data set allocation. If the SLDS data sets are not cataloged, IMS restart fails.

CDSLID(value)

Optional keyword that you use to set the cross-DBRC service level ID in the RECON data set. The service level ID indicates that the maintenance that corresponds to the given value has been applied to all systems that will be accessing this RECON data set.

Occasionally, maintenance must be applied to all systems that access the same RECON data set before you enable that maintenance. You must issue the INIT.RECON CDSLID() command. This command is used to enable the function provided by the maintenance after the maintenance is applied to all the systems. The value to specify on the command is indicated in the ++HOLD card. The default value for CDSLID is 2.

CMDAUTH()

Optional keyword you use to specify whether DBRC batch command authorization is to be performed.

NONE | SAF | EXIT | BOTH

Mutually exclusive subparameters that you use to specify your DBRC batch command security option.

NONE

Specifies that command authorization is to be skipped. This is the default.

SAF

Specifies that a security product is to be called for command authorization.

EXIT

Specifies that the DBRC Command Authorization exit (DSPDCAX0) is to be called for command authorization.

BOTH

Specifies that a security product and the DBRC Command Authorization Exit (DSPDCAX0) are to be called for command authorization. The security product is called first, then DSPDCAX0.

safhlq

High-level qualifier of the resource name defined to the z/OS® System Authorization Facility (SAF) product (RACF®) to define command authorization. safhlq must be specified with SAF, EXIT, or BOTH. safhlq is a name up to 8 alphanumeric characters in length.

rcnqual

Optional parameter you use for setting a string value in the RECON data set that will be used in DBRC command processing on the RECON to determine whether the data set is a copy and whether command authorization should be enforced. The rcnqual parameter can be specified only with SAF, EXIT, or BOTH.

When setting rcnqual, the string must be a substring of the RECON COPY1 data set name in order to prevent inadvertently disabling security for the production RECON data set. If rcnqual is specified with an asterisk (*) at the end and within quotation marks, the RECON COPY1 data set name must start with rcnqual or DBRC command authorization will not be enforced.

For command authorization to be enforced, the rcnqual value must be a substring of the RECON COPY1 data set name. Ideally it should be a substring that is common to all three RECON data set names in order to prevent any problems if RECON reconfiguration takes place. rcnqual can be up to 44 characters long and must follow DBRC data set naming conventions.

DASDUNIT()

Optional keyword you use to specify the unit type of the DASD device holding the records for log data sets. The unit type can be up to eight alphanumeric characters long.

If you do not use this keyword to specify a DASD device, then the INIT.RECON command defaults to DASD unit type 3400.

DBRC stores the value specified for DASDUNIT in the unit field of various RECON records. Multiple utilities use this value as the default value for the output device type.

NOFORCER | FORCER

Mutually exclusive, optional keywords that you use to specify whether all IMS databases must be registered in the RECON data set.

NOFORCER

Specifies that databases do not have to be registered.

FORCER

Specifies that all databases must be registered. If you specify FORCER and a job attempts to access an unregistered database, the database authorization call from IMS to DBRC fails.

CHECK17 | CHECK44 | NOCHECK

Mutually exclusive, optional keywords that you use to change the type of log data set name comparison that DBRC does.

CHECK17

Verifies that the last 17 characters of a log data set name are consistent with the RECON data set. If the name in the RECON data set does not match the names on the appropriate ddname, the utility stops.

CHECK44

Verifies that the 44-character log data set name is consistent with the RECON data set. If the name in the RECON data set does not match the name on the appropriate log ddname, the utility stops.

NOCHECK

Used if the data set name specified as input to the Database Recovery utility is longer than 17 characters and has a new high-level qualifier. DBRC does not compare the log data set name recorded in the RECON data set with the name on the appropriate ddname.

LIST()

Optional keyword that you use to set a default of STATIC or CONCURR for LIST commands. The default only applies to LIST commands processed when the RECON data set is in parallel access (or TVS) mode.

If the LIST keyword is not specified on the INIT.RECON command, STATIC is set as the default.

STATIC

Specifies that if the RECON data set is in parallel access mode and a LIST command is processed that did not specify the STATIC or CONCURR keyword, the default for list processing is STATIC.

CONCURR

Specifies that if the RECON data set is in parallel access mode and a LIST command is processed that did not specify the STATIC or CONCURR keyword, the default for list processing is CONCURR.

Recommendation: Because some LIST commands with the STATIC option are likely to be disruptive, set CONCURR as the default. STATIC can then be specified on specific commands, for example, when trying to resolve problems. (The default if the LIST keyword is not specified on INIT.RECON is STATIC rather than CONCURR only because LIST commands with serial RECON access always produce consistent output.)

LOGRET(001 | 'time_interval')

Optional keyword you use to specify the retention period for log data sets.

The retention period is the minimum amount of time in which a log becomes inactive after it is opened. (It is then eligible to be deleted.)

The time_interval is a partial, punctuated time stamp representing a time interval (days, hours, minutes, and seconds) rather than a date and time. The time stamp has the following format:

ddd|hh|mm|ss|t 

where:

ddd

Number of days (000 to 365)

hh

Number of hours (0 to 23)

mm

Number of minutes (0 to 59)

ss

Number of seconds (0 to 59)

t

Tenths of a second (0 to 9)

The punctuation for the time stamp (shown in the above format as a vertical bar ( | )) can be any non-numeric character, such as a period (.) or a comma (,). The time stamp must be enclosed in single quotation marks (') if it contains any blanks or special characters. The number of days must include any leading zeros, but you can omit trailing zeros. Valid intervals range from a tenth of a second to 365 days. The default value, 001, is 24 hours.

Because the time interval is treated as a time stamp, message DSP1048I might be issued for incorrect values. Some examples of valid time intervals include:

LOGRET(365)
LOGRET('030 12.00')
LOGRET('000 00:00:08.0')
LOGRET('000 00,00,00,1')
 

Two different valid formats for equivalent time stamp specifications are shown.

LOGRET(030)          LOGRET('030')       = 30 days
LOGRET('010 12,30')  LOGRET('010 12:30')  = 10 days, 12 hours, 30 minutes
 

For information about inactive logs and how they are determined by use of the log retention period and other conditions, see the INACTIVE keyword under the DELETE.LOG (for RLDS and SLDS) command.

If you do not use this keyword to specify a retention period, then the INIT.RECON command defaults to a period of 001 (24 hours).

Recommendation: Ensure that an appropriate log retention period is specified so that log information is kept in the RECON data set for a long enough period of time. Certain IMS functions depend on log information in the RECON data set, and these functions might fail if that information is deleted too soon. For example, one or more of the following functions might fail:

• Dynamic backout
• Batch message processing (BMP) extended restart (XRST)
• Unit of work table entry (UOWE) resynchronization

NOLISTDL | LISTDL

Mutually exclusive, optional keywords that you use to specify whether data set names deleted from the RECON (by the DELETE.LOG command or by an archive job log compression) are listed in the job output. The setting specified on this command can be overridden by the DELETE.LOG command. There is no way to override the setting for log compression during an archive job.

LISTDL

Specifies that names of deleted data sets are to be listed in the job output.

NOLISTDL

Specifies that names of deleted data sets are not to be listed in the job output.

MINVERS('13.1' | '14.1' | '15.1')

Optional keyword that specifies the lowest version of IMS that is allowed to sign on to DBRC. The default is MINVERS('13.1').

The format for the MINVERS keyword includes a period. DBRC considers this a special character and requires the value to be enclosed in single quotation marks.

Requirement:

• To run the DEDB Alter utility with the ALTERAREA function for a DEDB area with sequential dependent (SDEP) segments, the MINVERS value must be '14.1'.
• To specify that an HALDB database can have up to 8 gigabytes of data in an OSAM PHDAM or PHIDAM database data set, the MINVERS value must be '14.1' or it must be '13.1' with a CDSLID value of 2. When MINVERS is set to '14.1', it cannot be lowered if an HALDB database is defined as using 8-GB OSAM data sets. The CHANGE.RECON () fails and the DSP1256E message is issued. A CDSLID value of 2 indicates that the SPE APAR that enables the support of 8-GB OSAM data sets has been applied to all IMS Version 13 resident libraries that access the RECON data set.

NOREORGV | REORGV

Mutually exclusive, optional parameters you use to modify the HALDB partition reorganization number verification. The default is NOREORGV.

NOREORGV

Specifies that HALDB partition reorganization number verification is disabled. Any requests to store, update or verify the reorganization number will be ignored.

REORGV

Specifies that HALDB partition reorganization number verification is enabled. DBRC stores the reorganization number for each partition in the partition record in the RECON data set to prevent the reorganization number from being regressed.

SSID(name)

Optional keyword you use to specify the name of the IMS subsystem that is to be used as the default subsystem ID for the following commands:

• CHANGE.PRILOG
• CHANGE.SECLOG
• DELETE.LOG
• GENJCL.ARCHIVE
• GENJCL.CLOSE
• NOTIFY.PRILOG
• NOTIFY.SECLOG

name is an 8-character alphanumeric string that identifies a valid IMS subsystem ID.

NONEW | STARTNEW

Mutually exclusive, optional keywords that you use to specify whether new jobs are to be started when only one RECON data set is available.

NONEW

Specifies that new jobs are not to be started.

STARTNEW

Specifies that new jobs are to be started. If parallel RECON access is enabled, new jobs cannot start with a single available RECON data set if another DBRC instance is running with two active RECON data sets.

TAPEUNIT(unittype)

Optional keyword you use to specify the unit type of the tape device that is holding the records for log data sets. The unit type can be up to 8 alphanumeric characters long.

If you do not use this keyword to specify a tape device, then the INIT.RECON command defaults to unit type 3400.

DBRC stores the value specified for TAPEUNIT in the unit field of various RECON records. Multiple utilities use this value as the default value for the output device type.

Usage notes

The RECON will contain a new catalog name. This name will be defined indicating the DBRC is using the directory instead of the DBDLIB for commands that need to reference the database definition. This catalog name can be set on the INIT.RECON command as the default. The catalog name is not required; if it is not present then DBRC will continue to expect the IMS DD to contain the DBDLIB.

The catalog name defined during INIT.RECON is not validated because the catalog cannot be defined to the RECON yet.