COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

You can give a mnemonic-name to the switch itself, but you must declare at least one STATUS
phrase for the switch because only the condition-name of the STATUS phrase can be used for
testing within the program. The mnemonic-name has no purpose other than to qualify the
condition-name.
You can code either the ON STATUS or the OFF STATUS phrase first, but you can use only
one of each phrase for each system-name.
Example 25 ON STATUS Phrase
SPECIAL-NAMES.
SWITCH-4 IS TRANSACTION-TRACE,
ON STATUS IS TRACING-TRANSACTIONS ...
...
IF TRACING-TRANSACTIONS
WRITE ...
File-Mnemonic Clause
The File-Mnemonic clause is, technically, a variant of the “system-name IS mnemonic-name”
clause, but its purpose is significantly different. It defines file-mnemonic to be either a name
that Binder or the linker uses to resolve an external reference in the Procedure Division (see CALL
(page 293) and ENTER (page 319)) or a name suitable for use in ACCEPT and DISPLAY statements.
The keyword FILE informs the compiler that the next token is either an operating system file name
or (in the Guardian environment) a DEFINE name.
system-file-name
is a partially or fully qualified operating system file name. It can be represented as a nonnumeric
literal (enclosed in quotation marks).
In the Guardian environment, system-file-name must be represented as a nonnumeric
literal if it has the same spelling as a COBOL reserved word or has the form
subvolume-name.file-name. If system-file-name consists of a single user-defined
word or begins with one of the characters in this table, the compiler recognizes it as a file
name without its being in quotation marks:
MeaningFirst Character
System-name qualifier\
Volume-name or process-name qualifier$
Special operating system file name qualifier#
In the OSS environment, system-file-name must have the syntax described for filename
in OSS Pathnames for OSS Files (page 714).
define-name-literal
is a nonnumeric literal that specifies the name of a DEFINE of type MAP. For information about
DEFINE names, see DEFINEs (page 593).
Configuration Section 109