Will MSO need to run APF-authorized?
Many MSO features, including External Security, Usage Accounting, FastLoad, and the Resource Manager, require that MSO run APF-authorized. APF authorization is also required if MSO is to be brought up non-swappable.
By using MSO's Internal APF Authorization, it is possible to allocate unauthorized libraries to ddnames other than STEPLIB (USERLIB for FOCUS code; product-dependent ddnames for third-party products) while running MSO with APF authorization.
Will MSO run non-swappable?
For performance reasons, it is recommended that MSO be run non-swappable. MSO will still be subject to normal paging operations, but will not be swapped out.
Will user-level security be required for UDB access?
If user-level security is required, then the UDB exit DSN3SATH must be updated as described in this book.
In which performance group will MSO run? Will it require its own performance group?
MSO is a large on-line interactive address space. It should run in an appropriate performance group, and should most definitely not be run in the same performance group as typical batch jobs.
| Information Builders |