GENLIB OPTION Statement
A Generation Definition Statement member is provided in the sharedprefix.MICS.GENLIB library under the name VMCGENIN.
micsrm140
Review this file to check the OPTION statement definition for VMC. You can change the default definition to meet your needs, as described below.
Note:
The VMCGENIN member contains uppercase and lowercase characters. The keywords for the OPTION statement should be entered in uppercase.OPTION statement keywords for VMC:
VMACT/NOVMACT
Include
VM:Account
data elementsVMACH/NOVMACH
Include
VM:Account
charge fieldsECPMF/NOECPMF
Include 0/20 Monitor record fields
VMCGENIN Options - Impact on the Database
The options in VMCGENIN are used to cause the inclusion of elements in the database for the different levels of VM. This is accomplished by using cluster codes. Each element defined in VMCGENIN has a cluster code associated with it. These are:
OPTION Code Keyword Description ---- ------- -------------------------- 00 Not system level dependent 19 VMACT VM:Account fields 10 VMACH VM:Account charge fields only 20 ECPMF 0/20 Monitor Record Channel Path Extended Measurements fields
Note:
When VM is upgraded from one level to the next, the records created by the Monitor are not reformatted. Instead they are extended to provide space for the new information. This provides upward compatibility in the Monitor data. The same rule applies to VM/ESA and z/VM. z/VM is a successor to VM/ESA. OPTION ZVM3 will keep data elements for all z/VM releases; however, data elements added by the newer level of VM will not be found in the database until a VMCCGEN is run. By running a VMCCGEN, the new VM level is added to the MICS Complex
.Activating VM:Account Data Elements
VM:Account
Data ElementsThese options are provided to activate
VM:Account
data elements:VMACT/NOVMACT
activates and deactivates
VM:Account
non-charge data elements.VMACH/NOVMACH
activates and deactivates
VM:Account
charge data elements.ECPMF/NOECPMF
activates and deactivates Channel Path Measurement data elements from the 0/20 monitor record.
For example, if the VMCGENIN OPTION specification is VMACT NOVMACH,
VM:Account
data elements with cluster code 19 will be kept in the database and VM:Account
data elements with cluster code 10 will not be kept.