MIP access method for messages
There are the following MIP access methods for messages: ISAM, DLAM, LOCAL-DLAM, BAMR and MINIMIP. The access methods LOCAL-DLAM, BAMR and MINIMIP are reserved for internal use.
Message output destination
Documents one or more output destinations for the message. Although this specification is not evaluated, it should correspond to the DEST operand of the MSG7/MSG7X macro.
Routing Code
If the message output destination is a console, the message is assigned an additional single-digit identifier, the routing code (RC). The routing code is analyzed to ascertain the message destination if subsidiary consoles are used in addition to the main console.If multiple consoles are used, they are assigned to specific task areas. The routing codes are then used by the system to correlate specific messages with the appropriate consoles.
The routing code defined with MSGMAKER is used only if no value is specified for the UCDEST operand of the MSG7/MSG7X macro.
AC/RC | Task area |
A | System administration |
C | Operation of the data communication system |
D | Operation of disks |
E | General tasks and responsibilities |
W | Device management |
H | Hardware maintenance |
J | Job control |
K | OPR command management |
N | Monitoring of remote SPOOL |
O | Operation of printers |
P | Control of tasks |
R | Monitoring and control of system behavior |
S | Control of SPOOLOUT operation, load SPOOL |
T | Operation of magnetic tape devices |
U | File management |
W,X,Y,Z | Available to the user |
0 | Messages with this authorization code cannot be requested. Messages without a response are simply stored in the CONSLOG file. Messages with a response (queries) are delivered to the main console. |
9 | VM2000 administration |
# | POSIX |
* | Main console |
@ | Main console (only for messages requiring a response; messages requiring no response are stored in the CONSLOG file but not output) |
$ | Special meaning; not used for message outputs |
B,F,I,L,M,Q,V, | Reserved for future system expansion |
Table 42: Task areas and the routing codes (RCs) of messages
See also the table 45 in section "Functional areas and their allocation to consoles".
Weight Code
The weight code determines the message priority.
If the output destination of a message is a console, a weight code must be specified; otherwise any weight code assigned has no meaning. Messages with a destination other than a console can be assigned WEIGHT=*NONE. If a message not intended for a console is sent to a console nevertheless, it is assigned the default weight code 99.
Weight codes can be assigned within the range 0 through 99. A message with the weight code 99 has the highest priority. This message cannot be suppressed.
A message that requires a response (REPLY operand of the MSG7/MSG7X macro) should be assigned the weight code 90 or 98.
To control message suppression, four filter levels can be set for each command at the console. These filter levels correspond to the weight codes of the messages as shown below:
Filter level | Weight Code | Standard values |
1 | 0 - 19 | None |
2 | 20 - 39 | 30 |
3 | 40 - 59 | 50 |
4 | 60 - 79 | 70 |
Cannot be suppressed | 80 - 99 | 90,98,99 |
Filter level 1
The user can subsequently assign the weight of this range to messages which are considered irrelevant and allocate filter level 1 to the appropriate console or authorized user job to prevent the messages from being output there.
Filter level 2
A message with a weight code from this range is for information only and may be suppressed without jeopardizing safe operation.
Filter level 3
A message with a weight code from this range is for information only. This message may be suppressed without jeopardizing safe operation. The increased value is based on an additional aspect which may make output advisable, e.g. logging for data protection reasons or processing by an authorized user job.
Filter level 4
A message with a weight code from this range is for information only and does not require a response. However, the information is important for the operator. Its suppression might have adverse effects on the session.
Weight code range 80 - 99
A message with a weight code from this range either requires a response or is of utmost importance.
Weight Code 90
This weight code is assigned to acknowledgments for which, in conjunction with secured automation functions, suppression is conceivable in the future. At present, such acknowledgments cannot be suppressed.Weight Code 98
A message with this weight code requires a response and may not be suppressed. The priority of weight code 98 is equivalent to that of weight code 99.Weight Code 99
A message with this weight code has top priority and must not be suppressed under any circumstances (default value).
Warranty
The “warranty” message attribute is evaluated by MIP.
The attribute guarantees that for a message with such an attribute both the message key and the inserts (numbers and semantics) remain unchanged in future subsystem versions and versions of BS2000 OSD/BC.
MIP creates S variables for warranty messages (guaranteed messages). For detailed information, see section "Output of messages in S variables".