search cancel

How to avoid on multiple delete commands multiple job be submitted?

book

Article ID: 134683

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

During an operation to delete thousands files, archives etc., the VANTAGE STC generated more than 50,000 sysouts resulting in JES2 resource shortages.  In addition, the purges of these sysouts (intercepted by TWS) have resulted in the filling of the event dataset of TWS and in the loss of events as job ends.


Is there a way to prevent VANTAGE from creating so many sysouts ?

Environment

Release : 14.0

Component : CA Vantage Storage Resource Manager

Resolution

The following link explains the Model JCL feature which should be used in such case:

https://docops.ca.com/ca-vantage-storage-resource-manager/14-0/en/configuring/configuring-ca-gmi/configure-the-jcl-model-list-feature

 

In summary, define into the Ca Vantage User PARMLIB a new member named JCLMLIST. 

 

Here is how to proceed.

Refer to the sample provided into CCTUSAMP(JCLMLIST) and keep only the column definition. Be sure to not have numbering on the right side from column 72 to 80 into it.


Here a sample how it looks like:

DMSIXUPDIXUPDATE DELETE           .YOUR.VANTR14.JCLLIB DMSINDEX

The member name start in column 1 and is 8 characters long. The description start in column 9 and is 19 characters long. The data set name start in column 28 and is 44 characters long. The pattern start in column 72 and is 8 characters long. A full qualified object name or pattern should be listed in column 72 - CA Vantage pattern matching characters can be used. Then create into your Vantage JCLLIB a Ca disk member (DMSIXUPD for example) containing such JCL: %%INCLUDE MEMBER=DMSJCARD //*-------------------------------------------------------------------* //* THIS MEMBER CONTAINS THE SKELETON JCL FOR THE CA DISK ACTION * //* CUSTOMIZE IT FOR YOUR INSTALLATION NEEDS * //* DO NOT DELETE * //*-------------------------------------------------------------------* //IXUPDATE EXEC IXUPDATE //SYSIN DD * //*REPEAT* DELETE DSN=%%DMSDSNAM%% //*REPEATEND* Then verify that into that library the job card member DMSJCARD exists. If not, please create a job card for using Ca Disk. Notice that a JCCLIB ORDER could be required and defined. Once done, right click on the object tree entry for Ca Disk Dsnindex and select Model JCL. Once open execute the view on the top left section to get the Ca Disk JCL member entry name from JCLMLIST. Double click on the line displayed with the Ca Disk member name to expand the JCL on the right side. Then still on the left side but on the second section, select the entries to delete from the DSNINDEX and perform a drag and drop on the right side above the JCL DELETE command to get all delete data sets commands created. 

Select the submit icon when the substitution satisfies your needs and immediate or defer execution. 

Look at the output on the host side.