JCL and parameters for a SCAN run - syncsort_capacity_management - 12.60

To examine data, use member (HLQ).AVMvvvv.JCLLIB(SCANZVM) which con­tains JCL similar to the following.

//SCANEXECPGM=AVMMAIN,REGION=4M
//STEPLIB DD DSN=(HLQ).AVMvvvv.LOADLIB,DISP=SHR
Choose from:
//ZVMDATA DD DSN=YOUR.ZVM.DATA,DISP=SHR
-or-
//VELSYS DD DSN=YOUR.ZMON.SYSTEM.DATA,DISP=SHR
//VELUSR DD DSN=YOUR.ZMON.USER.DATA,DISP=SHR
//VELCPU DD DSN=YOUR.ZVVPS.CPU.DATA,DISP=SHR
//VELDEV DD DSN=YOUR.ZMON.DEVICE.DATA,DISP=SHR
//*
//VMMSGS DD SYSOUT=*
//VMREPORT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//PARMDATA DD *
RUNTYPE=SCAN
/*

To process Velocity Software’s data use the //VEL*** DDNAMEs. For z/VM MON­ITOR data use the ZVMDATA DDNAME.

File VMMSGS will contain several sets of information similar to the following. First is an echo of the parameters you used and the ones in effect:

File VMREPORT shows the z/VM name, the operating system version and machine types, and details of the date and time ranges of all the data processed. This does not mean there is data in the whole of these date/time ranges.