Advanced Log File Concepts under GDT / TCS / NET EXPRESS Revisited.

Advanced Log File Concepts under GDT / TCS / NET EXPRESS

Revisited

Advanced Log File Concepts RevisitedDoug Evans and Detlef Lexut

GDT 2008 International User ConferenceAugust 10 – 13 Lake Las Vegas, Nevada

The GDT Log Files

TDSEXCPT SYSEXCPT SYSSPAWN DISPLAY FLOW GEPFILE FSYS01 THINCLIENTSERVER



KEY NET EXPRESS LOGS

CCIERR FHNETERR MFDEBUG.LOG



GDTBATCH / TDS

GDTBATCH JOR

TDS TDSEXCPT.LOG

JOR / TDSEXCPT.LOG Show usual Runtime errors like illegal decimal etc..

SYSEXCPT Further detail on some errors shown in JOR and / or

TDSEXCPT.LOG GDT Internal Program issues

Unexpected situation occurred Wrongly programmed situation



TDSEXCPT LOG

Purpose: - Shows all TDS exceptions with some detail. - File is always created. - Information shown:

- Date and Time of the event - Short Text information - TPR name - User/User-id - Result Code



TDSEXCPT Log

Whenever an entry is added to TDSEXCPT.LOG, this will also be seen in the FLOW files as an aborted TX/TPR.

The SYSEXCPT may then have more details on why the situation was caused.

It is not mandatory that each time a record is created in SYSEXCPT.LOG that an entry must be seen in TDSEXCPT.LOG or vice versa. It depends on other circumstances and probably a retry of a operation may resolve a temporary issue that usually should not occur; this will be reported in SYSEXCPT.LOG but may not cause a TPR failure and therefore no abort.



TDSEXCPT Log



SAMPLE TDSEXCPT Log Content

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



T P R / 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 1466.LOCKVIOL .Accessed file is locked




00D3.CANEVT .Transaction cancelled (see CANCELTX) 1020.INDUNKN .Index unknown - TDS error 0A07.ITMNAV .Modification of protected file is not allowed 0204.KEYCHG .Attempt to change record key on re-issue of WRITE 1807.LNERR .Erroneous length for variable length record 1C04.NOCURREC .A seq. file request preceded a direct request 1C19.NODELETE .No DELETE allowed 0115.NOTALL .'M CANCEL' was incomplete 1C01.NOTOPEN .Referenced file is not open 0700.NOWAIT .Violation of nonconcurrency 1730.OPERATOR .Transaction cancelled by 'M CANCEL' command 1806.OPTERR .Option error (Journal suppressed) 1463.PMDVIOL .Processing mode violation 04C5.PROCEXP .Procedure exception within a program 1021.QUNKN .SYMBOLIC-QUEUE within INPUT CD is incorrect 1623.RESVIOL .Result of a resource handling violation 1442.RCVVIOL .Violation when wrong RECEIVE




0A18.SCIDXNAV .Secondary index not available (UFAS)

1214.SFNBOV .TDS.DEBUG: Directory overflow 1441.SNDVIOL .Violation when using SEND 1219.TABOV .Locked pages table overflow

(Currently allocated) 0029.TIMELIM .TPR time limit exceeded 1E05.UNRECIO .Unrecoverable I/O error 120F.COUNTOV .Locked pages table overflow

(Declared in TDSGEN) 186B.UBUGERR .IDS/2 user error




* 3000-30FF = Forms/Vipemul 3000.VIPNA .The module VIPEMUL is not available 3001.VIPINV .VIPEMUL directives invalid (run 'GDTVIPA /C' to check) * 3100-31FF = GTW/SPAWN/BMI 3100.GTWLESSP .not enough linkage parameters for GTWriter

procedures 3101.GTWDLLNF .GTW ZPRI32.DLL library not found 3102.GTWFHNF .GTW External Filehandler not found 3103.GTWDOSNE .GTW DOS call not successfull 3104.GTWSPLNE .GTW Windows printer spooling not executable 3105.SPWLESSP .not enough linkage parameters for spawning

procedures 3106.SPWFLNAV .The file 'H_SYSJOB' is not available 3107.BMILESSP .not enough linkage parameters for BMI procedures * 3200-32FF = GDT Monitors *200.SHRDUPD .Update on file declared with 'Shared Read' clause * 3300-33FF = PROGRAM 3300.PGMFAIL .program needs recompilation



SYSEXCPT LOG

Purpose Shows SYSTEM exceptions with some detail. Should be monitored Originally not designed to be used by the

customer Most Detail for internal use

If entry shows up, should alert customer to review the TDSEXCPT.LOG for further details by matching the date\time stamp entry

File is always created. Information shown:

- Date and Time of the event - Detail Text information



SYSEXCPT LOG

The file SYSEXCPT.LOG will contain additional information in case a TDS session aborted due to unusual situations.

Currently only the SPAWN handler (SPW: ...) and the the MEMORY-SWAP handler

(SWP: ...) are creating entries in this file. It is not mandatory that each time a record is created

in SYSEXCPT.LOG that an entry must be seen in TDSEXCPT.LOG or vice versa. It depends on other circumstances and probably a retry of a operation may resolve a temporary issue that usually should not occur; this will be reported in SYSEXCPT.LOG but may not cause a TPR failure and therefore no abort.



SYSEXCPT LOG



SAMPLE SYSEXCPT Log Content Pre GDT V4.1

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

SEE FILE STATUS ERRORS LISTED IN THE GDT HELP SYSTEM



What do the details mean?

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



SAMPLE SYSEXCPT Log Content GDT V4.1

GDT V4.1 view 050303 164035839 SPW: SYSJOB: f: 006 op: st:9/124

fn:$CustFS\H_SYSJOB 050315 120214179 SWP: To F/M: 9001 f: 050616 071412859 SWP: To F/M:

Date, Time, ID, Text Date in YYMMDD format Time in Hour, Minute, Second, Microsecond format ID indicates the Area where the problem occurs,

SPW=SPAWN, SWP=SWAP Text: additional information for Support



SYSSPAWN LOG

Purpose Always gets created when spawns are submitted by

the system for execution Cannot be turned off at this time Details:

Date/Time of spawn Username and Termid TX with the parameters FUTURE release will include success/non-success of TX.



SYSSPAWN LOG



SAMPLE SYSSPAWN Log Content Pre GDT V4.1

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



SAMPLE SYSSPAWN Log Content GDT V4.1

GDT V4.1 VIEW 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



DISPLAY LOG

Purpose DISP directive in GDTMON*.PAR to show displays

from TDS transactions. DISP 1 \INFOSOL\TXSVR_DISP_9999.LOG Flow level must be a 1



DISPLAY LOG



SAMPLE DISPLAY Log Content

********* 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 ISSUE 196 SUCCESSFUL EXIT OF CONF2005 PROGRAM ISSUE 196 SUCCESSFUL EXIT OF CONF2005 PROGRAM



FLOW LOG

Purpose 1 per Transaction Server in Thin Client To show flow of TPR/TX. Details

TX and TPR start and stop File I-O Inbound Messages Outbound Messages Restricted File I-O logging File Status SPAWN logging (stored/executed)



FLOW LOG

Bit Settings to show information in FLOW LOG Bit Value Report included

01 1 TX and TPR start and stop 02 2 File I-O 03 4 Inbound Messages 04 8 Outbound Messages 05 16 Restricted File I-O logging (Bit 2 MUST also be

set) File Status "00" will not be reported, except CMIT/RBCK

06 32 SPAWN logging (stored/executed)



FLOW LOG




A-MainRepeat (in) 00000 0 0 G-LOGIN Paragraph or Section name followed by additional

useful support information like client-id and internal flags, not for user




C-NormalTX 00000 0 0 G-LOGIN Paragraph or Section name followed by additional





C-NormTX (chkTX) 00000 0 0 G-LOGIN Paragraph or Section name followed by additional





C-NrmTXDo (route) 00000 0 0 G-LOGIN Paragraph or Section name followed by additional





-----> 76288 05/05/23 17.50.28.36 G-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




>>> 1 05/05/23 17.50.28.36 G-LOGIN OPERATOR 6 >>> and <<< are triggers for TPR in and TX out, they

are followed by the TPR number, date, time, TX-Name, Username and User-ID




--> OUTBOUND (CDF) EGI, length=00228 Send message, CDF for Forms, VIP for VIPEMUL,

ESI/EMI/EGI indicator and the length of message to send




Vektor details: 001 000 000 Vektor details: 000 003 001

Internal details to send message




Right after the VEKTOR Details "SSSSSSS"

"53535353535353" "SSSRRSS"

"53535352525353“ The Vektor settings for a FORMS send statement




Screen details: "00 DOUG "

"303020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202052555353202020202020 Just the buffer in character and hexadecimal

format




<<< 2 05/05/23 17.50.30.00 G-LOGIN RUSS 6 0000/00 LOGON >>> and <<< are triggers for TPR in and TX out, they

are followed by the TPR number, date, time, TX-Name, Username and User-ID




05/05/23 17.50.30.26 FA00|open|00 |rmt:TESTFILE 01000300 OSAL:IMW. 6000 LOGON $$CONF05\TESTFILE Fileaccess details

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




--> OUTBOUND (VIP) ESI, length=01024 Send message, CDF for Forms, VIP for VIPEMUL,

ESI/EMI/EGI indicator and the length of message to send




--> INBOUND (CDF) EGI, length=00228 Receive message, CDF for Forms, VIP for VIPEMUL,

ESI/EMI/EGI indicator and the length of message to receive




A-MainSpawnExec check for new 05/05/23 17.50.46.05 SPAWN: start scanning dummies

after DUMMY 05/05/23 17.50.46.05 SPAWN: check dummy 'TPR01' 05/05/23 17.50.46.06 SPAWN: check dummy 'CS2100' 05/05/23 17.50.46.12 SPAWN: check dummy 'NTTEST‘

These lines are showing the access to the internal spawn queue, start scanning shows where it restarted from the last successful spawn. Then the queue is checked till the end and restarted at the begin and will stop once the full queue was checked.

This assures that ALL dummies will get checked periodically and not accessed in a FIFO principle which can cause the dummies defined last to never get executed




05/05/23 17.50.54.51 SPAWN: submit dummy 'DUMMY' details=HP

0043431 NTWKBNT7NTWKBAP7HC 0000000000 000 RUSS A spawned TX was found and will submitted to the

Message Monitor (TCS or GDTSRV03)




05/05/23 17.50.54.77 SPAWN: end scanning dummies cur=DUMMY

init=DUMMY These lines are showing the access to the

internal spawn queue, start scanning shows where it restarted from the last successful spawn. Then the queue is checked till the end and restarted at the begin and will stop once the full queue was checked.

This assures that ALL dummies will get checked periodically and not accessed in a FIFO principle which can cause the dummies defined last to never get executed




A-MainSpawnExec check for new done 00009 00001 000000000000000000 A check for new SPAWNS has ended, some internal

numbers shown here will be returned to the Message Monitor (TCS or GDTSRV03)



GEPFILE

Purpose: Textfile that contains console log information and

basic abort information on jobs running via the console.



GEPFILE



GEPFILE Content Pre GDT V4.1

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



FSYS01

Purpose: For testing of FSYS01 issues Should never have logging feature on full time! Details

When FSYS01 is checking the H_SYSJOB system record When FSYS01 is getting jobs When FSYS01 is accepting keyboard input When FSYS01 is in shutdown When FSYS01 is modifying a job When FSYS01 is deleting a job When FSYS01 is moving a job When FSYS01 is adding a job



FSYS01.LOG



FSYS01 Content Pre GDT V4.1

125105 C-ChkSysR1 125105 C-ChkSysR2 125105 get ALL Jobs(i) 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 get ALL Jobs(l) Force/Delay/Time 0/0/1 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125105 UP-ChkMovJob 125125 get ALL Jobs(l) Force/Delay/Time 0/1/0 125125 UP-ChkMovJob 125125 UP-ChkMovJob 125125 UP-ChkMovJob 125125 UP-ChkMovJob 125125 UP-ChkMovJob 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



THINCLIENTSERVER.LOG

Produced by TCS Details: The thin client server log contains details about the transactions that are

running, the state of the transaction servers and the client connections (TC, Light weight and SPAWN tranactions). This file can be correlated (using the time stamps) with the individual transaction instances’ logs.

A transaction enters the client listener and then is queued, the transaction is picked up and is run on a free transaction instance. This transaction instance in monitored for success, failure or time out. Once the transaction has finished, no matter what its state, it is returned to the client.

The log file has 3 columns: The time stamp 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)

The msg Example:

Tue Mar 22 13:14:38:565744 [VIP] Transmitted response, size: 47



THINCLIENTSERVER LOG



THINCLIENTSERVER LOG Content

Wed May 11 15:34:47:781 [TXS] < Starting BMI Handler Wed May 11 15:34:47:781 [BMI] < Allocated memory for BMI Handler Wed May 11 15:34:47:781 [StartupRoutine] < sh.mem (io) for Startup

Server size: 66820 Wed May 11 15:34:47:828 [StartupRoutine] Startup transaction running Wed May 11 15:34:47:828 [StartupRoutine] Online: c:\CONF2005\bull\

source\online Wed May 11 15:34:49:828 [StartupRoutine] < TXStartup Server Complete: Wed May 11 15:34:49:828 [StartupRoutine] . Memory swapping is

enabled Wed May 11 15:34:49:828 [StartupRoutine] << Table (1) - $$GDTMON Wed May 11 15:34:49:828 [StartupRoutine] . Alloc global(G): Size: 512 Wed May 11 15:34:49:828 [StartupRoutine] << Table (2) - $$VSSWAP Wed May 11 15:34:49:828 [StartupRoutine] . Alloc for all servers(B): Size:

3328 Wed May 11 15:34:49:828 [StartupRoutine] << Table (3) - $$TRANSTOR Wed May 11 15:34:49:828 [StartupRoutine] . Alloc for all servers(B): Size:

32000




Wed May 11 15:34:49:843 [TXS] < TXStartup Server finished Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$VSSWAP:3328 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$TRANSTOR:32000 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$TDSSTO:116 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$FORM1:46916 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$FORM2:34566 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$FORM3:34560 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$FORM4:64000 bytes Wed May 11 15:34:49:843 [TXS] L:1042 alloc $$FORM5:49600 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$VSSWAP:3328 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$TRANSTOR:32000 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$TDSSTO:116 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$FORM1:46916 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$FORM2:34566 bytes Wed May 11 15:34:49:843 [TXS] L:1043 alloc $$FORM3:34560 bytes Wed May 11 15:34:49:859 [TXS] L:1043 alloc $$FORM4:64000 bytes Wed May 11 15:34:49:859 [TXS] L:1043 alloc $$FORM5:49600 bytes Wed May 11 15:34:49:859 [TXS] < Initializing the dispatcher Wed May 11 15:34:49:859 [DPR] < initializing transaction instances Wed May 11 15:34:49:875 [TX(1)] Sending Command: PINI - Message: 0000000002005051115344985 - to txs Wed May 11 15:34:49:875 [TX(1)] Program: RUNMW Wed May 11 15:34:49:875 [TX(1)] Started, using ISG_TC03_SHMEM_T00001 Wed May 11 15:34:49:890 [TX(2)] Sending Command: PINI - Message: 0000000002005051115344987 - to txs Wed May 11 15:34:49:890 [TX(2)] Program: RUNMW




Wed May 11 15:34:49:890 [TX(2)] Started, using ISG_TC03_SHMEM_T00002 Wed May 11 15:34:50:890 [TX(1)] < TXServer State: Started, PID=3924 Wed May 11 15:34:50:890 [TX(2)] < TXServer State: Started, PID=3616 Wed May 11 15:34:51:890 [TX(1)] Sending Command: PISU - Message: - to txs Wed May 11 15:34:51:890 [DPR] < TX instance #01 RETURN FIRST, PID=3924 Wed May 11 15:34:51:890 [DPR] < TX instance #02 READY, PID=3616 Wed May 11 15:34:52:890 [DPR] < TX instance #01 READY, PID=3924 Wed May 11 15:34:52:890 [TX(1)] Sending Command: SPWI - Message: - to txs Wed May 11 15:34:52:984 [DPR] < TX instance #01 OK SPWI, PID=3924 Wed May 11 15:34:53:93 [TX(2)] Sending Command: SPWI - Message: - to txs Wed May 11 15:34:53:187 [DPR] < TX instance #02 OK SPWI, PID=3616 Wed May 11 15:34:53:296 [TXS] < Starting Spawn Handler Wed May 11 15:34:53:296 [SPW] < Allocated memory for Spawn Handler Wed May 11 15:34:53:296 [TXS] < Starting vipServer Wed May 11 15:34:53:296 [VIP] Server Intialized to accept a maximum of 1024 clients Wed May 11 15:34:53:296 [TXS] < Starting ltServer Wed May 11 15:34:53:296 [LT] Server Intialized to accept a maximum of 1024 clients Wed May 11 15:34:53:296 [TXS] Starting Dispatcher thread Wed May 11 15:34:53:296 [TXS] Started Dispatcher thread Wed May 11 15:34:53:296 [TXS] Starting Responder thread Wed May 11 15:34:53:296 [TXS] Started Responder thread




Wed May 11 15:35:22:453 [TX(1)] Sending Command: EXEC - Message: DOUG DOUG - as user: DOUG DO

Wed May 11 15:35:22:609 [TX(1)] Transaction OK, took: 0.156000 seconds Wed May 11 15:35:22:609 [TX(1)] Transaction complete for client: 1 [lf5 Wed May 11,2005 15:35:22f5!not yet implemented fC-DOUG fC.DOUG fC/ fC0 f!

3your ID is unknown to the system f!4 [x[hfC-Wed May 11 15:35:22:609 [TX(1)] Transaction returning message size: 297

Wed May 11 15:35:22:625 [DPR] Sending response to client from TX instance: 1 Wed May 11 15:35:22:625 [TX(1)] Returning Request to a VIP client Wed May 11 15:35:22:625 [TXS] Posting Response to VIP client Wed May 11 15:35:22:640 [VIP] Transmitted response, size: 327 Wed May 11 15:35:25:765 [VIP] 1660 RCV 0078/0078 Wed May 11 15:35:25:765 [VIP] 1660 < QUEUED:PRTY=CONNECTING - User DEVANS TEST Wed May 11 15:35:25:765 [VIP] Queue size: 1 Wed May 11 15:35:25:765 [TXS] Request: regular TX Wed May 11 15:35:25:765 [TX(1)] Executing Request from a VIP client Wed May 11 15:35:25:765 [TX(1)] 3e 20 45 58 45 43 3a 20 44 45 56 41 4e 53 20 20 20 20 20 20 4d 43 4b 45 45 56 45 52 20 20 20 20 20 20 20 20 20

20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 Wed May 11 15:35:25:765 [TX(1)] Sending Command: EXEC - Message: DEVANS TEST - as

user: DEVANS TEST Wed May 11 15:35:25:906 [TX(1)] Transaction OK, took: 0.141000 seconds Wed May 11 15:35:25:906 [TX(1)] Transaction complete for client: 1 [l``Hello DEVANS

you are now connected to the GDT Transaction system




Wed May 11 15:41:13:250 [TX(1)] Sending Command: EXEC - Message: INF1 TEST PERSON - as user: DEVANS MC

Wed May 11 15:41:13:359 [TX(1)] Transaction OK, took: 0.109000 seconds Wed May 11 15:41:13:359 [TX(1)] Transaction complete for client: 1

v[h[001007fINF1 TODD JENNEX 220-550-88CCHRDWARE HARDWARE PURCHASE 220-800-22CCHRDWARE HARDWARE SALES 105 250.00LAPTOP Y 205 250.00LAPTOP 305 300.00DESKTOP 405 300.00DESKTOP Y [l[013034f [013075f [014034f [014075f [015034f [015075f [016034f [016075f [017034f [017075f [018034f [018075f [019034f [019075f [020034f [020075f [021034f [021075f [022034f [022075f J[024001fsI*** CHANGE MODE *** sR[hH [013031fWed May 11 15:41:13:375 [TX(1)] Transaction returning message size: 906

Wed May 11 15:41:13:375 [DPR] Sending response to client from TX instance: 1 Wed May 11 15:41:13:375 [TX(1)] Returning Request to a VIP client Wed May 11 15:41:13:375 [TXS] Posting Response to VIP client Wed May 11 15:41:13:406 [VIP] Transmitted response, size: 936 Wed May 11 15:41:20:812 [VIP] 1660> Disconnected



FHNETERR

The File Handling Redirector module automatically logs communications errors in a local file called fhneterr.log.

Details: The date and time that the last error 9/124 was

returned Last return code from the CCI module (a 4-digit

number) Message code (for the File Handling Redirector

module's internal use, a 2-digit number) The CCI error message text



FHNETERR LOG Content

CCI: 040723 14205217 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.



CCIERR LOG

Purpose: Log file produced by Micro Focus for any

communication problem between client and server programs using the CCI protocol.



CCIERR LOG Content

15:40:31 6/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:31 6/23/2004 CCITCP (tcpnet.c $Revision: 4.28 $:0017) 20000 E Namer_request(), called in NET_CONNECT, failed with return code 152.

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




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



MFDEBUG LOG

Log produced by Micro Focus to give detail event information during a protection violation

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.



MFDEBUG LOG CONTENT

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 03012858 EBX 02A8DC30 ECX 00000000 EDX 02A8DB04 DS 0023 ESI 02AB1984 ES 0023 EDI 20202020 FS 0038 GS 0000 CS 001B EIP 03008C58 SS 0023 ESP 00BBFE44 EBP 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 LegalCopyright Copyright (C) 1984-2002 Micro Focus International Ltd. 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

Advanced Log File Concepts under GDT / TCS / NET EXPRESS Revisited.

Documents

Transcript of Advanced Log File Concepts under GDT / TCS / NET EXPRESS Revisited.