CRURRSV Parameters

Execution parameters are provided on the PARM parameter of the EXEC statement. There are six required parameters and one optional parameter. An example showing all seven parameters is in Figure 1.

Figure 1. CRURRSV Execution Parameters - Example 1

//S1 EXEC PGM=CRURRSV,
// PARM='UCAT.BROKEN,12/05/04,14:32:58,12/06/04,19:46:27,60,2'

For ease of specification and alteration, you may wish to split the individual subparameters across multiple statements. An example of this is in Figure 2.

Figure 2. CRURRSV Execution Parameters - Example 2

//S1 EXEC PGM=CRURRSV,
// PARM=('UCAT.BROKEN',
//       '12/05/04','01:32:58',
//       '12/06/04','19:46:27',
//        60,
//         2)

The individual subparameters are described below.

Name of catalog to be recovered, or '**' (all catalogs)
- Length - 1 - 44 characters
- Implications - Used as basis for SMF record selection. If all catalogs are indicated ('**'), then all type 61/65/66 records that fall within the start/stop range will be selected. This allows CRURRSV to be used to separate the SMF data required for catalog recovery on a periodic basis.
- Restrictions - If a single catalogs is indicated, this must be the name specified when the catalog was DEFINEd, not an alias.
  This parameter is required.
Start date (Julian or Gregorian format)
- Length - 6 characters (Julian) or 8 characters (Gregorian)
- Format - YY.DDD (Julian - year.daynumber) or MM/DD/YY (Gregorian - month/day/year)
- Implications - Used to determine the starting point for SMF record selection.
- Restrictions - Leading zeros must be specified (for example, 12/05/04, not 12/5/04). To ensure correct synchronization of EXPORT and SMF data, this date should match the date of the EXPORT to be used as input to CRURRAP, if both programs are being run in series for recovery purposes. The EXPORT date will be found on the EXPORT SYSPRINT output, at the top of the first page. If a program other than EXPORT was used for backup, use the date that backup was taken. Such a procedure requires that the non-EXPORT backup be restored, and an EXPORT be done from that restored copy of the catalog. Hence the date of the EXPORT is not the correct starting point for use of SMF data. Expect message CRU104I when the start date/time do not match the EXPORT date/time. If CRURRSV is being used only to extract SMF data, any date may be specified.
  This parameter is required.
Start time
- Length - 8 characters
- Format - HH:MM:SS (hours:minutes:seconds)
- Implications and Restrictions are the same as for start date. Leading zeros are also required for start time (for example, 01:32:58, not 1:32:58).
  This parameter is required.
Stop date (Julian or Gregorian format)
- Length - 6 characters (Julian) or 8 characters (Gregorian)
- Format - YY.DDD (Julian - year.daynumber) or MM/DD/YY (Gregorian - month/day/year)
- Implications - Used to determine the stopping point for SMF record selection.
- Restrictions - Leading zeros must be specified (for example, 12/05/04, not 12/5/04). To ensure that all required SMF data is processed, this should be the date on which the recovery is being done, or the date on which access to the catalog was stopped.
  This parameter is required.
Stop time
- Length - 8 characters
- Format - HH:MM:SS (hours:minutes:seconds)
- Implications and Restrictions are the same as for stop date. Leading zeros are also required for stop time (for example, 01:32:58, not 1:32:58).
  This parameter is required.
Maximum acceptable gap between SMF records, in minutes
- Length - 1 to 4 numeric characters
- Format - MMMM
- Implications - Used to trigger warning messages about possible missing SMF data. Specify a value slightly smaller than the usual time to fill an SMF data set. If you do not know what this value is, try specifying 30 minutes and check CRURRSV output for SWITCH SMF records, which will indicate the dates and times at which switches were actually done.
- Restrictions - Leading zeros may be specified (for example, '0004') or omitted (for example, '4'). Specification of zero will cause the time between any two SMF records to be considered an unacceptable gap, and will create many warning messages.
  This parameter is required.
Maximum clock difference (multi-system operation only), in seconds
- Length - 1 to 4 numeric characters
- Format - SSSS
- Implications - When the catalog to be recovered may have been updated by more than one system, specification of this parameter causes adjustment of the effective start and stop times to allow for potential differences in the system clocks on the involved systems. A clock difference value of '2', for example, would cause 2 seconds to be subtracted from the start time and added to the stop time to calculate effective start/stop times. These adjusted times are then used as the basis for SMF record selection.
- Restrictions - Crossing midnight during this adjustment is not supported. Do not specify a start time which, if the clock difference is subtracted from it, would generate an effective start time on a different day than the specified start time. Likewise do not specify a stop time which, if the clock difference is added to it, would generate an effective stop time on a different day than the specified stop time. For example, a start time of 00:00:01 and a clock difference of 5 seconds would violate this restriction. If it is absolutely necessary to bypass this problem, specify a start time just before midnight (23:59:59) and the earlier start date, or a stop time just after midnight (00:00:01) and the later date, depending on whether your problem is with the start or stop adjustment.
  This parameter is required for multi-system operation, where the catalog to be recovered could have been updated by more than one system. For a single-system environment it can be omitted but should be specified as zero.