• Additional IMS Sysplex Management Enhancements being provided are intended to address customer requirements:
• IMS SYSPLEX SHOULD PRESENT A SINGLE SYSTEM IMAGE AND PROVIDE EASE OF USE THROUGH A SINGLE POINT OF CONTROL
• System management of IMSs sharing databases and/or message queues in a sysplex becomes more difficult as you add IMSs
• Most commands and automation processes today can only affect an individual IMS
• Commands may be entered using E-MCS console to route command to all IMSs in IMSplex
• Commands that affect the sysplex can be issued on each IMS
• VTAM GENERIC RESOURCE USERS NEED TO BE ABLE TO RESUME STATE ON ANOTHER IMS IN IMSPLEX
• User cannot resume state if routed to another IMS
• ONLINE CHANGE SHOULD BE COORDINATED AND MANAGED ACROSS THE IMSPLEX
• Manual online change process is extremely difficult in IMSplex
• Each IMS today manages its resources locally
• Resources must be genned on each IMS
• Resource definition consistency is not enforced. A transaction defined on one IMS can be defined as an lterm on another
• Multiple users with the same name can sign on at the same time
• Multiple nodes with the same name can log on at the same time
• Multiple lterms with the same name can be active at the same time
• ADDITIONAL IMS REQUIREMENTS
• Eliminate restriction that resource names and IMS keywords must be unique
• Provide synchronous responses for IMS commands

---