V/Seg DCSS usage auditing
search cancel

V/Seg DCSS usage auditing

book

Article ID: 263532

calendar_today

Updated On:

Products

VM:Spool

Issue/Introduction

We are needing to audit usage of a particular DCSS saved segment.  (e.g. want to know which users, if any, are loading a particular DCSS over time.)  I've been told that VM:Spool's V/SEG-Plus component has features for auditing DCSS usage.
So far, all I have found is that V/SEG can be configured to create "NSSC0" accounting records for logging of DCSS/NSS usage activity.

Does V/SEG have a method of analyzing those "NSSC0" accounting records over time, or any other method for auditing DCSS usage over time?

Environment

Release : 1.8

Resolution

Assuming you have enabled the ACCOUNT features of V/Seg, it will cut the NSSC0 records and they will appear in the DISKACCNT data file.

 

 VMACCT   RDR_9681   ; V 80 Blks=0 Col=1 Rec=1 of 82 Files=1
====>
AUTOVSEGVMLWORK CMSVMLIB      RESET   LOGOFF  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSPIPES      RESET   LOGOFF  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK INSTSEG       RESET   LOGOFF  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMS           RESET   LOGOFF  CMS                          NSSC0
VMLWORK VMANAGER040523172639                                                  01
AUTOVSEGVMLWORK CMS           IPL             CMS                          NSSC0
AUTOVSEGVMLWORK INSTSEG       LOAD    SHARED  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMSPIPES      LOAD    SHARED  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      LOAD    SHARED  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      RESET   LOGOFF  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSPIPES      RESET   LOGOFF  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK INSTSEG       RESET   LOGOFF  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMS           RESET   LOGOFF  CMS                          NSSC0
VMLWORK VMANAGER040523182639                                                  01
AUTOVSEGVMLWORK CMS           IPL             CMS                          NSSC0
AUTOVSEGVMLWORK INSTSEG       LOAD    SHARED  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMSPIPES      LOAD    SHARED  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      LOAD    SHARED  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      RESET   LOGOFF  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSPIPES      RESET   LOGOFF  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK INSTSEG       RESET   LOGOFF  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMS           RESET   LOGOFF  CMS                          NSSC0
VMLWORK VMANAGER040523192642                                                  01
AUTOVSEGVMLWORK CMS           IPL             CMS                          NSSC0
AUTOVSEGVMLWORK INSTSEG       LOAD    SHARED  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMSPIPES      LOAD    SHARED  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      LOAD    SHARED  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB     &RESET   LOGOFF  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSPIPES     &RESET   LOGOFF  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK INSTSEG      &RESET   LOGOFF  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMS          &RESET   LOGOFF  CMS                          NSSC0
VMLWORK VMANAGER040523202650       (                                          01
AUTOVSEGVMLWORK CMS           IPL             CMS                          NSSC0
AUTOVSEGVMLWORK INSTSEG       LOAD    SHARED  INSTSEG                      NSSC0
AUTOVSEGVMLWORK CMSPIPES      LOAD    SHARED  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      LOAD    SHARED  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSVMLIB      RESET   LOGOFF  CMSVMLIB                     NSSC0
AUTOVSEGVMLWORK CMSPIPES      RESET   LOGOFF  CMSPIPES                     NSSC0
AUTOVSEGVMLWORK INSTSEG       RESET   LOGOFF  INSTSEG                      NSSC
 1= Help       2= Top       3= Quit      4=           5= Last      6= Retrieve
 7= Back       8= Forward   9= =        10= Left     11= Right    12= 

 

You will then need to use the VM:Account RAWDATA and possibly the ACCTDATA UserEXITs to define the non-standard CP ACCOUNT records so VM:Account knows how to process them and does not REJECT them. 

Then use the VM:Account reporting to show usage over time, etc...

Additional Information

To support any accounting record type other than what VM:Account explicitly supports, you need to put in RAWDATA, ACCTDATA and COSTING user exits so the records can be passed through the VM:Account stream like other records with these user exits doing some of the processing.
 
However, if all you need is that a DCSS is used (vs. actual accounting type info), do the records really need to go through the VM:Account cycle?   Perhaps not...
 
Is there any reason you can't collect the records from the VM:Account REJECTS file and do your own reporting?   This may be a better option for you.
 
Assuming you only need user/DCSS information vs. real accounting data, there really isn't a good reason to send the records through VM:Account since you would have to produce your own reporting or modify VM:Account's to support these records.
 
Due to the reason you want to collect the records, you may want to just take the records from the REJECTS file and do your own processing to keep it simple. 
 
 
Here is the Record Layout for the NSSC0 Account Records that V/Seg provides:

SSXCARD  DSECT ,
SSXAUDOR DS    CL8                     Auditor
SSXAUDIT DS    CL8                     Auditee
SSXFNAME DS    CL8                     Filename of NSS/DCSS
SSXDATE  DS    XL3                     Packed yymmdd of record
SSXTIME  DS    XL3                     Packed hhmmss of record
SSXFUNC  DS    CL8                     Function name
SSXSFUNC DS    CL8                     Subfunction (if any)
SSXALIAS DS    CL8                     NSS/DCSS Alias or EBCDIC file number
         DS    XL21                    Reserved for future use
SSXCODE  DS    CL3                     Code

 

This is the format of the records as they are in the REJECTS files.