Slide 52 of 80
Notes:
- CI variables can be strings (up to 1024 bytes in length), 32 bit signed integers or boolean TRUE/FALSE. There is not support for 64 bit integers or unsigned 32 bit numbers.
- See the slides on variable arrays for a method to determine the maximum number of CI variables that can be defined. This maximum is a function of the length of the variable’s name and the length of its value. The longer your variable names and/or their values the fewer variables can be stored by the CI. A typical range is 8,000 to 9,000 user variables can be defined.
- A summary of all of the predefined variables is available by entering HELP VARIABLES. The details for a specific variable can bee seen by entering HELP varname. For example, if you have trouble remembering the new values for the HPMSGFENCE variable, enter HELP HPMSGFENCE and see: HPMSGFENCE A variable used by the CI that controls the output for all CI errors, warnings and skipped commands. Skipped commands refer to commands that are not executed by the CI because they follow a conditional expression that evaluated FALSE. HPMSGFENCE is divided into 2 fields, 3 bits each in size. The low order field (bits 29..31) controls the output of CI error and warning messages as: 0 = display all CI errors and warning 1 = show only errors, warning are suppressed 2 = suppress all CI errors and warning messages.
The next field (bits 26..28) controls the output of skipped commands and the "*** EXPRESSION FALSE: ...", "*** EXPRESSION TRUE: ...", and "*** RESUME EXECUTION OF COMMANDS" messages: 0 = show all skipped commands and the above "***…” messages 1 = show only the "***..." messages, suppress commands that are skipped. Integer value is 8. 2 = suppress the skipped commands and the "***...” messages. Integer value is 16.
- HPMAXPIN is new to 7.0 and returns the maximum number of processes supported by your system
