Syntax rules for BPXPRMxx

When customizing BPXPRMxx, these rules apply:
  • Statements that contain limiting keywords (like MAXUIDS, which limits the number of concurrent z/OS® UNIX users), should not be duplicated in the same BPXPRMxx member. You can have duplicates of limiting keywords across BPXPRMxx members, but only the last occurrence is used. Resource defining keywords (like MOUNT, which specifies a file system that z/OS UNIX is to logically mount onto the root file system or another file system) are cumulative. Resource defining keywords can be duplicated in the same BPXPRMxx member. Each time you specify a resource defining keyword, its value is added to the previous values.
  • If a statement that has a default is omitted, the default is used.
  • Use columns 1 through 71 for data; columns 72 through 80 are ignored.
  • Enter one or more statements on a line, or use several lines for one statement.
  • Use blanks as delimiters. Multiple blanks are interpreted as a single blank. Blanks are allowed between parameters and values; for example, MAXPROCSYS(500) and MAXPROCSYS (500) are allowed and have the same meaning.
  • Comments can appear in columns 1-71 and must begin with /* and end with */.
  • Enter values in uppercase, lowercase, or mixed case. The system converts the input to uppercase, except for values that are enclosed in single quotation marks, which are processed without changing the case.
  • These values require single quotation marks and are the only ones that are allowed to be in single quotation marks:
    • STEPLIBLIST
    • USERIDALIASTABLE
    • FILESYSTEM in the ROOT, MOUNT, and ALTROOT statements
    • MOUNTPOINT in the MOUNT and ALTROOT statement
    • PARM in the FILESYSTYPE, ROOT, MOUNT, SUBFILESYSTYPE, and ALTROOT statements
    • RUNOPTS
    • VERSION
    • AUTHPGMLIST
    • SC_EXITTABLE
  • Enclose values in single quotation marks, using the following rules:
    • Two single quotation marks next to each other on the same line are considered as a single quotation mark. For example, John''s file is considered to be John's file. One quotation mark in column 71 and another in column 1 of the next line are not considered as a single quotation mark. This input is treated as two strings or an error.
    • Because some values can be up to 1023 characters, a value can require multiple lines. Place one quotation mark at the beginning of the value, stop the value in column 71 of each line, continue the value in column 1 of the next line, and complete the value with one quotation mark. Figure 1 shows an example.
      Figure 1. Specifying values on multiple lines
      column                                                           column
1                                                                    71
|                                                                     |
   MOUNT FILESYSTEM('HFS.WORKDS') MOUNTPOINT('/u/john/namedir1/namedir2
/namedir3/namedir4') TYPE(ZFS) MODE(RDWR)

Rather than defining parameter limit values in their full decimal or hexadecimal form, you can use a one-character multiplier (denomination values) suffix when specifying them. This value will also be used in displays when the system returns responses to respective D OMVS commands. The multipliers are listed in Table 1

Restrictions:
  1. Only those SETOMVS parameters that support this C suffix specifically note that support and refer to Table 1..
  2. Values that contain a multiplier are limited to 8 digits (nnnnnnnnC) and those values are limited to X'00FF FFFF' (16 777 215 decimal).
  3. Values that do not contain a multiplier are limited to X'7FFF FFFF' (2 147 483 647 decimal).
Tip: A complete description of the D OMVS output can be found in message BPXO040I. To look up that message, go to z/OS MVS System Messages, Vol 3 (ASB-BPX).
Table 1. One-character parameter limit multipliers
Denomination value One-character abbreviation Bytes
null n/a 1
Kilo K 1,024
Mega M 1,048,576
Giga G 1,073,741,824
Tera T 1,099,511,627,776
Peta P 1,125,899,906,842,624