BrightStor CA-1 Tape Management - SupportConnect

CA-1 Product Documentation ChangeDATE: March 7, 2001RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Changes to External Data Manager InterfaceDESCRIPTION/DISCUSSION: CA-1 APAR LO87299, which will be included in Service Pack 3, introduceschanges to the External Data Manager (EDM) interface. After upgrade of CA-1 5.2 to Service Pack 3, thefollowing changes apply to the External Data Manager interface and may require a modification of existingEDM definitions.RESOLUTION: The functionality of the EDM interface was enhanced to prevent one EDM from expiringanother EDM's tapes in case the EDM databases are not synchronized correctly with the TMC. The EDMrules defined in PPOPTION member TMOEDMxx are now verified not only during tape creation, but alsowhen tapes are released from EDM control.Module TMSTMSTV, before expiring an EDM volume and turning the TMETMS flag on (FLAG2 bit x'01' -"deleted by CA-1, CA-11 or EDM"), now retrieves the EDM definitions to verify that the releasing EDMactually owns the volume being released.TMSTMSTV determines the EDMID of the releasing EDM using the following parameters:JOB - Job name of the executing job which releases the volumePGM - Program name of the executing programDD - Dummy ddname TMSEDMSCDSN - Data set name from the TMC volume record (no DSN is passed from the EDM)The obtained EDMID is compared to the one in the TMC record. Only if they are equal is the volume allowedto be expired. This means that job name and program name can be used to identify the releasing EDMand to prevent an EDM volume from being expired by a different EDM by mistake.Clients will need to ensure that their existing EDM definitions are still valid in this context and allow for acorrect, unique EDMID assignment. Changes will be required if:1. the JOB or PGM parameter is used and the creating job/program is different from the releasingjob/programor2. the DD parameter is usedPDC#: LI89532