Converting to DFSMSrmm from ASG-ZARA or AutoMedia

356 Converting to DFSMSrmm from ASG-ZARA or AutoMedia

end

exit(cc+mrc)

8.7.2 Other tape libraries

Whatever tape library is installed in your system, DFSMSrmm can support it

through a user interface that tells the library which volumes to return to scratch

status and which volumes must be ejected and moved to another storage

location.

With DFSMSrmm's reporting and command capabilities it is simple to build this

interface, using REXX, DFSORT, DFSMSrmm utilities, and TSO RMM

subcommands.

You must analyze what the vendor tape library requires as input for retention and

movement processing and then customize DFSMSrmm to provide the library

with the correct input.

Be sure to keep the vendor tape library catalog and the DFSMSrmm database

synchronized to avoid any mismatch that would cause rejection of tape mounts.

STK tape libraries

Below we provide you with a simple interface example between an STK Silo tape

library and DFSMSrmm to eject tapes that need to be moved to another location.

After running DFSMSrmm inventory management (storage location management

processing DSTORE), you can create a list of all volumes that are moving by

using DFSMSrmm commands. Follow these steps:

1. Use DFSMSrmm commands as shown in Example 8-3.

Example 8-3 RMM SEARCHVOLUME subcommands with specific destinations

RMM SV VOLUME(*) DESTINATION(LOCAL) CLIST(' ',' -')

RMM SV VOLUME(*) DESTINATION(REMOTE) CLIST(' ',' -')

RMM SV VOLUME(*) DESTINATION(DISTANT) CLIST(' ',' -')

RMM SV VOLUME(*) DESTINATION(my_loc) CLIST(' ',' -')

The resulting list, which is stored in the RMMCLIST data set, or the data set

prefix.EXEC.RMM.CLIST consists of VOLSERs only. The data set uses blocked,

Note: Unless you exploit the capability of APAR OW30790, and use a

pre-allocated RMMCLIST DD name, you can use only one TSO RMM

subcommand at a time, because each call to the CLIST option will

overwrite the data created before.

Chapter 8. Cutover to production 357

variable-length records, with a logical record length of 255. Where prefix is the

TSO user PROFILE PREFIX that the user has currently defined. If you have

specified NOPREFIX, DFSMSrmm allocates a data set using the RACF user

ID or the jobname, to avoid using EXEC.RMM.CLIST.

If you are using the TSO RMM subcommands in a batch job, you can set the

prefix in front of the TSO RMM subcommand. Example 8-4 shows sample

JCL.

Example 8-4 Using TSO RMM subcommands in a batch JOB

//RMMMOVE JOB ....

//STEP01 EXEC PGM=IKJEFT01

//SYSPRINT DD SYSOUT=*

//SYSTSPRT DD SYSOUT=*

//SYSTSIN DD *

PROF PREFIX(prefix)

RMM SV VOLUME(*) DESTINATION(my_loc) CLIST(' ',' -')

/*

2. Convert the list from variable-length records to fixed-length records.

HSC/MVS control statement syntax conventions: The control statement for

each utility program consists of a command (indicating the utility function)

followed by parameters, as applicable, in 80-character card-image records

(see the HSC/MVS Programmer's Guide, Volume 2 provided with the

product).

3. Edit this list and create an EJECT statement as shown in Example 8-5, which

can be used as input for the HSC utility.

Example 8-5 HSC EJECT statements

EJECT VOLSER( -

volser1 -

volser2 -

volser3 -

. . . . . . . -

) CAP(cap-list)

Please be aware that each single EJECT command causes an operator

interaction.

4. Run the HSC update utility, SLUADMIN (see the HSC/MVS System

Programmer's Guide, Volume 1 provided with the product).

358 Converting to DFSMSrmm from ASG-ZARA or AutoMedia

The HSC initialize cartridge utility (SLUADMIN)

Example 8-6 shows sample JCL that you can use to initialize cartridges with the

HSC SLUADMIN utility by using DFSMSrmm EDGINERS processing.

Example 8-6 Sample EDGINERS JCL

//JOBTINIT JOB (ACCOUNT),PROGRAMER

//*

//TINIT EXEC PGM=SLUADMIN,TIME=1440,PARM=MIXED

//TAPE DD UNIT=(580,1,DEFER),DISP=NEW

//* EDGINERS TAPE UNIT DD

//*

//SLSTAPE DD UNIT=AFF=TAPE INIT CARTRIDGES INIT TAPE

//* UNIT DD.

//SYSIN DD UNIT=VIO,SPACE=(TRK,1) EDGINERS CONTROL DATASET

//SLSPRINT DD SYSOUT=* UTILITY MESSAGES

//SYSPRINT DD SYSOUT=* EDGINERS MESSAGES

//SLSINIT DD *

INIT LABEL(SL) VOL(******)

/*

//SLSIN DD *

//*

* WHEN USING THE DFSMSrmm TAPE INITIALIZATION PROGRAM EDGINERS, YOU

* MUST SPECIFY THE 'PROGRAM' PARAMETER ON THE INIT CARTRIDGES

* CONTROL STATEMENT.

INITIALIZE CAP(000) PROGRAM(EDGINERS) OPTION(SCRATCH)

/*

The HSC scratch conversion SLUCONDB utility

The HSC scratch conversion SLUCONDB program is provided to generate

scratch transactions from DFSMSrmm. SLUCONDB calls the routine

SLUDRRMM to read the DFSMSrmm report extract file if RMM is specified in the

EXEC JCL statement. This program utilizes the DFSMSrmm EDGRVEXT macro

to map the layout of the extract file. The following list shows the fields that are

used:

 RVTYPE

 RVVOLSER

 RVLCDATE

 RVNAME

 RVSTATUS

 RVEXPDT

 RVEXPDTO

 RVLABEL