UNLOAD Control Statement

EMC Centera Disk Option › Secondary Disk Database Maintenance › UNLOAD Control Statement

UNLOAD Control Statement

The UNLOAD control statement allows you to unload the SYSOUT data for SYSOUT groups archived to secondary disk storage.

Syntax:

UNLOAD SECOND|NOSECOND

Where:

SECOND: Unload the SYSOUT data for SYSOUT archived to secondary disk storage.
NO SECOND: Do not unload the SYSOUT data for SYSOUT archived to secondary disk storage.

The SECOND/NOSECOND parameter has a default value of NOSECOND. Specifying SECOND can substantially increase the time required to perform the UNLOAD function.

Specifying SECOND when unloading does not make a difference to the process. The LOAD function never reloads the SYSOUT data for SYSOUT groups archived to secondary disk storage. The LOAD function merely transfers ownership of the secondary disk storage that is already archived.

You must specify SECOND when unloading the databases if you are going to use the MERGE function, because the MERGE function always reloads the SYSOUT data, either to primary or secondary disk.

Trace Centera API functions

A trace of the EMC API functions might be needed to diagnose communications and data errors. CA Support might request an EMC Centera API Trace along with other documentation to assist in the resolution of a problem. The trace function is available for both the CA View Centera Access Server (SARCAS) and the CA View Archival Task (SARSTC).

Note: Do not activate EMC API Tracing unless you are requested to do so by CA Support.

Tracing is activated by adding a DD Statement to either the SARCAS or SARSTC JCL with a control card that defines the fully qualified data set name of a preallocated file that contains the trace information. A unique data set is required when tracing both the SARCAS and SARSTC tasks. The following statements can be added to either SARCAS or SARSTC:

//FPCONFIG  DD *
FPLIBRARY_LOG_FILE_DEBUG=...trace_dataset_name...
/*

Where: trace_dataset_name

The fully qualified data set name of a file with the following attributes:

Organization . . . : PS

Record format . . . : VB

Record length . . . : 32756

Block size . . . . : 32760

Or:

//FPCONFIG DD DISP=SHR,DSN=...parm_library(...debug_statement...)

Where: The parameter library member contains the FPLIBRARY_LOG_FILE_DEBUG=...trace_dataset_name... statement.

Examples:

//SARSTC   PROC OPT=
//SARSTC   EXEC PGM=SARSTC,PARM='VIEW.SYSTEM1,&OPT'
//STEPLIB  DD DISP=SHR,DSN=CAI.CVDELOAD
//         DD DISP=SHR,DSN=CAI.CENnnnnn.PROGLIB.OPT
//SYSUDUMP DD SYSOUT=*
//SARPATAB DD DISP=SHR,DSN=CAI.CVDEOPTN(EROTAB)
//FPCONFIG DD DISP=SHR,DSN=CAI.CVDEOPTN(STCTRACE)
//SARBKLST DD SYSOUT=*
//SARD2LST DD SYSOUT=*
//         PEND

//SARCAS   PROC OPT=
//SARCAS   EXEC PGM=SARCAS,TIME=1440,
//            PARM=('CASTNAME=CAS1',
//            'NTHREADS=1')
//STEPLIB  DD DISP=SHR,DSN=CAI.CVDELOAD
//         DD DISP=SHR,DSN=CAI.CEN31477.PROGLIB.OPT
//FPCONFIG DD DISP=SHR,DSN=CAI.CVDEOPTN(CASTRACE)
//SYSUDUMP DD SYSOUT=*
//         PEND

Note: When you are tracing problems in the CA View Centera Access Server (SARCAS) task, only one communications thread can be active, NTHREADS (the maximum number of active threads) must be set to '1'.