User manual

Computer Gateway User Manual 4-132 5/96
4.11
4.11 CM JOURNAL ACCESS
4.11.1 Introduction to CM Journal Access
The Purpose of the CM Journal Access is to allow a request from a CM50 function to pass
and convert LCN Real-Time HM journals into ASCII files for a host processor. The
journal requests are passed to the CG/PLNM through a unique transaction code of 64.
Only one journal access request per CG/PLNM is allowed. Concurrent requests will not be
queued.
The following paragraphs explain the format and content of the CM Journal Access that a
host processor can make to an HM on the local LCN.
The host initiates all CM Journal Access operations and can also request abort of any
operation. For each CM Journal Access request from the host, there is a paired return from
the CG/PLNM. Descriptions of each CM Journal Access request/return pair begin at
heading 4.11.2.
4.11.2 Valid Combinations of Journal and Search Keys
The following combinations of journals, search keys selections, and unit ID numbers are
allowed. If any other combination is passed to the CG/PLNM, the appropriate error status
will be returned to the host processor, and the transaction is considered complete.
Journal Types Valid Search Keys
Process Alarms
Operator Messages
Process Changes
one unit AND
up to 8 modules*OR
up to 8 points*
SOE Events (Area SOE not configured) one unit
Area SOE all units for one HM OR
one unit on one HM
System Maintenance
System Errors
Status Notifications
up to 8 nodes OR
all system events
System Status up to 8 boxes on one hiway/UCN OR
all boxes on one hiway/UCN OR
all boxes on all hiways/UCNs OR
up to 8 nodes OR
all system events
* NOTE: Selected modules or points must be in the same unit.
4.11.3 CM Journal Access Request
The flow of data begins as the VAX user requests journal events from the LCN. The
CM50 sends the appropriate transaction request across the link to the CG/PLNM via the
VAX/CG/PLNM request message structure. The CG/PLNM responds to the request by
building the Journal Manager Request Record and calls the Journal Manager surrogate
subroutine.