In the MUF_CONFIG Dynamic System Table, one row exists for nearly all Multi-User startup options and console API commands that are not represented in another Dynamic System Table. For example, since FLEXPOOL is reflected in the MUF_OPTIONS table, the first or any changes to FLEXPOOL do not exist in MUF_CONFIG.
The only rows that exist in this table are those that have been provided by the user. If a user does not provide an option such as FORCE_NO_64BIT YES, it is not in the table. The user can deduce that missing items are the default values.
Because users can set the same item many times in a MUF execution, the last value for that item is the only one saved, allowing this table to have a reasonable number of records.
The key of the table is the MUF_NAME and the CONFIG_COMMAND.
Some console commands are excluded, including ?MEM, ZAP and DISPLAY.
Because the key fields are required to be unique, no command exists in this table that violates this rule.
The following Multi-User startup options and console-like commands can appear in this table:
The MUF_CONFIG (MCF) table has three columns with the following characteristics:
|
Column Name |
SQL Data Type |
Nullable |
Description |
|---|---|---|---|
|
MUF_NAME
|
CHAR(8) |
No |
Logical name for this MUF. |
|
CONFIG_COMMAND
|
CHAR(25) |
No |
The configuration command entered by the user, up to field maximum. The command is left justified with blanks padded on the right. One or more blanks between the command and operands are removed. |
|
CONFIG_PARMS
|
CHAR(65) |
No |
The operand or operands entered by the user, up to field maximum. The operand is exactly as the user specified it, to the 65-byte limit. One or more blanks between the command and operands are removed. |
|
Copyright © 2014 CA.
All rights reserved.
|
|