Form 2110-15 (figure 2-6). Although this form isprimarily designed as a record of received messages,only a pen-and-ink change is necessary for its use as asend log.JOURNAL LOGSIn most automated systems, all significant systemevents are entered in a journal log. This log is achronological record of data processing operations,which may be used to reconstruct a previous or updatedversion of a file.All system-level commands entered by an operatorare logged. Log entries are usually queued for deliveryto a printer as they are generated, but this is optional.However, they are always journaled to a file from whichthey can be recalled and printed at a later time, asdesired. This log gives a system operator or supervisorthe ability to review current and previous system events.In addition, the journal log supports messageaccountability. The system records the receipt of everyformal message and the termination of every formalmessage delivery that it schedules.PROCESSING OUTGOING MESSAGESOutgoing messages are those messages originatedby:llllThe command;Commands served by the communicationscenter;An afloat command if a flag officer is embarked;An addressable unit onboard the ship as well asall messages accepted for relay.The flow chart in figure 2-7 shows the actionsrequired to process outgoing messages.HANDLING AUTOMATICALLYPROCESSED OUTGOING MESSAGESThose messages introduced into theLDMX/NAVCOMPARS from a PCMT, VDT, papertape reader, data speed reader (DSR), card reader, ormagnetic tape are considered “outgoing.” They areprepared in JANAP 128, modified ACP 126, or otheracceptable formats. Most outgoing messages aredestined to be delivered to distant communicationscenters and commands. Others also have deliveryrequirements for in-house distribution to commandsFigure 2-7.—Steps for processing outgoing messages.2-15
Integrated Publishing, Inc. - A (SDVOSB) Service Disabled Veteran Owned Small Business