General User Release Notes
3.18 Documentation Corrections
Examples of TRADITIONAL and EXTENDED styles on an ODS-2 volume:
Disk AABOUT$DKA200:, 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, [1] subject to mount verification, file high-water
marking, write-back caching XQP enabled, write-through XFC caching enabled.
$ SET PROCESS /PARSE_STYLE=TRADITIONAL [2]
$ OPEN /WRITE FILE z.z.z.z
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special
characters \.Z\ [3]
$ SET PROCESS /PARSE_STYLE=EXTENDED [4]
$ OPEN /WRITE FILE z.z.z.z
%DCL-E-OPENIN, error opening
-RMS-E-CRE, ACP file create failed [5]
-SYSTEM-W-BADFILEVER, bad file version number
1. The volume is ODS-2.
2. The parse style is set to TRADITIONAL.
3. DCL returns an error message.
4. The parse style is set to EXTENDED.
5. DCL allows the file name, but XQP returns an error.
Examples of different error messages for the same syntax error:
$ SHOW DEVICE DKA500:/FULL
Disk AABOUT$DKA500:, device type RZ25 Disk, is online, allocated, deallocate
on dismount, mounted, file-oriented device, shareable.
Error count 0 Operations completed 155
.
.
.
Volume Status: ODS-5, [1] subject to mount verification, file high-water
marking, write-back XQP caching enabled, write-through XFC caching enabled.
$ SET PROCESS /PARSE_STYLE=TRADITIONAL [2]
$ CREATE a^<b.c
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special
characters
\^\ [3]
$ SET PROCESS /PARSE_STYLE=EXTENDED [4]
$ CREATE a^<b.c
%CREATE-E-OPENOUT, error opening a^<b.c as output
-RMS-F-SYN, file specification syntax error [5]
1. The volume is ODS-5.
2. The parse style is set to TRADITIONAL.
3. DCL returns an error message for a syntax error.
4. The parse style is set to EXTENDED.
5. RMS returns a different error message for the same syntax error.
3.18.5.6 Performing Image Backups to Disk
In section 11.15.3, the following note should be appended to the end of the section:
BACKUP does not preserve GUID signature during image restore operation of
the system disk on Integrity server systems. During restore, BACKUP calls
SETBOOT to create a new GUID signature. Hence, during image restore
operation BACKUP does not restore the original GUID signature, rather it
creates a new GUID signature. As a result of this, Integrity servers system does
not boot automatically from a disk created through an image restore operation.
General User Release Notes 3–15
