Managing Protected Conversations

To manage more than one protected conversation at a time, a server must register as a resource manager and use privately managed contexts to represent inbound allocate requests. Using privately managed contexts is only necessary for servers that are designed following the management-directed model. Other model types may process protected conversations as they would any other conversation, as long as each server subtask processes only one conversation at a time.

Note that designing and coding a server to act as a resource manager is relatively difficult. If you want to code a management-directed server to manage protected conversations, you need to:

Understand the concepts and requirements for resource recovery in z/OS MVS Programming: Resource Recovery.
Use the guidelines listed in General Considerations for Multi-Tasking Servers to design and code a management-directed server to act as a resource manager.