IBM
Shop Support Downloads
Home Products Consulting Industries News About IBM Search
IBM > Software > Transaction Systems > CICS > Library > Manuals >
 

 

Administration


[Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index] [Help]


Setting up client/server communication

     

This topic describes the following:

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 definitions

   

This 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:

  • Definitions required for communication products at the CICS server.

  • Definitions required on the CICS server.

  • Definitions required for the communication product at the CICS client.

  • Definitions required in the client initialization file

  • Example values for the definitions.

    As far as possible, the example values are based on the values in the supplied client initialization file, CICSCLI.INI. See "Preparing the client initialization file" for more information.

  • The definitions that must match.

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 for OS/2 System Initialization Table Definitions Ref. Key Example
Local System Appl ID 1 CICSOS2
NetBIOS Listener Adapter 2 0
Maximum NetBIOS Systems
15

CICS client definitions

Client Initialization File Definitions Ref. Key Example
Server
CICSNETB
Protocol
NETBIOS
Netname 1 CICSOS2
Adapter 2 0
Driver
NETBIOS
DriverName
CCLIBMNB

Table 2. Matching definitions: CICS Client for DOS to CICS for OS/2 using NetBIOS
Ref. Key CICS for OS/2 Client Initialization File Example
1 Local System Appl ID Netname CICSOS2
2 NETBIOS Listener Adapter Adapter 0

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 configuration

 

This 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 DOS

For 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 checklists

The 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 for OS/2 System Initialization Table Definitions Ref. Key Example
Local System Appl ID 1 CICSOS2
NetBIOS Listener Adapter 2 0
Maximum NetBIOS Systems
15

CICS client definitions

Client Initialization File Definitions Ref. Key Example
Server
CICSNETB
Protocol
NETBIOS
Netname 1 CICSOS2
Adapter 2 0
Driver
NETBIOS
DriverName
CCLIBMNB

Table 3. Matching definitions: CICS Client for DOS to CICS for OS/2 using NetBIOS
Ref. Key CICS for OS/2 Client Initialization File Example
1 Local System Appl ID Netname CICSOS2
2 NETBIOS Listener Adapter Adapter 0

CICS Client for OS/2

For 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 checklists

For 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 Windows

For 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 checklists

For 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 95

NetBIOS support is provided with Windows 95, and no further configuration is required after installation.

Definition checklists

For 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 NT

NetBIOS 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:

Network Route

0: Nbf->IbmTok4->IbmTok41

Lana Number

0. This matches the Adapter parameter in the client initialization file.

Definition checklists

For 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 resources

   

CICS 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:

NetBIOS Names

1

NetBIOS Commands

Value of MaxServers + 1

NetBIOS Sessions

Value of MaxServers.

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 configuration

   

This 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:      

  • The IP address/host name of the CICS clients
  • The IP address/host name of the CICS servers
  • The IP address/name of any domain nameserver
  • The subnet mask (if required)
  • The port number of the CICS servers

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 DOS

The following sections summarize TCP/IP configuration for CICS Client for DOS.

IBM TCP/IP for DOS

For 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 checklists

The following shows example definitions for connecting CICS Client for DOS to a CICS for AIX server:

CICS server definitions

TCP/IP for AIX/6000 Definitions Ref. Key Example
HOSTNAME 1 cicstcp.ibm.com
Internet ADDRESS 2 192.113.36.200
Network MASK 3 255.255.255.0
NAMESERVER Internet ADDRESS 4 192.113.36.250
DOMAIN Name 5 acme.ibm.com
TCP/IP service name 6 cicstcp
Port number 7 0
Protocol type (TCP only)
TCP

CICS for AIX Server Definitions Ref. Key Example
Listener Identifier
anyname
Protocol type (TCP only)
TCP
TCP adapter address 2 192.113.36.200
TCP service name 6 cicstcp

CICS Client Definitions

TCP/IP for DOS Definitions Ref. Key Example
Host name
myhost
IP Address
192.113.36.78
Subnet Mask 3 255.255.255.0
Domain name server address (DNSA) 4 192.113.36.250
Domain name 5 acme.ibm.com

Client Initialization File Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname (host name) 1 cicstcp.ibm.com
Netname (IP address) 2 192.113.36.200
Port 7 0
Driver
TCPIP
DriverName
CCLIBMIP

Table 4. Matching definitions: CICS Client for DOS to CICS for AIX using TCP/IP for DOS
Ref. Key TCP/IP for AIX/6000 CICS for AIX TCP/IP for DOS Client Initialization File Example
1 HOSTNAME

Netname (host name) cicstcp.ibm.com
2 Internet ADDRESS TCP adapter address
Netname (IP address) 192.113.36.200
3 Network MASK
Subnet Mask
255.255.255.0
4 NAMESERVER Internet ADDRESS
DNSA
192.113.36.250
5 DOMAIN Name
Domain name
acme.ibm.com
6 TCP/IP service name TCP service name

cicstcp
7 Port number

Port 0

TCP/IP from FTP Inc

For information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.

Definition checklists

The following shows example definitions for connecting CICS Client for DOS to a Transaction Server for Windows NT server:

CICS server definitions

TCP/IP for Windows NT Definitions Ref. Key Example
Host Name 1 cicstcp
IP Address 2 192.113.36.200
Subnet Mask 3 255.255.255.0
Domain Name Server 4 192.113.36.250
Domain Name 5 acme.ibm.com

CICS for Windows NT Listener Definitions Ref. Key Example
Listener name
ANYNAME
Protocol
TCP
Note: You can leave other listener definitions as the default values. See Transaction Server for Windows NT Administration Reference for more information.

CICS client definitions

PC/TCP for DOS/Windows Definitions Ref. Key Example
Hostname
myhost
IP Address
192.113.36.78
Router
192.113.36.25
Subnet Mask 3 255.255.255.0
DNS Server Address 4 192.113.36.250
Domain Name 5 acme.ibm.com

Client Initialization File Definitions Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname (host name) 1 cicstcp
Netname (IP address) 2 192.113.36.200
Port
0
Driver
TCPIP
DriverName
CCLFTPIP

Table 5. Matching definitions: CICS Client for DOS to CICS for Windows NT using PC/TCP
Ref. Key TCP/IP for Windows NT PC/TCP for DOS/ Windows Client Initialization File Example
1 Host Name
Netname (host name) cicstcp.ibm.com
2 IP Address
Netname (IP address) 192.113.36.200
3 Subnet Mask Subnet Mask
255.255.255.0
4 Domain Name Server DNS Server Address
192.113.36.250
5 Domain Name Domain Name
acme.ibm.com

Novell LAN Workplace for DOS

   

For information on installing and configuring Novell LAN Workplace for DOS, see the Novell LAN Workplace Installation Guide.

Definition checklists

The following shows example definitions for connecting CICS Client for DOS to a Transaction Server for Windows NT server:

CICS server definitions

TCP/IP for Windows NT Definitions Ref. Key Example
Host Name 1 cicstcp
IP Address 2 192.113.36.200
Subnet Mask 3 255.255.255.0
Domain Name Server 4 192.113.36.250
Domain Name 5 acme.ibm.com

CICS for Windows NT Listener Definitions Ref. Key Example
Listener name
ANYNAME
Protocol
TCP
Note: You can leave other listener definitions as the default values. See Transaction Server for Windows NT Administration Reference for more information.

CICS client definitions

LAN Workplace Definitions Ref. Key Example
Hostname
myhost
IP Address
192.113.36.78
Router
192.113.36.25
Subnet Mask 3 255.255.255.0
DNS Server Address 4 192.113.36.250
Domain Name 5 acme.ibm.com

Client Initialization File Definitions Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname (host name) 1 cicstcp
Netname (IP address) 2 192.113.36.200
Port
0
Driver
TCPIP
DriverName
CCLNOVIP

Table 6. Matching definitions: CICS Client for DOS to CICS for Windows NT using LAN Workplace
Ref. Key TCP/IP for Windows NT LAN Workplace Client Initialization File Example
1 Host Name
Netname (host name) cicstcp.ibm.com
2 IP Address
Netname (IP address) 192.113.36.200
3 Subnet Mask Subnet Mask
255.255.255.0
4 Domain Name Server DNS Server Address
192.113.36.250
5 Domain Name Domain Name
acme.ibm.com

CICS Client for OS/2

The following sections summarize TCP/IP configuration for CICS Client for OS/2.

IBM TCP/IP for OS/2

For 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 checklists

The following shows example definitions for connecting CICS Client for OS/2 to a CICS for OS/2 server:

CICS server definitions

TCP/IP for OS/2 Definitions Ref. Key Example
IP address of workstation 1 9.113.36.31
IP address of Domain Name Server 4 9.113.42.240
IP address of router
9.113.36.254
Subnet Mask
255.255.254.0
Hostname 2 cicstcp.ibm.com
Port number 3 0

CICS for OS/2 System Initialization Table Definitions Ref. Key Example
TCP/IP Local Host Name 1 or 2 *
TCP/IP Local Host Port 3 *
Maximum TCP/IP Systems
15
Note: You can enter values for the TCP/IP Local Host Name and TCP/IP Local Host Port, or use the default values of *. See CICS for OS/2 Customization for more information.

CICS client definitions

TCP/IP for OS/2 Definitions Ref. Key Example
IP address of workstation
9.113.36.25
IP address of Domain Name Server 4 9.113.42.240
Subnet Mask
255.255.254.0
IP address of router
9.113.36.254

Client Initialization File Definitions Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname 1 or 2 cicstcp.ibm.com
Port 3 0
Driver
TCPIP
DriverName
CCLIBMIP

Table 7. Matching definitions: CICS Client for OS/2 to CICS for OS/2 using TCP/IP for OS/2
Ref. Key TCP/IP on Server CICS for OS/2 on Server TCP/IP on Client Client Initialization File Example
1 IP address TCP/IP Local Host Name
Netname 9.113.36.31
2 Hostname TCP/IP Local Host Name
Netname cicstcp.ibm.com
3 Port number TCP/IP Local Host Port
Port 0
4 IP address of Domain Name Server
IP address of Domain Name Server
9.113.42.240

The following shows example definitions for connecting CICS Client for OS/2 to a CICS for AIX server:

CICS server definitions

TCP/IP for AIX/6000 Definitions Ref. Key Example
HOSTNAME 1 cicstcp.ibm.com
Internet ADDRESS 2 192.113.36.200
Network MASK 3 255.255.255.0
Client Hostname 4 myhost
Client Address 5 192.113.36.78
TCP/IP service name 6 cicstcp
Port number 7 0
Protocol type (TCP only)
TCP

CICS for AIX Server Definitions Ref. Key Example
Listener Identifier
anyname
Protocol type (TCP only)
TCP
TCP adapter address 2 192.113.36.200
TCP service name 6 cicstcp

CICS client definitions

TCP/IP for OS/2 Definitions Ref. Key Example
Host name 4 myhost
IP Address 5 192.113.36.78
Subnet Mask 3 255.255.255.0
Server IP Address 2 192.113.36.200
Server HostName 1 cicstcp.ibm.com

Client Initialization File Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname (host name) 1 cicstcp.ibm.com
Netname (IP address) 2 192.113.36.200
Port 7 0
Driver
TCPIP
DriverName
CCLIBMIP

Table 8. Matching definitions: CICS Client for OS/2 to CICS for AIX using TCP/IP for OS/2
Ref. Key TCP/IP for AIX/6000 CICS for AIX TCP/IP for OS/2 Client Initialization File Example
1 HOSTNAME
Server Hostname Netname (host name) cicstcp.ibm.com
2 Internet ADDRESS TCP adapter address Server IP Address Netname (IP address) 192.113.36.200
3 Network MASK
Subnet Mask
255.255.255.0
4 Client Hostname
Hostname
myhost
5 Client Address
IP Address
192.113.36.78
6 TCP/IP service name TCP service name

cicstcp
7 Port number

Port 0

TCP/IP from FTP Inc

For information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.

Definition checklists

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.

Novell LAN Workplace for OS/2

   

For information on installing and configuring Novell LAN Workplace for OS/2, see the Novell LAN Workplace Installation Guide.

Definition checklists

The 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 Windows

The following sections summarize TCP/IP configuration for CICS Client for Windows.

IBM TCP/IP for DOS

For 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 checklists

For 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 Inc

For information on installing and configuring PC/TCP Network Software, see the PC/TCP Network Software Installation Guide.

Definition checklists

For 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 DOS

For information on installing and configuring Novell LAN Workplace for DOS, see the Novell LAN Workplace Installation Guide.

Definition checklists

For 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 WINSOCK

TCP/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 95

TCP/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 checklists

For 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 NT

TCP/IP support is provided by the Windows NT operating system. Refer to the Windows NT documentation for information on configuring TCP/IP.

Definition checklists

For 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 Macintosh

 

For information on installing MacTCP, see the documentation supplied with your MacTCP package.

Definition checklists

The following shows example definitions for connecting CICS Client for Macintosh to a CICS for OS/2 server:

CICS server definitions

TCP/IP for OS/2 Definitions Ref. Key Example
IP address of workstation 1 9.113.36.31
IP address of Domain Name Server 4 9.113.42.240
IP address of router
9.113.36.254
Subnet Mask
255.255.254.0
Hostname 2 cicstcp.ibm.com
Port number 3 0

CICS for OS/2 System Intitialization Table Definitions Ref. Key Example
TCP/IP Local Host Name 1 or 2 *
TCP/IP Local Host Port 3 *
Maximum TCP/IP Systems
15
Note: You can enter values for the TCP/IP Local Host Name and TCP/IP Local Host Port, or use the default values of *. See CICS for OS/2 Customization for more information.

CICS client definitions

MacTCP Definitions Ref. Key Example
IP address of workstation
9.113.36.25
IP address of Domain Name Server 4 9.113.42.240
Subnet Mask
255.255.254.0
IP address of router
9.113.36.254

Client Initialization File Definitions Ref. Key Example
Server
CICSTCP
Protocol
TCPIP
Netname 1 or 2 cicstcp.ibm.com
Port 0
Driver
TCPIP
DriverName
CCLMACIP

Table 9. Matching definitions: CICS Client for Macintosh to CICS for OS/2 using MacTCP
Ref. Key TCP/IP on Server CICS for OS/2 on Server MacTCP on Client Client Initialization File Example
1 IP address TCP/IP Local Host Name
Netname 9.113.36.31
2 Hostname TCP/IP Local Host Name
Netname cicstcp.ibm.com
3 Port number TCP/IP Local Host Port
Port 0
4 IP address of Domain Name Server
IP address of Domain Name Server
9.113.42.240

Verifying the TCP/IP installation

To 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


# ping 9.113.36.31 56 3

PING 192.113.36.78: (192.113.36.78): 56 data bytes

64 bytes from 9.113.36.31: icmp_seq=0 ttl=255 time=3 ms

64 bytes from 9.113.36.31: icmp_seq=1 ttl=255 time=3 ms

64 bytes from 9.113.36.31: icmp_seq=2 ttl=255 time=3 ms



----9.113.36.31 PING Statistics----

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 3/3/3 ms

#


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:

  • Check for TCP/IP definition errors
  • Check for TCP/IP definition mismatches
  • Check the network physical connection

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 configuration

   

This section describes how to set up CICS clients for communication via the APPC protocol. Generally, the following are defined:      

  • The local node characteristics that are common to all APPC users at the workstation

  • A local logical unit (LU) definition for the client

  • A partner logical unit (PLU) definition for each CICS server with which the client will communicate

  • One or more mode definitions to specify sets of session properties that are used in binding APPC sessions  

  • A transaction program (TP) definition for the CRSR transaction. This is required if terminal emulation is supported by the CICS servers, and it is necessary to perform automatic transaction initiation (ATI) against the CICS client terminals.

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 DOS

The following sections summarize APPC configuration for CICS Client for DOS.

Communicating to CICS/400

 

Client 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 Network

   

You 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 settings

The 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

NetWare LU 6.2

CICSCLI.INI

Local LU name

LocalLUName

LU Local Address

SnaLocalLUAddr

LU Session Limit

SnaSessionLimit

Mode configuration data

NetWare LU 6.2

CICSCLI.INI

Data Link Control Name

SnaDLCName

Network Adapter Address

SnaPLUAdapterAddr

Remote LU configuration data

NetWare LU 6.2

CICSCLI.INI

Mode Name

Modename

Pacing Size

SnaPacingSize

Max RU Size

SnaMaxRUSize

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:

  • To use an independent LU, set SnaLocalLUAddr to X'00'.

  • To use a specific dependent LU, named in LocalLUName, set SnaLocalLUAddr to a value in the range X'01' to X'FE' to match that in the NetWare server profile.

  • To use any available LU from a group of dependent LUs, set SnaLocalLUAddr to X'FF' and LocalLUName to the name of the LU group.

  • To use any available dependent LU that is not a member of any LU group, set SnaLocalLUAddr to X'FF' and LocalLUName to *.

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

  • You can only configure NetWare for SAA Version 1.3 to use two NetWare server profiles at a time. However, you may be able to use one NetWare server profile to communicate with more than one CICS server.

  • Each client/server link must use a different local LU.

  • LU-LU verification security is not supported.

  • If you wish to run ECI applications that supply user IDs and passwords, you must ensure that the CICS server you intend to use is correctly configured to use SNA conversation level security.

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 checklists

The following shows example definitions for connecting CICS Client for DOS to a CICS/ESA server:

CICS server definitions

VTAM Definitions Ref. Key Example
NETID 1 USIBMC
LU 2 WXYZ9999
APPL 3 EFGH5678
Logmode 4 LU62PS
XID 5 05DA2072

CICS/ESA Version 3.3 Definitions Ref. Key Example
Netname in the LU6.2 connection definition 2 WXYZ9999
Applid (SIT parameter) 3 EFGH5678
Modename in the LU6.2 sessions definition 4 LU62PS
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.

CICS Client definitions

NetWare for SAA Definitions on the Gateway Ref. Key Example
SNA Network ID 1 USIBMC
BlockID/PUID 5 05DA2072

Client Initialization File Ref. Key Example
Server
CICSSNA
Netname 3 EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Modename 4 LU62PS
Driver
SNA
DriverName
CCLNOVSN

Table 10. Matching definitions: CICS Client for DOS to CICS/ESA using NetWare for SAA
Ref. Key VTAM CICS/ESA V3.3 Netware for SAA Client Initialization File Example
1 NETID
SNA Network ID
USIBMC
2 LU Netname
LocalLUName WXYZ9999
3 APPL Applid
Netname EFGH5678
4 Logmode Modename
Modename LU62PS
5 XID
BlockID/PUID
05DA2072

CICS Client for OS/2

The 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
File Contents
configname.CFG Communications Manager/2 configuration (.CFG) file
configname.NDF Node definitions (.NDF) file
configname.CF2 SNA configuration (.CF2) file (copy of .NDF file)
configname.SEC SNA security (.SEC) file
PROTOCOL.INI LAN Adapter and Protocol Support (LAPS) configuration file
     

Communications Manager/2 configuration (.CFG) file
 

The 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) file
   

The 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:

  • Local node characteristics
  • Connection to peer node or primary host
  • Connection to network node
  • Local logical unit
  • Partner logical unit
  • Mode
  • Transaction program

SNA configuration (.CF2) file
 

The 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) file
   

The SNA security (.SEC) file contains SNA definitions for session-level and conversation-level security.

APPC definitions

For APPC communication, the following are defined:

  • One local node Characteristics definition

  • At least one connection definition

  • A local logical unit (LU) definition

  • A partner logical unit (PLU) definition for each CICS server with which the client will communicate

  • One or more mode definitions to specify sets of session properties that are used in binding APPC sessions

  • A transaction program (TP) definition for the CRSR transaction.   This is required if terminal emulation is supported by the CICS servers, and it is necessary to perform automatic transaction initiation (ATI)     against the CICS client terminals.

Definition checklists

The following shows example definitions for connecting CICS Client for OS/2 to a CICS/ESA server over token-ring:

CICS server definitions

VTAM Definitions Ref. Key Example
XID (IDBLK+IDNUM) 1 05DA2072
PU

LU 2 WXYZ9999
Logmode 3 LU62PS
APPL 4 EFGH5678
NETID 5 ABCD1234

CICS/ESA V3.3 Definitions Ref. Key Example
Applid (SIT parameter) 4 EFGH5678
Netname in the LU6.2 connection definition 2 WXYZ9999
Modename in the LU6.2 sessions definition 3 LU62PS
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.

CICS client definitions

Communications Manager/2 Definitions Ref. Key Example
Network ID 5 ABCD1234
Local node name
SJA2072
Local node ID 1 05DA2072
LAN Destination Address
400008210200
Local LU 2 WXYZ9999
Partner LU 4 EFGH5678
Mode name 3 LU62PS
Transaction program
CRSR

Client Initialization File Definitions Ref. Key Example
Server
CICSSNA
Network.Netname 5.4 ABCD1234.EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Modename 3 LU62PS
Driver
SNA
DriverName
CCLIBMSN

Table 12. Matching definitions: CICS Client for OS/2 to CICS/ESA using Communications Manager/2
Ref. Key VTAM CICS/ESA V3.3 Communications Manager/2 Client Initialization File Example
1 XID
Local node ID
05DA2072
2 LU Netname Local LU LocalLUName WXYZ9999
3 Logmode Modename Mode name Modename LU62PS
4 APPL Applid Partner LU Netname EFGH5678
5 NETID
Network ID Network ABCD1234

The following shows example definitions for connecting CICS Client for OS/2 to a CICS/VSE server over SDLC:

CICS server definitions

VTAM Definitions Ref. Key Example
ADDR 1 C1
PU

LU 2 WXYZ9999
APPL 3 EFGH5678
NETID 4 ABCD1234

CICS client definitions

CICS/VSE V2.2 Definitions Ref. Key Example
Applid (SIT parameter) 3 EFGH5678
Netname in the LU6.2 connection definition 2 WXYZ9999
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.
Communications Manager/2 Definitions Ref. Key Example
Local station address 1 C1
Network ID 4 ABCD1234
Local node name
SJA2072
Local LU 2 WXYZ9999
Partner LU 3 EFGH5678
Transaction program
CRSR

Client Initialization File Definitions Ref. Key Example
Server
CICSSNA
Network.Netname 4.3 ABCD1234.EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Driver
SNA
DriverName
CCLIBMSN

Table 13. Matching definitions: CICS Client for OS/2 to CICS/VSE using Communications Manager/2 over SDLC
Ref. Key VTAM CICS/VSE V2.2 Communications Manager/2 Client Initialization File Example
1 XID
Local node ID
C1
2 LU Netname Local LU LocalLUName WXYZ9999
3 APPL Applid Partner LU Netname EFGH5678
4 NETID
Network ID Network ABCD1234

TP definition for CRSR transaction
 

Set up the Transaction Program Definitions panel of Communications Manager/2 as follows:

Service TP

Do not select.

Transaction program (TP) name

CRSR.

OS/2 program path and file name

For example, C:\CICSCLI\BIN\CCLSNOTP.EXE

Optional Comment

For example, IBM CICS Client Attach TP Profile

Conversation Security

Do not select

Program parameter string

CRSR

Icon path and file name

This is not required.

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:




  DEFINE_TP  TP_NAME(CRSR)

             DESCRIPTION(IBM CICS Client CRSR Attach TP Profile)

             PIP_ALLOWED(NO)

             FILESPEC(c:\cicscli\bin\cclsnotp.exe)

             PARM_STRING(CRSR)

             CONVERSATION_TYPE(ANY_TYPE)

             CONV_SECURITY_RQD(NO)

             SYNC_LEVEL(EITHER)

             TP_OPERATION(NONQUEUED_AM_STARTED)

             PROGRAM_TYPE(BACKGROUND)

             RECEIVE_ALLOCATE_TIMEOUT(INFINITE);



  START_ATTACH_MANAGER;




Starting APPC sessions
   

With 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:

  • Each time Communications Manager/2 is started:
    1. Select the Subsystem Management icon
    2. Select SNA Subsystem from the subsystem management screen
    3. Select LU 6.2 sessions
    4. Select Establish from the action bar to establish the required LU 6.2 sessions.

  • By the preferred method--adding the appropriate change number of sessions (CNOS) statements     to the NDF file (see the following sample):
    1. Add CNOS statements to the .NDF file to establish the sessions. Make sure that:

      1. LOCAL_LU_ALIAS matches the alias entered on the Local LU window (see the definition checklist for Communications Manager/2)

      2. FQ_PARTNER_LU_NAME matches your Network ID (5) and Partner LU name (4) (separated by a period)

      3. MODE_NAME matches the Mode name (3)

      4. PLU_MODE_SESSION_LIMIT matches the Mode session limit

      5. AUTO_ACTIVATE is not greater than PLU_MODE_SESSION_LIMIT (but it must be greater than zero to establish at least one user session).
    2. Run CMVERIFY to produce the .CF2 file.

Figure 16. Sample CNOS statements


  CNOS  LOCAL_LU_ALIAS(WXYZ9999)

        FQ_PARTNER_LU_NAME(ABCD1234.EFGH5678)

        MODE_NAME(SNASVCMG)

        SET_NEGOTIABLE(NO)

        PLU_MODE_SESSION_LIMIT(2)

        MIN_CONWINNERS_SOURCE(1)

        MIN_CONWINNERS_TARGET(1)

        AUTO_ACTIVATE(1);



  CNOS  LOCAL_LU_ALIAS(WXYZ9999)

        FQ_PARTNER_LU_NAME(ABCD1234.EFGH5678)

        MODE_NAME(LU62PS  )

        SET_NEGOTIABLE(NO)

        PLU_MODE_SESSION_LIMIT(8)

        MIN_CONWINNERS_SOURCE(4)

        MIN_CONWINNERS_TARGET(4)

        AUTO_ACTIVATE(8);


CICS Client for Windows

The following sections summarize APPC configuration for CICS Client for Windows.

Communicating to CICS/400

 

Client 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 Windows

 

APPC 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:

  • [Configuration]  

    This section specifies the type of communications adapter you use, the local LU name for your workstation, and other information. The LocalLUName in the client initialization file is not used. The fully qualified version of the LU name must be defined in the LOCALUNAME statement.

    Note: The node id must match the node ID configured in VTAM. Otherwise, the CICS client may be unresponsive when it tries to connect to the CICS server.

  • [LAN]

    This section defines the links. The link name defined in the TRLD statement must be the unqualified 8-character PLU name.

  • [MODES]

    This section specifies mode characteristics for sessions between your workstation and a remote computer. This section must include the modes that are used in the client initialization file.

  • [SIDEINFO]      

    This section provides side information required by a CPI-C program to communicate with a partner program on a remote computer. Side information indicates:

    • TP name
    • LU name
    • The mode name.

    You do not need to make any definitions for CICS clients.

  • [DEFINETP]

    This section provides information used to access incoming Attaches and to start programs on your workstation. You may need to add a definition for the CRSR transaction. This is required if terminal emulation is supported by the CICS server, and you want to perform ATI against client terminals.

    You should set up the CRSR definition as follows:

    Transaction Program Name

    CRSR

    File Specification

    C:\CICSCLI\BIN\CCLSNSTP.EXE

    Program Parameters

    CRSR

    Incoming Attach Time-out

    30 (the default)

    Accept_Conversation Time-out

    0 (the default)

    Transaction Program Operation

    ATTACH MANAGER STARTED

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.

Restrictions

If you are using APPC Networking Services for Windows, it is not possible to define the PUs to have any LU2 sessions.

Definition checklists

The following shows example definitions for connecting CICS Client for Windows to a CICS/ESA server over token-ring:

CICS server definitions

VTAM Definitions Ref. Key Example
XID (IDBLK+IDNUM) 1 05DA2072
PU

LU 2 WXYZ9999
Logmode 3 LU62PS
APPL 4 EFGH5678

CICS/ESA V3.3 Definitions Ref. Key Example
Applid (SIT parameter) 4 EFGH5678
Netname in the LU6.2 connection definition 2 WXYZ9999
Modename in the LU6.2 sessions definition 3 LU62PS
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.

CICS client definitions

APPC Networking Services for Windows Definitions Ref. Key Example
Network ID 5 ABCD1234
Local LU 2 WXYZ9999
Connection Type
LAN
Link Name
CICSESA
LAN Destination Address
400008210200
Mode name 3 LU62PS
Transaction program
CRSR
Node ID (in NSD.INI file) 1 05DA2072

Client Initialization File Definitions Ref. Key Example
Server
CICSSNA
Network.Netname 5.4 ABCD1234.EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Modename 3 LU62PS
Driver
SNA
DriverName
CCLIBMSN

Table 14. Matching definitions: CICS Client for Windows to CICS/ESA using APPC Networking Services for Windows over token-ring
Ref. Key VTAM CICS/ESA V3.3 APPC Networking Services for Windows Client Initialization File Example
1 XID
Local node ID
05DA2072
2 LU Netname Local LU LocalLUName WXYZ9999
3 Logmode Modename Mode name Modename LU62PS
4 APPL Applid Partner LU Netname EFGH5678
5 NETID
Network ID Network ABCD1234

The following shows example definitions for connecting CICS Client for Windows to a CICS/VSE server over SDLC:

CICS server definitions

VTAM Definitions Ref. Key Example
PU

ADDR 1 C1
LU 2 WXYZ9999
APPL 3 EFGH5678
NETID 4 ABCD1234

CICS/VSE V2.2 Definitions Ref. Key Example
Applid (SIT parameter) 3 EFGH5678
Netname in the LU6.2 connection definition 2 WXYZ9999
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.

CICS client definitions

APPC Networking Services for Windows Definitions Ref. Key Example
Network ID 4 ABCD1234
Local LU 2 WXYZ9999
Connection Type
SDLC
Link Name
CICSVSE
Local station address 1 C1
Transaction program
CRSR

Client Initialization File Definitions Ref. Key Example
Server
CICSSNA
Network.Netname 4.3 ABCD1234.EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Driver
SNA
DriverName
CCLIBMSN

Table 15. Matching definitions: CICS Client for Windows to CICS/VSE using APPC Networking Services for Windows over SDLC
Ref. Key VTAM CICS/VSE V2.2 APPC Networking Services for Windows Client Initialization File Example
1 ADDR
Local Station Address
C1
2 LU Netname Local LU name LocalLUName WXYZ9999
3 APPL Applid
Netname EFGH5678
4 NETID
Network ID Network ABCD1234

Communication via a Novell Network

   

You 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:




[LU62]

TRANS_FILE = TABLE.DAT

LU_TYPE = 6

NETWARE_SAA_SERVER       = CICSNET

NETWARE_SAA_USER_NAME    = SUPERVISOR

NETWARE_SAA_SERVICE_NAME = ESA_21

TRAN_SPX_READ_DOS_MEMORY = 8192

TRAN_SPX_GLOBAL_MEMORY   = 64000


To avoid WTSPX transport errors for NetWare for SAA Version 1.3:

  • Set the following in the WS.CFG file:
    
    TRAN_SPX_GLOBAL_MEMORY = 64000
    
    TRAN_SPX_REAL_DOS_MEMORY = 8192
    
    TRACE_MSG = 0
    
    

  • Ensure that all Open Data Link Interface (ODI) drivers are loaded into conventional memory.

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 settings
 

The 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

NetWare LU 6.2

CICSCLI.INI

Local LU name

LocalLUName

LU Loca l Address

SnaLocalLUAddr

LU Session Limit

SnaSessionLimit

Mode configuration data

NetWare LU 6.2

CICSCLI.INI

Data Link Control Name

SnaDLCName

Network Adapter Address

SnaPLUAdapterAddr

Remote LU configuration data

NetWare LU 6.2

CICSCLI.INI

Mode Name

Modename

Pacing Size

SnaPacingSize

Max RU Size

SnaMaxRUSize

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:

  • To use an independent LU, set SnaLocalLUAddr to X'00'.

  • To use a specific dependent LU, named in LocalLUName, set SnaLocalLUAddr to a value in the range X'01' to X'FE' to match that in the NetWare server profile.

  • To use any available LU from a group of dependent LUs, set SnaLocalLUAddr to X'FF' and LocalLUName to the name of the LU group.

  • To use any available dependent LU that is not a member of any LU group, set SnaLocalLUAddr to X'FF' and LocalLUName to *.

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

The 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 checklists

The definitions are the same as for CICS Client for DOS.

Microsoft SNA Server

   

APPC 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 client

On the SNA Server Windows client, you require the following settings:

SNA client mode

Remote

Primary Server

Name of the SNA Server workstation that the client systems using SNA Client will use. This computer name of the SNA Server is displayed in both the SNA Server Admin Servers and Connections window, and in the Network Settings control panel dialog box.

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=yes

Where 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 checklists

The following shows example definitions for connecting CICS Client for Windows to a CICS/ESA server over token-ring:

CICS server definitions

VTAM Definitions Ref. Key Example
XID (IDBLK+IDNUM) 1 05DA2072
PU

LU 2 WXYZ9999
Logmode 3 LU62PS
APPL 4 EFGH5678
NETID 5 ABCD1234

CICS/ESA V3.3 Definitions Ref. Key Example
Applid (SIT parameter) 4 EFGH5678
Netname in the LU6.2 connection definition 2 WXYZ9999
Modename in the LU6.2 sessions definition 3 LU62PS
Note: To enable Intersystem communication (ISC) on the CICS server, the DFHISC group must be installed.

CICS client definitions

SNA Server Definitions Ref. Key Example
Server Network Name 5 ABCD1234
Server LU Name 2 WXYZ9999
Server Connection Name
TOKEN1
Connection Type
802.2
Remote Network Address
400008210200
Local node ID 1 05DA2072
APPC Remote LU Properties: LU Name 4 EFGH5678
LU 6.2 Partners for EFGH5678 2 WXYZ9999
Mode 3 LU62PS

Client Initialization File Definitions Ref. Key Example
Server
CICSSNA
Network.Netname 5.4 ABCD1234.EFGH5678
Protocol
SNA
LocalLUName 2 WXYZ9999
Modename 3 LU62PS
Driver
SNA
DriverName
CCLWNTSN

Table 16. Matching definitions: CICS Client for Windows to CICS/ESA using SNA Server
Ref. Key VTAM CICS/ESA V3.3 Communications Manager/2 Client Initialization File Example
1 XID
Local Node ID
05DA2072
2 LU Netname Server LU Name LocalLUName WXYZ9999
3 Logmode Modename Mode Modename LU62PS
4 APPL Applid Partner LU Name Netname EFGH5678
5 NETID
Server Network Name Network ABCD1234

CICS Client for Windows 95

The following sections summarize APPC configuration for CICS Client for Windows 95.

Microsoft SNA Server

   

APPC 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 client

On the SNA Server Windows 95 client, you require the following settings:

SNA client mode

Remote

Primary Server

Name of the SNA Server workstation that the client systems using SNA Client will use. This computer name of the SNA Server is displayed in both the SNA Server Admin Servers and Connections window, and in the Network Settings control panel dialog box.

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 luname

where 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 checklists

The definitions are the same as for CICS Client for Windows.

CICS Client for Windows NT

The following sections summarize APPC configuration for CICS Client for Windows NT.

Microsoft SNA Server

   

APPC 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 client

On the SNA Server Windows NT client, you require the following settings:

SNA client mode

Remote

Primary Server

Name of the SNA Server workstation that the client systems using SNA Client will use. This computer name of the SNA Server is displayed in both the SNA Server Admin Servers and Connections window, and in the Network Settings control panel dialog box.

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 luname

where luname is the LocalLU you are using.

If CRSR is already configured, the LocalLU setting changes to match the new value.

Definition checklists

The definitions are the same as for CICS Client for Windows.

CICS Client for Macintosh

 

For 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:

  1. Select the SNA*ps Config icon in the SNA*ps folder. The SNA*ps Config resources window is displayed.

  2. Select the line type as Token Ring, SDLC, or Coax and enter the line information.

  3. Enter the correct settings for the partner.

  4. Enter the correct settings for the Local 6.2 LUs, that is the local LUs.

  5. Enter the correct settings for the transaction programs (TP).

  6. Enter the correct settings for the Remote 6.2 LUs, that is, the partner LUs.

  7. Enter the correct settings for the modes.

  8. Save the configuration file.

  9. Select the SNA*ps Admin icon in the SNA*ps folder. The Network Gateway Status window is displayed. Assign the configuration file to the required gateway.

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:

  • Stop or start, and verify the correctness of the configuration
  • Confirm that sessions are successfully established with the host
  • Stop or start line traces when communication problems need detailed investigation

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

   
Note

The procedures described in this section may be not be necessary, depending on the Novell NetWare LAN support provided by the operating system you are using. If you are in doubt about this, refer to the documentation supplied with your operating system.

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:

  1. Coexistence with Novell's IPX

    CICS clients can run on Novell NetWare workstations by making use of Novell's Open Data-Link Interface (ODI).     The ODI enables a workstation to support multiple communication protocols over a single network adapter. Therefore by using the ODI, a workstation can run a CICS client over either NetBIOS or TCP/IP, and access a NetWare file server over IPX. This requires no change to the setup of the CICS for OS/2 server because it receives normal NetBIOS or TCP/IP flows.

  2. Novell's emulation of NetBIOS over IPX

    Novell's NetBIOS emulator enables distributed client/server NetBIOS applications to run over IPX on a Novell LAN. NetBIOS emulator flows are transmitted with IPX headers. NetBIOS emulation is available on DOS, Windows and OS/2 workstations.

    CICS clients and CICS for OS/2 can use this emulator program. It means that a workstation can use IPX to access both a Novell file server and a CICS for OS/2 application server.

    When a workstation is configured to use Novell's NetBIOS emulator program it will only accept IPX flows, and will not accept native NetBIOS flows. Therefore, the CICS for OS/2 server will only accept input from CICS client workstations that have also been configured to use Novell's NetBIOS emulator over IPX.

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 Interface

Novell'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


* Figure ccla10 not displayed.


For further information on ODI, refer to the publications:

  • NOVELL: NetWare ODI Shell for DOS
  • NOVELL: NetWare Requester for OS/2.

Coexistence with Novell's IPX

       

This 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 clients

The 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.

  1. Install IBM LAN Support Program using the default values.

  2. In the CONFIG.SYS file, add the parameter O=Y to the DXMT0MOD.SYS device driver line so that the adapter is opened at startup. The CONFIG.SYS file should therefore contain lines like the following:
    
    DEVICE=\DXMA0MOD.SYS 001
    
    DEVICE=\DXMC0MOD.SYS
    
    DEVICE=\DXMT0MOD.SYS S=12 C=14 ST=12 O=Y
    
    

  3. Install NetWare Requester using the ODI drivers.

    1. Create a \NETWARE subdirectory on drive C, and then copy the necessary modules from the DOS/DOS ODI Workstation Services diskette (subdirectory \DOSODI) to the directory you created:
      • LSL.COM
      • LANSUP.COM
      • IPXODI.COM
      • ROUTE.COM (if you need source routing).

    2. Copy the NetWare shell NETX.COM, from the DOS/DOS ODI Workstation Services diskette to the \NETWARE subdirectory.

    3. Add the C:\NETWARE directory to the path in the AUTOEXEC.BAT file, and then add the following lines at the end of the file:
      
      LSL
      
      LANSUP
      
      ROUTE
      
      IPXODI
      
      NETX
      
      

NetWare OS/2 Requester running CICS Client for OS/2

The 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.

  1. Install NetWare Requester for OS/2 Version 2.0.1.

  2. You must now configure the ODINSUP interface for token ring operation:

    1. First you must replace each NDIS MAC driver name with the ODI driver name. Edit the PROTOCOL.INI file to replace all occurrences of:
      
              bindings = IBMTOK_nif
      
      

      with:
      
              bindings = TOKEN
      
      

    2. Next, you must prevent NDIS MAC drivers from loading. In CONFIG.SYS, comment out the line:
      
      DEVICE=C:\IBMLAN\MACS\IBMTOK.OS2
      
      

    3. In CONFIG.SYS, add the line:
      
      DEVICE=C:\NETWARE\ODINSUP.SYS
      
      

      Make sure that the new ODINSUP driver comes after the line:

      
      DEVICE=C:\NETWARE\ROUTE.SYS
      
      

    4. Now, you must enable the frame types and bind ODINSUP to your LAN driver. In the NET.CFG file, add the following lines:
      
      link driver TOKEN
      
        frame token-ring
      
        frame token-ring_snap
      
      
      
      protocol odinsup
      
        bind TOKEN
      
      

  3. Restart the workstation.

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


REM --- NetWare Requester statements BEGIN ---

SET NWLANGUAGE=ENGLISH

DEVICE=C:\NETWARE\LSL.SYS

RUN=C:\NETWARE\DDAEMON.EXE



REM -- ODI-Driver Files BEGIN --

DEVICE=C:\NETWARE\TOKEN.SYS

DEVICE=C:\NETWARE\ROUTE.SYS



REM ***** Next line added manually *****

DEVICE=C:\NETWARE\ODINSUP.SYS

REM -- ODI-Driver Files END --



DEVICE=C:\NETWARE\IPX.SYS

rem DEVICE=C:\NETWARE\SPX.SYS

rem RUN=C:\NETWARE\SPDAEMON.EXE

rem DEVICE=C:\NETWARE\NMPIPE.SYS

rem DEVICE=C:\NETWARE\NPSERVER.SYS

rem RUN=C:\NETWARE\NPDAEMON.EXE

DEVICE=C:\NETWARE\NWREQ.SYS

IFS=C:\NETWARE\NWIFS.IFS

RUN=C:\NETWARE\NWDAEMON.EXE

rem DEVICE=C:\NETWARE\NETBIOS.SYS

rem RUN=C:\NETWARE\NBDAEMON.EXE

rem DEVICE=C:\NETWARE\VIPX.SYS

rem DEVICE=C:\NETWARE\VSHELL.SYS PRIVATE

REM --- NetWare Requester statements END ---


Figure 19. Example of PROTOCOL.INI after setting up coexistence


[PROT_MAN]



   DRIVERNAME = PROTMAN$



[IBMLXCFG]



   IBMTOK_nif = IBMTOK.nif

   LANDD_nif = LANDD.NIF

   NETBEUI_nif = NETBEUI.NIF



[LANDD_nif]



   DriverName = LANDD$

;  Bindings = IBMTOK_nif  - This line manually replaced by next

   Bindings = TOKEN

   NETADDRESS = "08005a0347bf"

   ETHERAND_TYPE = "I"

   SYTEM_KEY = 0x0

   OPEN_OPTIONS = 0x2000

   TRACE = 0x0

   LINKS = 8

   MAX_SAPS = 3

   MAX_G_SAPS = 0

   USERS = 3

   TI_TICK_G1 = 255

   T1_TICK_G1 = 15

   T2_TICK_G1 = 3

   TI_TICK_G2 = 255

   T1_TICK_G2 = 25

   T2_TICK_G2 = 10

   IPACKETS = 250

   UIPACKETS = 100

   MAXTRANSMITS = 6

   MINTRANSMITS = 2

   TCBS = 64

   GDTS = 30

   ELEMENTS = 800



[NETBEUI_nif]



   DriverName = netbeui$

;  Bindings = IBMTOK_nif  - This line manually replaced by next

   Bindings = TOKEN

   NETADDRESS = "08005a0347bf"

   ETHERAND_TYPE = "I"

   USEADDRREV = "YES"

   OS2TRACEMASK = 0x0

   SESSIONS = 210

   NCBS = 250

   NAMES = 40

   SELECTORS = 5

   USEMAXDATAGRAM = "NO"

   ADAPTRATE = 1000

   WINDOWERRORS = 0

   MAXDATARCV = 4168

   TI = 30600

   T1 = 500

   T2 = 200

   MAXIN = 1

   MAXOUT = 1

   NETBIOSTIMEOUT = 500

   NETBIOSRETRIES = 8

   NAMECACHE = 0

   PIGGYBACKACKS = 1

   DATAGRAMPACKETS = 2

   PACKETS = 350

   LOOPPACKETS = 1

   PIPELINE = 5

   MAXTRANSMITS = 6

   MINTRANSMITS = 2

   DLCRETRIES = 5

   NETFLAGS = 0x0



[IBMTOK_nif]



   DriverName = IBMTOK$

   ADAPTER = "PRIMARY"

   MAXTRANSMITS = 6

   RECVBUFS = 2

   RECVBUFSIZE = 256

   XMITBUFS = 1


Novell's emulation of NetBIOS over IPX

     

Novell'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 server

For 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:

  1. Configure the workstation as a NetWare Requester
  2. Install IBM NetWare Requester Support from LAPS
  3. Bind the NetBIOS protocol to the adapter.

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

  1. Install the NetWare DOS Requester code.

  2. Install and configure NetWare NetBIOS emulation:

    1. The file NETBIOS.EXE (the NetBIOS emulator program) should have been copied to your hard disk during installation of the NetWare client code. If not, locate the file on the NetWare disks and copy it.

    2. In the file C:\NWCLIENT\STARTNET.BAT (see Figure 22), add the line:
      
      NETBIOS
      
      

      immediately before the line:
      
      CD \
      
      

    3. Restart the works tation to confirm that NetBIOS support will correctly load at startup.

Setting up CICS Client for OS/2

You set up the client in three steps:

Step 1--Conf igure the workstation as a NetWare OS/2 Requester

You must first configure the workstation as a NetWare OS/2 Requester with NetBIOS emulator support:

  1. Insert the Novell Workstation for OS/2 diskette and enter A:\install at the command prompt.

  2. Select the Requester on Workstation option from the Installation pull down menu.

  3. Enter a directory in the Set Target Directory panel, if you do not want the default.

  4. On the Requester Installation panel, select Edit CONFIG.SYS and Copy All Files.

  5. Enter the name of the LAN driver required, for example, TOKEN.SYS, or select a driver from the list.

  6. In the next panel select On or Off for IPX Support for DOS and Windows. (This is not critical for NetBIOS emulation.)

  7. On the Choose Optional Protocols panel, select NetBIOS Emulation for OS/2 Sessions. Select On or Off for Remote Named Pipes Support. (This is not critical for NetBIOS emulation.)

  8. Select Save and allow the installation to complete in the usual way.

  9. Ignore the instruction to restart at this stage.

The statements added to CONFIG.SYS are shown in Figure 20.

Step 2--Install IBM NetWare Requester Support from LAPS

The LAN adapter and protocol support (LAPS) program is used to     configure the protocol to the adapter. LAPS is discussed in the CICS for OS/2 Intercommunication book. You can obtain LAPS from different sources; in this technique it is obtained from IBM Network Transport Services/2 (NTS/2). (See the NTS/2 Lan Adapter and Protocol Support Configuration Guide.)

  1. From the configure function of LAPS, display the Configure Workstation panel.

  2. In the Protocols listbox in the Configure Workstation panel, select the IBM OS/2 NetBIOS and IBM NetWare Requester Support protocols and add them using the Add button. This adds the protocols to the Current Configuration listbox.

  3. Select the IBM NetWare Requester Support protocol from the Current Configuration listbox and edit its parameters by selecting the Edit button. The Parameters for IBM NetWare Requester Support panel is then displayed.

  4. Enter the hexadecimal address of the workstation's adapter card into the Network Adapter Address field. You can find this address in the LANTRAN.LOG file.

  5. Complete the configuration of LAPS in the usual way.

  6. Do not restart the system at this stage.

This step adds ODI2NDI.OS2, which maps the lower-level NDIS protocol APIs to the upper layer ODI APIs.

Step 3--Bind the NetBIOS protocol to the adapter

The NetBIOS protocol added in the above steps must now be bound to the adapter as follows:
     

  1. Edit the file C:\IBMCOM\PROTOCOL.INI by adding the following:
    
    [NETBIOS]
    
      DriverName = NetBios$
    
      Bindings = IBMTOK_nif
    
      ADAPTER0 = IPXNB$,0
    
    

    Remember, this example is for a token ring adapter.

An example of a PROTOCOL.INI file resulting from setting up NetBIOS emulation over IPX is shown in Figure 21.

At this point you can restart the workstation.

Figure 20. Statements added to CONFIG.SYS for NetWare Requester for OS/2 and LAPS


REM --- NetWare Requester statements BEGIN ---

SET NWLANGUAGE=ENGLISH

DEVICE=C:\NETWARE\LSL.SYS

RUN=C:\NETWARE\DDAEMON.EXE

REM -- Following statement added by LAPS

DEVICE=C:\IBMCOM\PROTOCOL\ODI2NDI.OS2



REM -- ODI-Driver Files BEGIN --

REM DEVICE=C:\NETWARE\TOKEN.SYS

DEVICE=C:\NETWARE\ROUTE.SYS

REM -- ODI-Driver Files END --



DEVICE=C:\NETWARE\IPX.SYS

rem DEVICE=C:\NETWARE\SPX.SYS

rem RUN=C:\NETWARE\SPDAEMON.EXE

rem DEVICE=C:\NETWARE\NMPIPE.SYS

rem DEVICE=C:\NETWARE\NPSERVER.SYS

rem RUN=C:\NETWARE\NPDAEMON.EXE

DEVICE=C:\NETWARE\NWREQ.SYS

IFS=C:\NETWARE\NWIFS.IFS

RUN=C:\NETWARE\NWDAEMON.EXE

DEVICE=C:\NETWARE\NETBIOS.SYS

RUN=C:\NETWARE\NBDAEMON.EXE

rem DEVICE=C:\NETWARE\VIPX.SYS

rem DEVICE=C:\NETWARE\VSHELL.SYS PRIVATE

REM --- NetWare Requester statements END ---


Figure 21. Example of PROTOCOL.INI after setting up NetBIOS emulation


[PROT_MAN]



   DRIVERNAME = PROTMAN$



[IBMLXCFG]



   NETBEUI_nif = NETBEUI.NIF

   ODI2NDI_nif = ODI2NDI.NIF

   IBMTOK_nif = IBMTOK.nif



[NETBEUI_nif]



   DriverName = netbeui$

   Bindings = IBMTOK_nif

   ETHERAND_TYPE = "I"

   USEADDRREV = "YES"

   OS2TRACEMASK = 0x0

   SESSIONS = 210

   NCBS = 250

   NAMES = 40

   SELECTORS = 5

   USEMAXDATAGRAM = "NO"

   ADAPTRATE = 1000

   WINDOWERRORS = 0

   MAXDATARCV = 4168

   TI = 30600

   T1 = 500

   T2 = 200

   MAXIN = 1

   MAXOUT = 1

   NETBIOSTIMEOUT = 500

   NETBIOSRETRIES = 8

   NAMECACHE = 0

   PIGGYBACKACKS = 1

   DATAGRAMPACKETS = 2

   PACKETS = 350

   LOOPPACKETS = 1

   PIPELINE = 5

   MAXTRANSMITS = 6

   MINTRANSMITS = 2

   DLCRETRIES = 5

   NETFLAGS = 0x0



[NETBIOS]

  DriverName = NetBios$

  Bindings = IBMTOK_nif

  ADAPTER0 = IPXNB$,0



[ODI2NDI_nif]

   DriverName = odi2ndi$

   Bindings = IBMTOK_nif

   NETADDRESS = "10005a6ecddb"

   TOKEN-RING = "yes"

   TOKEN-RING_SNAP = "no"

   ETHERNET_802.3 = "no"

   ETHERNET_802.2 = "no"

   ETHERNET_II = "no"

   ETHERNET_SNAP = "no"

   TRACE = 0x0



[IBMTOK_nif]



   DriverName = IBMTOK$

   ADAPTER = "PRIMARY"

   MAXTRANSMITS = 6

   RECVBUFS = 2

   RECVBUFSIZE = 256

   XMITBUFS = 1


Setting up CICS Client for Windows

  1. Install the NetWare DOS Requester code, ensuring that you select Windows support.

  2. Install and configure NetWare NetBIOS emulation:

    1. The file NETBIOS.EXE (the NetBIOS emulator program) should have been copied to your hard disk during installation of the NetWare client code. If not, locate the file on the NetWare disks and copy it.

    2. In the file C:\NWCLIENT\STARTNET.BAT (see Figure 22), add the line:
      
      NETBIOS
      
      

      immediately before the line:
      
      CD \
      
      

    3. Restart the workstation to confirm that NetBIOS support will correctly load at startup.

Figure 22. Example of a STARTNET.BAT file for DOS and Windows clients


@ECHO OFF

c:

CD \NWCLIENT

SET NWLANGUAGE=ENGLISH

LSL

TOKEN.COM

IPXODI

VLM

NETBIOS   *** This line added manually ***

CD\



[Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index] [Help]


[ IBM home page | (C) | (TM) ]
© IBM Corporation 1994, 1997. All Rights Reserved
 
Privacy Legal Contact