|
|
|
|
Administration
Setting up client/server communication
This topic discusses how to set up the communication links between CICS clients and the CICS servers. The NetBIOS, TCP/IP, or APPC protocols can be used to enable clients and servers to communicate. See "Planning before installation" for details of what levels of the various protocols are required. This topic summarizes the products and definitions that are required on CICS servers. Full details of setting up a CICS server for communication are given in the individual CICS server books, see "CICS publications". After the client has been installed, and the server has been set up for communication, the following steps are necessary:
Client/server definitionsThis topic includes definition checklists for each CICS client. Definition checklists show the definitions required to allow client/server communication using a particular product and protocol:
The following is a simple example of a set of definition checklists. It shows the definitions required to connect a CICS Client for OS/2 to a CICS for OS/2 server. The example values are samples only--you must enter your own values. However, in the checklists in this topic, the values shown for DriverName in the client initialization file are the actual driver names that you must use.
CICS server definitions
CICS client definitions
Table 2. Matching definitions: CICS Client for DOS to CICS for OS/2 using NetBIOS
In the above tables the definitions that must match are indicated by reference keys, (1), (2), and so on. Definitions with the same reference key must match.
This book does not give details for every possible client/server configuration. Typical examples are given representing the most likely configurations. More example configurations are described in the CICS Clients Unmasked book.
NetBIOS configurationThis section describes how to set up CICS clients for communication via the NetBIOS protocol. All communication between a client and server is multiplexed on one NetBIOS session.
CICS Client for DOSFor CICS Client for DOS, NetBIOS can be provided by the IBM LAN Support Program Version 1.3. For information on installing this program, see the Local Area Network Support Program Version 1.3 User's Guide, and the associated READ.ME file on the installation diskette. CICS Client for DOS can also run in a Virtual DOS Machine (VDM) under OS/2 (a so-called "DOS box") and utilize the NetBIOS Virtual Device Driver (VDD) support offered by OS/2. VDD support is initialized by running SETUPVDD.EXE from the \IBMCOM directory in an OS/2 session, which writes the following lines to CONFIG.SYS: DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2 When you restart the system, NetBIOS support is ready for use from a VDM. A DOS client from a VDM can run against a CICS for OS/2 server in the same workstation.
Definition checklistsThe following shows example definitions for connecting CICS Client for DOS to a CICS for OS/2 server (these are also applicable to CICS for Windows NT Version 2):
CICS server definitions
CICS client definitions
Table 3. Matching definitions: CICS Client for DOS to CICS for OS/2 using NetBIOS
CICS Client for OS/2For CICS Client for OS/2, NetBIOS is provided by, for example, Network Transport Services/2. (See "CICS Client for OS/2 software requirements" for a list of products that provide NetBIOS.)
Definition checklistsFor connecting CICS Client for OS/2 to a CICS for OS/2 (or CICS for Windows NT Version 2) server, the definitions are the same as for CICS Client for DOS.
CICS Client for WindowsFor CICS Client for Windows, NetBIOS can be provided by the IBM LAN Support Program Version 1.3. For information on installing this program, see the Local Area Network Support Program Version 1.3 User's Guide, and the associated READ.ME file on the installation diskette.
Definition checklistsFor connecting CICS Client for Windows to a CICS for OS/2 (or CICS for Windows NT Version 2) server, the definitions are the same as for CICS Client for DOS.
CICS Client for Windows 95NetBIOS support is provided with Windows 95, and no further configuration is required after installation.
Definition checklistsFor connecting CICS Client for Windows 95 to a CICS for OS/2 (or CICS for Windows NT Version 2) server, the definitions are the same as for CICS Client for DOS.
CICS Client for Windows NTNetBIOS support is provided with Windows NT, because NETBEUI (NetBIOS extended user interface) is automatically installed during Windows NT setup. However, via the Network Settings panel, you must configure the NetBIOS Interface with settings like the following example, which is for an IBM Auto 16/4 Token Ring ISA adapter:
Definition checklistsFor connecting CICS Client for Windows NT to a CICS for OS/2 (or CICS for Windows NT Version 2) server, the definitions are the same as for CICS Client for DOS.
NetBIOS resourcesCICS Clients have a NetBIOS resource requirement that is in addition to products such as LAN Server and DB2/2. The CICS client requirement for NetBIOS resources is affected by the MaxServers parameter in the client initialization file. The resource requirements must therefore be increased as follows:
For CICS Client for OS/2, the NetBIOS resource requirements are coded in the \IBMCOM\PROTOCOL.INI file. PROTOCOL.INI is the LAN adapter and protocol support (LAPS) configuration file. For information on how to code NetBIOS resource requirements for other CICS clients, refer to the documentation for the NetBIOS-providing product. "CICS clients in Novell NetWare LANs" describes how CICS clients can communicate over NetBIOS in a Novell NetWare LAN.
TCP/IP configurationThis section describes how to set up CICS clients for communication via the TCP/IP protocol. To configure TCP/IP for communication with CICS servers, you need to know the following:
If you are using a domain nameserver you can specify symbolic hostnames rather than IP addresses. Hostnames are easier to remember, and can be made meaningful. Your system administrator can supply this information, which is also used in preparing the client initialization file. Note: In the \ETC\SERVICES file, you can enter CICS in either uppercase or lowercase.
CICS Client for DOSThe following sections summarize TCP/IP configuration for CICS Client for DOS.
IBM TCP/IP for DOSFor information on installing and configuring IBM TCP/IP for DOS, see the IBM TCP/IP Version 2.1.1 for DOS Installation and Maintenance book.Note: If you are running CICS Client for DOS in the DOS box of OS/2, you must have the DOS/Windows Access Kit for TCP/IP Version 2.0. (This is also supplied with Warp Connect and Warp Server.) You can use the TCPCHECK program to verify the installation. TCPCHECK verifies the configuration parameters, and sends a TCP/IP PING command to check the route to all defined servers.
Definition checklistsThe following shows example definitions for connecting CICS Client for DOS to a CICS for AIX server:
CICS server definitions
CICS Client Definitions
Table 4. Matching definitions: CICS Client for DOS to CICS for AIX using TCP/IP for DOS
TCP/IP from FTP IncFor information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.
Definition checklistsThe following shows example definitions for connecting CICS Client for DOS to a Transaction Server for Windows NT server:
CICS server definitions
CICS client definitions
Table 5. Matching definitions: CICS Client for DOS to CICS for Windows NT using PC/TCP
Novell LAN Workplace for DOSFor information on installing and configuring Novell LAN Workplace for DOS, see the Novell LAN Workplace Installation Guide.
Definition checklistsThe following shows example definitions for connecting CICS Client for DOS to a Transaction Server for Windows NT server:
CICS server definitions
CICS client definitions
Table 6. Matching definitions: CICS Client for DOS to CICS for Windows NT using LAN Workplace
CICS Client for OS/2The following sections summarize TCP/IP configuration for CICS Client for OS/2.
IBM TCP/IP for OS/2For information on installing and configuring IBM TCP/IP for OS/2, see, for example, the IBM TCP/IP Version 2.0 for OS/2 Installation and Maintenance book.
Definition checklistsThe following shows example definitions for connecting CICS Client for OS/2 to a CICS for OS/2 server:
CICS server definitions
CICS client definitions
Table 7. Matching definitions: CICS Client for OS/2 to CICS for OS/2 using TCP/IP for OS/2
The following shows example definitions for connecting CICS Client for OS/2 to a CICS for AIX server:
CICS server definitions
CICS client definitions
Table 8. Matching definitions: CICS Client for OS/2 to CICS for AIX using TCP/IP for OS/2
TCP/IP from FTP IncFor information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.
Definition checklistsFor connecting CICS Client for OS/2 to a CICS for Windows NT server, the definitions are the same as for CICS Client for DOS.
Novell LAN Workplace for OS/2For information on installing and configuring Novell LAN Workplace for OS/2, see the Novell LAN Workplace Installation Guide.
Definition checklistsThe definitions are the same as for CICS Client for DOS. For connecting CICS Client for OS/2 to a CICS for Windows NT server, the definitions are the same as for CICS Client for DOS.
CICS Client for WindowsThe following sections summarize TCP/IP configuration for CICS Client for Windows.
IBM TCP/IP for DOSFor information on installing and configuring IBM TCP/IP for DOS, see the IBM TCP/IP Version 2.1.1 for DOS Installation and Maintenance book.Note: If you are running CICS Client for Windows in the WIN-OS2 subsystem of OS/2, you must have the DOS/Windows Access Kit for TCP/IP Version 2.0. (This is also supplied with Warp Server and Warp Connect.) You can use the TCPCHECK program to verify the installation. TCPCHECK verifies the configuration parameters, and sends a TCP/IP PING command to check the route to all defined servers.
Definition checklistsFor connecting CICS Client for Windows to a CICS for AIX server, the definitions are the same as for CICS Client for DOS. However, the DriverName parameter in the client initialization file must be set to CCLWINIP.
TCP/IP from FTP IncFor information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.
Definition checklistsFor connecting CICS Client for Windows to a CICS for Windows NT server, the definitions are the same as for CICS Client for DOS. However, the DriverName parameter in the client initialization file must be set to CCLWINIP.
Novell LAN Workplace for DOSFor information on installing and configuring Novell LAN Workplace for DOS, see the Novell LAN Workplace Installation Guide.
Definition checklistsFor connecting CICS Client for Windows to a CICS for Windows NT server, the definitions are the same as for CICS Client for DOS. However, the DriverName parameter in the client initialization file must be set to CCLWINIP.
Other TCP/IP products conforming to WINSOCKTCP/IP can be provided by any other product conforming to the WINSOCK API. For information on installing such products, see the associated documentation. Note that the DriverName parameter in the client initialization file must be set to CCLWINIP.
CICS Client for Windows 95TCP/IP support is provided by the Windows 95 operating system. Refer to the Windows 95 documentation for information on configuring TCP/IP. TCP/IP can also be provided by any other product conforming to the WINSOCK API. For information on installing such products, see the associated documentation.
Definition checklistsFor connecting CICS Client for Windows 95 to a CICS for AIX server, or CICS for Windows NT server, the definitions are the same as for CICS Client for DOS. However, the DriverName parameter in the client initialization file must be set to CCLWNTIP.
CICS Client for Windows NTTCP/IP support is provided by the Windows NT operating system. Refer to the Windows NT documentation for information on configuring TCP/IP.
Definition checklistsFor connecting CICS Client for Windows NT to a CICS for AIX server, or CICS for Windows NT server, the definitions are the same as for CICS Client for DOS. However, the DriverName parameter in the client initialization file must be set to CCLWNTIP.
CICS Client for MacintoshFor information on installing MacTCP, see the documentation supplied with your MacTCP package.
Definition checklistsThe following shows example definitions for connecting CICS Client for Macintosh to a CICS for OS/2 server:
CICS server definitions
CICS client definitions
Table 9. Matching definitions: CICS Client for Macintosh to CICS for OS/2 using MacTCP
Verifying the TCP/IP installationTo verify that CICS clients can communicate with CICS servers, you can use the TCP/IP PING command to check the route to the CICS server: PING [machine address | name] Therefore, to start PING, enter a command like the following: PING 9.113.36.31 where 9.113.36.31 is an example of an IP address of the CICS server. If you are using a Domain Name Server, you can specify the symbolic hostname rather than the IP address of the server. To stop the PING command, press the Ctrl+C keys simultaneously. If you have installed TCP/IP correctly, you see messages as shown in the following figure: Figure 15. Example messages returned by PING command
If the statistic messages show a value other than 0% packet loss, it is likely that you did not install or customize TCP/IP correctly. Therefore:
Depending on the platform, the implementation of the PING command might be slightly different, regarding the operation of the utility (icon or command) and the parameters that can be used. For more information, refer to the documentation associated with your TCP/IP product.
APPC configurationThis section describes how to set up CICS clients for communication via the APPC protocol. Generally, the following are defined:
Note: The terms used to describe these definitions vary with the product used to provide APPC support. The terms used above are the ones used by IBM Communications Manager/2.
CICS Client for DOSThe following sections summarize APPC configuration for CICS Client for DOS.
Communicating to CICS/400Client Access/400 for DOS provides APPC communication to CICS/400, via the DOS Router. For information on installing Client Access/400 for DOS, refer to the Client Access/400 for DOS Setup book. To configure Client Access/400 for DOS for APPC communication, refer to Client Access/400 for DOS Application Programming Interface Reference. For Client Access/400, the partner LU name is an 8-character PLU name rather than a fully qualified 17-character name. This partner LU name corresponds to NetName in the client initialization file. The NetName in the client initialization file must match the system name of a link specified by a TRLI identifier in the Client Access/400 configuration file. If you want to use the default remote system specified by the RTDN identifier in the Client Access/400 configuration file, then specify * for NetName in the client initialization file. The LocalLUName in the client initialization file is the unqualified Local LU name specified by the RTLN key in the CONFIG.PCS file. You do not need to specify a value for ModeName in the client initialization file. This is because Client Access/400 always specifies the fixed modename of QPCSUPP. Routing on CICS/400 must be set up using AEGISRTR and must be done in the same subsystem as that in which the normal Client Access/400 routing is done on the mode QPCSUPP. The routing entries for the CCIN, CPMI, CTIN, and CRTE transactions must have a lower sequence number than any routing-table entry specifying comparison data of QPCSUPP starting in column 1 of the routing data, or PGMEVOKE starting in column 29 of the routing data. For full details, refer to the book CICS/400: Intercommunication, SC33-1388. Before the CICS client is started, Client Access/400 must be started and links established.
Communication via a Novell NetworkYou must install NetWare for SAA in the gateway, as described in the Novell NetWare for SAA Administration Guide. In the client, you must first install Novell 3270 LAN Workstation for DOS as described in the Attachmate NetWare 3270 LAN Workstation for DOS User's Guide, and then configure it for APPC as described in the Attachmate NetWare 3270 LAN Workstation for DOS Configuration Guide. If you are using NetWare for SAA Version 1.3, in the client you must first install Novell 3270 LAN Workstation for DOS as described in the Attachmate NetWare 3270 LAN Workstation for DOS User's Guide. Then you must configure it for APPC as described in the Attachmate NetWare 3270 LAN Workstation for DOS Configuration Guide. If you are using NetWare for SAA Version 2.0 or later, in the client you must install the Novell NetWare for SAA DOS Client as described in the NetWare for SAA API Configuration Guide for DOS and NetWare Clients. The client workstation must be configured to use expanded or extended memory, or both.
CICSCLI.INI settingsThe Novell NetWare DOS client uses the APPC rather than the Common Programming Interface for Communication (CPI-C) API. However, some of the values required in the client initialization file are the same as those described for the CPI-C side information files in the Novell documentation. The following shows the mapping between the side information file names and the initialization file names:
Local LU configuration data
Mode configuration data
Remote LU configuration data
For NetWare for SAA Version 1.3 only, for the client to use parallel sessions, a node type 2.1 service profile must be configured on the NetWare server. This uses independent LUs. For the client to use single sessions, a node type 2.0 service profile must be configured on the NetWare server to use dependent LUs. For parallel session configurations, two sessions are established using the SNASVCMG mode. These sessions are in addition to the SnaSessionLimit sessions established using the ModeName defined in client initialization file. For large networks or slow servers, you may need to increase the value of SnaRetryCount from the default. The following applies to the SnaLocalLUAddr and LocalLUName settings in the client initialization file:
You should specify the Netname in the client initialization file as a fully qualified partner LU name, that is, an 8-character LU name prefixed with an 8-character network name, and separated by a period. Note: In this release of IBM CICS Clients the network name prefix is ignored.
Restrictions
With NetWare for SAA Version 1.3 it is not possible to configure a server profile to use both dependent and independent LUs. The NetWare for SAA Gateway Server must be started before the CICS client is started.
Definition checklistsThe following shows example definitions for connecting CICS Client for DOS to a CICS/ESA server:
CICS server definitions
CICS Client definitions
Table 10. Matching definitions: CICS Client for DOS to CICS/ESA using NetWare for SAA
CICS Client for OS/2The following sections summarize APPC configuration for CICS Client for OS/2.
Configuring Communications Manager/2
A Communications Manager/2 configuration is defined in a set of files as shown in
Table 11.
Table 11. Communications Manager/2 configuration files
Communications Manager/2 configuration (.CFG) fileThe Communications Manager/2 configuration (.CFG) file contains definitions that specify the environment within which the workstation operates. The .CFG file is the central configuration file and is the minimum requirement for the installation or use of Communications Manager/2. When the workstation is connected to a LAN or an SNA network, you need additional files as indicated in Table 11. Configuration files are not supplied for SNA network definitions or for LAN Adapter and Protocol Support.
Node definitions (.NDF) fileThe node definitions (.NDF) file contains the node SNA network definitions in the form of system management configuration verbs. The following definitions are included in the .NDF file:
SNA configuration (.CF2) fileThe SNA configuration (.CF2) file contains a binary translation of the .NDF file and is used to initialize the node SNA definitions when APPC is started.
SNA security (.SEC) fileThe SNA security (.SEC) file contains SNA definitions for session-level and conversation-level security.
APPC definitionsFor APPC communication, the following are defined:
Definition checklistsThe following shows example definitions for connecting CICS Client for OS/2 to a CICS/ESA server over token-ring:
CICS server definitions
CICS client definitions
Table 12. Matching definitions: CICS Client for OS/2 to CICS/ESA using Communications Manager/2
The following shows example definitions for connecting CICS Client for OS/2 to a CICS/VSE server over SDLC:
CICS server definitions
TP definition for CRSR transactionSet up the Transaction Program Definitions panel of Communications Manager/2 as follows:
In the Additional TP Parameters panel, select the radio buttons for the presentation type Background and the operation type Non-Queued Attach Manager Started. The following is the associated .NDF file definition:
Starting APPC sessionsWith Communications Manager/2, before the client connection to the server is started, the sessions between the client and the server must be started. You can do this using either of the following methods:
Figure 16. Sample CNOS statements
CICS Client for WindowsThe following sections summarize APPC configuration for CICS Client for Windows.
Communicating to CICS/400Client Access/400 for Windows 3.1 supports APPC communication to CICS/400. The APPC support is provided by the same Router as APPC Networking Services for Windows, therefore the same APPC verbs are supported. For information on installing Client Access/400 for Windows, refer to the Client Access/400 for Windows 3.1 Setup book. To configure Client Access/400 for Windows for APPC communication, refer to the Client Access/400 for Windows 3.1 Application Programming Interface Reference. For Client Access/400, the partner LU name is an 8-character PLU name rather than a fully qualified 17-character name. This partner LU name corresponds to NetName in the client initialization file. The NetName in the client initialization file must match the system name of a link specified by a TRLI identifier in the Client Access/400 configuration file. If you want to use the default remote system specified by the RTDN identifier in the Client Access/400 configuration file, then specify * for NetName in the client initialization file. The LocalLUName in the client initialization file is the unqualified Local LU name specified by the RTLN key in the CONFIG.PCS file. You do not need to specify a value for ModeName in the client initialization file. This is because Client Access/400 always specifies the fixed modename of QPCSUPP. Routing on CICS/400 must be set up using AEGISRTR and must be done in the same subsystem as that in which the normal Client Access/400 routing is done on the mode QPCSUPP. The routing entries for the CCIN, CPMI, CTIN, and CRTE transactions must have a lower sequence number than any routing-table entry specifying comparison data of QPCSUPP starting in column 1 of the routing data, or PGMEVOKE starting in column 29 of the routing data. For full details, refer to the book CICS/400: Intercommunication, SC33-1388. Before the CICS client is started, Client Access/400 must be started and links established.
APPC Networking Services for WindowsAPPC support can be provided by APPC Networking Services for Windows. For information on installing this program, see the APPC Networking Services for Windows: Getting Started book. Note: APPC Networking Services for Windows cannot run in the WIN-OS2 subsystem of OS/2. To use APPC Networking Services for Windows, you must provide configuration information. Some configuration information is required when you install APPC Networking Services for Windows. Other configuration information can be provided either when you start APPC Networking Services for Windows or after you have started APPC Networking Services for Windows. To provide configuration information when you start APPC Networking Services for Windows, you must create or customize the configuration file NSD.INI. This file must reside in the \WINDOWS subdirectory of the directory in which Windows was installed. The NSD.INI file includes the following sections:
To provide configuration information after you start APPC Networking Services for Windows, or to change information that has already been provided, you can use node operator application program interface (API) verbs. These verbs can be issued by application programs, or you can issue them through the Windows user interface or from the DOS command prompt. For more information on configuring APPC Networking Services for Windows, refer to the APPC Networking Services for Windows: Configuration Parameters Reference for Administrators and Application Programmers. Note: APPC Networking Services for Windows is an independent LU type 6.2., physical unit (PU) type 2.1. It cannot be configured as a dependent LU. You can use the Check Connection (APING) program on the APPC Networking Services for Windows desktop. This sample CPI-C program checks the connection between the workstation and a remote computer.
RestrictionsIf you are using APPC Networking Services for Windows, it is not possible to define the PUs to have any LU2 sessions.
Definition checklistsThe following shows example definitions for connecting CICS Client for Windows to a CICS/ESA server over token-ring:
CICS server definitions
CICS client definitions
The following shows example definitions for connecting CICS Client for Windows to a CICS/VSE server over SDLC:
CICS server definitions
CICS client definitions
Communication via a Novell NetworkYou must install NetWare for SAA in the gateway, as described in the Novell NetWare for SAA Administration Guide. If you are using NetWare for SAA Version 1.3 or later, In the client, you must install Novell NetWare LU6.2 for Windows, (which is included in the NetWare for SAA product), as described in the NetWare LU6.2 for Windows Configuration Guide. Note: NetWare for SAA cannot run in the WIN-OS2 subsystem of OS/2. You must then configure NetWare LU6.2 for Windows for APPC communication with CICS servers. This is also described in the Configuration Guide. If you are using NetWare for SAA Version 2.0 or later, in the client you must install the Novell NetWare for SAA Windows Client as described in the NetWare for SAA API Configuration Guide for Microsoft Windows Clients. The client workstation must be configured to use expanded or extended memory, or both. For parallel session configurations, two sessions are established using the SNASVCMG mode. These sessions are in addition to the SnaSessionLimit sessions established using the ModeName defined in the client initialization file. For NetWare for SAA Version 1.3, the protocol boundary can be loaded prior to starting the client, or can be automatically loaded by the client. You can predefine the server name, user name, and service name in the WS.CFG file in the \WINDOWS directory. If you do not predefine these, you are prompted for them at run time (together with the password, if security is in use). For example:
To avoid WTSPX transport errors for NetWare for SAA Version 1.3:
For NetWare for SAA Version 2.0 or later, use the NetWare for SAA API configuration utility (APICFG) to create a configuration file (NWSAAPI.INI by default) for LU6.2.
CICSCLI.INI settingsThe Novell NetWare Windows client uses the APPC rather than the Common Programming Interface for Communication (CPI-C) API. However, some of the values required in the client initialization file are the same as those described for the CPI-C side information files in the Novell documentation. Some of the values in the CPI-C side information files must be used in preparing the client initialization file. The following shows the mapping between the information file names and the initialization file names:
Local LU configuration d ata
Mode configuration data
Remote LU configuration data
For NetWare for SAA Version 1.3, for the client to use parallel sessions, a node type 2.1 service profile must be configured on the NetWare server. This uses independent LUs. For the client to use single sessions, a node type 2.0 service profile must be configured on the NetWare server to use dependent LUs. For parallel session configurations, two sessions are established using the SNASVCMG mode. These sessions are in addition to the SnaSessionLimit sessions established using the ModeName defined in client initialization file. For large networks or slow servers, you may need to increase the value of SnaRetryCount from the default. The following rules apply to the SnaLocalLUAddr and LocalLUName settings in the client initialization file:
You should specify the NetName in the client initialization file as a fully qualified partner LU name, that is, an 8-character LU name prefixed with an 8-character network name, and separated by a period. Note: In this release of IBM CICS Clients the network name prefix is ignored.
RestrictionsThe restrictions are essentially the same as for NetWare for SAA in the CICS Client for DOS environment, see "Restrictions". The NetWare for SAA Gateway Server must be started before the CICS client is started.
Definition checklistsThe definitions are the same as for CICS Client for DOS.
Microsoft SNA ServerAPPC support can be provided by Microsoft SNA Server. In this case, CICS Client for Windows will be installed on a machine that has SNA Server client installed. Communication with the CICS server is therefore through the SNA Server machine. For information on installing and configuring Microsoft SNA Server, and SNA Server clients, see the Microsoft SNA Server Installation Guide, and the Microsoft SNA Server Administration Guide. To allow workstations using the Windows SNA Client to communicate with other systems, the LUs used by the client systems should be defined as Local APPC LUs to the SNA Server workstation.
Setting up the SNA Server Windows clientOn the SNA Server Windows client, you require the following settings:
Before you start the Server Windows 3.x client, you must run WNAP.EXE to start the SNA Server Client SnaBase. If you do not do so, the CICS Client will not be able to communicate with the SNA Server. To receive ATI on SNA Server Windows 3.x client terminals, add the following to the WIN.INI file: [SNAServerAutoTPs] CRSR=xxxxxxxx [xxxxxxxx] PathName=d:\path\CCLSNSTP.EXE LocalLU=name Parameters=CRSR Queued=yesWhere xxxxxxxx is any string naming the CRSR TP parameters, d:\path is the drive and path of the CICS Client code, and name is the name of the local LU configured for the connection.
Definition checklistsThe following shows example definitions for connecting CICS Client for Windows to a CICS/ESA server over token-ring:
CICS server definitions
CICS client definitions
Table 16. Matching definitions: CICS Client for Windows to CICS/ESA using SNA Server
CICS Client for Windows 95The following sections summarize APPC configuration for CICS Client for Windows 95.
Microsoft SNA ServerAPPC support can be provided by Microsoft SNA Server. In this case, CICS Client for Windows 95 will be installed on a machine that has SNA Server client installed. Communication with the CICS server is therefore through the SNA Server machine. For information on installing and configuring Microsoft SNA Server, and SNA Server clients, see the Microsoft SNA Server Installation Guide, and the Microsoft SNA Server Administration Guide. To allow workstations using the Windows 95 SNA Client to communicate with other systems, the LUs used by the client systems should be defined as Local APPC LUs to the SNA Server workstation.
Setting up the SNA Server Windows 95 clientOn the SNA Server Windows 95 client, you require the following settings:
To receive ATI on SNA Server Windows 95 client terminals, you must run the CCLMSATI command to configure the SNA Server Client for the CRSR transaction. The syntax of the command is: CCLMSATI lunamewhere luname is the LocalLU you are using. If CRSR is already configured, the LocalLU setting changes to match the new value. Before you start the Server Windows 95 client, you must run SNABASE.EXE to start the SNA Server Client SnaBase. If you do not do so, the CICS Client will not be able to communicate with the SNA Server.
Definition checklistsThe definitions are the same as for CICS Client for Windows.
CICS Client for Windows NTThe following sections summarize APPC configuration for CICS Client for Windows NT.
Microsoft SNA ServerAPPC support can be provided by Microsoft SNA Server. You can install SNA Server itself on the CICS Client for Windows NT machine, but it is more likely that you will install SNA Server client. Communication with the CICS server is therefore through the SNA Server machine. For information on installing and configuring Microsoft SNA Server, and SNA Server clients, see the Microsoft SNA Server Installation Guide, and the Microsoft SNA Server Administration Guide. To allow workstations using the Windows NT SNA Client to communicate with other systems, the LUs used by the client systems should be defined as Local APPC LUs to the SNA Server workstation.
Setting up the SNA Server Windows NT clientOn the SNA Server Windows NT client, you require the following settings:
To receive ATI on SNA Server Windows NT client terminals, you must run the CCLMSATI command to configure the SNA Server Client for the CRSR transaction. The syntax of the command is: CCLMSATI lunamewhere luname is the LocalLU you are using. If CRSR is already configured, the LocalLU setting changes to match the new value.
Definition checklistsThe definitions are the same as for CICS Client for Windows.
CICS Client for MacintoshFor CICS Client for Macintosh, APPC communication with a CICS server is achieved via a SNA*ps gateway. You must install the SNA*ps Gateway software in the gateway machine as described in the SNA*ps Administrator's Guide. SNA*ps installation and AppleTalk installation is also described in the IBM/Apple Enterprise Networking Guide for SNA Products book. This book provides an overview of Apple/SNA networking and gives examples of the ways in which SNA*ps can be configured for APPC communication. You must then configure SNA*ps Gateway for use with a CICS server. You can use one of the supplied configuration files as a basis. The general procedure is:
Note: The APPC Remote LU name must be used for the NetName parameter in the client initialization file. The SNA*ps Gateway will normally be configured to automatically activate the connection to the host on startup of the Gateway workstation. You can also use the SNA*ps Admin application to:
Note: While it is possible for several CICS Client for Macintosh systems to use the same LocalLUName at the same time (all concentrated through a common SNA*ps Gateway machine) this is not recommended, as incoming Allocates may be routed to the wrong client. Unless all you are using under the client is ECI applications, you should define multiple Local LUs in your SNA*ps configuration file and use a different one in each CICS Client for Macintosh connected through the Gateway.
CICS clients in Novell NetWare LANs
You can install CICS clients on workstations that are part of a Novell NetWare LAN. Such CICS clients can run transactions on a CICS for OS/2 server just as they can in an IBM LAN Server network. Novell LANs normally use the Internet Packet Exchange (IPX) protocol, rather than IBM's NetBIOS for their LAN transport, but you can overcome this in two ways:
Both of these techniques result in the same operation for end users. Note: There are different ways in which coexistence and NetBIOS emulation can be achieved. This book describes techniques for token ring networks. You may have to adapt the described techniques to your own environment.
An overview of the Open Data-Link InterfaceNovell's ODI supports multiple protocols and multiple LAN adapters in a single workstation. The implementation of ODI is shown in Figure 17. You can use more than one protocol on the same LAN cabling because the link support layer (LSL) part of the ODI allows the LAN driver for an adapter to service more than one protocol.
Open Data-Link Interface Network driver interface specification Support (ODINSUP) is an interface that allows the coexistence of ODI and Network Driver Interface Specification (NDIS). ODINSUP therefore allows LAN Server or other NDIS protocols to coexist with NetWare's ODI on a network. When OS/2 LAN Requester or Extended Services is installed with NetBIOS support, a LAN adapter-specific NDIS LAN driver is installed and loaded in CONFIG.SYS. For example, in an IBM token ring network, the IBMTOK.OS2 NDIS MAC (Medium Access Control) driver is installed. To allow coexistence with NetWare Requester for OS/2, the NDIS LAN driver must be replaced with TOKEN.SYS (the ODI LAN driver for IBM token ring). Figure 17. Implementation of Novell's ODI layer and driver
For further information on ODI, refer to the publications:
Coexistence with Novell's IPXThis section describes how to set up a workstation both as a NetWare Requester and as an IBM LAN Server Requester. It assumes that the LAN Server software has already been installed.
NetWare DOS and Windows Requesters running CICS clientsThe following procedure allows coexistence between LAN Server and NetWare, using NetWare ODI drivers, in a token ring network. For more information refer to Coexistence Guide for OS/2 LAN Server and NetWare from IBM.
NetWare OS/2 Requester running CICS Client for OS/2The following describes the procedure for a token ring network. For more information refer to Coexistence Guide for OS/2 LAN Server and NetWare from IBM.
This procedure results in a CONFIG.SYS (see Figure 18) and PROTOCOL.INI file (see Figure 19) like the following: Figure 18. Statements added to CONFIG.SYS for coexistence
Figure 19. Example of PROTOCOL.INI after setting up coexistence
Novell's emulation of NetBIOS over IPXNovell's NetBIOS emulator supports two kinds of NetBIOS: NetBIOS NB30 and NetBIOS Submit. For communication with CICS for OS/2, NetBIOS NB30 is required. For more information refer to the NOVELL: NetWare Requester for OS/2 manual.
Setting up the CICS serverFor the CICS for OS/2 system to act as the CICS server on a Novell LAN and use Novell's NetBIOS emulator, the workstation must be configured in a similar manner to an OS/2 NetWare Requester workstation, but with extra steps to allow the use of NetBIOS. The stages in the configuration process are:
The process is described in the CICS for OS/2 Intercommunication book, and is essentially the same as for setting up CICS Client for OS/2 on a Novell LAN.
Setting up CICS Client for DOS
Setting up CICS Client for OS/2You set up the client in three steps:
At this point you can restart the workstation. Figure 20. Statements added to CONFIG.SYS for NetWare Requester for OS/2 and LAPS
Figure 21. Example of PROTOCOL.INI after setting up NetBIOS emulation
Setting up CICS Client for Windows
Figure 22. Example of a STARTNET.BAT file for DOS and Windows clients
[ IBM home page | (C) | (TM) ] © IBM Corporation 1994, 1997. All Rights Reserved
|