01.01.2013 Views

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 7-9 Formatting the <strong>Gateway</strong> dump in IPCS<br />

8. On the resulting IPCS formatted dump output, you now need to find the EXCI<br />

trace table. To do this, enter the command FIND ‘TRACE TABLE’.<br />

Example 7-23 show the output from our job. Note the ECI_PARAMETERS_OUTPUT<br />

line. <strong>The</strong> return code of -9 equates to an ECI_ERR_SYSTEM_ERROR, which<br />

is a generic code for many types of EXCI failures.<br />

Example 7-23 IPCS dump trace table<br />

INTERNAL TRACE TABLE<br />

IKJ56650I TIME-01:29:19 PM. SERVICE-2194025 SESSION-01:28:36 MAY 29,2002<br />

BLS18122I Init in progress for DSNAME('DUMP.D0529.H17.SC66.#MASTER#.S00072')<br />

BLS18124I TITLE=JGATE DUMP RRS<br />

BLS18223I Dump written by z/OS 01.02.00 SVC dump - level same as IPCS level<br />

BLS18222I z/Architecture mode system<br />

BLS18160D May summary dump data be used by dump access?<br />

Enter Y to use, N to bypass.<br />

Y<br />

BLS18123I 43,332 blocks, 180,261,120 bytes, in<br />

DSNAME('DUMP.D0529.H17.SC66.#MASTER#.S00072')<br />

IKJ56650I TIME-01:29:44 PM. CPU-00:00:05 SERVICE-2393143 SESSION-01:29:00 MAY<br />

Dump of z/OS 01.02.00 - level same as IPCS level<br />

***<br />

XCI EXCI EX 1001 XCPRH EXIT INITIALIZE_USER OK,OK<br />

XCI EXCI EX 8000 JVDLL ENTRY ECI_PARAMETERS_PASSED Worker-0,1<br />

XCI EXCI EX 8003 JVDLL DATA CONVERTED_PARAMETER Worker-0,jstrServer,SCSCPJA1<br />

XCI EXCI EX 8003 JVDLL DATA CONVERTED_PARAMETER Worker-0,jstrProgram,EC02<br />

XCI EXCI EX 8004 JVDLL DATA INBOUND_COMMAREA Worker-0,80,11517C78<br />

XCI EXCI EX 8030 ????? ????? **_POINT_ID_NOT_RECOGNISED_**<br />

XCI EXCI EX 8007 JVDLL EXIT ECI_PARAMETERS_OUTPUT Worker-0,1,-9<br />

XCI EXCI EX 03ED ????? ????? **_POINT_ID_NOT_RECOGNIZED_**<br />

XCI EXCI EX 8000 JVDLL ENTRY ECI_PARAMETERS_PASSED Worker-0,1<br />

However, at this stage the EXCI trace doesn’t give us enough information to<br />

solve the error, so we continue on to the <strong>Gateway</strong> daemon trace.<br />

Tip: You can also use the MVS generalize trace facility (GTF) to analyze both<br />

<strong>CICS</strong> and EXCI traces. However, this tracing is better suited to in-depth error<br />

analysis, since it requires the GTF proc to be started and initialized in order to<br />

collect the data. It does, however, provide the very useful feature of being able<br />

to interleave both EXCI and <strong>CICS</strong> trace entries. For further details on how we<br />

used GTF tracing, refer to “GTF tracing” on page 179.<br />

Chapter 7. TCP connections to the <strong>Gateway</strong> daemon on z/OS 173

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!