Case-sensitive processing means that an environment distinguishes
and handles characters as either uppercase or lowercase:
FILE1 is
not the same file as
file1. The availability of case-sensitive
processing depends on the environment:
- Shell
- Case-sensitive. In the file system, you can use mixed-case path
names.
- ISPF
- To issue a TSO/E command with a z/OS UNIX path name and
get case-sensitive processing of the path name, enter the command
on a command line that supports mixed-case processing, for example
the Command Processor panel (usually ISPF option 6). Some ISPF option
panels convert the command and file name to uppercase before they
are processed.
The default ISPF edit profile usually folds to
uppercase the data you enter in a file. To prevent this, type caps
off on the command line before you begin working in the file.
After you enter caps off, it remains in your profile.
If
you are working on a file and realize that you have been typing in
uppercase when you really wanted lowercase, you can change the contents
of the file to all lowercase. Type this on the command line:
c all p'>' p'<'
- TSO/E
- Case-sensitive.
Follow the syntax rules of the command you are using. For instance,
make sure to enclose a path name in single quotation marks when using
commands such as ALLOCATE, OPUT, and so on.
- JCL
- Case-sensitive.
You can specify z/OS UNIX files
in DD statements by giving the absolute path name (no relative path
names) and enclosing the names in single quotation marks. Be careful
to keep JCL keywords such as DD, PATH, and so on, in uppercase.
Note: Traditional MVS™ utilities
may define their own requirements for allowing mixed-case file names
to be specified as input (as compared with the rules for specifying
mixed-case file names on DD statements in JCL). For example, you need
to use the binder's CASE=MIXED option if you want to bind a load module
into the file system and give the load module a lowercase name.