Usage

How to Submit the MAINTAIN ASF Statement

You submit the MAINTAIN ASF statement to CA IDMS/DB only through the batch command facility. You must be running CA IDMS/DB in local mode.

All affected areas must be varied offline to all central versions.

Run ASFOOAKD Dialog after Load or Delete

After loading a table or deleting a table that will be reloaded by some other means, you must run the ASFOOAKD dialog.

Use the task code ASFOOAKD to invoke the dialog, and supply the table definition number in response to the TABLE DEFINITION NUMBER prompt.

ASFOOAKD performs the following functions:

If an RFUR-nnnnnn-OOAK record exists for the table, ASFOOAKD updates the time/date stamp in the record and saves the database key of the record as data in the RDEFREC occurrence associated with the table.
If no RFUR-nnnnnn-OOAK record exists for the table, ASFOOAKD stores an RFUR-nnnnnn-OOAK record and saves the database key of the record as data in the RDEFREC occurrence associated with the table.

When to Specify TEST

Specify TEST if you want to verify the results of the operation without running through it completely.

Important! Specify TEST only when loading or extending a table into a test database. The incomplete processing performed is likely to corrupt a working database.

SORTEXIT and FROM/STEP

When using the FROM and STEP options with the SORTEXIT option, each pair of SORTn and DBLx steps are considered to be one step. If either half of the SORTn/DBLx is specified on a FROM or STEP option, processing will start with the SORTn step and the DBLx step will also be executed. For example:

FROM IDMSDBL3 will start with step SORT3 and will continue to the end.
STEP SORT3 will run steps SORT3 and IDMSDBL3.

SORTEXIT/REUSE WORKFILE Restart Considerations

Since SORTEXIT combines each SORTn step with the DBLx step that follows it, if a failure occurs in the DBLx step, a restart (if a restart is possible) must begin with the sort step and the input to the step will be resorted. Non-SORTEXIT mode will take longer to run but can be restarted after the sort in this case. Therefore, if restart time is more critical than normal runtime do not run the utility as a sortexit.

If the REUSE WORKFILE option is used with SORTEXIT, some input workfiles will be used as output files in the same step. Therefore if these two options are used together and a failure occurs, the utility must be restarted from the beginning.