How IMODs Execute

IMODs are executed by ISERVE under the control of CA‑GSS or as batch programs using SRVBATCH.

CA-GSS initiates an ISERVE in its address space. This is the primary ISERVE. You can also have secondary ISERVEs in other address spaces. The primary ISERVE processes all requests not specifically routed to secondary ISERVEs.

Note: Secondary ISERVEs are useful for testing or chargeback purposes.

IMODs are executed in the following ways:

At the direction of certain CA products:
- CA Deliver
- CA Insight Database Performance Monitor for DB2 for z/OS
- CA Jobtrac Job Management
- CA OPS/MVS Event Management and Automation
- CA SYSVIEW Performance Management
- CA View
At the request of CA agents running on non‑z/OS platforms (such as AS/400, HP/9000, RS/6000, Windows, and others)
At the request of another IMOD using an external subroutine call
In response to installation‑defined operator console commands
In response to WTO messages that serve as triggers
At the request of a TSO user from the IMOD editor test facility
As batch programs using the SRVBATCH program
At the request of TSO/E REXX (or compatible) EXECs using the SRVCALL() function
To support a user session under the Logon Facility

Tell Technical Publications how we can improve this information