TIMESTMP keyword

• For normal and special time stamp recoveries, you can specify any time stamp at which the database is deallocated (no ALLOC record for the database data set exists in DBRC). DBRC searches backwards until it finds a valid recovery point. For point-in-time recoveries, you can specify any time stamp, but you must recover all databases to the same time stamp. If the time stamp you specify is before the end-of-volume (EOV) time of the log, there must not be any updates to the database data set from the specified time stamp forward to the EOV time, unless you specify PIT (Y) or STR(Y).
• Use LASTIC if you want to recover a database by using only the last batch image copy (not flagged IN ERROR) that is stored in DBRC as input. DSALLOC(Y) and DBRC(Y) are required. RECOVERY PLUS for IMS allows recovering a database to a time when the last batch image copy was taken by specifying recovering to time stamp.
  • The recovery utility also allows recovery to a TIMESTMP(LASTIC-n) where n is an integer between 1 and 4.
  • The recovery utility uses the nth good batch image copy before the last good batch image copy recorded in the RECON. The utility bypasses any fuzzy, concurrent, or online image copies and does not count those in the search for the nth good batch image copy.
  • For a HALDB partition, if an Online Reorganization (OLR) was performed after the LASTIC-n copy was created, then you cannot use the TIMESTMP(LASTIC-n) keyword to specify the recovery time. This is to prevent any change in the active DBDS set between the LASTIC and LASTIC-n. In such cases, you must provide an explicit time stamp value for the recovery. 
    
  • If the utility cannot find the requested Image copy, the job abends with an appropriate error message.
  • If the utility finds the requested image copy, it prints an informational message with the time stamp of the requested image copy.
  • You can use this option only when the recovery is running with DBRC active.
• Use LASTPITCA to search the RECONs for the latest PIT CA record (as created by the BMC Change Accumulation utility), read the change accumulation time from this record, and use this time for the recovery time stamp. If you specify TIMESTMP(LASTPITCA) and a PIT CA record is not found, the job fails with a GENJCL error. The selected PIT CA can be one that was created with or without a specified time stamp. You must also specify PIT(Y).

The following time stamp formats are valid:

• 
  
  • yydddhhmmsst or yydddhhmmssthmiju
  • yy.ddd.hh.mm.ss.t or yy.ddd.hh.mm.ss.thmiju
  • 'yyyy.ddd hh.mm.ss.t zone' or 'yyyy.ddd hh.mm.ss.thmiju zone'
  • 'yyyy.ddd hh.mm.ss.t offset' or 'yyyy.ddd hh.mm.ss.thmiju offset'
  • 'yy.ddd hh.mm.ss.t zone' or 'yy.ddd hh.mm.ss.thmiju zone'
  • 'yy.ddd hh.mm.ss.t offset' or 'yy.ddd hh.mm.ss.thmiju offset'
  • 'yyyydddhhmmsst zone' or 'yyyydddhhmmssthmiju zone'
  • 'yyyydddhhmmsst offset' or 'yyyydddhhmmssthmiju offset'
  • 'yydddhhmmsst zone' or 'yydddhhmmssthmiju zone'
  • 'yydddhhmmsst offset' or 'yydddhhmmssthmiju offset'
  • LASTIC
  • LASTPITCA

The variables in these values have the following meanings:

• 
  
  • yy–Last two digits of year
  • yyyy–Four-digit year
  • ddd–Julian day of year
  • hh–Two-digit hour (00-23)
  • mm–Two-digit minute (00-59)
  • ss–Two-digit second (00-59)
  • t–One-digit tenth of a second (0-9)
  • hmiju–Microseconds (00000-99999). Microsecond values are valid for IMS releases that support microsecond time stamp precision. If you specify a microsecond value in IMS 9.1 and earlier environments, the value is ignored.
  • zone–One- to five-digit label of the user-defined variable that is set with the TIMEZONE parameter of the DBRC CHANGE.RECON command and that sets the displacement from UTC (for example, the variable CST could be defined as -0600 or six hours less than UTC)

offset

Signed (+ or -) four-digit (0000-1159) literal that specifies the hour and minute displacement from UTC (for example, -0600 means six hours less than GMT; +0800 means eight hours greater than UTC).

If you do not supply an offset, the product uses the offset as determined from the TIMEZIN value specified in the RECONs.

The offset is important when the boundary between daylight savings time and standard time is crossed. If you are performing a recovery to a local time that has a different offset from the current system offset, the time stamp must contain the offset for the local time. This situation applies to PIT recoveries. For a detailed explanation of IMS time stamps, see the IBM IMS documentation.

• While using the keyword in Archive IC recovery JCL, you can specify either a fully qualified time stamp or LASTIC. Using TIMESTMP(LASTIC) requests to use the last recorded Archive Image copy in the Directory.

A fully qualified time stamp must have the following format:

• 
  
  • yydddhhmmssthmiju
  • yyyydddhhmmssthmiju
  • ‘yy.ddd hh:mm:ss.thmiju‘
  • ‘yyyy.ddd hh:mm:ss.thmiju’
    
    The variables in these values have the following meaning:
  • yy–Last two digits of the year
  • yyyy–Four-digit year
  • ddd–Julian day of the year
  • hh–Two-digit hour (00–23)
  • mm–Two-digit minute (00–59)
  • ss–Two-digit second (00–59)
  • t–One-digit tenth of a second (0–9)
  • hmiju–Microseconds (00000–99999)

No offset or zone values are allowed in the time stamp while you use the keyword in an Archive Image Copy recovery JCL.