|
|
|
Up to 256 primary SVCs can be defined to z/OS. They are specified by one or more IEASVCxx members of the logical Parmlib. See SVCUPDTE later in this chapter for more information. Each SVC is assigned a type from 1 to 6. The type indicates to the operating system (among other things) where the SVC is stored. If it is type 1, 2, or 6, it is link edited into the z/OS system nucleus into the IEANUC0x member of SYS1.NUCLEUS, where x is an one‑character suffix (usually 1). If it is type 3 or 4, it is stored in an LPA library. If it is type 5, it is a dummy place holder entry in the SVC table and does not exist anywhere. It can be changed later to a real SVC entry by using the superzap program.
Additional IBM SVCs are also defined by the Extended SVC Routing facility, or ESR. This facility was provided in earlier MVS releases to extend the number of SVCs available for each SVC type.
The SVC Analysis Display (3.7) shows you the type of each SVC displayed. Because CA Auditor gets its information directly from the z/OS memory‑resident SVC table, it is more reliable than reviewing the IEASVCxx logical Parmlib members because the display includes SVC entries that might have been dynamically created by suitably authorized processes. By convention, IBM supplies SVCs with numbers less than 200. See the System Review Checklist for specific tests to perform on these SVCs.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |