My Oracle Support Banner

Failure Tesing COBOL Copybook With Tuxedo (Doc ID 2259534.1)

Last updated on MAY 19, 2020

Applies to:

Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.1.3 and later
Information in this document applies to any platform.


On SALT 12.1.3 version, User has COBOL copybook exposed as webservice using Tuxedo + SALT + TMA for SNA.

User is running workflow that starts with the Tuxedo server, goes to the TMA for SNA, and then into the CICS and go to DB2.

When user tested with SoapUI along with TMTRACE=ws:ulog:dye enabled the followings are logged in Tuxedo ULOG:

090106.TuxMachineName! TRACE:ws:GWWS_CAT:1626: TRACE: Delivering a message to Tuxedo, service name =CopybookSvc, SCO index=4094
090106.TuxMachineName!GWSNAX.xxxx.1617527264.0: LIBGWS_CAT:9087: WARN: Input buffer is smaller than RECORD, received(197), configured RECORD length(325)
090106.TuxMachineName! TRACE:ws:GWWS_CAT:1627: TRACE: Got a message from Tuxedo, SCO index=4094
090106.TuxMachineName! TRACE:ws:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:tuxedo="urn:pack.COPYBook_typedef.salt11" xmlns:tx=""><SOAP-ENV:Header><tx:tpurcode>0</tx:tpurcode></SOAP-ENV:Header><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:TuxMachineName</faultcode><faultstring>GWWS_CAT:1054: Internal Error: Failed to get output type from configuration.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOA
090106.TuxMachineName! TRACE:ws:P-ENV:Envelope>

If user hard coded the test data then the work-flow worked but does not actually call DB2.
If user did not hard coded the test data then the call does DB2 work, the transaction will abend with AD2U.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.