OPS Message Codes 0-86 are all LabVIEW error codes.

0	
1	Argument error
2	Memory is full
3	Out of zone
4	End of file
5	File already open
6	Generic file I/O error
7	File not found
8	File permission error
9	Disk is full
10	Duplicate path
11	Too many files open
12	System feature not enabled
13	Resource file not found
14	Cannot add resource
15	Resource not found
16	Image not found
17	Image memory error
18	Pen does not exist
19	Config type invalid
20	Config token not found
21	Config parse error
22	Config memory error
23	Bad external code format
24	Bad external code offset
25	External code not present
26	Null window
27	Destroy window error
28	Null menu
29	Print aborted
30	Bad print record
31	Print driver error
32	Windows error during printing
33	Memory error during printing
34	Print dialog error
35	Generic print error
36	Invalid device refnum
37	Device not found
38	Device parameter error
39	Device unit error
40	Cannot open device
41	Device call aborted
42	Generic error
43	Cancelled by user
44	Object ID too low
45	Object ID too high
46	Object not in heap
47	Unknown heap
48	Unknown object (invalid DefProc)
49	Unknown object (DefProc not in table)
50	Message out of range
51	Invalid (null) method
52	Unknown message
53	Manager call not supported
54	Bad address
55	Network operation in progress
56	Network operation timed out
57	Connection is busy
58	Network attribute not supported
59	Network error
60	Address in use
61	System out of memory
62	Connection aborted
63	Connection refused
64	Not connected
65	Already connected
66	Connection lost
67	Initialization error (interapplication manager)
68	Bad occurrence
69	Wait on unbound occurrence handler
70	Occurrence queue overflow
71	Dialog type conflict
72	Unused
73	Unrecognized type (interapplication manager)
74	Memory corrupt
75	Failed to make temporary DLL
76	Old CIN version
77	Drag socket not found
78	Failed to load drop-object
79	Failed to register OLE object
80	Failed to release OLE object
81	Format specifer type mismatch
82	Unknown format specifier
83	Too few format specifiers
84	Too many format specifiers
85	Scan failed
86	Unknown error code

OPS Message Event Codes 87 - 2000 are all LZP Assembly_Decom message and error codes.
	
Event 87 and 88 are the two alternatives for reporting initialization status in AD sequence frame 2.  At that point the startup parameter file has been read, the oracle SID has been checked, and the required directory paths have been verified. 
87	Assembly_Decom.vi initialized successfully
88	Assembly_Decom.vi initialization failed

Obsolete message?
89	amf file location checked

In Assembly.vi, during initialization is sequence frame 0, after checkparm.vi has been called, if the parameters so far are all valid we set "valid startup parameters" TRUE and Event 90 is reported.  If "valid startup parameters" is FALSE, we report Event 910
90	Assembly.vi has received valid startup parameters
In Assembly.vi, during initialization in sequence frame 0, getMJFbase is called to get a base 
91	getMJFbase obtained base MJF time for MJF time check
92	getMJFbase did not obtain MJF time for MJF time check

Events 94-96 originate from Assembly.vi in sequence frame 1, depending on the status of the amf file.
94	Assembly.vi had error on amf file
95	Assembly.vi received end of file on amf file, clearing buffers this cycle
96	Assembly.vi in afst bfst file posting cycle

97	session talley report follows 
99	BFST posting error
100	BFST posted
102	BFST dropped
109	GFST posting error
110	GFST posted
112	GFST dropped
113	amf file name version not obtained, defaulting to version V000
114	amf file name version obtained
115	statistics generation error
129	station_table error
130	station_table read successfully
167	No current lpointer found in system_state table before timeout
169	Invalid Oracle system_state table:  multiple lpointers found
170	Valid Oracle system_state table:  current lpointer found
171	Oracle recon final rule name not found.
172	Oracle recon final rule name found.
189	Oracle rt file error
190	Oracle rt file processed successfully
191	getgrtbase did not obtain QL window of time
192	getgrtbase obtained QL window of time successfully
193	getQLwindow did not obtain QL window of time
194	getQLwindow obtained QL window of time successfully
200	reconstruction started
201	recon.vi initialized
202	recipesize completed
203	recipe table dump to file step completed
204	reconstruction procedure completed successfully
205	error encountered during reconstruction
206	getMJFrecipe completed
207	getMJFrecipe had an error
208	completed Data Record Header for a MJF
209	recipe contains no entries
210	recipe contains an error
211	reconstruction timeout limit exceeded
212	reconstruction completed for a MJF
214	reconstruction completed for all MJF in recipe table
216	obtained CDM from afst for a MJF
217	could not obtain the CDM from the afst for a MJF
218	obtained CDM from bfst for a MJF
219	could not obtain the CDM from the bfst for a MJF
220	obtained CDM from gfst for a MJF
221	could not obtain the CDM from the gfst for a MJF
224	dropped the gfst that recon created for quicklook
230	UNDO procedure executed successfully
231	UNDO procedure failed
240     during recipe table dump to file step an error was detected

If the mode extracted from the telemetry for a mission does not correspond to a known valid LZP science data mode for that mission, and we cannot infer the mode based on other means, we report the Decom Index as unknown.  Note this situation is not the same as the case of a major frame whose mode cannot be unpacked, but for which the mode and hence the Decom Index can be determined from context (e.g. the mode is known for data before or after the problem major frame).  If Event Message 256 is reported, it was not possible to derive the Decom Index, so the data for that major frame will be skipped:  it will not be decommutated at all.

	
256	unknown Decom Index
259	could not move amf file as indicated
260	moved amf file into amf directory

As a double check against anomalous data or initialization errors, the length of each instrument data packet is compared to the value expected.  If a packet is not the correct length, it is destroyed, not written to DPS, and an error is reported.  Event Message 267 indicates that such an error has occured.  This error is not normal and most likely indicates a corrupt AD decom table configuration or corrupt input data. 

267	Invalid instrument packet-length packet destroyed

During the initial socket handshake between AD and DPS, DPS returns the Spacecraft ID it is expecting.  AD checks this SC ID against the ID of the data is is trying to process: if the ID's do not match that is regarded as a fatal error.

290	DPS SC ID matches Assembly_Decom SC ID
299	DPS SC ID does not match Assembly_Decom SC ID



Event Messages 300-323 are TTCD-related messages:

300	TTCDmain started
301	TTCDmain ended
302	Unable to retrieve latest Link counter from TTCDHIST table
303	Unable to retrieve latest TTCD entry from TTCDVALUE table
304	Unable to retrieve latest job number from TTCDACCT table
305	Cannot find a pair of valid TTCD entries
306	Unable to insert a TTCD record into TTCDHIST table
307	Unable to insert a valid TTCD record into TTCDVALUE table
308	Unable to insert an accounting record into TTCDACCT table
310	Date Received not found while reading TTCD file
311	Move of file not done after reading TTCD file
312	No TTCD file found to process
314	TTCD file processed
320	Unable to get total number of records from TTCDVALUE table
321	Unable to retrieve a record from TTCDVALUE table
322	Cannot find a good TTCD from TTCDVALUE buffer for interpolation
323	TTCDVALUE table is empty


For a given mission, if all initialization is successful up through reading the decommutation tables, a final step prior to beginning processing data is to enable decommutation.  Decommutation is disabled by default, so that in the event of an error initializing the session, data is not sent to DPS.  Event Messages 409 and 410 report failure or success of this enabling action.
 
409	Inst_Decom_Enable failure
410	Inst_Decom_Enable success


601	Fatal Error writing to DPS socket connection

Event Messages 700-711 are Oracle Reconstruction table configuration-related.

700	Oracle Recon Semaphore Table queries completed successfully
701	Fatal Error during Oracle Recon Semaphore Table queries 
702	Oracle config_parm table copied fresh from config_parm_master table
703	Fatal Error copying from Oracle config_parm_master table
710	Oracle config_parm table updated successfully
711	Fatal Error updating Oracle config_parm table

Event 750 and 751 result from AD executing shell commands to confirm the amount of free space available in the current mission instance.  This check is done in AD sequence frame 3, when initialization has occured successfully, before any data has actually been processed. Normally the current disk percent capacity logged and execution continues, however when the percent disk used is >= 97%, AD regards this as a fatal error and it will auto-exit.  Tis is done to help prevent a corrupt processing state from being created due to running out os space during a session.

750	Disk Capacity checked and sufficient capacity is available
751	Fatal Error insufficient free disk space or error checking disk capacity

Event 900 is reported when AD detects that "perform a controlled stop" has been set.  This variable is set by any one of the three frame assembly states, Assembly, Recon, or Recon_Quicklook, and causes the Major Frame Assembly/Major Frame Decommutation while loop in AD sequnce frame 4 to terminate.  The remaining sequence frames 5-8 in Assembly_Decom are concerned with generating reports and exiting cleanly from the current session.
900	normal termination by performing a controlled stop


901	session summary report follows
910	invalid startup parameters
1000	Unknown error code

The following four messages are a set.  The first two are for a completely manual AD run (not the ordinary lzp_process manual run, but one where the user starts AD directly via Labview), thus these two messages won't ever occur in operations.  The latter two messages do show up in operations, they are the normal AD wrap-up messages at the end of a session that indicate overall success (event 2000) or failure (event 1999) of the session.

1899	Fatal Error during manual execution of Assembly_Decom
1900	Successful Completion of manual execution of Assembly_Decom
1999	Fatal Error during ftp replay execution of Assembly_Decom
2000	Successful Completion of ftp replay execution of Assembly_Decom

