CA 1 provides an External Data Manager (EDM) interface to allow other system software products to manage their own tapes. CA Disk is one such system. It is through this interface that the greatest amount of control with the least amount of risk is available. See the CA 1 guides for a complete description of the External Data Manager Interface. The advantages of using this method to control CA Disk-created tapes over any other methods are as follows:
When CA Disk is identified as an EDM to CA 1, any archive/backup tapes created by CA Disk will be managed by CA Disk (that is, CA Disk will inform CA 1 when to scratch the tape). CA 1 exempts these tapes from its normal processing. Any tapes created through sequential migrate--or UNLOAD to tape--processing is not considered externally managed, however, and is scratched by CA 1 based on the tape's expiration date.
A tape can be identified as externally managed by its expiration date (99365) and an indicator flag within the volume's TMC record. The actual expiration date of the tape is kept in the ARCHVOLS record within the FILES. Normally this is 1999365, if the default value of sysparm DYNEXPDT is used. If this is so, the date i scratched when the last data set on the tape expires. When CA Disk determines that all data o the tape has expired, it expires the tape through the EDM interface. Directly changing the expiration date for a tape must be done through the appropriate CA Disk commands, not through CA 1. Only when a tape is expired by CA Disk should the status within the TMC change.
The activation of EDM support is done in two parts: First, sysparm TMSCTLEX must be set to indicate to use the CA Disk EDM program as the tape management interface. Set this sysparm to ADSTH014. Second, CA Disk must be identified as the EDM within CA 1 This is accomplished by modifying the TMOEDMxx member of your CAI.PPOPTION data set. The easiest method of identifying CA Disk as an EDM is by program name. For example:
EDM=DISK,PGM=ADSMI002 EDM=DISK,PGM=ADSMI302
“DISK” is an example of an EDM name. Any name with 4 characters can be used.
ADSMI002 – The program that creates or expires tapes in all CA Disk processes .
ADSMI302 – For problem determination, Technical Support may ask you to add PET Tracing to your job (Program Event Tracing). So, this entry insures that the output tapes in the abended job will be EDM managed and will not expire prematurely.
Note: For more information on the External Data Manager Interface, see the CA 1 guides.
If you have previously created archive/backup tapes with CA Disk, you also need to change their status within the TMC to indicate that they are also externally managed. This action is required because CA Disk attempts to scratch the tapes through the EDM interface as soon as the sysparm TMSCTLEX is set.
Convert the CA 1 volume records currently in use by CA Disk to EDM management. Run a CA Disk LISTV to get a list of all the volsers currently in use. Then, set up the following utility to convert all of the fields for each volser as shown in this example setup:
//STEP1 EXEC PGM=TMSUPDTE //TMSRPT DD SYSOUT=* //SYSIN DD * VOL 123456,NODSN,NOCHAIN REP FLAG3=20 REP EDMID=DISK REP VOLSEQ=1 REP 1STVOL=HEXZEROS REP NEXTVOL=HEXZEROS REP PREVVOL=HEXZEROS REP EXPDT=PERM
“EDMID=xxxx” is the value specified for CA Disk in the TMOEDM00 member.
Note: If the conversion of existing tapes is not done properly, CA 1 begins issuing TMSTVEXT-08 messages. Circumvent this problem by executing the TMSUPDTE Utility, changing flag 3 to 20. For more information about this utility, see your CA 1 guides.
Procedures that are more detailed can be obtained from CA 1 Technical Support for the release of CA 1 you are running.
Other CA Disk sysparms, which control the data set name, expiration date, and catalog action of CA Disk tapes can be set as described in the following section. The expiration date on the internal label of an externally managed tape is not affected by the EDM facility.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|