Hi Community,
I am seeking assistance regarding a persistent ORA-19702 error ("device parameter exceeds maximum length of string") occurring in an Enterprise Server 11.0 environment on Windows.
Environment Summary:
- Product: Rocket Enterprise Developer / Enterprise Server 11.0.
- Architecture: 32-bit region (Working Mode 32).
- Database: Oracle 19c via XA interface.
- Switch Module: Custom-built dynamic module (ESORAXA_D.dll) compiled using the 32-bit Oracle precompiler (
procob) and Microsoft Manifest Tool (mt.exe).
Context and Troubleshooting History: We have already overcome several initial configuration hurdles:
- Current Status: The Resource Manager now initializes successfully during region startup, as confirmed by the console log:
CASXO0015I DBP XA interface initialized successfully.
The Current Problem: The issue arises during runtime. When a COBOL program executed via JCL attempts to open a cursor (SQL DECLARE/OPEN), the system returns: SQLCODE=-0000019702 (ORA-19702: device parameter exceeds maximum length of string)
Open String Configuration: I have tested multiple variations in ESCWA, currently using: LogDir=C:\Oracle\XALogs+DbgFl=0+Oracle_XA+SesTm=100+SqlNet=DBD_LINUX+Acc=P/user/password+BATCHONLY=T.
Tests Performed to resolve ORA-19702:
- Path Shortening: We reduced the
LogDirpath to the absolute minimum (e.g.,C:\,C:\L, and even omitting it), but the "device parameter" error persists. - Batch Isolation: We are using
BATCHONLY=Tto ensure the resource is only managed by JES Batch SEPs and avoid CICS recovery conflicts. - Environment Cleanup: The
PATHandLIBvariables in the[ES-Environment]section have been cleaned to include only essential Oracle and Rocket directories.
Questions for the Forum:
- Is there a specific internal buffer limit in the Enterprise Server 11.0 OCI wrapper for the
LogDirparameter when running in 32-bit mode? - Could the inclusion of the Rocket-specific parameter
BATCHONLY=Tbe causing Oracle to miscalculate the total length of the native OCI open string? - Are there any known issues with Oracle 19c Instant Client (32-bit) handling XA trace parameters when invoked from a Service Execution Process (SEP)?
Any insights or recommended CTF trace levels to further diagnose this would be greatly appreciated.
Best regards,

