CONSOLxx and PFKTABxx let you define the PFKs for all
your MCS, HMCS or SMCS consoles on a system.
For each console, you activate a PFK table — a table that your installation
has defined — by specifying the PFK table name on the CONSOLE statement.
The PFK table resides, optionally with PFK tables for other consoles,
in a PFKTABxx Parmlib member.
Using entries in the PFK table, you can:
- Assign one or more commands to a PFK for the console
You can
associate the text of one or more commands with a PFK. Later, when
an operator presses this PFK on the console, the commands are entered
into the system.
- Assign one or more other PFKs to a PFK for the console
You
can associate the commands assigned to other PFKs with a PFK.
To create PFK table entries, use the following keywords in the
PFKTABxx member of Parmlib:
- TABLE
- Defines
the table to contain PFKs for the console. You associate this table
with the console by specifying the table name on the PFKTAB keyword
of the CONSOLE statement.
- PFK
- Defines
the program function key.
- CMD
- Defines the command or commands to be assigned
to the PFK.
- KEY
- Associates
the PFK you define with another key or list of keys.
- CON
- Defines whether
the PFK you define operates in conversational or nonconversational
mode.
Conversational or nonconversational mode applies to commands defined
to a PFK. In nonconversational mode, the commands associated with
a key are entered immediately when the operator presses the key on
the console. In conversational mode, pressing a PFK causes the command
to appear in the entry area, but no enter action takes place. Operators
can change, enter, or cancel the command according to their requirements.
In conversational mode, the cursor normally appears
under the third non-blank character when the command is in the entry
area. If you want the cursor to appear in a different location, when
you define the command, type an underscore immediately to the right
of the character under which the cursor is to appear. The system deletes
the space occupied by the underscore in the actual command. For example,
if you add the following entry to a PFK table:
PFK(5) CMD('D U,L=_XXX') CON(Y)
pressing PFK 5 causes the following to appear in the entry area:
D U,L=XXX
If you want an underscore to appear in the command,
use two underscores. They are treated as one underscore, and are not
used for cursor placement. For example, if the PFKTAB table contains:
PFK(17) CMD("E_XXXXXXXX,SRVCLASS=BATT__HI"),CON(Y)
when you press PFkey 17, the entry area will contain
E XXXXXXXX,SRVCLASS=BATT_HI
Selector pens also use the definitions in PFK tables.
When you have created your PFK tables in PFKTABxx, you can associate
them with the consoles in your configuration. Specify the following
keyword on the CONSOLE statement to associate a PFK table with the
console:
- PFKTAB
- Defines the name of the PFK table defined
in PFKTABxx that contains PFKs for this console. The name must be
the same as the name for TABLE in PFKTABxx.
When you have defined the PFK tables for all your consoles, you
can activate the PFKTABxx member that contains the table definitions
at IPL. Use the following keyword on the INIT statement of CONSOLxx
to activate PFKTABxx:
- PFK
- Defines
the name of the PFKTABxx member that contains the PFK definition tables
for your consoles. For PFK you specify a value that corresponds to
xx in PFKTABxx. If you specify NONE for PFK, the system uses IBM® defaults for console PFKs.
If you do not specify PFKs for your consoles or if the system does
not find the PFK parameter, it issues the message:
IEA180I USING IBM DEFAULT PFK DEFINITIONS. NO PFK TABLES REQUESTED.
IBM supplies
defaults for PFKs 1 through 8 in IEESPFK in SAMPLIB.
In a sysplex, PFK settings have system scope; they apply only to
the consoles on the system where they are defined.