Technical data
Using Files and Directories
10.1 Understanding Extended File Specifications Features
10.1.2 Setting Users’ Expectations of Extended File Specifications
A system manager can help users become accustomed to Extended File
Specifications by explaining the differences between ODS-2 and ODS-5 file
names. These differences become most apparent when users change from ODS-2
to ODS-5 styles.
If you pass the following usage notes along, users might find them helpful. These
notes are divided into the following categories:
• New Extended File Specifications characteristics
• ODS-2 and ODS-5 used together
• Architecture-related notes
10.1.2.1 New Extended File Specifications Characteristics
The following notes discuss issues related to new Extended File Specifications
characteristics that are unfamiliar to users.
Be Aware of Volume Structure
Make sure you know whether a disk is an ODS-2 or ODS-5 volume so that you
can place ODS-5 files on ODS-5 volumes.
You can display the type of volume by entering commands similar to the following:
$ SHOW DEVICE DKA500:/FULL
Disk AABOUT$DKA500:, device type DZ25 Disk, is online, allocated, deallocate
on dismount, mounted, file-oriented device, shareable.
Error count 0 Operations completed 155
.
.
.
Volume Status: ODS-5, subject to mount verification, file high-water
marking, write-back caching enabled.
$ SHOW DEVICE DKA200:/FULL
Disk AABOUT$DSA200:, device type RZ25 Disk, is online, allocated, deallocate
on dismount, mounted, file-oriented device, shareable.
Error count 0 Operations completed 232
.
.
.
Volume Status: ODS-2, subject to mount verification, file high-water
marking, write-back caching enabled.
After each command, the Volume Status: that is displayed indicates whether
the volume is ODS-5 or ODS-2.
Do Not Use Extended File Names on ODS-2 Volumes
You cannot create a file with an ODS-5 extended file name on an ODS-2 volume.
In the following example, DKA200: is an ODS-2 volume, and the parse style is
EXTENDED, which causes RMS to return an error message.
$ SET DEFAULT DKA200:[TEST]
$ CREATE x.x.x.x
%CREATE-E-OPENOUT, error opening DKA200:[TEST]X^.X^.X.X; as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILEVER, bad file version number
Using Files and Directories 10–3