Under normal circumstances, CICS ignores the VTAM-supplied CINIT and builds a BIND image based on some of the other DFHTCT or TYPETERM parameters. You can overcome this by specifying LOGMODE=0 in the DFHTCT or LOGMODE(0) in the RDO TYPETERM.
Specifying a LOGMODE prevents CICS from building its own BIND image but does not inhibit any of the other parameters that CICS normally uses to build the BIND. The CICS internal logic ignores the VTAM-supplied information and assumes that the coded TCT parameters are correct.
This situation is typically not a problem, but when large data streams such as those generated by graphics applications or expected by the CEDF transaction that uses the 3270 Read Buffer command, CICS transactions can be confused and various error conditions including ATNI abends can be expected. If you omit the conflicting parameters in the TCT, CICS will pay attention to the VTAM CINIT values. The CINIT provided by this product to CICS is optimized for both network and CA TPX behavior. CICS ignores the VTAM BIND parameter and uses the TCT definitions.
Because this product is not notified of the CICS TCT parameter, do the following to avoid ATNI or AEDF abends:
|
Copyright © 2013 CA.
All rights reserved.
|
|