Home

	Expand Search

DirectConnect for DB2/MVS Connectivity Guide

Chapter 2: Planning the Connection Configuration

Chapter 2

Before you install DirectCONNECT for DB2/MVS, you must configure both the MVS mainframe and the server so that they can communicate with each other. Before you start, you should know what to configure and complete a configuration checklist. This chapter provides these details in the following sections:

• Configuration Task Summary
• Configuration Checklist

The instructions in this guide describe the configuration of the MVS mainframe and the LAN server. In addition, this guide describes how to test the connection between the MVS mainframe and the LAN server to ensure that they are communicating. These tasks must be completed before you install DirectCONNECT for DB2/MVS.

Configuration Task Summary

The following table shows the tasks you perform to plan, configure, and test the connection between the MVS mainframe and the server.

Table 2-1: Configuration process

Task	For TCP/IP Environment Information	For LU6.2 Environment Information
Review the planning tasks and complete the configuration checklist.	This chapter	This chapter
Complete the LU6.2 configuration worksheet.	Not applicable	Appendix A, "LU6.2 Configuration Worksheets"
Configure the MVS mainframe to communicate with the server.	Chapter 3, "Configuring the MVS Mainframe for a TCP/IP Environment"	Chapter 4, "Configuring the MVS Mainframe for an LU6.2 Environment"
Configure the server to communicate with the MVS mainframe.	Not applicable	Chapter 5, "Configuring HP SNAplus"
Not applicable	Chapter 6, "Configuring SNA Server/6000"
Not applicable	Chapter 7, "Configuring SNA Server for Windows NT"
Test the connection between the MVS mainframe and the server.	Chapter 8, "Testing Connectivity in a TCP/IP Environment"	Chapter 9, "Testing Connectivity in an LU6.2 Environment"

Configuration Checklist

Before you configure the MVS mainframe or the server, you should complete the tasks on the configuration checklist, which are summarized in the following steps:

1. Hold a preliminary planning session.

2. Check the system requirements.

Details about each item in the configuration checklist are described in the following sections.

Holding a Preliminary Planning Session

The primary purpose of conducting a preliminary planning session is to have the following team members meet:

• VTAM/NCP system programmer
• CICS system programmer
• Mainframe security administrator
• MVS mainframe system programmer
• LAN system administrator

All these persons are required because each person knows a key piece of information for the configuration parameters.

During this planning session, the team members should perform the activities listed in the following sections as appropriate for an LU6.2 or a TCP/IP environment.

Assigning LU6.2 Configuration Tasks

Use the following checklist to plan to configure an LU6.2 environment. If a step contains a team member in parentheses, this means that this team member should perform the step.

1. Determine type of connection you want to use, such as one of the following:
   • Token ring or Ethernet attachment through a local 3174 or 3172
   • Token ring or Ethernet attachment through front-end processor (FEP)
   • Remote SDLC connection
2. Determine the type of session to run:
   • Single session
   • Parallel sessions
3. Check the other MVS mainframe configuration properties in the tables in Chapter 3, including:
   • VTAM and NCP node definitions (VTAM/NCP system programmer)
   • CICS terminal definitions (CICS system programmer)
4. Fill out the appropriate LU6.2 configuration worksheet for your platform in Appendix A (all team members).

5. Check the server configuration values in the table in Chapter 3 (LAN system administrator).

6. Determine who performs the MVS mainframe configuration.

7. Determine who performs the server configuration.

8. Determine who runs the snaping connectivity test for the APPC/LU6.2 environment.

Assigning TCP/IP Configuration Tasks

Use the following checklist to plan for a TCP/IP environment.

1. Check the server configuration values in Chapter 4 (LAN system administrator).

2. Determine who performs the MVS mainframe configuration.

3. Determine who performs the server configuration.

4. Determine who runs the cicsping connectivity test for the TCTP/IP environment.

Checking the System Requirements

Verify that you have the platform and operating system components listed in this section before you configure the MVS mainframe and the server.

MVS Mainframe in an LU6.2 Environment

The MVS mainframe platform supports DirectCONNECT and provides APPC connectivity. The following are mainframe requirements for different system configurations.

• If you use Open ServerCONNECT or MainframeCONNECT in the LU6.2 environment, the following components are required:
  • An MS/SP version 3 (MVS/ESA) environment running on an IBM System/390 mainframe adequate to support CICS and the target database.
  • A CICS/VS system running on an IBM System/390 mainframe at version 2.1.2 or later, or CICS/ESA system running on an IBM System/390 mainframe at version 3 or later.
  • For DB2 access, a DB2 database running on an IBM System/390 mainframe at version 2 release 3 to version 3 release 1.
  • VTAM running on an IBM System/390 mainframe at version 3.2.

    Note: If you are using Advanced Peer-to-Peer Networking (APPN), you need VTAM, version 4 release 2 or later.

• One of the following versions of NCP:
  • NCP, version 4.5 for 3725 and parallel session support
  • NCP, version 5.2 for 3745 and parallel session support
• For DB2 access, DSNC (an IBM transaction that provides DB2 access for CICS transactions) must be running in the CICS region.
• For APPC connections, no additional host software is required.
• Up-to-date vendor products.

  Contact IBM for details on these releases and any required Authorized Program Analysis Reports (APARs) for APPC support.

• If you use a channel-attached 3174 model 11L (cluster controller) and want to use parallel sessions, the following special requirements apply:
  • VTAM, version 3 release 4
  • MVS/ESA
• Appropriate request for price quotations (RPQs) applied, contact IBM for details on this configuration.
• Microcode Level "C"
• APPN LIC Feature, contact IBM for appropriate details on this configuration.

  Note: If your channel-attached control unit is not an IBM product, but it is a Harris, McData, or other brand product, contact the appropriate vendor for any special requirements for the unit.

• If your site uses one of the following external security products, perform the recommended action:
  • IBM Resource Access Control Facility (RACF), make sure you have the appropriate updates to support APPC communications.
  • ACF2 or Top Secret security packages from Computer Associates, Sybase strongly suggests that you contact the vendor before proceeding with your LU6.2 installation to ensure that you have the release, user modifications, and fixes necessary to support APPC processing.
  • ACF2 release 5.2, you need to obtain and apply APAR UM87688 from Computer Associates.

    Note: This guide does not provide information about configuring these security products. Contact the vendor for the appropriate information and support.

See Also

• Call Sybase Technical Support as specified in "About This Book" to determine whether any new release levels or bug fixes of Sybase or vendor products are required
• DirectCONNECT for DB2/MVS Release Bulletin for the most current information

MVS Mainframe in a TCP/IP Environment

TheMVS mainframe platform supports DirectCONNECT and provides TCP/IP connectivity. The following are mainframe requirements for different system configurations.

• An MVS/SP version 3 (MVS/ESA) environment running on an IBM System/390 mainframe adequate to support CICS and the target databases.
• A CICS/VS system running on an IBM System/390 mainframe at version 2.1.2 or later, or CICS/ESA system running on an IBM System/390 mainframe at version 3 or later.
• For DB2 access, DB2 application running on an IBM System/390 mainframe at version 2 release 3 to version 3 release 1.
• Up-to-date vendor products, including the following:
  • TCP/IP for MVS (there are dependencies based on the version of Open ServerCONNECT)
  • TCP/IP Sockets Interface
  • TCP/IP Listener

  Contact IBM for details on these releases and any required APARs for TCP/IP support.

• The proper link libraries must be available.

See Also

• Call Sybase Technical Support as specified in "About This Book" to determine whether any new release levels or bug fixes of Sybase or vendor products are required
• DirectCONNECT for DB2/MVS Release Bulletin for the most current information

HP UX Server

DirectCONNECT for DB2/MVS is compatible with:

• OpenServerCONNECT release 3.1
• SQL Server release 10.0.2 and higher
• CICS 3.3 and higher, and PTF UN90057 for full functionality with the password expiration manager (PEM) feature

To use DirectCONNECT for DB2/MVS with HP, you must have, at a minimum, an HP 9000(8xx) workstation with the system configuration shown in the following table.

Table 2-2: System requirements for the HP-UX server

Item	Requirement
CPU	An HP 9000(8xx) system.
RAM	A minimum of 32 MB of RAM to run HP 9000(8xx) and any DirectCONNECT for DB2/MVS products.
Storage	A minimum of 24 MB, plus: 24 MB for the install tar file Space for the largest log file you expect to maintain Space for the largest trace file you expect to accommodate At least 500,000 bytes for each locale you plan to support
Software	The production release of HP 9000(8xx), HP-UX 10.01 or 10.10. HP-UX SNAplusLink for Series 800 and SNAplusAPI version 4.2 or 4.3.
Additional hardware	A 1/4-inch or an 8mm cartridge tape drive, or a CD-ROM drive.
Network support	An interface card compatible with HP 9000(8xx).

IBM RISC System/6000 Server

DirectCONNECT for DB2/MVS is compatible with the following:

• Open Server release 10.0.4
• OpenServerCONNECT release 3.1
• SQL Server release 10.0.2 and higher
• InfoHub release 2.3.0
• CICS 3.3 and higher, and PTF UN90057 for full functionality with the password expiration manager (PEM) feature
• To useDirectCONNECT for DB2/MVS with AIX, you must have, at a minimum, a RISC/6000 workstation with the system configuration shown in the following table.

  Table 2-3: System requirements for the AIX server

  Item	Requirement
  CPU	An IBM RISC System/6000.
  RAM	A minimum of 32 MB of RAM to run AIX and any DirectCONNECT for DB2/MVS products.
  Storage	A minimum of 24 MB, plus: Space for the largest log file you expect to maintain Space for the largest trace file you expect to accommodate At least 500,000 bytes for each locale you plan to support
  Software	The production release of AIX 4.1.x. SNA Communications Manager version 3, release 1.0 or later.
  Additional hardware	An 8mm cartridge tape drive.
  Network support	An interface card compatible with AIX. Sybase recommends a 32-bit card for best performance.

Windows NT Server

DirectCONNECT for DB2/MVS is compatible with:

• Open Server release 10.0.4
• OpenServerCONNECT release 3.1
• SQL Server release 10.0.2 and higher
• InfoHub release 2.3.0

To use DirectCONNECT for DB2/MVS with Windows NT, you must have, at a minimum, a Windows NT-compatible PC with the system configuration shown in the following table

Table 2-4: System requirements for Windows NT server

Item	Requirement
CPU	An 80486 or faster Intel-based processor. Sybase recommends a Pentium processor.
RAM	32 MB of RAM to run Windows NT and any DirectCONNECT for DB2/MVS products.
Storage	A minimum of 12 MB, plus: Space for the largest log file you expect to maintain Space for the largest trace file you expect to accommodate At least 500,000 bytes for each locale you plan to support
Software	The production release of Microsoft Windows NT 3.5.1 or Microsoft Windows NT Advanced Server. Sybase recommends Microsoft Windows NT Server for best performance. Microsoft SNA Server 2.11 for APPC.
Additional hardware	A 3.5 inch floppy drive or CD-ROM drive, depending on your installation media.
Network support	A Windows network interface card compatible with Windows NT. Sybase recommends a 32-bit card for best performance.