Overriding the Auto-Condense or Auto-Discard Date

Administration Guide › Managing Existing Catalogs › Updating Catalogs › Overriding the Auto-Condense or Auto-Discard Date

Overriding the Auto-Condense or Auto-Discard Date

To specify a new auto-condense or auto-discard date, follow these steps:

Type update in the Command column of the Manage Existing Catalogs screen next to the catalog you want to update.
Update the auto-condense date, the auto-discard date, or both dates.
- To update the auto-condense date, move the cursor to the Auto-Condense column, and type a new date over the displayed date.
- To update the auto-discard date, move the cursor to the Auto-Discard column, and type a new date over the displayed date.
Type the dates in the format mm/dd/yy. You can enter one or two digits when specifying mm, dd, or yy. Use the following conventions when specifying yy:
- Type 42 through 99 for the years 1942 through 1999
- Type 00 through 41 for the years 2000 through 2041
For example, to specify November 15, 1997, type 11/15/97; to specify March 17, 2015, type 3/17/15.

Note: If you enter a date that is earlier than or the same as the current date, CA VM:Backup displays a warning message.
Press ENTER.

Important! If you specified a new auto-discard date for a catalog on the Manage Existing Catalogs screen or using the UPDATE command, update the expiration dates of the tapes associated with the catalog if necessary.

Updating Tape Expiration Dates

The procedure for updating tape expiration dates differs according to the tape management system. The following sections describe the various procedures.

Compile a List of Tapes

Compile a list of the tapes associated with the updated catalog. If CA VM:Tape manages the tapes, only the first volser for each tape stream and each copy that is part of the catalog is required. Otherwise, the list must include all volsers for all streams and all copies.

Issue the CA VM:Backup line mode CHECK command or the PRINT command on the Manage Existing Catalogs screen to produce a report about the catalog, including the tapes used in the backup.

Example:

The following example shows the first two tapes from copy 1, CA5037 and CA5038, and the first two tapes from the copy (or twin), HA2310 and HA2311, that are the first volsers for each copy of each stream.

vmbackup check (catalog 00000009 Filetype Count DUMPJOB 8 FILENNNN 28 DETAIL 17 -Total- 53 >>>01.01 Full backup dated: 02/14/14 14:28:27<<< 00000009 DUMPJOB ---Stream 01--- CA5037 FILE0001 00000016 DETAIL CA5039 FILE0001 00000018 DETAIL ---Twin 1--- HA2310 FILE0001 00000016 DETAIL HA2313 FILE0001 00000018 DETAIL ---Stream 02--- CA5038 FILE0001 00000017 DETAIL ---Twin 1--- HA2311 FILE0001 00000017 DETAIL VMBMAP0890I 0 errors were found on catalog minidisk 01B0.

Ready;

Tapes Managed by CA VM:Tape

If CA VM:Tape manages the tapes, extend the expiration date of the tapes in the tape management catalog (TMC). Follow these steps:

Compile a list of tapes. See Compile a List of Tapes.
Convert the new catalog expiration date from the Gregorian format (mm/dd/yy) that CA VM:Backup requires to the Julian format (yyyy/ddd) that CA VM:Tape requires. Use the CMS Pipelines DATECONV stage.
Example:
```
pipe literal 03/15/15|dateconv 1.8 short julian|console
2015.074
Ready;
```

Verify that the current expiration date that is stored in the CA VM:Tape TMC for each tape. Issue the CA VM:Tape LIST command.

Example:

vmtape list CA5037 (short VOLSER EXPDT DSNAME CA5037 2014/075 VMBACKUP.PRIMARY Ready;

vmtape list CA5038 (short VOLSER EXPDT DSNAME CA5038 2014/075 VMBACKUP.PRIMARY Ready;

Convert the Julian format expiration date that the LIST command provides to the Gregorian format expiration date used with CA VM:Backup. Use the CMS Pipelines DATECONV stage.

Example:

pipe literal 2014.075|dateconv 1.8 julian short | console 03/16/14 Ready;

Update the expiration date of the tapes in the CA VM:Tape TMC for one or more copies of the tapes. The new expiration date must be set at least as far into the future as the catalog expiration date. Issue the CA VM:Tape CATALOG command with the ANYTAPE option and specify the date in Julian format.
Note: For more information about the CA VM:Tape CATALOG command, see the CA VM:Tape Command Reference Guide.

Example:
```
vmtape  catalog CA5037 EXPDT 2015/074  (anytape
VMTCAT0507I 2 volumes based on 'CA5037' expiration date is now 2015/074.
Ready;  
```
```
vmtape catalog CA5038 EXPDT 2015/074  (anytape
VMTCAT0107I Volume 'CA5038' expiration date is now 2015/074.
Ready;
```
Issue the CATALOG command for each of the first tapes in each stream of the copy you want to keep.

Note: In a multivolume stream, changing the expiration date of the first tape in the stream changes the expiration date for all tapes in the stream. For more information about the CA VM:Tape CATALOG command, see the CA VM:Tape Command Reference Guide.

Verify that the new expiration date is stored in the CA VM:Tape TMC for each tape. Issue the CA VM:Tape LIST command.

Example:

vmtape list CA5037 (short VOLSER EXPDT DSNAME CA5037 2015/074 VMBACKUP.PRIMARY Ready;

vmtape list CA5038 (short VOLSER EXPDT DSNAME CA5038 2015/074 VMBACKUP.PRIMARY Ready;

Tapes Managed by CA VM:Backup

If CA VM:Backup is not interfaced with CA VM:Tape, CA VM:Backup does not use a tape when one of the following conditions applies:

The catalog that the tape is associated with has not expired.
The expiration date of the tape has passed and the tape is a member of the only tape set associated with the unexpired catalog.

You do not have to modify the expiration date in the actual tapepool file. If you extend the catalog auto-discard date, CA VM:Backup does not select those tapes for use in a backup job. It is safe to change only the catalog auto-discard date and not the tapepool file expiration date.

If you need to change the tapepool file expiration date anyway, END CA VM:Backup and edit the tapepool file on the resource pool minidisk (POOLDISK), usually the CA VM:Backup 1C0 minidisk.

Example:

For each record in the tapepool file, the first set of dates is the expiration date and the second set is the creation date.

In this example, the expiration date can be changed from 06/27/15 to 06/27/17.

M40015 06/27/17 06/25/15 FULL 00000000 BB6C0AE428127565 M40016 06/27/17 06/25/15 FULL 00000001 BB6C0BA9323C5143 M40019 06/27/17 06/25/15 FULL 00000002 BB6C0BFC34295164