When a CMAS is initialized, up to 9 MVS™ dataspaces are created. These dataspaces are used by CICSPlex® SM to allow quick access to data from a CMAS and the MASs attached to it. Although the dataspaces are logically owned by the CMAS, they are physically owned by the ESSS address space (EYUX310). The dataspaces are deleted when the CMAS (that logically owns the dataspaces) and all local MASs that are attached to that CMAS are terminated. The dataspaces are recreated when the CMAS is initialized again.
The size of the dataspaces is dependent upon the amount of work (end-user interface, workload management, MAS resource monitoring, and real-time analysis processing) the CMAS is performing and the number of MASs connected to the CMAS. The size may range from 20MB of storage in a relatively idle CICSPlex SM configuration to well over 100MB of storage in a configuration that is complex in both the number of MASs and the amount of work requested. If you do not prepare for such an increase in storage usage, you may encounter auxiliary storage shortages when you first start to use CICSPlex SM.
As an effort to prevent such auxiliary storage shortages, you should ensure that your auxiliary storage capabilities can handle an increase of 100MB of storage within the environment. Additionally, you can monitor CICSPlex SM’s dataspace usage by using an external monitor package to determine the amount of storage the EYUX310 job uses.
If auxiliary storage shortages do occur, you can alleviate the problem by either dynamically increasing your auxiliary storage capability or by causing CICSPlex SM to free the allocated dataspaces, as follows:
If a local MAS is acting as a CICSPlex SM WLM TOR, and the DTR program is specified as EYU9XLOP for that MAS, you must change the DTR program from EYU9XLOP before you can use the MAS view STOp action against that MAS. (For example, you can change it to the IBM default program DFHDYP.)
After the CICSPlex SM agent is terminated in all local MASs, terminate the CMAS itself.
After the auxiliary storage capability is increased, you can restart the CMAS.To
reconnect any local MASs that remained active after the CICSPlex SM
agent was stopped, execute the COLM transaction within those CICS® regions.
You can execute CORM or COLM using a modify command from the CONSOLE.