Comparison of type-1 AOI and type-2 AOI
There are two different types of the automated operator interface (AOI): type-1 and type-2. The type-1 AOI uses the DFSAOUE0 exit routine and the type-2 AOI uses AOIE type exit routines (including DFSAOE00). You can use the type-1 AOI in the IMS DB/DC and DCCTL environments. You can use the type-2 AOI in all IMS environments, DB/DC, DBCTL, and DCCTL.
The following comparisons show the differences between the type-1 AOI and type-2 AOI:
- Type-1 AOI uses the IMS message queues; type-2 AOI does not.
- AOIE type exit routines can be used for control if messages are logged to the secondary master; DFSAOUE0 cannot.
- AOIE type exit routines can process internal commands and commands from a type-2 AO application; DFSAOUE0 cannot.
- DFSAOUE0 can send a message to an alternate destination and request the edited command buffer when the message is a command; AOIE type exit routines cannot.
- AOIE type exit routines use IMS AOI callable services; DFSAOUE0 does not.
- The
ICMDcall uses RACF® (or equivalent), the Command Authorization exit routine (DFSCCMD0), or both, for security. TheCMDcall uses RACF (or equivalent), the Command Authorization exit routine (DFSCCMD0), or both for security. - An AO application program issues
GUandGNcalls to retrieve a message from DFSAOUE0; it issuesGMSGcalls to retrieve messages from AOIE type exit routines. - MPP and message-driven BMP regions can issue
CMDandGCMDcalls in the IMS DB/DC and DCCTL environments. MPP, BMP, and IFP regions, DRA threads, and CPI Communications driven applications can issueICMDandRCMDcalls in the IMS DB/DC, DBCTL, and DCCTL environments. - Only specifically identified IMS applications
are permitted to issue type-1 AOI
CMDandGCMDcalls. To identify IMS applications to issue these type-1 AOI calls, include the AOI= parameter on the system definition TRANSACT macro. All IMS applications are permitted to issue type-2 AOIICMDandRCMDcalls.