HP Desk Logging Files [ HP DeskManager Customization ] MPE/iX 5.0 Documentation
HP DeskManager Customization
HP Desk Logging Files
Both the HP Desk logging files STATSFIL and AUDITFIL have a record length
of 85 bytes in the following format:
yy*ddd*hh:mm:ss.tt*aaa*bbb*eee*fff**nnnnnnnnnnrrrrrrrrrr**comment
where:
* represents a space.
yy is a two digit field and represents the last two digits of
the year in which the event was logged.
ddd is a three digit field and represents the numeric day of
that year.
hh:mm:ss.tt represents the time that the event was logged, in hours,
minutes, seconds and hundredths of a second.
aaa is a three digit field. The number here corresponds to the
program to which the event relates.
bbb is a three digit field. The number here is associated with
the program.
eee is a three digit field. The number here corresponds to the
type of event being logged.
fff is a three digit field. The number here is associated with
the type of event.
nnnnnnnnnn is a ten digit field which represents a tracking number.
This number is the internal Item-Number within the HP Desk
database. This field is of particular importance when
analyzing the log files as it can can be used to track the
message as it moves from one system to another.
rrrrrrrrrr is a ten digit field which represents an auxiliary tracking
number (again an internal database Item-Number), or
sometimes other information. The contents of this field
vary depending on the type of event being logged.
comment is used to add further information such as the name of a
computer, mail node name, user name, and so on, depending
on the type of event being logged. Comment is limited to
27 bytes.
The contents of these fields is explained in further detail below.
The aaa and bbb fields are common to both the AUDITFIL and the STATSFIL,
and so are explained together. However, the eee, fff, nnnnnnnnnn,
rrrrrrrrrr and comment fields contain different data depending on which
file they are in, and are explained separately for each file.
Identification of Programs
The aaa field, represents the program that was causing the event at that
particular moment. There is sometimes extra information in the bbb
field. This is the case for both the AUDITFIL and STATSFIL as follows:
Number | Program
|
-----------------------------------------------------------------------------------------
|
001 | Transport Manager -
| In addition the bbb field may contain the number of the Master Truck for
| messages sent to a truck from the Transport Manager.
|
002 | Master Truck -
| In addition the bbb field will contain the number of the Master Truck.
|
003 | Slave Truck
|
004 | Mailroom
|
005 | Clock Tick Generator
|
006 | User Interface
|
007 | FSC ARPA Truck
|
008 | FSC ARPA Reference Truck
|
009 | Supervisor
|
010 | NS Slave Truck
|
011 | Bin Emptier
|
012 | Garbage Collector (Shredder)
|
013 | Intrinsics Driver process
|
014 | Intrinsics Gateway Manager
|
STATSFIL Events
eee and fff fields
In the STATSFIL the eee field records events, which are mainly program
events, for example starts, stops, and error conditions. The fff field
may contain extra information relating to these events. The following
information only applies to the STATSFIL.
The events are represented as follows:
Number | Event
|
-----------------------------------------------------------------------------------------
|
001 | Program initialized
|
002 | Clock Tick - List of mail nodes to which mail is to be sent rescheduled.
| This happens every 15 minutes
|
003 | Reporting Status (Trucks) - Details are given in the fff field as follows:
|
| 001 REMOTE HELLO to another system
| 002 REMOTE BYE
| 003 Line connected to remote system but Truck idle
| 004 Line disconnected hence Truck idle
| 005 Truck has shut down
| 006 Master Truck connected to an NS Slave Truck
| 007 Master Truck disconnected from an NS Slave Truck
| 008 Intrinsics Gateway signon
| 009 Intrinsics Gateway signoff
|
004 | Reported status. (Transport Manager) - Details are given in the fff field
| as follows:
|
| 001 REMOTE HELLO to another system
| 002 REMOTE BYE
| 003 Line connected to remote system but Truck idle
| 004 Line disconnected hence Truck idle
| 005 Truck has shut down
| 006 Master Truck connected to an NS Slave Truck
| 007 Master Truck disconnected from an NS Slave Truck
|
005 | Slave Truck has shut down - Details are given in the fff field as follows:
|
| 001 Slave Trucks were not enabled on remote computer
| 002 Normal end of transmission
| 003 Slave Truck on remote computer aborted/abandoned.
|
006 | Mail node made unavailable. Probably because the computer was not available
|
Number | Event
|
-----------------------------------------------------------------------------------------
|
007 | Command issued by the Transport Manager - details are given in the fff field
| as follows:
|
| 001 Transmit to a mail node
| 002 Close line currently open
| 003 Open line to a computer
| 004 Stop sending mail
| 005 Shutdown
|
008 | Sign-on to user interface session
|
009 | Sign-off from user interface session
|
010 | Invalid password given for a user
|
011 | DS error - details are given in the fff field as follows:
|
| 001 POPEN fail
| 002 PWRITE fail
| 003 CLOSE fail
| 004 BYE fail
| 005 OPEN fail
| 006 HELLO fail
|
012 | Wrong location given by a Slave Truck
|
013 | Activate Slave Truck
|
014 | Unknown Mail Node on target computer
|
015 | Service Mail Node
|
016 | No Slave Trucks available on the remote computer
|
017 | Illegal route
|
018 | Sending mail node not known
|
019 | EFT/FSC error - details are given in the fff field as follows:
|
| 001 EFT/FSC fail. A file system error occurred in the file named in the
| comment field. The File System error number is given in the first
| tracking number field
| 002 EFT messages fail. File System error in writing to the file containing
| the outgoing messages
| 003 EFT Routine fail - internal error
|
020 | FSC incoming message file opened; name of file given in comment field
|
021 | FSC incoming message file closed; name of file is given in comment field
|
022 | FSC incoming message file deleted; name of file given in comment field
|
Number | Event
|
-----------------------------------------------------------------------------------------
|
023 | FSC error - details are given in the fff field as follows:
|
| 001 database full
| 003 entry/format type not recognized
| 005 referenced file access error; name of file given in comment field
| 999 other error; details given in job history
|
024 | Supervisor requests to HP Desk processes or activities - details of the
| requests are given in the fff field as follows:
|
| 001 start process/activity
| 002 stop process/activity
| 003 kill/abort process/activity
| 004 modify tracing
| 005 stop all processes
| 006 abort all processes
|
025 | A User Password change. The name of the user that has changed the password
| is given in the comment field
|
026 | A masquerading sending computer has been detected. This occurs when a
| remote computer attempting to connect to an NS Slave Truck is found to have
| a different IP address to that recorded in its configuration
|
027 | An NS error has been detected. This can occur in either the Master Truck or
| the NS Slave Truck - details are given in the fff field as follows:
|
| 001 connection failed
| 002 validation failed
|
| The NS error number will be detailed in the nnnnnnnnnn field.
|
999 | The Slave Truck has shutdown
|
The nnnnnnnnnn Field
This field may contain
* The item-number of the message (in the HP Desk database) being
tracked through the system, which can be used to track the message
as it moves from one system to another.
* NS error numbers.
* FS error numbers.
The rrrrrrrrrr and comment Fields
The auxiliary tracking number (field rrrrrrrrrr) will contain the entry
number for the relevant process or activity, and the comment field will
contain the shortform name of that process or activity as given in the
following list.
Entry | Short | Full Name of Process or Activity
Number | Name |
-------------------------------------------------------------------------------------------
-6 - STOREDAT - Set store date in Mailmaint
-5 - MAINTSH - Maintenance (shared mode)
-4 - MAINTEX - Maintenance (exclusive mode)
-3 - DSSLAVE - Slave Truck
-2 - DSMTRUCK - Master Truck
-1 - USERINT - User interface
0 - SUPRVISR - Supervisor program
1 - SUPTIMER - Timer
2 - MAILROOM - Mailroom
3 - TMANAGER - Transport Manager
4 - SCHEDMSG - HP Schedule message server
5 - SCHEDREP - HP Schedule reply server
7 - BINEMPTY - Bin Emptier process
8 - SHREDDER - Garbage Collector
9 - - unused
10 - MAINT - Maintenance suite
11 - RECOVER - Recover/Housekeeping program
12 - STORE - Store database
13 - RESTORE - Restore database
14 - UNLOAD - Unload database
15 - MAILTELL - User notification program
16 - TICKLER - Diary reminder/Tickler server program
17 - ADMIN - Remote Directory updates server
18 - MAILSTRM - Job streamer
19 - SEARCHER - Filing Cabinet search server program
20 - OPERINT - Allocated operator interface
21 - HPMAIL - Allocated user interface
22 - USRABORT - User interface session abort program
Entry | Short | Full Name of Process or Activity
Number | Name |
-------------------------------------------------------------------------------------------
23 - DIUPDATE - Diary update server program
24 - INSTALLH - Help text and scripts installer
25 | PRODSCAN | Conversion Information Updater (at
| | installation)
26 to 29 - - unused
30 - LIBRARY - HP File/Library server program
31 - PCMAIL - PC Mail server program
32 - LIBMAINT - HP File/Library maintenance program
33 - ARCHIVE - HP File/Library Archive program
34 - RETRIEVE - HP File/Library Retrieve program
36 - EFT - EFT Slave Truck
37 - EFT - EFT 2nd Slave Truck
38 - EFT - EFT 3rd Slave Truck
39 - EFT - EFT 4th Slave Truck
40 - EFT - EFT 5th Slave Truck
41 to 43 - - reserved for more EFT Slave Trucks
44 - FSCARPA - FSC ARPA Slave Truck
45 - FSCARPA - FSC ARPA 2nd Slave Truck
46 - FSCARPA - FSC ARPA 3rd Slave Truck
47 - FSCARPA - FSC ARPA 4th Slave Truck
48 - FSCARPA - FSC ARPA 5th Slave Truck
49 to 51 - - reserved for more FSC Slave Trucks
52 - FSCAREF - FSCAREF Slave Truck
53 - FSCAREF - FSCAREF 2nd Slave Truck
54 - FSCAREF - FSCAREF 3rd Slave Truck
55 - FSCAREF - FSCAREF 4th Slave Truck
56 - FSCAREF - FSCAREF 5th Slave Truck
57 to 59 - - reserved for more FSCAREF Slave Trucks
61 - DLSERVER - Everyone server
62 - X400 - X400 process
63 - TROUTER - Transport Router
64 - INTRGMGR - Intrinsics Gateway Manager
65 - UPDATSRV - ECD Update server
70 - DMUPDATE - HP DeskMon remote update server
71 - OMGATE - HP OpenMail Gateway
72 - SNADS - SNADS monitor process
74 - NSMONITOR - NS Slave Truck monitor
Sample STATSFIL File
_______________________________________________________________________________
| |
| |
| 91 211 18:36:58.70 002 001 003 003 0 0 |
| 91 211 18:36:58.80 001 001 004 003 0 0 |
| 91 211 18:36:58.90 001 020 007 002 0 0 |
| 91 211 18:37:00.90 002 001 003 002 0 0 |
| 91 211 18:37:03.70 002 001 003 004 0 0 |
| 91 211 18:37:03.80 001 001 004 004 0 0 |
| 91 211 18:37:25.30 006 000 009 000 PARKER,CARL |
| 91 211 18:37:46.20 003 000 001 000 0 0 TONTO |
| 91 211 18:37:47.50 003 000 015 000 0 0 HP160001 |
| 91 211 18:37:55.70 003 000 999 000 0 0 TONTO |
| 91 211 18:39:31.70 009 000 024 005 |
| 91 211 18:39:31.90 009 000 024 002 16 TICKLER |
| 91 211 18:39:32.40 009 000 024 002 3 TMANAGER |
| 91 211 18:39:32.60 009 000 024 002 30 LIBRARY |
| 91 211 18:39:32.80 001 000 007 005 0 0 |
| 91 211 18:39:32.90 001 000 007 005 1 0 |
| 91 211 18:39:32.90 001 000 999 000 0 0 |
| 91 211 18:39:36.80 002 001 999 000 0 0 |
| 91 211 18:39:37.00 009 000 024 002 2 MAILROOM |
| 91 211 18:39:37.60 009 000 024 002 21 HPMAIL |
| 91 211 18:39:38.80 009 000 024 002 20 OPERINT |
| 91 211 18:39:40.10 009 000 024 002 1 SUPTIMER |
| 91 211 18:39:42.40 009 000 024 002 -1 USERINT |
| 91 211 18:39:42.50 009 000 024 002 -3 DSSLAVE |
| 91 211 18:39:42.50 009 000 024 002 15 MAILTELL |
| 91 211 18:39:52.80 004 000 999 000 |
| 91 211 18:40:01.20 002 000 011 005 253 1 HECTOR |
| 91 211 18:40:01.30 002 000 003 002 0 0 |
| 91 211 18:40:01.30 002 000 003 004 0 0 |
| 91 211 18:40:02.00 002 000 999 000 0 0 |
| 91 211 18:40:24.70 009 000 999 000 |
| 91 211 18:46:29.70 006 000 009 000 LEECH,MARTIN |
| 91 211 18:56:40.70 006 000 009 000 DRAPER,COLIN |
| 91 211 19:16:28.00 003 000 001 000 0 0 TONTO |
| 91 211 19:16:29.90 003 000 999 000 0 0 TONTO |
| 91 211 19:31:01.10 003 000 999 000 0 0 ******** |
| |
_______________________________________________________________________________
COBOL Record Structure of Statistics File
FD STATS-FILE
RECORD CONTAINS 85 CHARACTERS
DATA RECORD IS I-STATS-LAYOUT.
*
01 I-STATS-LAYOUT
03 I-YEAR PIC 99.
03 I-DAY-OF-YEAR PIC 9(4).
03 FILLER PIC X.
03 I-TIME-STAMP PIC X(11).
03 I-ENVIRONMENT PIC 9(4).
88 TMANAGER VALUE 1.
88 MASTER-TRUCK VALUE 2.
88 SLAVE-TRUCK VALUE 3.
88 MAILROOM VALUE 4.
88 CLOCK-TICK VALUE 5.
88 USER-INTERFACE VALUE 6.
88 FSC'ARPA'TRUCK VALUE 7.
88 FSC'AREF'TRUCK VALUE 8.
03 I-TRUCK-NUMBER PIC 9(4).
03 I-MESSAGE-TYPE PIC 9(4).
88 INITIALIZED VALUE 1.
88 CLOCK-TICK-MESSAGE VALUE 2.
88 REPORTING-STATUS VALUE 3.
88 STATUS-REPORT VALUE 4.
88 SLAVE-HAS-SHUTDOWN VALUE 5.
88 NODE-MADE-UNAVAIL VALUE 6.
88 SEND-COMMAND VALUE 7.
88 SIGNON VALUE 8.
88 SIGNOFF VALUE 9.
88 BAD-PASSWORD VALUE 10.
88 DS-ERROR VALUE 11.
88 WRONG-LOCATION VALUE 12.
88 ACTIVATE-SLAVE VALUE 13.
88 UNKNOWN-NODE VALUE 14.
88 SERVICE-NODE VALUE 15.
88 NO-SLAVES VALUE 16.
88 ILLEGAL-ROUTE VALUE 17.
88 SENDER-NOT-KNOWN VALUE 18.
88 EFT-ERROR VALUE 19.
88 FSC-FILE-OPENED VALUE 20.
88 FSC-FILE-CLOSED VALUE 21.
88 FSC-FILE-DELETED VALUE 22.
88 FSC-ERROR VALUE 23.
88 SUPERVISOR-REQUEST VALUE 24.
88 PASSWORD-CHANGE VALUE 25.
88 MASQ-COMPUTER VALUE 26.
88 NS-ERROR VALUE 27.
88 SHUTDOWN VALUE 999.
03 I-MESSAGE-SUBTYPE PIC 9(4).
* STATUS REPORT SUB TYPES
88 HELLO VALUE 1.
88 BYE VALUE 2.
88 LINE-CONNECTED VALUE 3.
88 LINE-DISCONNECTED VALUE 4.
88 MASTER-SHUT VALUE 5.
* SLAVE HAS SHUT SUB TYPES
88 NOT-ENABLED VALUE 1.
88 STOPPED VALUE 2.
88 ABORTED VALUE 3.
* SEND COMMAND TYPES
88 TRANSMIT VALUE 1.
88 CLOSE-LINE VALUE 2.
88 OPEN-LINE VALUE 3.
88 SUSPEND-ACTION VALUE 4.
88 SHUTDOWN-COMMAND VALUE 5.
* DS ERRORS
88 POPEN-FAIL VALUE 1.
88 PWRITE-FAIL VALUE 2.
88 CLOSE-FAIL VALUE 3.
88 BYE-FAIL VALUE 4.
88 OPEN-FAIL VALUE 5.
88 HELLO-FAIL VALUE 6.
* EFT ERRORS
88 EFT-IPC-FAIL VALUE 1.
88 EFT-MSGS-FAIL VALUE 2.
88 EFT-ROUTINE VALUE 3.
* FSC ERRORS
88 FSC-DB-FULL VALUE 1.
88 FSC-INVALID-FORMAT-TYPE VALUE 3.
88 FSC-REF-FILE-ERROR VALUE 5.
88 FSC-OTHER-ERROR VALUE 999.
* SUPERVISOR REQUESTS
88 START-REQUEST VALUE 1.
88 STOP-REQUEST VALUE 2.
88 ABORT-REQUEST VALUE 3.
88 TRACE-REQUEST VALUE 4.
88 STOP-ALL-REQUEST VALUE 5.
88 ABORT-ALL-REQUEST VALUE 6.
88 UNKNOWN-REQUEST VALUE 999.
* NS ERRORS
88 NS-CONNECT-FAIL VALUE 1.
88 NS-VALIDATION-FAIL VALUE 2.
88 UNKNOWN-REQUEST VALUE 999.
03 FILLER PIC XX.
03 I-ORIGINAL-ITEM-NO PIC S9(10).
03 I-CURRENT-ITEM-NO PIC S9(10).
03 FILLER PIC XX.
03 I-USER-NAME PIC X(36).
03 I-NODE-INFO REDEFINES I-USER-NAME.
05 I-NAME
07 I-LOCATION PIC X(6).
07 I-SUB-LOCATION PIC XX.
05 FILLER PIC X(28).
AUDITFIL Events
Events logged to the Audit file mostly refer to the movement of messages
into, around and out of the system. Where further information is
required, it is given in subsequent sections.
The eee Field
The events listed below can be logged in the eee field.
Number - Event
-----------------------------------------------------------------------------------------
001 - Message to Error queue
002 - Message acknowledgment
003 - Message to Deferred queue
004 - Message to Mail Node queue
005 - Collect from Out Tray
006 - Deliver to user's In Tray
007 - Mail
008 - Private message that would have gone to General Delivery discarded
010 - Transmit message
011 - EFT/FSC outgoing message file generated
012 - A routed message returned to the originator because it was badly addressed
The fff Field
If the fff field in AUDITFIL contains a number, it refers to a message
type as follows:
100 Message transmitted to a neighboring computer
300 Reply
301 Read acknowledgment
302 Delivery acknowledgment
303 Message received at target computer acknowledgment.
If the eee field has a value of 001, then this field contains information
relating to the reason that an item was attached to the Error queue.
The Other Fields
The nnnnnnnnnn, rrrrrrrrrr and comment fields contain data relating
specifically to the events logged in the eee field. Therefore, each of
the numbered events is described separately below.
AUDIT File Event Type 1 (Message to Error Queue)
This event produces a standard output for the nnnnnnnnnn, rrrrrrrrrr and
comment fields
AUDIT File Event Type 2 (Message acknowledgment)
This event produces a standard output for the nnnnnnnnnn, rrrrrrrrrr and
comment fields
AUDIT File Event Type 3 (Message to Deferred Queue)
This event produces a standard output for the nnnnnnnnnn, rrrrrrrrrr and
comment fields
AUDIT File Event Type 4 (Message to mail node queue)
This event type can take two forms, depending upon which process logged
the event:
* If the Mailroom logged the event the original item number is held
in the nnnnnnnnnn field (the primary tracking field), and the new
item number is held in the rrrrrrrrrr field (the auxiliary
tracking number field), and the comment field contains the
destination and source nodes.
* If the Slave Truck logged the event the delivery time and the size
of message are held in the original rrrrrrrrrr field (the
auxiliary tracking number field), and the to node, from node, last
computer, priority indicator and ack indicator are held in the
original comment field. The alternative record layout for the
audit logging is described below:
...fff**nnnnnnnnnnddddddssss**ttttttttffffffffcccc*
Where:
* represents a space
nnnnnnnnnn original item number
ddddd delivery time in minutes
sssss size in sectors
tttttttt To node
ffffffff From node
cccccccc last computer
p priority indicator:
2 urgent
3 normal
a ack indicator for the level of requested
acknowledgment:
5 reply
4 read
3 delivery
2 receive
1 transmit
Fields n to s contain data in the tracking fields, and fields f to
a contain data in the comment field.
AUDIT File Event Type 5(Collect from Out Tray)
In a record of Event Type 5, the auxiliary tracking number field is used
to record the number of different mailnodes to which the message is being
sent, and the number of recipients addressed. The format of the field
is:
(NM * 1000)+NR
where NM is the number of mailnodes and NR is the number of recipients.
For example, the number 9027 indicates that the message was being
transported to nine different mailnodes and to a total of 27 recipients
at those mailnodes.
AUDIT File Event Type 6(Delivery to In Tray)
In the record of an Event Type 6, the first six characters of the
auxiliary tracking number field contains the delivery time in minutes, as
indicated below:
...fff**nnnnnnnnnndddddd******uuuuuuuuuuuuuuuuuuuu
where:
* represents a space
nnnnnnnn original item number
ddddd delivery time in minutes
uuu...u recipient name (first 27 characters)
AUDIT File Event Type 7 (Mail message)
In the record of an Event Type 7, the last two characters of the
auxiliary tracking number field contain the priority indicator and
acknowledgment level respectively for posted messages.
AUDIT File Event Type 8 (Private message discarded)
This event produces a standard output for the nnnnnnnnnn, rrrrrrrrrr and
comment fields
If a private message is badly addressed, then it may or may not get
returned to the sender, depending on the value of the RETURNTOSENDER JCW.
AUDIT File Event Type 10 (Transmit message)
In the record of an Event Type 10, the auxiliary tracking number field is
used to record the number of sectors occupied by the message, and the
comment field shows:
* The mailnode from which the message originated
* The mailnode to which the message is addressed
* The route computer to, or through which, the message is being
transported; that is, the next computer in the network, not
necessarily the target computer
Each of the above elements occupies eight characters, with the source and
target mailnodes shown in the form:
LLLLLLSS
where LLLLLL is the location and SS is the sublocation. Any unused
characters are replaced by ASCII blanks. For example, the mailnode
EM160/99 is recorded as "EM160 99".
Where Audit Event Type 10 is used for the Master Truck, the record has a
similar layout to that used for the Slave Truck in Type 4, with the same
values for the priority and ack indicators:
...fffnnnnnnnnnn******ssss**ffffffffttttttttccccccccpa*
Where :
* represents a space
nnnnnnnnnn original item number
ssss size in sectors
ffffffff from node
tttttttt to node
cccccccc next computer
p priority indicator
a ack indicator
AUDIT File Event Type 11
The record of an Event Type 11 gives the name of an EFT/FSC message file
that has been generated by the Master Truck in its comment field.
AUDIT File Event Type 12
This event produces a standard output for the nnnnnnnnnn, rrrrrrrrrr and
comment fields.
This indicates that a routed message has been returned to its originator
because is was incorrectly addressed.
Sample AUDITFIL File
_____________________________________________________________________________________________
| |
| |
| 91 211 18:35:47.60 002 001 002 303 20609985 17203019 MAILSYS******************* |
| 91 211 18:35:47.60 002 001 010 303 20609985 1 HP160001HP160002TONTO 30 |
| 91 211 18:35:47.60 002 001 002 302 20609985 17203057 LITYNSKI,TONY |
| 91 211 18:35:47.60 002 001 010 302 20609985 1 HP160001HP160002TONTO 30 |
| 91 211 18:36:39.30 006 000 007 000 17202392 34 PARKER,CARL |
| 91 211 18:36:41.30 004 000 004 007 17202392 17202392 HP4420HP |
| 91 211 18:36:41.30 004 000 005 100 17202392 1001 PARKER,CARL |
| 91 211 18:36:57.50 002 001 002 100 17202392 17202392 PARKER,CARL |
| 91 211 18:36:57.50 002 001 010 100 17202392 12 HP160001HP4420HPTONTO 34 |
| 91 211 18:37:53.60 003 000 002 100 20610308 17203095 TONTO |
| 91 211 18:37:53.60 003 000 004 100 20610308 9 9 HP160001HP160002TONTO 20 |
| 91 211 18:37:54.80 004 000 006 100 20610308 9 DRAPER,COLIN |
| 91 211 18:37:55.30 004 000 006 100 20610308 9 LEECH,MARTIN |
| 91 211 20:17:14.70 003 000 002 300 17201480 17203152 TONTO |
| 91 211 20:17:15.20 003 000 004 300 17201480 93 7 HP160001HP160000TONTO 30 |
| 91 211 20:17:21.70 003 000 002 301 17091964 17203209 TONTO |
| 91 211 20:17:21.80 003 000 004 301 17091964 242 1 HP160001HP4600L3TONTO 30 |
| 91 211 20:17:24.70 003 000 002 303 17195514 17203228 TONTO |
| 91 211 20:17:24.80 003 000 004 303 17195514 161 1 HP160001HP4800 TONTO 30 |
| 91 211 20:17:25.50 004 000 006 300 17201480 93 WILD,GRAHAM |
| 91 211 20:17:28.80 003 000 002 303 17195514 17203247 TONTO |
| 91 211 20:17:28.90 003 000 004 303 17195514 161 1 HP160001HP4800SYTONTO 30 |
| 91 211 20:17:32.10 003 000 002 302 17195514 17203266 TONTO |
| 91 211 20:17:32.10 003 000 004 302 17195514 160 1 HP160001HP4800SYTONTO 30 |
| 91 211 20:25:01.70 003 000 002 100 16006191 17203285 TONTO |
| 91 211 20:25:01.80 003 000 004 100 16006191 159 12 HP160001HPD600NWTONTO 30 |
| 91 211 20:25:04.70 004 000 006 100 16006191 159 HARRISON,BRIAN |
| |
_____________________________________________________________________________________________
COBOL Record Structure of Audit Files
FD AUDIT-FILE
RECORD CONTAINS 85 CHARACTERS
DATA RECORD IS I-AUDIT-LAYOUT
*
01 I-AUDIT-LAYOUT
03 I-YEAR PIC 99.
03 I-DAY-OF-YEAR PIC 9(4).
03 FILLER PIC X.
03 I-TIME-STAMP PIC X(11).
03 I-ENVIRONMENT PIC 9(4).
88 MASTER-TRUCK-MESSAGE VALUE 2.
88 SLAVE-TRUCK-MESSAGE VALUE 3.
88 MAILROOM-MESSAGE VALUE 4.
88 USER-INTERFACE VALUE 6.
88 FSC-ARPA-TRUCK VALUE 7.
88 FSC-AREF-TRUCK VALUE 8.
88 SUPERVISOR VALUE 9.
03 I-TRUCK-NUMBER PIC 9(4).
03 I-MESSAGE-TYPE PIC 9(4).
88 MESSAGE-ACKNOWLEDGEMENT VALUE 2.
88 MESSAGE-TO-ERROR-QUEUE VALUE 1.
88 MESSAGE-TO-DEFER-QUEUE VALUE 3.
88 MESSAGE-TO-NODE-QUEUE VALUE 4.
88 DETACH-OUTTRAY VALUE 5.
88 ATTACH-INTRAY VALUE 6.
88 MESSAGE-POST VALUE 7.
88 PRIVATE-MESSAGE-DITCHED VALUE 8.
88 TRANSMIT-MESSAGE VALUE 10.
88 FSC-FILE GENERATED VALUE 11.
88 ROUTED-UNDELIVERED VALUE 12.
03 I-MESSAGE-SUBTYPE PIC 9(4).
88 MESSAGE VALUE 100.
88 REPLY-ACK VALUE 300.
88 READ-ACK VALUE 301.
88 DELIVERY-ACK VALUE 302.
88 TARGET-ACK VALUE 303.
88 SOURCE-ACK VALUE 304.
03 FILLER PIC XX.
03 I-ORIGINAL-ITEM-NO PIC S9(10).
03 I-CURRENT-ITEM-NO PIC 99(10).
03 FILLER PIC XX.
03 I-USER-NAME PIC X(27).
03 I-NODE-INFO REDEFINES I-USER-NAME.
05 I-NAME.
07 I-LOCATION PIC X(6).
07 I-SUB-LOCATION PIC XX.
07 I-LOCATION2 PIC X(6)
07 I-SUB-LOCATION2 PIC XX
07 I-COMPUTER PIC X(8)
07 I-PRIORITY PIC 9
07 I-ACK PIC 9
07 FILLER PIC X
03 I-COMMENT REDEFINE I-NODE-INFO.
MPE/iX 5.0 Documentation