End of support This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Control card syntax

Use the following information to create your control cards:

Guidelines

The following list describes guidelines for specific control card parameters:

  • The DELETE keyword begins a specification. All parameters preceding the next DELETE keyword or the end of the input file are part of the specification.
  • Parameters can be on the same line or separate lines. There is no line continuation character.
  • Parameters can start in any column.
  • Comments must be on separate lines. A comment must have an asterisk in column 1.
  • Blank lines are allowed.

Name masking

All MainView SRM name masks can be used with the DSN parameter. These mask characters are fully described in Using-MainView-SRM-products. Briefly, the mask characters are as follows:

 

%

Any numeric character

?

Any character except period (.)

/

Any number of characters, to the end of a name

*

Any number of characters in a single name qualifier

**

Any nonzero number of name qualifiers

SMHSMUTL does not support the use of MainView SRM variables.

Messages

SMHSMUTL issues the following messages to SYSOUT (SMHSMPRM is the parameter processing program in SMHSMUTL):

SMHSMPRM REQUIRED PARAMETER MISSING: parameter
SMHSMPRM INVALID PARAMETER: parameter
SMHSMPRM DUPLICATE PARAMETER: parameter
SMHSMPRM INVALID VALUE FOR PARAMETER: parameter
SMHSMPRM CDS=MCDS/BOTH NOT ALLOWED WITH BAKDAYS
SMHSMPRM CDS=BCDS ONLY VALID WITH BAKDAYS
SMHSMPRM MAXIMUM OF 3140 DELETE STATEMENTS REACHED

Job required for the SMHSMUTL utility

In the following JCL, STEP10 executes SMHSMUTL to generate DFSMShsm control cards; STEP20 executes TSO in batch to have DFSMShsm process the cards.

The ddnames are defined as follows:

  • STEPLIB specifies the library that contains MainView SRM load modules. If the MainView SRM load modules have been added to the LNKLST, this STEPLIB DD statement can be removed.
  • BCDS specifies the DFSMShsm backup control data set.
  • MCDS specifies the DFSMShsm migration control data set.
  • HSMCMD specifies an output data set for the generated control cards.
  • SYSIN specifies the input data set containing control cards for SMHSMUTL.
//STEP10     EXEC   PGM=SMHSMUTL,REGION=2M
//STEPLIB      DD   DSN=EMP.?prefix.BBLINK,DISP=SHR
//SYSPRINT     DD   SYSOUT=*
//BCDS         DD   DSN=dfsmshsm.backup.control,DISP=SHR
//MCDS         DD  DSN=dfsmshsm.migration.control,DISP=SHR
//HSMCMD       DD  DSN=&&HSMOUT,DISP=(NEW,PASS),
//                  SPACE=(TRK,(10,10)),UNIT=SYSDA,
//                   DCB=(LRECL=80,BLKSIZE=13680,RECFM=FB)
//SYSIN        DD  *
DELETE DSN=**.TRAN* CDS=MCDS MIGDAYS=20
/*
//STEP20     EXEC  PGM=IKJEFT01
//SYSTSPRT     DD  SYSOUT=*
//SYSTSIN      DD  DSN=&&HSMOUT,DISP=(OLD,DELETE)

Examples

The following examples show syntax for the SMHSMUTL batch program:

 

Command

Result

DELETE CDS=MCDS
  DSN=**.SRCHFOR./ REFDAYS=10

Delete migration entries for search-results data sets after 10 days of not being used.

DELETE
  CDS=MCDS
  DSN=AP*.**.TRANS**
  CREDAYS=90

Delete migration entries for accounts-payable-transaction data sets 90 days after creation.

DELETE CDS=BOTH DSN=/ MIGDAYS=180

Delete all backup and migration entries 180 days after migration.

DELETE CDS=BCDS
  DSN=GLYTD*.**.UPD**
    BAKDAYS=20 KEEPBACKV=5

Delete all but 5 backup versions of genera- ledger-update data sets 20 days after backup.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*