A site implementing MSO may desire to create separate performance groups for MSO address spaces. Because MSO is designed to run non-swappable, the regular parameters needed for SRM swapping recommendations are not required. However, the dispatching priority may be changed depending on the type of work to be executed in an MSO region. A high priority MSO region using efficient, pre-written routines would be assigned a favorable dispatch priority, while an MSO region for users reporting from large databases might get a low dispatch priority.
In general, MSO should have dispatch priorities just below those for production CICS and IMS regions, as well as TSO period 1. MSO should get a higher dispatch priority than test CICS, IMS, and batch regions, as well as lower period TSO regions.
Using storage isolation for very high priority applications, such as intensive data entry applications, can be appropriate. In such applications, assigning a minimum working set size of 1.5MB per user will ensure that MSO region always has adequate main memory to provide good response time for users. For a three-user region, specifying
PGN=...,(....,PWSS=(1000,1000))
ensures that this small MSO address space will always have about 4MB of main storage dedicated to it.
| Information Builders |