Run System Scripts Appropriately

Many sample system scripts are delivered with your Vantage installation. However, you need to select, configure, and actively use the system scripts to meet your business needs. Certain system scripts can be quite intensive regarding the amount of I/O, memory, CPU, and elapsed time is consumed. The following information is important:

Running scripts that you do not need, or running scripts more often than needed, wastes valuable resources.
Running scripts at inappropriate times consumes resources that may be needed by other workloads.
Running scripts simultaneously not only causes contention for the I/O, memory, and CPU resources, but also causes the I/O, memory, and CPU usage to spike at a much higher value. If I/O and CPU are already constrained, these spikes can impact both Vantage and system performance. If Vantage memory is constrained or already in use for other functions, the memory spikes caused by running scripts concurrently can cause needed functions to fail due to the lack of sufficient memory.

To improve performance and keep all functions running smoothly, ensure that you run your scripts at time and frequencies that are appropriate to your needs and overlap other scripts as little as possible. For example, run scripts once a week or once a month rather than every day or several times a day. Consider running audits at inactive times, such as on weekends or late at night.

Available System Scripts

The following list of system scripts provides the description, required license, resource consumption, and recommendations for when and how often to run each script. The list is followed by specific tasks to help you adjust the schedules for each script.

ACESCR
Submits batch CREWSACE which creates the data for Vantage SRM objects for CREW, such as “Free space from CREWSCHK,CREWSCHK Using defaults” and several others.
License Required: GMI CREWS
Resource Usage: Batch job has high I/O and elapsed time (unloads catalogs)
When to Run: Not prime shift
How Often: Weekly or as needed
ADAFILE
Creates Disk Checkpoint file for object ADAFCB for the ADABAS Database files object
License Required: Vantage Database Option
Resource Usage: Low resource usage but moderate elapsed time
When to Run: Not prime shift
How Often: Daily
ASTEX00
Creates ASTEX00 LI object in memory for Vantage SRM objects for support Astex. Include object ASTEX00 in your warmstart list.
License Required: GMI ASTEX
Resource Usage: Low
When to Run: Intervals throughout the day
How Often: Every 30 minutes or as needed
CA7SCR
Submits batch job CREWSCA7 which creates the data for Vantage SRM objects for CA 7 interface.
License Required: GMI CREWS
Resource Usage: Batch job has high I/O and elapsed time (unloads CA 7 and catalog data)
When to Run: Not prime shift
How Often: Weekly or as needed
DATACOM
Creates DATACOM LI objects in memory. Include objects DATACOMM, DATACOMA, DATACOMB, DATACOMT and DATACOMZ in your warmstart list.
License Required: GMI Datacom
Resource Usage: Moderate memory usage
When to Run: Intervals throughout the day
How Often: Every 120 minutes or as needed
DB2LITS
Creates LI object OBJ12029 to show DB2 Table Space Occupancy.
License Required: Vantage Database Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: After the RUNSTAT utility ends
How Often: Weekly or as needed
DB2NAMES
Creates LI objects DB2DETAL, DB2NAMES and DB2TABLS to show DB2 Indexspaces and Tablespaces. Include the objects in your warmstart list.
License Required: Vantage Database Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: After the VSAMVVDS script ends and the flat file is sorted
How Often: Weekly or as needed
DB2RTS
Creates LI objects OBJ12027 and OBJ12028 to show DB2 REAL TIME Indexspaces and Tablespaces. Include the objects in your warmstart list.

Important!
- The statistics data is as fresh as when the RUNSTAT utility was executed on that particular DB2 system.
- This script should not be run at the same time as the script DB2NAMES.
License Required: Vantage Database Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: After the VSAMVVDS script ends and the flat file is sorted
How Often: Weekly or as needed
DLMDISCR
Submits batch job DLMDIJCL which creates Disk Interval data for several Vantage SRM objects for EMC DLm support, such as EMC DLm Space utilization, EMC DLm Virtual Tape Drives,EMC DLm replication status
License Required: Vantage Base System
Resource Usage: High CPU and elapsed time
When to Run: Not prime shift
How Often: Dailyor as needed
DSKCATLF
Copies the CATALOGF real time object records to a sequential (PS) check point data set
There is no need to configure the script unless the following apply:
- The vantage system parameters CPKPFX (%%DSNPFX%%.C) and CAPPOOL (SYSALLDA) do not fit your environment.
- The SET_NUMB_RECORDS=2000000 does not indicate roughly the number of records that the master holds. This parameter is used to calculate space for allocating the disk data set.
- The default input list of INPUT_LIST_SET=/ does not fit your environment. The input list can be used to filter out what object records you want to have in the disk checkpoint. The input list also reduces the resource consumption of the script
License Required: GMI
Resource Usage: High I/O
When to Run: Avoid high CPU when catalog information is not necessary by requested in Real Time
How Often: Daily or as needed
DSKCIDSD
Copies the OBJ06111 DFSMShsm CIDS details real time records to a sequential (PS) check point data set for further use.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of CIDS data set
How Often: Daily or as needed
DSKHSMCB
Copies the HSMCB BCDS Data Set Records records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of BCDS data set
How Often: Daily or as needed
DSKHSMCC
Copies the HSMCC BCDS Data Set Records records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of BCDS data set
How Often: Daily or as needed
DSKHSMCD
Copies the HSMCD MCDS Data Set Records records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of MCDS data set
How Often: Daily or as needed
DSKHSMRC
Copies the HSMTTORC OCDS recycle candidates to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of OCDS data set
How Often: Daily or as needed
DSKHSMRS
Copies the OBJ06072 OCDS recycle candidates in a silo records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of OCDS data set
How Often: Daily or as needed
DSKHSMTD
Copies the HSMTTDSN OCDS tape dataset records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of OCDS data set
How Often: Daily or as needed
DSKHSMTT
Copies the HSMTTOC OCDS tape volumes records to a sequential (PS) check point data set.
License Required: Vantage Interface for DFSMShsm
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift, and avoid HSM backup periods of OCDS data set
How Often: Daily or as needed
DSKIBMAU
Creates Disk Checkpoint file for object VISIVTAU for the IBM VTS Copy Audit report (for TS7700).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMCC
Creates Disk Checkpoint file for object VISIVTCC for the IBM VTS Cache Contents Information (for TS7700 and 3494).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMPL
Creates Disk Checkpoint file for object VISIVTPL for the IBM VTS Physical to Logical Volume Mapping (for TS7700 and 3494).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMPM
Creates Disk Checkpoint file for object VISIVTPM for the IBM VTS Physical Media Pool (for TS7700 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMPP
Creates Disk Checkpoint file for object VISIVTPP for the IBM VTS PTP Volume Status Info (for 3494 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMPV
Creates Disk Checkpoint file for object VISIVTPV for the IBM VTS Physical Volume Status (for TS7700 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMVH
Creates Disk Checkpoint file for object VISIVTVH for the IBM VTS Vnode and Hnode history objects (for TS7700 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low resource usage but moderate elapsed time
When to Run: Not prime shift
How Often: Daily
DSKIBMVP
Creates Disk Checkpoint file for object VISIVTVP for the IBM VTS Vnode and Hnode point-in-time objects (for TS7700 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low resource usage but moderate elapsed time
When to Run: Not prime shift
How Often: Daily
DSKIBMVS
Creates Disk Checkpoint file for object VISIVTVS for the IBM VTS Volume Status Information (for TS7700 only).
License Required: Vantage Tape Resource Option
Resource Usage: Low
When to Run: Not prime shift
How Often: Daily or as needed
DSKIBMVT
Creates Disk Checkpoint file for object IBMTAPVT for the IBM VTS Virtual Tape Volumes (for TS7700 and 3494).
License Required: Vantage Tape Resource Option
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Daily or as needed
DSKRMMF
Submits batch job RMMFRPT to run the IBM DFSMSrmm Extract Utility. Batch job unloads the RMM control file files on volumes information to the Disk Imterval object flat file.
License Required: Vantage Tape Resource Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
DSKRMMV
Creates Disk Checkpoint file for VISRMMV object for IBM DFSMSrmm Volumes.
License Required: Vantage Tape Resource Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
DSKTLMSF
Submits batch job TLMSDSKF which creates the data for several Vantage SRM “files” object for TLMS support (Common Tape System Utility).
License Required: GMI TLMS
Resource Usage: High I/O
When to Run: Avoid high tape usage periods
How Often: Daily or as needed
DSKTLMSU
Submits batch job TLMSDSKU which uses the Common Tape System Utility to read the TLMS VMF and creates the Disk Interval data for Vantage SRM object for TLMS support.
License Required: GMI TLMS
Resource Usage: High I/O
When to Run: Avoid high tape usage periods
How Often: Daily or as needed
DSKTLMSV
Submits batch job TLMSDSKV which creates the data for several Vantage SRM “volumes” object for TLMS support (Common Tape System Utility).
License Required: GMI TLMS
Resource Usage: Moderate I/O
When to Run: Avoid high tape usage periods
How Often: Daily or as needed
DSKTMCF
Create a Disk Checkpoint file for Vantage SRM tape volume objects for CA 1 interface.
License Required: GMI CA 1
Resource Usage: High I/O
When to Run: Avoid high tape usage periods
How Often: Daily or as needed
DSKTMCV
Create a Disk Checkpoint file for Vantage SRM tape files objects for CA 1 interface.
License Required: GMI CA 1
Resource Usage: Moderate I/O
When to Run: Avoid high tape usage periods
How Often: Daily or as needed
DSKZARF
Creates Disk Checkpoint file for VISZDSNB object for ASG-Zara Files.
License Required: Vantage Tape Resource Option
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
DSKZARV
Creates Disk Checkpoint file for VISZARA object for ASG-Zara Volumes.
License Required: Vantage Tape Resource Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
DUPEDSNS
Creates LI object DUPEDSNS showing all duplicate named data sets found on primary disk storage. Include the object in your warmstart list.
License Required: Vantage Base System
Resource Usage: Low to moderate CPU and elapsed time
When to Run: Weekly or as needed, depend on if you using DTOCDUPS Y/Z instead of N/O
Note: For more information, see the description of the DTOCDUPS system parameter.

How Often: Object can be created during each DTOC scan (without using the script)
GRPSTATS
Creates LI object GRPCBS with statistics about all disk data sets on primary storage belonging to each application. Include the object in your warmstart list.
License Required: Vantage Base System
Resource Usage: High CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
HFSPDSE
Creates LI object HFSPDSE to show idle space (and other attributes) for HFS and PDSE data sets. Include the object in your warmstart list.
License Required: Vantage Base System
Resource Usage: Low to moderate I/O, CPU and elapsed time
When to Run: Any time
How Often: Weekly or as needed
MCAT
Submits batch job MCTBATCH which creates the data for several Vantage SRM object for MasterCat support.
License Required: GMI MasterCat
Resource Usage: Batch job has high I/O and elapsed time (unloads all catalogs, sorts, and reloads to a single VSAM cluster)
When to Run: Not prime shift
How Often: Weekly or as needed
MVDETAIL
Creates LI objects MVDETAIL and MVDSNS showing all multi-volume data sets and their segment details. Include the objects in your warmstart list.
License Required: Vantage Base System
Resource Usage: Low CPU and elapsed time
When to Run: Run only when you modify the default setting of sysparm DTOCMVDS from (Y) to (N).

Note: For more information, see the description of the DTOCMVDS system parameter.

How Often: Objects are created each DTOC scan (without using the script)
SCRIDMS
Submits batch job JCLIDMS which creates Vantage IDMSAREA,IDMSSDMCL,IDMSRECS object for IDMS interface.
License Required: GMI IDMS
Resource Usage: Batch job has low to moderate I/O
When to Run: Intervals throughout the day
How Often: Every 120 minutes or as needed
STK10058
Submits batch job STKJOBRE to run the STK SMCUUUI report/extract utility. Batch job creates flat files for VOLRPT data.
License Required: Vantage Tape Resource Option
Resource Usage: Batch job has moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Daily or as needed
STK10060
Submits batch job STKJOBVI to run the STK SMCUUUI report/extract utility. Batch job creates flat files for VTVRPT data.
License Required: Vantage Tape Resource Option
Resource Usage: Batch job has moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Daily or as needed
STKACS
Submits batch job ACSRPT to run the STK SLUADMIN report utility. Batch job creates the Disk Interval object flat files with Volume information.
License Required: Vantage Tape Resource Option
Resource Usage: Batch job has moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
STKACSX
Submits batch job ACSRPTX to run the STK SLUADMIN report utility. Batch job creates the Disk Interval object flat file with command DISPLAY ACS information in XML format. HSC 6.2 and higher is required.
License Required: Vantage Tape Resource Option
Resource Usage: Batch job has moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
STKVSM
Submits batch job VSMRPT to run the STK SWSADMIN report/extract utility. Batch job creates flat files for MVC, VTV, and MVC Pools Vantage SRM object.
License Required: Vantage Tape Resource Option
Resource Usage: Batch job has moderate I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed
TAPSTATS
Creates LI object TAPCBS with statistics about all tape data sets in each application using CA 1. Include the object in your warmstart list.
License Required: GMI CA 1, TLMS, or Vantage Tape Resource Option
Resource Usage: High I/O, CPU and elapsed time
When to Run: Not prime shift
How Often: Monthly or weekly
TMCDSNB
Creates LI object VISTMCM with DSNB usage for each volume CA 1. Include the object in your warmstart list.
License Required: GMI CA 1
Resource Usage: Moderate I/O and memory usage
When to Run: Run this only if you use Real Time (RT) access to the CA 1 Volumes object. In this case, run it after your daily TMC clean process has ended.
How Often: Daily
VNS12030
Creates LI object OBJ12030 to show DB2 Index Space Occupancy.
License Required: Vantage Database Option
Resource Usage: Moderate I/O, CPU and elapsed time
When to Run: After the RUNSTAT utility ends
How Often: Weekly or as needed
VSAMVVDS
Unloads VVDS records from all volumes to a flat file and then submits a job VVDSORT which sorts the records for Vantage SRM object.
License Required: Vantage Base System
Resource Usage: Moderate to high I/O, CPU and elapsed time
When to Run: Not prime shift
Weekly or as needed
ZFSDSNS
Creates Last Interval object OBJ11100 Mounted zSeries File Systems showing space and other attributes for zFS file systems.
License Required: Vantage Base System
Resource Usage: High CPU and elapsed time
When to Run: Not prime shift
How Often: Weekly or as needed

Run Scripts at Appropriate Times

To ensure that you are running the appropriate scripts at the appropriate times, start by identifying the scripts that you want to run. The list of available scripts in the previous section provides general and relative guidelines about the resources consumed by each script process and the suggested frequencies to run each script. Measure and assess the values for your needs and your specific installation. Many of the scripts provide configuration options that range from process everything to process a small subset. Then, identify any scripts that collide with each other and adjust the start times and frequencies.

Follow these steps:

Select the Automation and Logging folder in the object tree.
The Automation and Logging folder expands.
Click the Automation Script Schedules object.
The Automation and Script Schedules object is displayed.
Click the Filter icon.
The Filter dialog is displayed.
Create a filter with the following statement:
"Event Type" INCL sys/
This filter statement finds all the System scripts you currently have scheduled.
Click the Apply and Execute icon.
The Filter dialog closes and the Automation Script Schedules object is displayed with the filter applied.
Examine the Scheduled Run Date and Scheduled Run Time columns and mark any scripts that start at the time on the same date, or close.
You have identified the scripts with processing times that need to be updated to avoid resource conflicts.

After amending the processing times of your scripts that are scheduled to run concurrently, find the elapsed time of your system scripts to determine the proper spacing of start times.

Follow these steps:

Select the Automation and Logging folder in the object tree.
The Automation and Logging folder expands.
Click the System Script Activity Log object.
The System Script Activity Log object is displayed.
Click the Filter icon.
The Filter dialog is displayed.
Create a Filter with the following filter statement:
Number = VKG0903 OR Number = VKG0904
Click the Apply and Execute icon.
The Filter dialog closes and the System Script Activity Log object is updated with the filter applied.
Click the Sort icon and create a Sort.
The Sort dialog has the following information displayed in the Sort order pane with the Sort symbol arrow pointing down:
- Script Name
- Message Dt
- Time
Click the Apply and Exit icon.
The Sort dialog closes and the System Script Activity Log object is updated with both the filter and sort applied.

Note: The System Script Activity Log object shows only those entries from the current memory buffer. If you do not see your scripts, select Vantage Internal Management, System Activity, and then click the Vantage Messages object. In the Vantage Messages object select the menu option View, Mode and then Log, and apply the same filter and sort.
Compute and record the elapsed time for each script for reference when making the adjustments in the last step.

After identifying the elapsed time of your audit scripts, find the CPU usage for each script.

Follow these steps:

Select the Automation and Logging folder from the object tree.
The Automation and Logging folder expands.
Click the All Scripts Loaded object.
The All Scripts Loaded object is displayed.
Click the Filter icon.
The Filter dialog is displayed.
Create a Filter with the following filter statement:
"Event Type" INCL sys/
Click the Apply and Execute icon.
The Filter dialog closes and the All Scripts Loaded object is updated and displayed with only system scripts.
Scroll to the far right in the All Scripts Loaded object to find the CPU m-sec shift column, and sort the column in descending order by clicking on the column heading until the column contents are sorted that way or use the Sort icon.

To reduce the CPU usage of a high consumer, reduce the run frequency, specify configuration options that reduce the scope of processing, or both.

Note: For more information about configuration options that reduce the scope of processing, see INCLEXCL - Local PARMLIB Member.

Adjust the script start dates and times to distribute resource consumption as appropriate. Use the results from all of the previous steps and determine appropriate start times and frequencies for each script. Remember to run high resource consuming system scripts only as frequently as you plan to examine the results and make any needed corrections. Running these scripts frequently but routinely ignoring the results is a large waste of resources. Instead, leave these scripts without any scheduled times, and then fire the scripts when you are ready to do any cleanup that may be needed. When you are ready to make changes, use the System Script wizard to modify each script and assign the appropriate execution schedule.

Note: For more information about the System Script wizard, see Customize System Scripts.

Feedback

thumb_up Yes

thumb_down No