So, having restored all the systems we had backed up, I can now re-visit this.
<snip>
Is dfHSM defined as an EDM (External Data Manager) to dfRMM?
If not, there is a section in the dfHSM Installation and Customization Guide on
how to do this.
</snip>
Allan,
I can't find a dfHSM Installation and Customization Guide. I do have a
DFSMShsm Implementation and Customization Guide, but can't find anything in
there about making RMM an EDM.
It does however say things like "DFSMShsm invokes the EDGTVEXT exit to
communicate the status of empty tapes to DFSMSrmm" and I also fond "DFSMSrmm
uses the EDGDFHSM programming interface to release DFSMShsm tape volumes. The
interface between DFSMShsm and DFSMSrmm is automatically in place when you
install DFSMS, so you do not need to take any action to activate it or to call
it."
So that seems to say that RMM knows all about HSM, and there is no need to
define HSM to RMM. Can someone please confirm this assumption?
<snip>Please post the LV display for one of your DFHSM tapes. I'm guessing
it's retained with a VRS. </snip>
Tom,
Here you go: -
Volume . . . . . . : D30026 VOL1 volser : Rack number :
Media name . . . . : V3480 Status . . : MASTER
More:
Volume type . . . : PHYSICAL Stacked count . . . . . . : 0
Retention date . . : CYCL/99999 Expiration date . . . . . : 2015/138
Set retained . . . : NO Original expiration date . : 2015/138
Description . . . :
Data set name . . : 'HSM.MCDS.BACKUP.V0005355'
Media type . . . . : CST Release actions:
Label . . . . . . : SL Return to SCRATCH pool . : YES
Current version : Replace volume . . . . . : NO
Required version : Return to owner . . . . : NO
Density . . . . . : 3480 Initialize volume . . . : NO
Recording format . : 18TRACK Erase volume . . . . . . : NO
Compaction . . . . : NONE Notify owner . . . . . . : NO
Attributes . . . . : NONE Expiry date ignore . . . : NO
Availability . . . : VITAL RECORD Scratch immediate . . . : NO
Owner . . . . . . : HSM Owner access . . . . . . . : ALTER
Assigned date . . : 2015/138 Assigned time . . . . . . : 03:10:03
File 1 system ID . : MHZ3
Security name . . :
Classification . . :
Account number . . :
MVS use . . . . . . . . . : YES
Jobname . . . . . : HSM VM use . . . . . . . . . . : NO
Loan location . . : Last changed by . . . . . : *HKP
Previous volume . : Next volume . . . . . . . :
Volume access list : Access . . . . . . . . . . : NONE
User . . . . . . : User . . . . . . . . . . :
User . . . . . . : User . . . . . . . . . . :
User . . . . . . : User . . . . . . . . . . :
User . . . . . . : User . . . . . . . . . . :
User . . . . . . : User . . . . . . . . . . :
User . . . . . . : User . . . . . . . . . . :
Volume use count . : 1 Volume usage (Kb) . . . . : 28122
Capacity (Mb) . . : 200 Percent full . . . . . . . : 0
Create date . . . : 2013/063 Create time . . . . . . . : 16:54:30
System ID . . . . . . . . : MHZ3
Date last read . . : 2015/138 Date last written . . . . : 2015/138
Drive last used . : 157B
Volume sequence . : 1 Number of data sets . . . : 1
Data set recording . . . . : ON
Errors:
Temporary read . : 0 Temporary write . . . . . : 0
Permanent read . : 0 Permanent write . . . . . : 0
Actions pending:
Return to SCRATCH pool . : NO Initialize volume . . . . : NO
Replace volume . . . . . : NO Erase volume . . . . . . . : NO
Return to owner . . . . : NO Notify owner . . . . . . . : NO
Storage group . . :
In container . . . :
Move mode . . . . : AUTO Movement tracking date . . :
In transit . . . . . . . . : NO
Location: Current: Destination: Old: Required: Home:
---------- -------- ------------ -------- --------- --------
Name . . . : SHELF SHELF
Type . . . :
Bin number :
Media name :
Product details:
Product number . :
Level . . . . . :
Feature code . . :
I see that availability is VITAL RECORD - is that what you are referring to?
Thanks again. Vince.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
