Defining Message Advisor data sets
When defining Message Advisor data set names during options customization, be sure to note the names that you assign to these data sets since you will use these names in the subsequent allocation step. When allocating data sets, consider the following points:
- A unique CHECKPOINT data set is required for each IMSID specified during options customization. Message Advisor Checkpoint Tracking uses this data set to maintain a record of checkpoints, which may later be used for requeue processing. Message Advisor Checkpoint Tracking automatically activates when you install the Message Advisor libraries in the IMS control region.
- A SPILL1 data set may be required for each IMSID specified during options customization. Message Advisor uses this data set during a REQUEUE TYPE=COLD/EREFAIL/REPROCESS to hold overflow from main storage for checkpoint records. If overflow occurs and this data set is not available, the requeue process fails. You can specify this data set at command execution time. This data set is required if the extended private storage is exhausted during a requeue.
- A SPILL2 data set is required for each IMSID specified during options customization. Message Advisor uses this data set during a REQUEUE TYPE=EREFAIL/REPROCESS to hold log data that will be sorted. You cannot specify this data set at command execution time. This data set is always required for REQUEUE TYPE=EREFAIL/ REPROCESS. This data set will be created dynamically as temporary files if the DSNs specified in the IMSID options are not found.
- A unique SPILL3 data set is required for each IMSID specified during options customization. Message Advisor uses this data set during a REQUEUE TYPE=EREFAIL/REPROCESS, which begins from a SNAPQ, to hold overflow from main storage. This data set contains 01, 03, and 3X log records. You cannot specify this data set at command execution time. This data set is required if the extended private storage is exhausted during a requeue. This data set will be created dynamically as temporary files if the DSNs specified in the IMSID options are not found.
- A unique SPILL4 data set is required for each IMSID specified during options customization. Message Advisor uses this data set during a REQUEUE TYPE=EREFAIL/REPROCESS to hold overflow from main storage. The data set contains 01 and 03 log records. You can specify this data set at command execution time. This data set is required if the extended private storage is exhausted during a requeue.
- The UNLOAD command set and the DEQUEUE MODE=UNLOAD_DEQUEUE command set require that you provide a data set to which messages will be unloaded. This data set can be supplied during options customization or specified at command execution. If specified at command execution, you use the OUTPUT subcommand. Specify OUTPUT DSN to provide a preallocated data set for the UNLOAD or DEQUEUE command sets. For more information about data set characteristics, see MAQCNTL member QMR#ALLO. For more information about the UNLOAD command, see Unloading-messages.
- An EXTRACT data set is optional for each IMSID specified during options customization. This data set can be supplied during options customization or specified at command execution. If specified at command execution, you use the EXTRACT subcommand. Specify EXTRACT DSN to provide a preallocated data set for the extract process. For more information about data set characteristics, see MAQCNTL member QMR#ALLO. This data set is required if you use REQUEUE MODE=EXTRACT, which copies messages into this data set. These messages can later be used as input to a requeue if you use REQUEUE TYPE=FILE. For more information about the REQUEUE command, see Requeueing-messages.
- A SCRAP data set is optional for each IMSID specified during options customization. This data set can be supplied during options customization or specified at command execution. If specified at command execution, you use the SCRAP subcommand. Specify SCRAP DSN to provide a preallocated data set for the unload procedure. For information about data set characteristics, see MAQCNTL member QMR#ALLO. If this data set is available during a requeue, Message Advisor writes messages to the data set that cannot be requeued. These messages cannot be requeued because of an exception condition. For example, an exception condition could include an LTERM or transaction that no longer exists in IMS. For more information about the REQUEUE command, see Requeueing-messages.
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*