MustGather - WDI CICS processing

Technote (troubleshooting)


Problem(Abstract)

Collect troubleshooting data for problems with IBM WebSphere Data Interchange. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time

Resolving the problem

This document is for collecting troubleshooting data specifically for when WebSphere Data Interchange server running on CICS does not complete successfully or produces unexpected results.


CICS processing via WDI program EDIFFUT

Most commonly, the WDI utility program (EDIFFUT) is executed by a user written back-end program or application, either synchronously via EXEC CICS LINK or asynchronously via EXEC CICS START of EDIB transaction. If running WDI in this manner, please gather the required information:

1) Ideally, run the same PERFORM command instead using the EDIW utility provided with WDI for CICS. See "Using EDIW to invoke the WebSphere Data Interchange Utility" in Chapter 3 of the WDI 3.3 Programmer's Reference. This will help to isolate the problem and allow you to readily capture further documentation.

2) If encountering any CICS system errors, include the JES joblog associated with the CICS region. Save the complete joblog to a dataset, such as via System Display and Search Facility (SDSF). From the "Display Active" output display, beside the CICS region JOBNAME, issue the XDC command to invoke "SDSF Open Print Data Set" panel. Save the CICS joblog to a dataset.

3) If the CICS task is encountering a system or CICS ABEND (abnormal end), then obtain a dump of the ABEND as described at Collect troubleshooting data: Using dumps for CICS problem determination on z/OS. Note: MVS System dump is preferred over a CICS transaction dump.

- Also check for the following error message in the WDI Event Log or Print File:
"CE0050*12*Abend xxxx occurred while processing CICS transaction EDIW. A ROLLBACK was issued and a dump with dumpcode EDI1 was taken."
In which case, check for a transaction dump with dump code = EDI1.

- Since many WDI CICS programs run under Language Environment (LE) there may also be pertinent messages and/or dump information in dd: CEEDUMP, CEEOUT, or CEEMSGS.

- Lastly, if an abend is occurring in the JVM (Java), such as when WDI is parsing XML for Data Transformation, then obtain the information as described at Collect troubleshooting data for pooled JVM (Java) problems in CICS TS for z/OS. See the section, "Collecting data for pooled JVM problems"

4) Since Data Transformation or Translation is typically involved, include an export of the associated map as described under MustGather - WDI Mapping.

5) If using WebSphere MQ for either input or output, please also "Export to file" the following WDI artifacts specific to your WMQ usage:
- Mailbox profile
- Network Profile
- Queue profile

6) If requested by Support, capture a CICS AUXTRACE as follows:
- Quiesce as much other CICS activity as possible as an aux tracing encompasses all CICS tasks
- Use CEMT SET AUXT to start the auxtrace. Note which trace dataset is active (A) or (B)
- Run the WDI failing function, e.g. via EDIW
- Use CEMT SET AUXT to stop the auxtrace.
- Trace data is written to DFHAUXT or DFHBUXT depending on which is active when started.
Note: do not format the auxiliary trace data set(s) with Trace utility print program prior to submitting to IBM.



CICS processing via Continuous Receive

The WDI utility program (EDIFFUT) can also be executed via the Continuous Receive adapter interface. If the problem is specific to this interface, then gather the following in addition to that as described above.
The WDI Continuous Receive Profile controls how the data is processed. Please include an export of this profile and, if running the adapter specifically with WMQ, also include these additional WDI profiles
- Service profile, if applicable
- Mailbox profile
- Network Profile
- Queue profile

Note: The Continuous Receive profile contains very specific information about processing; such as whether a Service profile is being invoked, where WDI writes its Print file output, and which mailbox profile is involved. The mailbox profile provides the Network profile, from which the Queue profile can be determined.



Submitting information to IBM Support

After a PMR is open, you can submit diagnostic MustGather data to IBM. If using Service Request (SR), update the PMR to indicate that data has been sent.



Related information

MustGather - WDI Mapping
MustGather - WDI Client database errors
MustGather - WDI MultiPlatform (AIX or Windows) processing
MustGather - WDI z/OS Batch (JCL) processing
Exchanging information with IBM Technical Support
Featured documents for WebSphere Data Interchange


Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Data Interchange
WDI 3.3 z/OS

Software version:

3.3

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

1628231

Modified date:

2013-04-18

Translate my page

Machine Translation

Content navigation