MS Major Vector Applicable Message-Unit Structures
Alert NMVT
Change Control CP-MSU
Reply to Execute Command NMVT
Reply to Analyze Status NMVT
Reply to Query Resource Data NMVT
Reply to Test Resource NMVT
Reply Activation Acceptance CP-MSU
Send Message To Operator NMVT
RTM NMVT
Reply Product Set 10 NMVT
Request Change Control CP-MSU
Execute Command NMVT
• The description of each major vector includes a matrix indicating the sub-vectors that may be included within it.
MS Major Vector Formats
Alert (X I 0000 I) MS Major Vector
PU ~ SSCP
This major vector provides unsolicited notification of a problem or
impending problem, type of problem, identification of the cause, and identifi-cation of the component that caused the problem.
Alert (X' 0000') MS Major Vector Byte
0-1 2-3
4-n
Bit Content
Length (n
+
1), in binary, of this MS major vector Key: X' 0000'MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X'OO' -X'7F', and in "Alert MS Subvectors" on page 8-16 for subvector keys X'80' -X'FE'.
Note: The following subvector keys may be used as indicated:
8-14
SNA FormatsPresence in NMVT
Subvector Alert (X'OOOO')
Major Vector
Text Message (X'OO') 0 Note 1
Date/Time (X'Ol) CP Note 2
Hierarchy Name List (X'03') CP Note 3 SNA Address List (X'04') CP Note 4 Hierarchy/Resource List (X' 05') CP Note 5
Pro~uct Set ID (X'10') Pen) Note 6 Self-Defining Text Msg. (X '31') 0
Relative Time (X'42') CP Note 7
Supporting Data Correl. (X'48') CP Note 8
LAN Link Connection CP Note 9
Subsystem Data (X'51')
LCS Configuration Data (X'52') CP Note 10 SDLC link Station Data (X'8C') CP Note 11
Basic Alert (X'91') 0 Note 12
Generic Alert Data (X'92') P Probable Causes (X'93') P
User Causes (X'94') CP Note 13
Insta 11 Causes (X'95') CP Note 13 Fa il ure Causes (X '96') CP Note 13 Cause Undetermined (X'97') CP Note 14
Detailed Data (X'98') 0
Detail Qualifier O(n) Note 15
(X' AD' or X' AI' )
P Present one time
CP(n) Present one or more times
CP Conditionally present one time (See Notes for conditions.)
o
Optionally present one timeO(n) Optionally present one or more times
Notes:
1. This subvector may be optionally included by an Alert sender. to transport text in a single Alert major vector that can be processed by both a non-generic Alert and a non-generic Alert focal point. If this subvector is present.
the X 1911 subvector must also be present.
2. If the PU sending the Alert major vector has the capability of providing it. it places this subvector in the NMVT. See Note 7.
/
-3. This subvector may be optionally included in the NMVT by an Alert sender in order to create a single Alert major vector that can be processed by both a non-generic Alert and a generic Alert focal point. When it is present, this subvector identifies an origin of the Alert condition that is not an SNA network addressable unit. If this subvector is present, the X 1911 subvector must also be present.
4. This subvector is present when it is necessary to identify, with an SNA address, the origin of the Alert condition. If the origin of the Alert condition is the PU sending the Alert, this subvector is not present.
5. This subvector is present in the NMVT instead of, or in addition to, the SNA Address List (XI041) 5ubvector if the origin (other than the PU sending the Alert) of the Alert condition cannot be represented in the SNA Address List (XI041) subvector.
6. An instance of this subvector describing the PU sending the Alert is always present. A second instance is present if the origin of the Alert condition is a hardware or software product, and is not the PU sending the Alert. If a second instance is present, it is placed immediately after the first instance of the XI101 subvector.
In an Alert containing two instances of the Product Set ID subvector, the fol-lowing terms refer, respectively, to these two instances:
• "Alert Sender PSID" identifies the PU sending the Alert
• "Indicated Resource PSID" identifies the resource on which the Alert is reporting
In an Alert with only one instance of the Product Set ID, this instance is referred to both as the Alert Sender Product Set ID and as the Indicated Resource Product Set ID.
7. If the PU sending the Alert cannot provide a Date/Time (X 101 1) subvector, it places this subvector in the NMVT instead.
8. This subvector is present if the Alert sender has preserved supporting data, e.g., a storage dump, to which the Alert must be correlated.
9. This subvector is present when the Alert reports an error on a LAN, and the node sending the Alert is attached to the LAN.
10. This subvector is present when the Alert reports a problem with a logical link using the SDLC or LAN LLC protocol.
11. This subvector is present when the Alert reports a problem with a logical link using the SDLC or LAN LLC protocol.
12. This subvector may be optionally included by an Alert sender in order to create a single Alert major vector that can be processed by both a non-generic Alert and a non-generic Alert focal point.
13. Any or all of these subvectors are present in an Alert, depending on the probable causes of the Alert condition identified by the Alert sender.
14. This subvector is present in an Alert if and only if none of the X 194 1, X 195 1, and X 196 I subvectors is present.
15. Up to a total of three instances of these subvectors may be optionally included by an Alert sender, in order to create a single Alert major vector that can be processed by both a non-generic Alert and a generic Alert focal
point. If either of these subvectors is present, the X 1911 subvector is also present.