Journal Logs

Form 2110-15 (figure 2-6). Although this form is primarily designed as a record of received messages, only a pen-and-ink change is necessary for its use as a send log. JOURNAL LOGS In most automated systems, all significant system events are entered in a journal log. This log is a chronological record of data processing operations, which may be used to reconstruct a previous or updated version of a file. All system-level commands entered by an operator are logged. Log entries are usually queued for delivery to a printer as they are generated, but this is optional. However, they are always journaled to a file from which they can be recalled and printed at a later time, as desired. This log gives a system operator or supervisor the ability to review current and previous system events. In addition, the journal log supports message accountability. The system records the receipt of every formal message and the termination of every formal message delivery that it schedules. PROCESSING OUTGOING MESSAGES Outgoing messages are those messages originated by: l l l l The command; Commands served by the communications center; An afloat command if a flag officer is embarked; An addressable unit onboard the ship as well as all messages accepted for relay. The flow chart in figure 2-7 shows the actions required to process outgoing messages. HANDLING AUTOMATICALLY PROCESSED OUTGOING MESSAGES Those messages introduced into the LDMX/NAVCOMPARS from a PCMT, VDT, paper tape reader, data speed reader (DSR), card reader, or magnetic tape are considered “outgoing.” They are prepared in JANAP 128, modified ACP 126, or other acceptable formats. Most outgoing messages are destined to be delivered to distant communications centers and commands. Others also have delivery requirements for in-house distribution to commands Figure 2-7.—Steps for processing outgoing messages. 2-15