CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

Figure 3-5 ScanPort utility
3. Started the CICS region SCSCPJA1.
4. Started the CICS TG connection to the CICS region using the command
CICSCLI /S=SC62PJA1. (SC62PJA1 is the server name given in the Client
configuration step in Figure 3-3 on page 46.)
5. Checked the status of the connection to the CICS region using the command
CICSCLI /L. The connection status is available, as shown in Example 3-5.
Example 3-5 Checking connection status
C:\>CICSCLI /L
CCL8001I CICSCLI - CICS Client Control Program
CCL0002I (C) Copyright IBM Corporation 1994,2001. All rights reserved.
CCL8041I The CICS Client is using the following servers:
CCL8042I Server 'SC62PJA1' (using 'TCP62' to 'USIBMSC.SCSCPJA1') is available
6. Issued the CICSTERM /S=SC62PJA1 command to install a client terminal on the
CICS region.
7. Ran the CICS-supplied transaction CEMT I CONN to display the status of our
TCP62 connection (Figure 3-6 on page 54). You can see that our TCP62
connection has been autoinstalled as 62LU, which are the last four characters
of the LU name (CCLI62LU), and is marked Acq, meaning SNA sessions are
bound. The other connection displayed is CBPS, the APPC connection
autoinstall template.
Chapter 3. TCP62 connections to CICS 53