Syntax rules for CONSOLxx

Use the general syntax rules listed in General syntax rules for the creation of members with the following exceptions and additions:

• In shared mode, you can define up to 100 consoles (including the system console) within a CONSOLxx member. The maximum number of consoles within a system or sysplex is 99, plus one system console for each system.
• In distributed mode, you can define up to 251 consoles (including the system console) within a CONSOLxx member. The maximum number of consoles per system in the sysplex is 250 and 99 of which can be concurrently active, plus one system console for each system.
• Data must be contained in columns 1-71; the system ignores columns 72-80.
• Comments can appear in columns 1-71 and must begin with /* and end with */.
• You do not need to code delimiters between parameters; you can use either blanks or commas between parameters.
• One or more blanks can precede or follow the statement types (CONSOLE or INIT, for example).
• At least one blank must immediately follow the statement types (INIT, DEFAULT, HARDCOPY, and CONSOLE).
• Parameter values must be set off by parentheses. If you code multiple values on certain keywords, separate the values with a comma. Some keywords will allow you to separate multiple values with a blank. See the keyword documentation for specific syntax.
• Do not use blanks in the middle of a keyword, in the middle of a value, or between the parameter and the left parentheses before the value.
• A statement type must be the first data item on a record.
• You can code comments before any statement type.
• A statement type continues to the next statement type in the member or until the end of the member.
• System symbolics can be used anywhere within the CONSOLxx member.
• For the CONSOLE statement, use the following rules:
  • On each CONSOLE statement, DEVNUM is required and must be the first parameter.
  • Any values you specify for the NAME parameter on the CONSOLE statement must be unique across the sysplex.
  • Do not use a name on the NAME parameter that might be confused with a device number. For example, the console name BEAD is not recommended, since it might be confused with device number X'BEAD'.

When you define consoles within a sysplex, note the different console constraints in shared mode and distributed mode shown in Table 1.