Migration Audit and Plan Summary Report

Understanding the Log Files in a

GDT / Net Express Environment

Log Files in GDT / Net Express

Prepared for

GDT Customers

Prepared by

Doug Evans and Detlef Lexut

September 2009

Infosol, Inc.19/27/2018

Understanding the Log Files in a

GDT / Net Express Environment

TDSEXCPT log ………………………………………………. Page 3

SYSEXCPT log ………………………………………………. Page 5

SYSSPAWN log………………………………………………. Page 7

DISPLAY log ………………………………………………. Page 9

FLOW log ………………………………………………. Page 11

GEPFILE log ………………………………………………. Page 14

FSYS01 log ………………………………………………. Page 16

THINCLIENTSERVER log ……………………………………Page 18

FHNETERR log ………………………………………………. Page 21

CCIERR log ………………………………………………. Page 22

MFDEBUG log …………………………………………...…. Page 23

TPR / Transaction Abort Codes ……………………………Page 24

FILE Status Codes ……………………………………………Page 26

Extended File Status Codes ………………………………..Page 29

Runtime System Error Messages ………………………….Page 33SECTION 1:GDT Log Files

TDSEXCPT Log

This log is used to show usual runtime errors such as illegal decimal etc… This log will show all TDS exceptions with some detail. The file is always created. Some of the particular information you will find in the file is:

Date and Time of the event

Short text information describing the event

TPR name that aborted

User / User ID

Result Code

Whenever an entry is added to the TDSEXCPT log, this will also be seen in the FLOW log file(s) as an aborted TX/TPR.

You may want to look at the SYSEXCPT log to gather more details as to why the event happened. Not all events will be seen in both the TDSEXCPT log and SYSEXCPT log.

It will depend on the circumstances surrounding the event.

Figure 1-A GDT system flow for TDSEXCPT log

SECTION 1:GDT Log Files

TDSEXCPT Log continued

040614 15475177 TPR abort INFADDR2 DOUG 00000 04C5/FE

040629 11240726 TPR abort IPROJECT DOUG 00000 04C5/FE

040629 11244085 TPR abort IPROJECT DOUG 00000 04C5/FF

040629 11345180 TPR abort IPROJECT DOUG 00000 04C5/FF

040629 11433480 TPR abort IPROJECT DOUG 00000 04C5/FF

040629 13394045 TPR abort IPROJECT DOUG 00000 04C5/FE

040629 13411563 TPR abort IPROJECT DOUG 00000 04C5/FE

040629 13534763 TPR abort IPROJECT DOUG 00000 04C5/FE

040629 13575818 TPR abort IPROJECT DOUG 00000 04C5/FF

040629 14021516 TPR abort IPROJECT DOUG 00000 04C5/FE

040706 12312964 TPR abort IPROJECT DOUG 00000 04C5/FF

040706 14382779 TPR abort IPROJECT DOUG 00000 04C5/FF

040714 12370213 TPR abort IPROJECT DOUG 00000 04C5/FF

Figure 2-A Sample details from the TDSEXCPT log

SECTION 1:GDT Log Files

SYSEXCPT Log

This log file shows “System” exceptions with some detail. This log should be monitored. This log was not originally designed to be used by the customer. It contains mostly detail for internal use that would be provided to InfoSol Inc for review.

If an event shows up in this log, this should alert the viewer to review the TDSEXCPT log file for further details. The view should match up event information by the date and time stamp provided in the logs. This file is always created. Some of the particular information you will find in the file is:

Date and Time of the event

Detail text information describing the event

This log file will contain additional information in case a TDS session aborted due to unusual situations. Currently spawn handler and memory-swap handler information is directed to this log file.

Figure 1-B GDT system flow for the SYSEXCPT log

SECTION 1:GDT Log Files

SYSEXCPT Log continued

050217 15092673 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15133682 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15141371 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15145840 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15171387 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15184987 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050217 15201651 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050218 09305132 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050302 10563015 SPW: SYSJOB: f: 004 op:oi st:9/124 fn:$FILESHARE/\H_SYSJOB

050302 10563023 SPW: TMPJOB: f: 004 op:oi st:41 fn:SPW_2890000.TMP

Figure 2-B Sample details from SYSEXCPT log

050217 15092673 SPW: SYSJOB: f: 006 op: st:9/124 fn:$$CONF05\H_SYSJOB

050302 10563015 SPW: SYSJOB: f: 004 op:oi st:9/124 fn:$FILESHARE/\H_SYSJOB

050302 10563023 SPW: TMPJOB: f: 004 op:oi st:41 fn:SPW_2890000.TMP

Date

Time

ID: SPW for spawn or SJB for subjob

IFN the internal filename i.e. SYSJOB

f: internal function id (for GDT internal debugging purposes only)

op: internal operation id (for GDT internal debugging purposes only)

st: file status

fn: filename that caused the status

Figure 2-C Describing the SYSEXCPT log.

SECTION 1:GDT Log Files

SYSSPAWN Log

This log file always gets created when spawns are submitted by the system for execution. Some of the particular information you will find in the file is:

Date and Time of the spawn
Username and Terminal ID
Transaction with the parameters
Success / non-success of transaction

Figure 3-A GDT system flow for the SYSSPAWN log

040622 09225788 DOUG NTWKBBP7 ISPN 00000000 S

040622 09225925 DOUG NTWKBBP7 ISPN 00000000 S

040622 09230065 DOUG NTWKBBP7 ISPN 00000000 S

040622 09255131 DOUG NTWKBBP7 ISPN 00000000 S

Figure 3-B Sample details from the SYSSPAWN log

SECTION 1:GDT Log Files

SYSSPAWN Log continued

050608 154522819 e OPERATOR ONP11121 ZEBCARDSTX013094H0 M

050608 154523219 d OPERATOR ONP11121

Date, Time, ID, User, TX, Parameters

Date in YYMMDD format

Time in Hour, Minute, Second, Microsecond format

ID indicates e=entered for execution, d=done, F=failed, s=submitted into queue

User the User-Id under which tx ran

TX the Transaction to be executed

Params the Transaction input parameters

Figure 3-C Describing the SYSSPAWN log.

SECTION 1:GDT Log Files

DISPLAY Log

The purpose of this log is to show displays from TDS transactions. This is triggered via the COBOL DISPLAY statement in the source. To turn this feature on, the GDTMONR.PAR file must correctly have the DISP parameter set. The following is an example:

DISP 1 C:\INFOSOL\TXSVR_DISPLAY_9999.LOG

Note:

The 9999 will allow DISPLAY log(s) to be produced for each TCS (transaction server) that is running. The flow setting of ‘1’ is mandatory.

Figure 4-A GDT system flow for the DISPLAY log

SECTION 1:GDT Log Files

DISPLAY Log continued

********* STARTUP ROUTINES BEGINNING *********

232 TEST RECORDS LOADED INTO MEMORY

008 TEST2 RECORDS LOADED INTO MEMORY

621 TEST3 CODES LOADED INTO MEMORY

391 TEST4 CODES LOADED INTO MEMORY

********* STARTUP ROUTINES COMPLETED *********

ISSUE 196 SUCCESSFUL EXIT OF CONF2005 PROGRAM

Figure 4-B Sample details from the DISPLAY log

SECTION 1:GDT Log Files

FLOW Logs

The purpose of the flow logs are to flow, at various levels of detail, TDS transactions.

Other critical information is also entered into this log such as Opening and Closing of files along with the file status for each file. There is 1 flow log generated per transaction server (TCS).

Some of the particular information you will find in the file is:

Transaction start and stop

File I-O

Inbound and Outbound messages to the TPR

File Status information

Spawn logging

The amount of detail to be shown in the Flow logs is determined by the FLOW setting in GDTMONR.PAR. The following is a sample FLOW setting:

Flow 255 C:\INFOSOL\LOGS\GOPHERtcredir_9999.LOG writethru

*--> │Bit │ value │ │

*--> │ 1 │ 1 │ TX/TPR start and stop │

*--> │ 2 │ 2 │ File I-O│

*--> │ 3 │ 4 │ Inbound messages (receive) │

*--> │ 4 │ 8 │ Outbound messages (send) │

*--> │ 5 │ 16 │ Restrict File-IO (no '00') │

*--> │ 6 │ 32 │ Spawn │

*--> │ 7 │ 64 │ Concurrency │

*--> │ 8 │ 128 │ SQL (ODS) │

*--> │ 9 │ 256 │ not used │

*--> │ .. │ ... │ not used │

*--> │ 31 │ 1073741824 │ not used │

*--> │ 32 │ 2147483648 │ internal debug #1 │

Figure 5-AFLOW log settings (add up the value’s for each detail you want to have and

that is the FLOW setting to use).

SECTION 1:GDT Log Files

FLOW Logs continued

Figure 5-BGDT system flow for the FLOW logs

-----> 7628805/05/2317.50.28.36G-LOGIN OPERATOR 6

-----> and <----- are triggers for TX in and TX out, they are followed by the TX number, date, time, TX-Name, Username and User-ID

Figure 5-C Transaction in and out triggers

> 105/05/2317.50.28.36G-LOGIN OPERATOR 6

> and < are triggers for TPR in and TPR out, they are followed by the TPR number, date, time, TX-Name, Username and User-ID

Figure 5-D TPR and TPR in and out triggers

SECTION 1:GDT Log Files

FLOW Logs continued

OUTBOUND(CDF)EGI, length=00228

Send message, CDF for Forms, VIP for VIPEMUL, ESI/EMI/EGI indicator and the length of message to send

Figure 5-E Outbound message

INBOUND (CDF) EGI, length=00228

Receive message, CDF for Forms, VIP for VIPEMUL, ESI/EMI/EGI indicator and the length of message to receive

Figure 5-F Inbound message

"00 DOUG " "303020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202052555353202020202020

Just the buffer in character and hexadecimal format

Figure 5-G Screen details

05/05/2317.50.30.26FA00|open|00 |rmt:TESTFILE 01000300 OSAL:IMW. 6000LOGON $$CONF05\TESTFILE

Date, Time, file-operation ID (documented in the MF Books), file-operation text, filestatus, rmt=remote or lcl=local access, filename, filehandle. OSAL=3 characters First=OPENMODE(I=Input, O=output, U=Update) second=SHAREMODE(M=Monitored,O=Onewrite,E=Exclusive) third=ACCESSMODE(R=Read, W=Write), Internal Number, TX-Name ExternalFilename

Figure 5-H File access details

SECTION 1:GDT Log Files

GEPFILE Log

The purpose of the GEPFILE is to hold the information that you would see on the GDT Console. This is a standard text file that can be easily imported into EXCEL for ease of viewing. Contains console log information and basic abort information on jobs running via the GDT Console.

Figure 6-A GDT system flow for the GEPFILE log

SECTION 1:GDT Log Files

GEPFILE Log continued

040409165020 x00006 IN \INFOSOL\PROD\JCL\PROJECTS.JCL

040409165022 x00006 SCH JOB scheduled

040409165023 x00006 PROJECTS EX

040409165023 x00000 PROJECTS ISM gu=DOUG,wn=DEVANSXP

040409165023 x00006 PROJECTS PNLSACCT DSP ENTER P FOR ONLY ACCOUNT NUMBERS

040409165023 x00006 PROJECTS PNLSACCT DSP ENTER F FOR FULL LISTING

040409165023 x00006 PROJECTS WFR waits for reply

040409165030 x00000 PROJECTS ISM accepted 'P'

040409165031 x00006 PROJECTS OUT JOB completed

040412091537 x00004 DEL JOB deleted

040412091537 x00005 DEL JOB deleted

040412091537 x00006 DEL JOB deleted

040415155628 x00000 CLI \INFOSOL\PROD\JCL\SEND2.JCL

040415155628 x00007 IN \INFOSOL\PROD\JCL\SEND2.JCL

040415155635 x00007 SCH JOB scheduled

040415155644 x00007 SEND2 EX

040415155644 x00000 SEND2 ISM gu=DOUG,wn=DEVANSXP

040415155645 x00007 SEND2 SND 'TDORSOLD -- SENT REC KEY NOF DTLSOLD - 95231'

040415155645 x00007 SEND2 OUT JOB completed

Figure 6-B Sample details from the GEPFILE log

* Gepfile = C:\GOPHER\PROD\SOURCE\BATCH\gepfile

Gepfile = "\\127.0.0.1\HPOffice"

Figure 6-C In GDTBATCH.PAR, you can direct the GDT Console output to go directly to a printer instead of the GEPFILE log. It is best to use a line printer set up accordingly under Windows to truly print line by line.

SECTION 1:GDT Log Files

FSYS01 Log

The purpose of the this log is for investigating FSYS01 issues. Logging of FSYS01 should never be left on full time.

Some of the particular information you will find in the file is:

Details on when FSYS01 is checking the H_SYSJOB record
Details on when FSYS01 is getting jobs
Details on when FSYS01 is accepting keyboard input
Details on when FSYS01 is in shutdown mode
Details on when FSYS01 is modifying a job
Details on when FSYS01 is deleting a job
Details on when FSYS01 is moving a job
Details on when FSYS01 is adding a job

Figure 7-A GDT system flow for the FSYS01 log

SECTION 1:GDT Log Files

FSYS01 Log continued

START "FSYS01" FSYS01 -uid OPERATOR -pwd OPERATOR

START "FSYS01" FSYS01 -T -uid OPERATOR -pwd OPERATOR

Figure 7-B The –T will allow you to start FSYS01 in “Trace” mode which will create the FSYS01.LOG in the default directory that FSYS01 is started in.

125105 C-ChkSysR1

125105 C-ChkSysR2

125105 get ALL Jobs(i)

125105 UP-ChkMovJob

125105 get ALL Jobs(l) Force/Delay/Time 0/0/1

125105 UP-ChkMovJob

125125 get ALL Jobs(l) Force/Delay/Time 0/1/0

125125 UP-ChkMovJob

125125 UP-AddJob2Exec 00017

125125 > UP-ExecJob 00017

125125 . >lock job

125125 . <lock job 0

125125 . commited

125125 < UP-ExecJob

125136 get ALL Jobs(l) Force/Delay/Time 0/1/0

Figure 7-CSample details from the FSYS01 log

SECTION 1:GDT Log Files

ThinClientServer Log

The purpose of this log is to present details about the TDS transactions that are running as well as the state of the transaction servers and the client connections. You can match up entries from this log to the individual FLOW logs via the date / time stamps provided.

How this works: a transaction enters the client listener and then is queued. The transaction is then picked up and is run on a free transaction instance. This transaction instance is monitored for success, failure or time out. Once the transaction has finished, no matter what its state is, it is returned to the client. All of this information is captured in the ThinClientServer log. Location of this log is based on the TCS_LOGFILE setting in the \TCS\CFG\GDT.CFG configuration file.

The log file has 3 columns:

1. The time stamp

2. The part of the [service] reporting the msg, i.e. tcp/ip service (vip), transaction server (txs), dispatcher or transaction instance (dpr, tx(1)), startup routine (startup rtn), batch message interface (bmi), spawn (spw)

3. The msg

Figure 8-A. Describing the ThinClientServer log.

SECTION 1:GDT Log Files

ThinClientServer Log continued

Figure 8-B GDT system flow for the ThinClientServer log

SECTION 1:GDT Log Files

ThinClientServer Log continued

you are now connected to the GDT Transaction system

JIMS Ready: Fri Sep 04 09:27:52:250 [TX(1)] Transaction returning message size: 87

Fri Sep 04 09:27:52:250 [TX(1)] Returning Request to a VIP client

Fri Sep 04 09:27:52:250 [TXS] Posting Response to VIP client

Fri Sep 04 09:27:52:250 [VIP] Transmitted response, size: 117

Fri Sep 04 09:27:52:343 [VIP] 1620 RCV 0063/0000 (1)

Fri Sep 04 09:27:52:343 [VIP] 1620 < RCV END (1)

Fri Sep 04 09:27:52:343 [VIP] Received 63 of the expected 63 bytes

Fri Sep 04 09:27:52:343 [VIP] 1620 < QUEUED:PRTY=NORMAL:(1)

Fri Sep 04 09:27:52:343 [VIP] Queue size: 1

Fri Sep 04 09:27:52:343 [TXS] Request: regular TX

Fri Sep 04 09:27:52:343 [DPR] Request from client index 1 is being run on TX 1

Fri Sep 04 09:27:52:343 [TX(1)] Executing Request from a VIP client

Fri Sep 04 09:27:52:343 [TX(1)]

3e 20 45 58 45 43 3a 20 4a 55 54 58 33 31 20 20 49 4f 4b 20 20 30 31 50 39 39 4a 55 54 58 30 31 30 49 4e 46 4f 53 4f 4c 20

Fri Sep 04 09:27:52:343 [TX(1)] Sending Command: EXEC - Message: JUTX31 IOK 01P99JUTX010INFOSOL - as user: INFOSOL

Fri Sep 04 09:27:52:593 [TX(1)] Transaction OK, took: 0.250000 seconds

Fri Sep 04 09:27:52:593 [TX(1)] Transaction complete for client: 1

JUTX31 IOK 01P99JUTX014INFOSOL Fri Sep 04 09:27:52:593 [TX(1)] Transaction returning message size: 101

Fri Sep 04 09:27:52:593 [TX(1)] Returning Request to a VIP client

Fri Sep 04 09:27:52:593 [TXS] Posting Response to VIP client

Fri Sep 04 09:27:52:593 [VIP] Transmitted response, size: 131

Figure 8-CSample details from the ThinClientServer log

SECTION 2:MicroFocus Log Files

FHNETERR log file

Fileshare Error Reporting - Fileshare clients log messages returned from CCI in both the fhredir.msg and fhneterr.log files in the current directory. Be aware that this file exists. This may be something that Infosol may request if you are experiencing connection issues.

CCI: 040723 14205217 0009 07 CCITC32-0016E Cannot find CCITCP2 - CCITCP cannot be used without a CCITCP2 process.

CCI: 040723 14205227 0009 07 CCITC32-0016E Cannot find CCITCP2 - CCITCP cannot be used without a CCITCP2 process.

CCI: 040723 15423518 0009 07 CCITC32-0016E Cannot find CCITCP2 - CCITCP cannot be used without a CCITCP2 process.

CCI: 040723 15423531 0009 07 CCITC32-0016E Cannot find CCITCP2 - CCITCP cannot be used without a CCITCP2 process.

CCI: 040810 13325037 0001 07 CCITC32-0001I A CCITCP call has timed-out.

CCI: 040810 13345175 0001 07 CCITC32-0001I A CCITCP call has timed-out.

CCI: 040810 14223826 0001 07 CCITC32-0001I A CCITCP call has timed-out.

Figure 9-ASample details from the FHNETERR log

(Communication Errors).

You may run across a situation where FILESHARE does not start and aborts with a 9/124 error.

Error status 9/124 on an I/O operation indicates that a communications error has occurred between the Fileshare Client and the Fileshare Server.

The most common time for error 9/124 to occur is on the very first I/O request that your program makes. It is then that the Fileshare Client tries to contact the Fileshare Server. If the Fileshare Client is unable to do this, it returns error 9/124. If you receive this error, examine the configuration of Fileshare and check that:

Stop and restart the MicroFocus Directory Server (service) – this should do the trick.
The Fileshare Server is started and operational.

Verify that you have a working network connection between the Fileshare Client and the Fileshare Server .

SECTION 2:MicroFocus Log Files

CCIERR log file

The CCIERR Log file is produced by Micro Focus for any communication problem between client and server programs using the CCI protocol.Be aware that this file exists. This may be something that Infosol may request if you are experiencing connection issues.

15:40:316/23/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0050) 20000 E existence_check(), called in service_request_fn, failed with return code 152.

15:40:316/23/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0017) 20000 E Namer_request(), called in NET_CONNECT, failed with return code 152.

10:42:286/28/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0014) 20000 E parse_names(), called in NET_CONNECT, failed with return code 151.

10:43:066/28/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0014) 20000 E parse_names(), called in NET_CONNECT, failed with return code 151.

17:59:136/29/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0020) 20000 E closesocket(), called in NET_DISCONNECT, failed with return code 10093.

Figure 10-ASample details from the CCIERR log

SECTION 2:MicroFocus Log Files

MFDEBUG log file

The MFDEBUG Log file is produced by Micro Focus to give detail event information during a protection violation. Be aware that this file exists. This may be something that Infosol may request.

2 error codes that will produce this:

COBRT114 Attempt to access item beyond bounds of memory: Memory access violation has been detected by your operating system.

COBRT115 Unexpected signal (Fatal): A signal the run-time system was not expecting has been caught.

NetExpress Exception Handler - 07/20/2004 09:44:55

C:\PROGRA~1\MERANT\NETEXP~1\BASE\BIN\COBOL.EXE caused an exception at address : 0x03008C58

Exception type - EXCEPTION_ACCESS_VIOLATION on Read. Address 0x23215FA3

Registers:

EAX 03012858EBX 02A8DC30

ECX 00000000EDX 02A8DB04

DS 0023ESI 02AB1984

ES 0023EDI 20202020

FS 0038GS 0000

CS 001BEIP 03008C58

SS 0023ESP 00BBFE44EBP 03013108

Flags 00010246

Error occurred in : TOKEN.gnt

COBOL call stack:

COBOL0TOKEN(gnt program), loaded from C:\Program Files\MERANT\Net Express\Base\BIN\check.lbr

CHECKER(gnt program), loaded from C:\Program Files\MERANT\Net Express\Base\BIN\check.lbr

COBCLI(gnt program), loaded from C:\Program Files\MERANT\Net Express\Base\BIN\COBCLI.lbr

cobol(obj program)

Run-time : C:\Program Files\MERANT\Net Express\Base\BIN\CBLRTSS.DLL, loaded at 0x60080000

CompanyName Micro Focus International Limited

FileDescription Micro Focus 32-bit RTS

FileVersion 3.872, 3.659

OriginalFileName cblrtss.dll

ProductName Micro Focus Net Express

ProductVersion 3.1.11

SpecialBuild RTS Websync 3.1.013

OS Information:

Windows NT 5.1 (Build 2600: Service Pack 1)

CPU: Intel Pentium Model 8 step 1, 1 processors

Available memory - 294384 KB

Figure 11-ASample details from the MFDEBUG log

Appendix A:TPR / Transaction Abort Codes

0980.USERREQ .Abort requested by user (TPR)

1E04.BREAK .Break request from terminal ( [ESC] )

0804.ADDROUT .Address out of bounds

1853.ARGERR .SYMBOLIC-QUEUE: wrong item

1510.ARVIOL .Access right violation

1206.BUFNBOV .TDS buffer pool overflow

1878.NOMATCH .The next program name is unknown

1223.ENTRYOV .Entry overflow

1C0B.EXHAUST .End-of-file already signalled

1228.FILEOV .file overflow due to a record insertion

0A06.FLNAV .File in alert status - must be recovered

0A05.FUNCNAV .Unavailable function for specified file

Migration Audit and Plan Summary Report

Table of Contents:

TDSEXCPT log ………………………………………………. Page 3

SYSEXCPT log ………………………………………………. Page 5

SYSSPAWN log………………………………………………. Page 7

DISPLAY log ………………………………………………. Page 9

FLOW log ………………………………………………. Page 11

GEPFILE log ………………………………………………. Page 14

TDSEXCPT Log

TDSEXCPT Log continued

SYSEXCPT Log

SYSEXCPT Log continued

SYSSPAWN Log

SYSSPAWN Log continued

DISPLAY Log

DISPLAY Log continued

FLOW Logs

FLOW Logs continued

FLOW Logs continued

GEPFILE Log

The purpose of the GEPFILE is to hold the information that you would see on the GDT Console. This is a standard text file that can be easily imported into EXCEL for ease of viewing. Contains console log information and basic abort information on jobs running via the GDT Console.