SUBCONFIG Directory Statement

Purpose

The SUBCONFIG statement starts a subconfiguration entry. This entry contains a set of directory statements in a multiconfiguration virtual machine definition that are specific to one of its virtual machine instances within the SSI cluster.

How to Specify

No additional operands are allowed after the id. If you specify extra operands, DIRECTXA produces an error message and the directory will not be updated.

Operands

id

defines the virtual machine's 1- to 8-character SUBCONFIG ID. LOGNxxxx, LOGLxxxx, LOGVxxxx, LOGNSYSC, LOGNSYSG, SYSTEM, and SYSTEMMP are reserved for CP use.

The SUBCONFIG ID cannot be the same as a user ID specified on an IDENTITY statement or USER statement.

You should not assign SUBCONFIG IDs that are system keywords (such as command names, command operands, or 1- to 4-digit user IDs that could be spool IDs). Assigning system keywords as IDs can cause unpredictable results. For a list of restricted user IDs, see Restricted User IDs.

You should not assign SUBCONFIG IDs that contain colons (:), periods (.), semicolons (;), or slashes (/). These characters are used, or might be used in the future, as delimiters in several CP commands that also take a user ID as a parameter. Results are unpredictable when these commands are entered with a SUBCONFIG ID containing any of these delimiter characters.

Translation test tables in HCPTBL allow only the following characters in SUBCONFIG IDs:

alphabetics

A-Z

numerics

0-9

The following, comma-delimited characters are also allowed:

@, #, $, _ (underscore), - (hyphen)

Note: It is recommended that the characters @, #, ¢, and " not be used in the id because the system, by default, assigns these characters as logical line editing symbols. For more information, see Logical Line Editing Symbols.

You can override the translation tables in HCPTBL. For more information, see TRANSLATE_TABLE Statement.

Usage Notes

1. The SUBCONFIG statement is used in combination with the IDENTITY and BUILD statements to specify a multiconfiguration virtual machine definition. For more information, see IDENTITY Directory Statement and BUILD Directory Statement.
2. If duplicate specifications exist in an identity entry and its subconfiguration entry, the specification in the subconfiguration entry overrides the one in the identity entry. Refer to the individual statement descriptions for specific override rules.
3. The ID on a SUBCONFIG entry must match the ID specified on a BUILD statement. SUBCONFIG IDs that are not referenced by BUILD statements are not allowed.
4. A null SUBCONFIG definition is allowed. This enables a multiconfiguration virtual machine instance to be logged on to different members in the SSI cluster simultaneously by using just the statements in the identity entry.
5. The following statements are not allowed within a subconfiguration entry:
   • ACCOUNT
   • ACIGROUP
   • APPCPASS
   • AUTOLOG
   • BUILD
   • CLASS
   • CPU
   • D80NECMD
   • INCLUDE
   • IOPRIORITY
   • IUCV
   • LOGONBY
   • MACHINE
   • NAMESAVE
   • NOPDATA
   • POOL
   • POSIXGLIST
   • POSIXINFO
   • POSIXOPT
   • STDEVOPT
   • XAUTOLOG
6. The following OPTIONs are not allowed within a SUBCONFIG definition:
   • ACCT
   • APPLMON
   • CFUSER
   • CFVM
   • CHPIDVirtualization
   • COMSRV
   • CRYMEASURE
   • DEVINFO
   • DEVMAINT
   • DIAG88
   • DIAG98
   • D84NOPASS
   • IGNMAXU
   • LKFAC
   • LNKEXCL
   • LNKNOPAS
   • LNKSTBL
   • MAINTCCW
   • NETACCOUNTING
   • NETROUTER
   • RMCHINFO
   • SETORIG
   • STGEXEMPT
   • SVMSTAT