You must set up a ConnectionFactory in the J2EE server for each CICS® transaction
accessed through protocol CICSJ2C.
If a generated Java™ wrapper is making the CICSJ2C call, you can handle
security in any of the following ways (where a wrapper-specified value overrides
that of the J2EE server):
- Set the userid and password in the wrapper's CSOCallOptions object; or
- Set the userid and password in the ConnectionFactory configuration in
the J2EE server; or
- Set up the CICS region
so that user authentication is not required.
When calling a program from WebSphere
® 390, the following restrictions
apply:
- If the callLink element property luwControl is
set to CLIENT, the call fails. The WebSphere 390 connect implementation
does not support an extended unit of work.
- The setting of deployment descriptor property cso.cicsj2c.timeout has
no effect.
By default, timeouts never occur. In the EXCI options table
generated by the macro DFHXCOPT, however, you can set the parameter TIMEOUT,
which lets you specify the time that EXCI will wait for a DPL command (an
ECI request) to complete. A setting of 0 means to wait indefinitely.
For details, see Java Connectors for CICS: Featuring the J2EE Connector Architecture (SG24-6401-00),
which is available from web site http://www.redbooks.ibm.com.