EXTBKUP (Extract from Backup File) › How to Use

How to Use

The MUF must be active when you execute this command. Execute the EXTBKUP function using the following command format:

Extract from Backup File (z/OS)

►►─ EXTBKUP DDNAME=dddddddd ─┬─────────────────────────┬──────────────────────►◄
                             └─ FORMAT= ─┬─ EXTRACT ─┬─┘
                                         └─ BACKUP ──┘

Command

EXTBKUP

Invokes the function to extract data from a backup file in expanded form.

Required Keywords

DDNAME=

Specifies the name of the input backup file.

A DDNAME is not acceptable for sequential input or output files if it is a name reserved for a CA Datacom area. Names with the following patterns are therefore not acceptable for DDNAME=:

• 3-byte names that end with XX, meaning they are reserved as either current or future CA Datacom control areas.
• 6-byte names that end with what could be a database ID from 001 through 999.
• 7-byte names that end with what could be a database ID from 1000 through 9999.

  The DDNAME= value is verified for acceptability to protect you from unintentionally causing data corruption. The DDNAME check is the default but optional. You can prevent the DDNAME check by using a DBSIDPR parameter (DBUTLTY_EDIT_DATA_SET=) for individual MUF environments. However, we recommend that you allow the DDNAME check.

  The data corruption risk involves not the DDNAME itself but the content of the data set. For example, suppose that you used the CXX DDNAME as the output of a backup. You then copied the CXX DD statement and changed the DDNAME of the copy to be acceptable, avoiding the DDNAME= error. The backup would, however, then overlay the CXX data set, which is not the intent of a backup.

  If you specify an unacceptable name for DDNAME=, message DB10059E is generated. For more information about DB10059, see the CA Datacom/DB Message Reference Guide.

  Note: We recommend that you allow DDNAME= check protection. You can, however, disable DDNAME= protection. To disable protection, assemble the DBSIDPR module used for this CA Datacom environment and specify NONE for the DBUTLTY_EDIT_DATA_SET= parameter. The default is DBUTLTY_EDIT_DATA_SET=FULL_1, which allows DDNAME= protection. For more information about DBSIDPR and DBUTLTY_EDIT_DATA_SET=, see the CA Datacom/DB Database and System Administrator Guide.

  Valid Entries:

  Any name valid to z/OS JCL specifications

  Default Value:

  (No default)

Optional Keywords

FORMAT=

If you do not specify FORMAT= (or if you specify FORMAT=EXTRACT), output is one or more extracted files, as was the case before Version 12.0 (in r11). If you specify FORMAT=BACKUP, the output is a single file in backup format with all records compressed by any option to be expanded. When FORMAT=BACKUP, you are required to have a previous single FILEOUT function to define the single output file, and in that FILEOUT function the keyword TABLE= must be set to *** (three asterisks) to specify that all tables be written to the output file.

In support of FORMAT=, message DB13279E could be received if there is an edit error (for details about the message, see the CA Datacom/DB Message Reference Guide).

Note: VAR or NONE are not valid entries for FORMAT= in EXTBKUP and, if specified, are considered an error.

Valid Entries:

EXTRACT or BACKUP

Default Value:

EXTRACT