AMSOUT


The AMSOUT global option is valid in the Reorg function global options module (FRF$GLBL).

You can also specify it in the JCL as a DD statement. You cannot specify an AMSOUT keyword in the PLUSIN control statement data set. There is no default.

When you specify the AMSOUT global option, an AMSOUT file is dynamically allocated. The AMSOUT file contains restart information. The Online Reorg function and the Reorg function use the AMSOUT file when you delay data set name swapping and when you restart post-processing tasks.

If you specify a PDS or PDSE for the AMSOUT file, the member name will be the DBD name. For best performance, BMC recommends using a PDSE.

If you want to specify an AMSOUT file in the global options module, modify the #FRFGLBL member of the sample library. Use the following syntax, and provide any valid data set name:

AMSOUT='dataSetName'

You can specify an AMSOUT DD statement in the JCL as follows:

//AMSOUT DD DSN=dataSetName,DISP=SHR

The AMSOUT file is required for the Online Reorg function.

The AMSOUT file is required for the Reorg function if you want to execute the restart process to perform post-processing tasks. (You must use the restart process if post-processing tasks fail or you swap data set names manually.) DBRC must be active and the database must be registered.

Warning

Note

Do not modify the AMSOUT file. The AMSOUT file contains BMC generated information that is required for the restart process. Do not specify a disposition (DISP) that will delete the AMSOUT file if the job fails.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MAXM Reorg for IMS 5.0 and MAXM Reorg for IMS with Online/Defrag Feature 5.0