Check that your CICS® Transaction Server is working correctly, for example by looking at the CICS log. Insufficient storage on the CICS region may cause CICS Universal Client to hang.
To test whether CICS Universal Client has stopped responding, issue cicscli -l from the command line. If the call hangs then CICS Universal Client is not responding.
Try to reproduce the problem with tracing turned on. Take a client trace with as many components as possible active. As a minimum you need the API, DRV and CCL tracepoints; add TRN if possible. (Use wrapping trace if you do not want the trace file to get too large.) The summary trace shows whether the client or user application has stopped responding, and gives an indication as to whether the problem is in the client or server.
Check also that your message queues are correctly configured; see Configuring message queues.
Use the syscalls event set and ipcs related trace options. Format it to show pids, tids, current system calls, and elapsed time options. Consider increasing the buffer file settings.
ps -ef | grep cclclntInformation about the process is displayed:
root 26864 27348 3 11:06:51 pts/2 0:00 grep cclclnt bartfast 28266 1 0 11:06:46 pts/0 0:00 cclclnt
dbx -a 28266 ./cclclnt
Waiting to attach to process 28266 ... Successfully attached to cclclnt. Type 'help' for help. reading symbolic information ...warning: no source compiled with -g stopped in _pthread_ksleep at 0xd0139164 ($t2) 0xd0139164 (_pthread_ksleep+0x9c) 80410014 lwz r2,0x14(r1)
_pthread_ksleep(??, ??, ??, ??, ??) at 0xd0139164 _pthread_event_wait(??) at 0xd01395c0 _cond_wait_local(??, ??, ??) at 0xd0135494 _cond_wait(??, ??, ??) at 0xd0135998 pthread_cond_timedwait(??, ??, ??) at 0xd0136368 OsEventTimedWait() at 0xd00a78b4 .() at 0x100005b8 _pthread_body(??) at 0xd012f358
thread state-k wchan state-u k-tid mode held scope function $t1 wait 0xc0000100 running 21793 k no sys >$t2 run blocked 32425 k no sys _pthread_ksleep
To make thread 1 the current thread, type thread current 1.
.() at 0x1000c784 .() at 0x10000ae0 .() at 0x10000ae0 .() at 0x100003f4
To close dbx, type quit.
Ensure that the /etc/system file allows sufficient queue entries; see Configuring message queues. If the value is too low, the client may freeze while waiting for a queue entry to become available.