Troubleshooting
Problem
You share printers among several CICS regions. If one particular CICS region acquires the printer when the region first comes up, the printer will never be released. If you use CEMT to release the printer, the printer then works properly. It will acquire when there is a print task, and release the connection when requested.
Cause
The printer is not responding properly to RELREQ when using AUTOCONNECT(YES).
Diagnosing The Problem
The TCTTE in the dump shows:
TCTECCT CLSDST needs to be done
TCTERELR RELREQ received
TCTESBIS SBI sent and TCTEBISS BIS sent
TCTESBIF is NOT on, so SBI and BIS is NOT supported
TCTENSH is NOT on, so "No SHUTD support" is NOT on,
The TCTENSH bit is backwards logic.
Because it is NOT on, then the SHUTD command IS supported.
The other bit settings indicate that
- CICS received and processed the release request (RELREQ).
- CICS sent the shut down (SHUTD) command
- CICS is waiting for the Shutdown Complete(SHUTC) to come from the device.
The printer hangs because it never sends the SHUTC command.
The device only fails to send SHUTC if CICS acquired the device due to AUTOCONNECT being on. It sends the SHUTC if the device is acquired for work to be done. This is a problem with the device, not with CICS. The assumption is that the device has a problem because no work is ever sent from CICS for it to work with. Since it never receives a request to do any work, it assumes CICS will send a request and never sends the SHUTC.
In this case, since the printer is shared, there is no need to use AUTOCONNECT when the region starts. CICS is able to acquire the printer when needed, so setting AUTOCONNECT to NO circumvents the printer problem.
Resolving The Problem
Change AUTOCONNECT from YES to NO on the TYPETERM definition.
Product Synonym
CICS/TS CICS TS CICS Transaction Server CICS/VSE VSE z/VSE
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21107379