FILE SYSTEM CHANGES IN OpenVMS V8.4

More documents

Recommendations

Info

ANALYZE /DISK /REPAIR– $ analyze/disk checks consistency of symlink attributes/flags• Checks if dir entry flag DIR$V_SPECIAL corresponds to File Header file orgFAT$C_SPECIAL• Checks version limit = 1 for symlink file– /REPAIR „upgrades‟ V8.3 symlink entry to <strong>V8.4</strong> entry• This is recommended.$analyze/disk/repair $10$DKB200:…%ANALDISK-W-BADSYMENTRY, directory entry for SYM_ON_83. in directory(61531,39558,0) example.link does not match symlink attribute in fileheader…40© Copyright 2010 Hewlett-Packard Development Company, L.P.
RMS: SYML<strong>IN</strong>KS AS LOGICAL NAMES- Translates the first element of an absolute pathname- Equivalence string in the path is substituted in the path if thetranslation succeeds.- Logical Name can be a search list.41© Copyright 2010 Hewlett-Packard Development Company, L.P.
Page 1: FILE SYSTEM CHANGES INOpenVMS V8.4S
Page 7 and 8: V8.4 Solution: Use new [NO]DATA key
Page 9 and 10: V8.3 Limitations and V8.4 Solutions
Page 11 and 12: V8.3 limitations and V8.4 Solutions
Page 13 and 14: V8.4: Now we can…-Free-up „oran
Page 15 and 16: 2 TB support15© Copyright 2010 Hew
Page 17 and 18: V8.4: 2TB volumes- Device drivers a
Page 19 and 20: 2 TB on older VMS version- Older VM
Page 21 and 22: SYMLINKENHANCEMENTS21© Copyright 2
Page 23 and 24: About symlinks- Symbolic link, syml
Page 25 and 26: Symlinks on OpenVMS- Available star
Page 27 and 28: Symlinks on OpenVMS27© Copyright 2
Page 29 and 30: Symlink file attributes$ dir /full
Page 31 and 32: V8.3 symlink limitations•Implemen
Page 33 and 34: Programming interface changes- No c
Page 35 and 36: V8.3 Metadata limitation•No symli
Page 37 and 38: V8.3 False AUDIT ALARM- Only File H
Page 39: COMPATIBILITY: V8.3, V8.4 SYMLINKSA
Page 43 and 44: RMS: SYMLINKS WILDCARD CONTROL- In

FILE SYSTEM CHANGES IN OpenVMS V8.4

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?