Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > ARINC 653 for VxWorks 653 code > ARINC 653 for VxWorks 653 profile items > System state entry (ARINC for VxWorks code)
  
System state entry (ARINC for VxWorks code)
A SystemStateEntry represents the state (or the action of entering the state) for a partition, the module or the system as a whole. SystemStateEntries are scoped by and created on any of the 3 HMTables. For more information see the ARINC SPECIFICATION 653P1-2, December 1, 2005.
A System State Entry models a <SystemState> element in an ARINC 653 configuration, which appears in the Module XML file. The <SystemState> element can be a child element of a <ModuleHMTable>, <SystemHMTable> or <PartitionHMTable> element. The content of a <SystemState> element is defined by the Error ID Actions and Error ID Levels it contains.
The structure of the <SystemState> element is as follows for VxWorks:
<SystemState>
<ErrorIDAction
ErrorIdentifier=""
ErrorAction="">
</ErrorIDAction
<ErrorIDLevel
ErrorIdentifier=""
ErrorLevel="">
</ErrorIDLevel>
</SystemState>
Create a System State Entry on a Configuration Diagram: click the System State Entry toolbar button, and then click within a Module HM Table, Partition HM Table or System HM Table.
* 
The New > Integration Project command creates default System State Entries in the model. For more information, see the related links below.
* 
System State Entry items are not shown in the Packages pane, but they are shown in the Parts pane.
When shown on a Configuration Diagram a System State Entry's notation is as follows:
You can view all the System State Entries in the model through the SystemStateEntry folder in the ARINC 653 Profile pane.
A System State Entry is based on a UML Attribute.
The following sections provide information about how a System State Entry is used in the model.
Shown on these diagrams
Configuration Diagram
ARINC properties
None.