|
- A RACF® operator command
must contain the RACF subsystem
prefix. A command such as the DISPLAY command could be entered on
the command line as follows:
#DISPLAY xxxx
Where:
- #
- specifies the subsystem prefix. The subsystem prefix specifies
that the RACF subsystem is
the processing environment of the command. The subsystem prefix can
be either the installation-defined prefix for RACF (1 - 8 characters) or, if no prefix
has been defined, the RACF subsystem
name followed by a blank. If the command prefix was registered with
CPF, you can use the MVS command D OPDATA to display it or you can
contact your system programmer.
If no subsystem prefix has been
defined, and the subsystem name is rac1, the same command
would be entered as follows:
rac1 DISPLAY xxxx
Note: If you need to find out what the subsystem prefix is, contact
your system programmer.
- xxxx
- specifies DISPLAY operands.
- Separate operands with commas. Do not specify commas before the
first operand or after the last operand.
For example, enter a DISPLAY
command with two operands as follows:
#DISPLAY xxxx,yyyy
- You can also separate operands with blanks. This practice is not
encouraged, however, because future releases might not allow this.
- The order in which you specify the operands on the command line
does not affect the command. For example: the commands #DISPLAY xxxx,yyyy and #DISPLAY yyyy,xxxx give
the same result.
- RACF commands entered as RACF operator commands must meet
the MVS restrictions on command length and operand content. A command
with intended mixed-case input cannot be entered as an operator command
because it is automatically translated to uppercase before it is sent
to RACF. In addition, command
messages and output from RACF to
the console are also translated to uppercase. When dealing with profile
names or fields requiring mixed-case characters, enter the command
as a TSO command, not as an operator command.
|