Defining OTMA destination descriptors

You can create, delete, and update OTMA destination descriptors either by using the online type-2 IMS commands or by coding them directly in the DFSYDTx member of the IMS.PROCLIB data set.

By default, you can define a maximum of 510 destination descriptors. You can change the maximum by specifying the DDESCMAX parameter in the DFSOTMA descriptor.

The type-2 commands for administering OTMA destination descriptors include:

• CREATE OTMADESC
• DELETE OTMADESC
• QUERY OTMADESC
• UPDATE OTMADESC

Changes made to the OTMA destination descriptors by any of the above type-2 commands become effective immediately and are recorded in both the IMS system logs as x'221B' log records and in the IMS checkpoint logs as x'4035' log records. The changes made by the type-2 commands are not stored in the DFSYDTx PROCLIB member and are retained only across warm starts and emergency restarts of IMS. The changes made by the type-2 commands are not retained across cold starts of IMS.

If you use the type-2 commands to create, modify, or delete OTMA destination descriptors, the changes override any existing definitions for the same descriptors that are in the DFSYDTx until the next cold start.

Changes made in the DFSYDTx member require a cold start of IMS to take effect, because IMS reads the DFSYDTx member only during a cold start.

In the DFSYDTx member, the OTMA destination descriptors are distinguished from the OTMA client descriptors, which are also stored in the DFSYDTx member, by a D in the first column of the descriptor entry.

You can update and delete OTMA destination descriptors that are coded in the DFSYDTx member with the type-2 commands; however the changes are not reflected in the DFSYDTx member. The modified or deleted descriptors are recorded in the logs, and the log records override the descriptor statements that are stored in the DFSYDTx member.

The QUERY OTMADESC command returns information about the OTMA destination descriptors as it is currently recorded in the logs.