New Features › New Database Structure Using CA Datacom/AD › DMPQ Shutdown and MOVQ Startup Options

DMPQ Shutdown and MOVQ Startup Options

In this version, tables in the CA Datacom/AD database replace the queue data sets. Now, when the database is backed up or the database is restored, the queues are included. The product no longer has a separate process to dump or load the queues during a shutdown or a startup. With the DMPQ and MOVQ removal, user exits SASSXXQB and SASSXXQD are removed.

The shutdown options that previously requested queue backup, Z4, Z5, and DMPQ, are obsolete in this version. The /SHUTDOWN command continues to accept these options but substitutes the equivalent non-DMPQ option for processing.

To avoid a substitution and the SCM2-31 message, modify the following items:

• Operator and automated procedures to discontinue use of any DMPQ-type shutdown options
• The SHUTDOWN keyword on the OPTIONS statement in the initialization file to discontinue use of any DMPQ-type shutdown options

The MOVQ restart type is also obsolete in this release. The CA 7 Online JCL execution TYPE= parameter, the TYPE keyword on the INIT statement in the initialization file, or both are sometimes specified with MOVQ.

The following types are valid for startup:

FORM

Resets all queues, including prior-run.

COLD

Resets all queues, but keeps prior-run.

WARM

Keeps all queues and messages.

ERST

Keeps all queues but deletes messages.

CKPT

Keeps all queues but reinitializes checkpoint file (a new startup type).

Other specialized startup types include EDIT and DORM.

Note: For more information about the startup types, see the Systems Programming Guide.

When the TYPE keyword on the INIT statement specifies MOVQ, the following WTO is written to the JES job log during startup:

CA-7.593 TYPE=MOVQ obsolete

When MOVQ is specified in the CA 7 online JCL parameter, an ERST startup is done. The following WTO is issued to the JES job log:

CA-7.952 TYPE=MOVQ obsolete – TYPE=ERST will be used

The INIT statement requires the TYPE= keyword or a U0910 abend occurs.

The following table shows what you can expect at startup when MOVQ is specified in either location.

This version does not provide functions that the DMPQ/MOVQ user exits (SASSXXQD and SASSXXQB) previously performed. If the user exit was simply capturing queue records, it is sometimes possible to implement similar functionality using CA Datacom/AD utilities, SQL, or both.

Note: For more information about restart types, see the Systems Programming Guide.