CONDENSE Command

System Programmer Reference › Commands › CONDENSE Command

CONDENSE Command

Authorization: SYSADMIN

To convert a file-level detail catalog to a domain-level detail catalog, use the CONDENSE command. This command removes all file, track, and block information from the catalog.

When you condense a catalog, the CONDENSE command also condenses any dependent catalogs that an incremental backup creates. CONDENSE converts these dependent catalogs regardless of their own defined auto-condense dates. For example, a catalog with an auto-condense period of 30 days that is based on a catalog with an auto-condense period of 15 days is converted to domain-level detail when the base catalog is condensed.

You cannot enter CONDENSE while another catalog job or command (for example, CHECK, DISCARD, or UPDATE) is executing.

This command has the following format:

CONdense dumpjob

Definitions

dumpjob: Condenses a single catalog and any catalogs that are based on it, where dumpjob is the filename of the catalog's DUMPJOB file. (The filename is the number that this product assigns when the catalog is created.) Enter one to eight digits for dumpjob. To see the filename, use the CHECK command.

Screen Advantages

There are advantages to using the Condense Catalogs system administrator screen instead of the CONDENSE command to condense catalogs. For example:

You do not have to use the CHECK command to see a specific catalog's DUMPJOB number.
CA VM:Backup displays all associated catalogs that will be condensed before the condense process actually occurs.

Note: For more information about this screen, see the chapter “Managing Existing Catalogs” in the Administration Guide.

DASDTAPE Command

Authorization: SYSADMIN

To examine the contents of CA VM:Backup DASDtape resource pools and superpools and produce a report on tape allocation and pool usage, use the DASDTAPE QUERY or LIST command. To check the status of mounted DASDtapes, use the DASDTAPE STATUS command. To change the expiration date of a DASDtape to the current date, use the DASDTAPE EXPIRE command.

Note: For more information about using DASDtapes, see the DASDtapes topic in the "Managing Tape and DASD Resources" chapter.

This command has the following format:

DAsdtape {"Parms"} [("Options"...[)]]

Parms:

Expire volser
List name
Query name
Status

Options:

ALL
IN days
NOHeader
DISK [APPEND] | PRINTer | TERMinal | STACK [FIFO | LIFO]

Definitions

Expire volser

Indicates the DASDtape to be expired. In the resource pool of which volser is a member, this command changes the expiration date to the current date. The expiration date on the tape label of DASDtape volser is not changed.

volser: Specifies the volser of the DASDtape to be expired.

Note: DASDTAPE EXPIRE does not support options.

List name

Reports on existing TAPE files.

name: Specifies the name of the DASDtape resource pool or superpool to be listed.

Query name

Reports on tape disk usage.

name: Specifies the name of the DASDtape resource pool or superpool to be queried.

Status

Reports on mounted TAPE files.

ALL

Queries all DASDtape resource pools individually that belong to superpool name. If this option is not specified, the entire superpool is displayed as a single line. If the name specified is a DASDtape resource pool and not a superpool, this option is ignored.

Note: ALL can be specified only by the DASDTAPE QUERY command.

IN days

Specifies the effective date in days from the current date. The default value of days is 0, making the effective date the same as the current date.

Note: A DASDtape is considered expired if its expiration date is earlier or the same as the effective date. IN can only be specified with DASDTAPE QUERY and LIST.

NOHeader

Specifies that the header be suppressed in the displayed output.

DISK [APPEND] | PRINTer | TERMinal | STACK [FIFO | LIFO]

Specifies the destination of the report. You can specify only one output option.

DISK writes the report to the DASDTAPE OUTPUT file on the A-disk of the requesting user ID. If this file already exists, it is replaced by the new report file unless the APPEND option is specified, in which case, the report will be appended to the existing file. You cannot use this option with SMSG or issue it from the CA VM:Backup console.

PRINTER sends the report to the virtual printer. You cannot use this option with SMSG or issue it from the CA VM:Backup console.

TERMINAL displays the report on the virtual console.

STACK writes the report to the CMS program stack of the issuing user. By default, the output is stacked FIFO. You cannot use this option with SMSG or issue it from the CA VM:Backup console.

DASDTAPE LIST Report

The following list describes the information included in the report produced by the DASDTAPE LIST command:

Volser: Filename of the existing DASDtape (TAPE) file
Tapepool: DASDtape resource pool (TAPEPOOL) that the DASDtape is defined in
Job-Date/Time: Job start date and time
Exp-Date: Expiration date of the DASDtape
Days: Number of days until the volume expires. If 0, the volume is expired
Blocks: Number of disk blocks in use by the DASDtape
Job Name: Creating job (template) name
Dumpjob: Creating dumpjob number
Owner: Volume owner if used by an authorized client. For example, CA VM:Archiver

DASDTAPE QUERY Report

The following list describes the information included in the report produced by the DASDTAPE QUERY command:

Label

One of the following:

Label of the DASDtape resource pool minidisk (or TAPEDISK) if a DASDtape resource pool is being queried
‘-‘ if a superpool is being queried

Vdev

One of the following:

Virtual device number of the DASDtape resource pool minidisk (or TAPEDISK) if a DASDtape resource pool is being queried
‘SUP’ if a superpool is being queried

Tapes

Number of volsers defined to a DASDtape resource pool (TAPEDISK) or superpool

Alloc

Number of DASDtape tapes that exist on the DASDtape resource pool minidisk or superpool minidisks. This is the same as the number of TAPE files that exist on the TAPEDISK(s).

Tot Blks

Total number of formatted blocks on the DASDtape resource pool minidisk(s). This is the same as the total number of formatted blocks on the TAPEDISK(s).

Used Blks

Number of blocks in use on the DASDtape resource pool minidisk(s). This is the same as the number of blocks in use on the TAPEDISK(s).

Expired

Number of DASDtape tapes that are expired on the DASDtape resource pool minidisk(s). This is the same as the number of TAPE files that are expired on the TAPEDISK(s).

Exp Blks

Number of blocks occupied by expired DASDtape tapes on the DASDtape resource pool minidisk(s). This is the same as the number of blocks occupied by expired TAPE files on TAPEDISK(s).

Available –(%)

Number of blocks and the percentage of space available on the DASDtape resource pool minidisk(s). This is the same as the number of blocks and the percentage of space available on the TAPEDISK(s).

DASDTAPE STATUS Report

The following list describes the information included in the report produced by the DASDTAPE STATUS command:

Volser: Filename of the existing DASDtape (TAPE) file
Tapepool: DASDtape resource pool (TAPEPOOL) that the DASDtape is defined in
Blocks: Number of disk blocks in use by the DASDtape
Stat: Mounted R/O or R/W
Job Name: Creating job name (template name). This field is omitted when Stat is R/O

Examples

To list allocated DASDtapes for a DASDtape resource pool named tpool2, enter the following command:

vmbackup dasdtape list tpool2

CA VM:Backup issues a response similar to the following example:

Volser Tapepool Job-Date/Time Exp-Date Days Blocks Job Name Dumpjob Owner 112001 TPOOL2 03/06/14 16:54 04/05/14 26 1886 BKP4 0000000 112002 TPOOL2 03/06/14 16:54 04/05/14 26 1880 BKP4 0000000 112003 TPOOL2 03/06/14 16:54 04/05/14 26 1883 BKP4 0000000 112004 TPOOL2 03/06/14 16:54 04/05/14 26 477 BKP4 0000000

To query pool usage for a DASDtape resource pool, enter the following command:
```
vmbackup dasdtape query pool1
```
CA VM:Backup issues a response similar to the following:
```
Label  Vdev Tapes Alloc   Tot Blks  Used Blks  Expired   Exp Blks  Available-(%)
DTP001 0101    20    16     600660     600605        2      77527      77582-13 
```
There are twenty tapes defined to DASDtape resource pool pool1, of which sixteen are allocated and two are expired. Of the total blocks defined to the resource pool, 13% is available for use.
To query pool usage for a superpool, enter the following command:
```
vmbackup dasdtape query suppool1 
```
CA VM:Backup issues a response similar to the following:
```
Label  Vdev Tapes Alloc   Tot Blks  Used Blks  Expired   Exp Blks  Available-(%)
-      SUP    350   299   12600660   12578320       20    1177527    1199867-10
```
There are 350 tapes defined to the collection of DASDtape resource pools defined to the superpool suppool1, of which 299 are allocated and 20 are expired. Of the total blocks defined to the superpool, 10% is available for use.

To query pool usage for a superpool with each individual resource pool minidisk being displayed, enter the following command:

vmbackup dasdtape query suppool1 (all

CA VM:Backup issues a response similar to the following:

Label Vdev Tapes Alloc Tot Blks Used Blks Expired Exp Blks Available-(%) DTP001 0111 50 5 54000 30728 3 18375 23275-44 DTP002 0112 20 0 9000 6 0 0 8994-100 DTP003 0113 20 3 9000 6155 0 0 2845-32

There are three resource pools defined to the superpool super1.

To query the status of mounted DASDtapes enter the following command:

vmbackup dasdtape status

CA VM:Backup issues a response similar to the following:

Volser Tapepool Blocks Stat Job Name 112008 TPOOL2 344 R/W BKP1 111006 TPOOL1 370 R/O 112009 TPOOL2 129 R/W BKP1

To change the expiration date of DASDtape 112010 to the current date, enter the following command:
```
vmbackup dasdtape expire 112010
```
CA VM:Backup issues a response similar to the following:
```
VMBDAT2020I DASDtape 112010 expiration date changed to today, 07/21/14.
Ready;
```