Sample Client trace

This sample Client daemon trace shows the trace information recorded during the successful connection of a Client daemon to a CICS® server using the TCP/IP protocol.

This trace was generated using the command:
cicscli -s=cicstcp -d
and stopped using the command:
cicscli -o
Figure 1. Sample Client daemon trace
14:19:16.146 [0000232c,000021c0] [1007] TRC:CCL1042T *** 22/01/13 IBM CICS Transaction Gateway Client trace for Windows v9.0.0.0 Build Level c900-20121113-1813. ***
14:19:16.147 [0000232c,000021c0] [2189] CCL:CCL2047T MaxRequests is set to '256'
14:19:16.148 [0000232c,000021c0] [2183] CCL:CCL2048T Maximum trace data size set to 512
14:19:16.158 [0000232c,000021c0] [2233] CCL:CCL2227I Service trace has started
14:19:16.164 [0000232c,000021c0] [2082] TRC:CCL2229I Client components to trace have been set to 'DRV,API,CCL,TRN'
14:19:19.230 [0000232c,000021c0] [2114] CCL:CCL2142T GetNextTimeout timeout is 3660 seconds
14:19:19.234 [0000232c,000021c0] [2030] CCL:CCL2106T Comms Event : LINK-UP
14:19:19.235 [0000232c,000021c0] [2019] CCL:CCL2055T Connection with server established (LinkId=1)
14:19:19.235 [0000232c,000021c0] [2035] CCL:CCL2109T Send server TCS data
14:19:19.236 [0000232c,000021c0] [2196] CCL:CCL2161T Server request count: 1 (LinkId=CICSTCP)
14:19:19.237 [0000232c,000021c0] [3214] CCL:CCL3251T Comms Allocate request (LinkId=1, Tran='CCIN')
14:19:19.238 [0000232c,000021c0] [3217] CCL:CCL3238T Comms Allocate completed (LinkId=1, ConvId=1, RC=0)
14:19:19.241 [0000232c,000021c0] [2127] CCL:CCL2143T CommsBegin - OK
14:19:19.242 [0000232c,000021c0] [3100] CCL:CCL3113T CCIN install request: ApplId='*       ', Code page=437
.
.
.

14:19:19.295 [0000232c,000021c0] [3102] CCL:CCL3114T CCIN install response: ApplId='-0000002', Code page=, RC=0
14:19:19.296 [0000232c,000021c0] [3241] CCL:CCL3255T Comms Complete request (ConvId=1)
14:19:19.297 [0000232c,000021c0] [4520] DRV:CCL1040T Variable *BlkPP          = cd1058
14:19:19.298 [0000232c,000021c0] [3244] CCL:CCL3246T Comms Complete completed (ConvId=1, RC=0)
14:19:19.299 [0000232c,000021c0] [3218] CCL:CCL3252T Comms Deallocate request (ConvId=1, Reason=0)
14:19:19.300 [0000232c,000021c0] [4430] DRV:CCL4449T TCP/IP (to CICSTCP) Deallocating conversation, nothing to send, LinkId=1 ConvId=1
14:19:19.300 [0000232c,000021c0] [3221] CCL:CCL3239T Comms Deallocate completed (ConvId=1, RC=0)
14:19:19.302 [0000232c,000021c0] [2150] CCL:CCL2150T CTINInProgress Count = 0 for link 1, link state = 4
14:19:19.303 [0000232c,000021c0] [2197] CCL:CCL2161T Server request count: 0 (LinkId=CICSTCP)
14:19:19.304 [0000232c,000021c0] [2042] CCL:CCL2114T Processed TCS Reply - Server connected
14:19:19.306 [0000232c,000021c0] [2229] CCL:CCL2223I Connected to server 'CICSTCP ' using 'TCPIP' to 'winmvs23.hursley.ibm.com'
14:19:19.309 [0000232c,000021c0] [2114] CCL:CCL2142T GetNextTimeout timeout is 0 seconds
14:19:25.128 [0000232c,000021c0] [1004] TRC:CCL1043T *** Service trace ended ***
Message ID Explanation
CCL1042T Start of trace message. Each time a trace is started, a backup of the old trace file is created, and the trace file is overwritten. You can delete the file when required. Check the time stamp to ensure that you are reading the correct trace.
CCL2048T Maximum trace data size is at the default size of 512 bytes. You can modify this size by specifying the size value in the start command for the client trace; see the cicscli -d command.
CCL3251T The client sends a CCIN transaction to the server to install its connection definition on the server.
CCL3238T A conversation ID has been successfully allocated. If more than one conversation is active, use the conversation ID to distinguish between them.
CCL3113T The client sends a CCIN transaction to the server with Appl ID set to * to install its application. The Appl ID is specified in the configuration file as Client=*. This requests the server to dynamically generate an Appl ID that is unique within the CICS server system.
CCL3114T This shows the dynamically generated Appl ID.
CCL1043T End of trace message.
The following sample shows trace information recorded when we tried to connect to a CICS server over TCP/IP using an invalid port number. The port number specified in the configuration file file was not defined in the services file of the server. Hence, the connection could not be established.
Figure 2. Client daemon trace: using an invalid port number
14:37:06.748 [00002348,00002284] [1007] TRC:CCL1042T *** 22/01/13 IBM CICS Transaction Gateway Client trace for Windows v9.0.0.0 Build Level c900-20121113-1813. ***
14:37:06.749 [00002348,00002284] [2189] CCL:CCL2047T MaxRequests is set to '256'
14:37:06.750 [00002348,00002284] [2183] CCL:CCL2048T Maximum trace data size set to 512
14:37:06.764 [00002348,00002284] [2082] TRC:CCL2229I Client components to trace have been set to 'DRV,API,CCL,TRN'
14:37:06.768 [00002348,00002284] [2114] CCL:CCL2142T GetNextTimeout timeout is 0 seconds
14:37:07.827 [00002348,00002088] [9085] TRN:CCL9041T Awoken with Event code = 297, Session id = 2192672, Priority = 1, Session type = Requester
14:37:08.878 [00002348,00002284] [3207] CCL:CCL3249T Comms Open request (Server=CICSTCP, Driver=CCLWNTIP)
14:37:08.891 [00002348,00002284] [4408] DRV:CCL4413I TCP/IP (to CICSTCP) address=9.20.5.156:3, port=3, socket=472
14:37:08.899 [00002348,00002284] [2114] CCL:CCL2142T GetNextTimeout timeout is 3660 seconds
14:37:14.666 [00002348,00002284] [1004] TRC:CCL1043T *** Service trace ended ***
Message ID Explanation
CCL4413I Shows the port number used for this connection request.
You must check your definitions in the SIT on the server, the configuration file on the workstation, and the services file for the port number specified.

You must provide a valid port number or use the default value.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/samptrc.html