Enhance CRUISE log file displays to provide more information and improve usability

1. FUNCTION name in system log: The system log does not identify the function that was executed. It would be helpful if the function was included in the log. Looking at the log it is not possible to tell what function was run. .
SSU CPU DATE TIME TERM ENTRY
WN 0 02/07/14 22:46:39 010000 START-C400-TEST
WN 0 02/07/14 15:53:09 010000 TABLE -C400-TEST- COMPLETED

Adding the function to the log will make the log more useful . The display might look like this:
SSU CPU DATE TIME TERM ENTRY

WN 0 02/07/14 14:45:41 010000 TABLE -C400-TEST- COMPLETED
WN 0 02/07/14 13:59:14 010000 START-C400-TEST - RST
WN 0 02/07/14 13:20:34 010000 TABLE -C400-TEST- COMPLETED
WN 0 02/07/14 12:25:35 010000 START-C400-TEST - CAP

Table log file:
2. Display multiple table level log entries: Currently the table log file shows only the result of the most recent table run. The log file should contain the log from multiple executions. It should be a user specifiable no. of blocks or lines of display. As new information is added and the allocated space is filled up, the oldest record or log entry can be deleted to make room for the new one.

3. Split status messages and error messages in the log: The status messages and error messages are combined in the same log file. This makes it more difficult to see the status information. One has to scroll through and page down through the error messages to view the status. The status and error information should be split into two different displays. They can be physically split or the display entry can be modified to show one or the other and the log filtered to show the requested information.
zfcru display-log-c400-test
CSMP0097I 15.21.25 CPU-0 SS-BSS SSU-WN IS-01
FCRU0000I 15.21.25 MESSAGE LOGGING TABLE -C400-TEST-
CPU *0* SSU WN DATE 01/16/14 TERMINAL 010000
WN 14:46:11 TABLE -C400-TEST-
FUNCTION-CAP STARTED
WN 14:46:11 CHAIN CHASE STARTED PROCESSING COMMON RECORDS _
WN 14:46:12 FIND ERROR - C063 - 0000000069CCE93D SRCH ADR
- C402 - 0000000064D80086 FROM REF
WN 14:46:12 FIND ERROR - C063 - 000000000300C723 SRCH ADR
- C402 - 0000000064D80086 FROM REF
WN 14:46:12 FIND ERROR - C063 - 000000005EE2BA3D SRCH ADR _
MORE DATA AVAILABLE, ENTER ZPAGE TO CONTINUE+
zpage

Many lines and more pages skipped ………………..

CSMP0097I 15.21.32 CPU-0 SS-BSS SSU-WN IS-01
WN 14:46:12 FIND ERROR - C063 - 000000005FAD5C66 SRCH ADR
- C402 - 0000000064D7F532 FROM REF
WN 14:46:12 FIND ERROR - C063 - 0000000060DBC6B1 SRCH ADR
- C402 - 0000000064D80086 FROM REF _

WN 15:20:25 CHAIN CHASE FINISHED PROCESSING COMMON RECORDS
WN 15:20:25 CHAIN CHASE STARTED PROCESSING SSU-WN
WN 15:20:25 CHAIN CHASE FINISHED PROCESSING SSU-WN
WN 15:20:25 003337331 RECORDS FOUND _
003337331 RECORDS WRITTEN TO BFA
WN 15:20:25 TABLE -C400-TEST-
FUNCTION-CAP COMPLETED
000041365 ERRORS DETECTED

FCRU0000I 15.21.40 END OF DISPLAY+

4. Display FVN in log entries: The completion messages in the table specific log should include the File Version Number (FVN). This will avoid ambiguity and provide better information about what was chain-chased. The FVN displayed should be the one specified with the REF entry in the actual table that was run.
Current display
zfcru display-log-wnt3pocx

CSMP0097I 12.36.48 CPU-0 SS-BSS SSU-WN IS-01
FCRU0000I 12.36.48 MESSAGE LOGGING TABLE -WNT3POCX-
CPU *0* SSU WN DATE 02/09/14 TERMINAL 010000
WN 12:31:17 TABLE -WNT3POCX-
FUNCTION-VER STARTED
WN 12:31:17 CHAIN CHASE STARTED PROCESSING COMMON RECORDS
WN 12:31:30 CHAIN CHASE OF FILE ID-C1C9 COMPLETED
WN 12:31:36 CHAIN CHASE OF FILE ID-C3C9 COMPLETED
WN 12:32:43 CHAIN CHASE OF FILE ID-C3D3 COMPLETED
WN 12:33:08 CHAIN CHASE OF FILE ID-C3D7 COMPLETED
Display with proposed changes
WN 12:31:30 CHAIN CHASE OF FILE ID-C1C9 FVN-00 COMPLETED
WN 12:31:36 CHAIN CHASE OF FILE ID-C3C9 FVN-02 COMPLETED
WN 12:32:43 CHAIN CHASE OF FILE ID-C3D3 FVN-00 COMPLETED
WN 12:33:08 CHAIN CHASE OF FILE ID-C3D7 FVN-01 COMPLETED