|
What version of HSM are you using? Prior to V2.1, EOF on the cache
files was not set correctly which prevented cache files from being
viewed (typed, etc.). This problem was most likely introduced in
V2.0/V2.0A. This problem did not interfere with unshelving. Here
is a sample DUMP of one of these cache files:
Dump of file DKB500:[HSM_CACHE]AA.A$8447907406;1 on 8-OCT-1996 16:06:10.55
File ID (77,1,0) End of file block 0 / Allocated 3
File Header
Header area
Identification area offset: 40
Map area offset: 100
Access control area offset: 128
Reserved area offset: 255
Extension segment number: 0
Structure level and version: 2, 1
File identification: (77,1,0)
Extension file identification: (0,0,0)
VAX-11 RMS attributes
Record type: Undefined
File organization: Sequential
Record attributes: <none specified>
Record size: 0
Highest block: 3
--> End of file block: 0
--> End of file byte: 0
If this is what you are seeing, you might want to try a SET FILE/END
on the cache file and retry your copy.
Barb
|
|
I don't remember the version of HSM, but that's right there is no
Problem with unshelving. I will ask to the customer to try "Set file/end", but
i can't give you the result before 14-apr-97, because he is to DECUS and after
that in Holidays.
Thank's for your quick answer.
Regis..;
|