Technical data

Using Files and Directories
10.1 Understanding Extended File Specifications Features
$ SET PROCESS /PARSE_STYLE=TRADITIONAL "
$ OPEN /WRITE FILE z.z.z.z
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special
characters \.Z\ #
$ SET PROCESS /PARSE_STYLE=EXTENDED $
$ OPEN /WRITE FILE z.z.z.z
%DCL-E-OPENIN, error opening
-RMS-E-CRE, ACP file create failed
%
-SYSTEM-W-BADFILEVER, bad file version number
! The volume is ODS-2.
" The parse style is set to TRADITIONAL.
# DCL returns an error message.
$ The parse style is set to EXTENDED.
% 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,
! subject to mount verification, file high-water
marking, write-back caching enabled.
$ SET PROCESS /PARSE_STYLE=TRADITIONAL "
$ CREATE a^<b.c
%DCL-W-PARMDEL, invalid parameter delimiter - check use of special
characters
\^\ #
$ SET PROCESS /PARSE_STYLE=EXTENDED $
$ CREATE a^<b.c
%CREATE-E-OPENOUT, error opening a^<b.c as output
-RMS-F-SYN, file specification syntax error %
!
The volume is ODS-5.
" The parse style is set to TRADITIONAL.
# DCL returns an error message for a syntax error.
$ The parse style is set to EXTENDED.
% RMS returns a different error message for the same syntax error.
Be Aware of Implicit File Name Output
Be wary of defaults when you allow utilities to create output files based on the
file name being processed. Be sure you know where a file is being placed so you
will not inadvertently try to place a file with an extended name on an ODS-2
volume.
The following examples show files being placed somewhere you might not expect:
• An error results if an application or a utility attempts to write an ODS-5
extended file name to an ODS-2 (DKA200:) volume; for example:
Using Files and Directories 10–7