Appendix BConfiguration Files
is not included, SNAplus2 uses the default value of MEDIUM. The optional parameters description and pool_name are also not included.
[define_lu_0_to_3] lu_name = LU$01 nau_address = 1 pu_name = PU2
lu_model = 3270_DISPLAY_MODEL_2
B.2.3 Subrecord Format
Some configuration records include data whose format can vary between instances of that record type. For example, the [define_cos] record includes a variable number of node rows and TG rows. To handle this variability, the variable data is specified in optional subrecords. This means that a record consists of a series of parameters common to all instances of that record type, followed by subrecords containing the variable data.
A record that contains one or more subrecords is defined as follows:
[command_name] parameter_name = value
.
.
parameter_name = value
{subrecord_name} parameter_name = value
.
.
parameter_name = value
{subrecord_name} parameter_name = value
.
.
parameter_name = value
The subrecord_name must be enclosed in braces. It is followed by a series of parameter entries associated with this subrecord, each on a separate line.
All the parameters associated with the command_name (and not with a subrecord) must be listed after the command_name and before the first subrecord_name; all the parameters associated with a particular subrecord_name must be listed after that subrecord_name and before the next subrecord_name, if any, or the next command_name. However, the order of individual parameters within a subrecord is not important. For more information, see Section 1.1.2, Parameter Syntax Used for Administration Commands.
B.3 Changes Made to the Configuration Files by the Motif Administration Program
When you use the Motif administration program to configure parameters, the Motif program updates the node and domain configuration files. The entries in the configuration file may differ from what you entered on the Motif screens in the following ways:
•If you enter a name on a Motif screen using fewer characters (or fewer hexadecimal bytes) than allowed for that name, SNAplus2 pads the name with blank characters (or expands the hexadecimal value) to make the length equal to the maximum length allowed (or full hexadecimal width) for that name. For example, if you enter Node1 for the node_name parameter (which allows 128 characters) when you are defining a node, SNAplus2
630
