You can run multiple IMS systems on a single z/OS image or on multiple z/OS images. One instance of an IMS system (a control region and all its associated dependent regions) is referred to as one IMS system. In many cases, these IMS systems would be production and testing systems. A batch IMS system (for example, DB batch) is also considered one IMS system. Running Multiple IMS Systems on a Single z/OS ImageThe number of IMS subsystems you can run on a single image of z/OS depends on many factors, including the size of each IMS system (the amount of z/OS common service area [CSA] required by each IMS is often one of the most limiting factors in the equation). In most installations, you can run up to four IMS subsystems, although some installations run as many as eight small subsystems concurrently. Each IMS subsystem should have unique VTAM access method control block (ACB) and IMSID (IMS subsystem identifier to the operating system) names. The dependent regions use the IMSID to connect to the corresponding IMS control region. If the dependent region starts and there is no control region running using that IMSID, the dependent region issues a message to the z/OS system console and then waits for a reply. Each IMS subsystem can have up to 999 dependent regions. However, there are other limiting factors, such as storage limitations due to pool usage. Running Multiple IMS Systems on Multiple z/OS ImagesThere are basically three ways to run multiple IMS subsystems on multiple z/OS images:
|