C2MS11 — Make all subjects be buildable from fields in the message

Almost all miscellaneous subject elements for messages are specified as mapping to fields in the message. But a few are not. For example, see the Miscellaneous Elements table 8-46 for the Control message. The elements DESTINATION_NODE and DESTINATION_FACILITY do not exist as fields in the message. (Note: it may be more appropriate to add some of these fields to the Message Header rather than many/most messages.) In this particular example, this may be resolved by C2MS11-28, but each message type would need to be evaluated to see what other subject elements are not mapped to fields.

Address node and facility terms to DESTINATION-NODE and DESTINATION-FACILITY

The following fields are added to 8.1 C2MS Message Header, optional fields:

DESTINATION-NODE=Header String
DESTINATION-FACILITY=Header String

These fields are also now associated ME3 and ME4 in all other tables within the document
where they are used or not otherwise specified.

==================================================================

8.5.1.1 Configuration Status Message Subjects
Table 8-40. Configuration Status Message
Column ME3 [Node] --> ME3 [COMPONENT-NODE]
Column ME4 [Facility] --> ME3 [COMPONENT-FACILITY]

==================================================================

Table 8-41. Properties of the Miscellaneous Elements for the Configuration Status Message

ME3 = destination node ---> DESTINATION-NODE
ME4 = destination facility --> DESTINATION-FACILITY

(soon after that table)

Examples
Publishing / Sending Configuration Status messages:
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1 or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1.COMPONENT or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1.COMPONENT.NODE.FACILITY

****TO*****

Examples
Publishing / Sending Configuration Status messages:
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1 or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1.DESTINATION-COMPONENT or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CFG.APP1.DESTINATION-COMPONENT.DESTINATION-NODE.DESTINATION-FACILITY

==================================================================
8.5.2.1 Control Message Subjects
Table 8.45. Control Message Subject Naming

Column ME3 [Node] --> ME3 [COMPONENT-NODE]
Column ME4 [Facility] --> ME3 [COMPONENT-FACILITY]

Table 8-46. Properties of the Miscellaneous Elements for the Control Message

ME3 = destination node ---> DESTINATION-NODE
ME4 = destination facility --> DESTINATION-FACILITY

(Then...)

Examples
Publishing / Sending Control messages:
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1 or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.COMPONENT or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.COMPONENT.NODE.FACILITY or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.COMPONENT.NODE.FACILITY.KEY
WORD

********TO*********

Examples
Publishing / Sending Control messages:
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1 or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.DESTINATION-COMPONENT or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.DESTINATION-COMPONENT.DESTINATION-NODE.DESTINATION-FACILITY or
C2MS.DOM1.DOM2.MSSN.CNS1.SAT1.MSG.CNTL.APP1.DESTINATION-COMPONENT.DESTINATION-NODE.DESTINATION-FACILITY.KEY
WORD