A server IMOD is a commonly used service that is provided as a subroutine. It is an IMOD task that is started, does not terminate, and processes requests from other IMOD tasks. It permits the same code to that is used by a variety of callers and ensures that the appropriate resources are always used in a compatible manner.
You can use server IMODs to manage and synchronize the use of certain data. You can use them to provide an initialized environment for high‑performance execution of requests, or to serialize the use of a particular process or resource. Other possible uses for server IMODs:
You use the SRVCALL() function to invoke an IMOD that passes data to a server. The server owns a sequential data set where the data is logged. The individual TSO users do not need to allocate and synchronize the use of the data set. No TSO user needs authorization to access the data set. GoalNet provides automatic access for multiple CPU configurations.
Rather than having to synchronize all access to the data set, you can give ownership to a server IMOD. The server IMOD honors requests for reading from and writing to the data set. The SRVIMOD subroutine provides access to the server. It is callable from any installation‑provided program.
This routine, an IMOD running under SRVBATCH, uses CA SYSVIEW Performance Management to read and analyze SYSOUT data queued by previous job steps. Information from this analysis is then passed to a server (using the SRVCALL() function) and is retained in a VSAM KSDS. Later, an IMOD (initiated from CA Jobtrac Job Management) can request the server to return specific data that is used to control the scheduling of more jobs.
You can also provide more IMODs to extract summary information for display using TSO and the operator console, and to produce printed reports.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|