5. FILES › 5.2 VMC Information Area Files › 5.2.3 VM RSCS Accounting File (VMCVRA) › 5.2.3.3 VMCVRA Usage Considerations
5.2.3.3 VMCVRA Usage Considerations
Special considerations or techniques related to using the
VMCVRA File are provided below:
o RSCS does not provide an account number in the account
record it creates for data transmission activity, because
none is provided by the CP. If your installation uses the
VMCVRA File for accounting, the algorithm for building the
account structure must rely on USER or some other element.
o If your installation is using SMF type 26 records to
charge for VM-originated print on your MVS system, you may
be exposed to duplicate charging if both the BATSPL and
VMCVRA Files are used for cost recovery. One solution to
this problem is to use each file to recover only resources
used on the system that generated the account record (C0
VM Account or type 26 SMF). Alternately, either records
for data sent to or received from your MVS system can be
disregarded when the VMCVRA is processed for accounting.
o The VMCVRA File contains the element VRALCLNN (Local Node
Name), which is set in the exit %VMC0EXIT. Together with
the elements VRAORGNN (Origin Node Name) and VRALSTNN
(Last or Destination Node Name), an analysis of
node-to-node spooled data traffic through your VM and CMS
Analyzer can be made.
o The VMCVRA File provides information about the use of your
RSCS virtual machine(s) and the workload placed on RSCS by
users in your spool network. The information available
allows you to apportion the workload between users of the
network based on print or punch records sent or received,
and the origin or destination for the file.
The elements USER and VMCACNT are set to the value of
VRAORGID (originating userid). VMCACNT is defaulted to
USER because RSCS does not supply an account number. It
may be desirable to modify VMCACNT or USER based on your
installation's requirements for charging for RSCS activity
in the file exit for the VMCVRA File located in
prefix.MICS.USER.SOURCE(#VMCEXIT).