CDNTGETSTARTED

PN 00194
Getting Started with CONNECT:Direct for Windows NT
Version 3.3
Getting Started with CONNECT:Direct for Windows NT Version 3.3 First Edition This document was prepared to assist licensed users of the Sterling Commerce, Inc., CONNECT:Direct for Windows NT system; its contents may not be used for any other purpose without prior written permission. The material contained herein is supplied without representation or warranty of any kind and is based on typical use. Any unusual use may produce unpredictable results. Sterling Commerce, therefore, assumes no responsibility and shall have no liability of any kind arising from the supply or use of this document or the material contained herein. References in this manual to Sterling Commerce products, programs, or services do not imply that Sterling Commerce intends to make these available in all countries in which Sterling Commerce operates. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 52.227-19. 1995, 1999 Sterling Commerce, Inc. All rights reserved, including the right to reproduce this document or any portion thereof in any form. Printed in the United States of America. CONNECT:Direct is a trademark of Sterling Commerce, Inc. All other brand or product names are trademarks or registered trademarks of their respective companies.
CDNTGS906
Contents
Preface
Using CONNECT:Direct for Windows NT Documentation .................... CONNECT:Direct for Windows NT Documentation............................... Using This Guide ...................................................................................... vii ix x
Chapter 1
Preparing for Installation

Product Hardware and Software Requirements ........................................ Compatibility Requirements for CONNECT:Direct at Remote Nodes.................................................................................... Configure Windows NT User Privileges .................................................. Configure Connectivity for Your System ................................................. TCP/IP Connectivity.......................................................................... SNA Connectivity (Optional) ............................................................ Install and Configure Microsoft SQL Server (Optional) .......................... Automated CONNECT:Direct for Windows NT Installation................... Prepare the CONNECT:Direct Installation Worksheet ............................ 1-2 1-3 1-4 1-4 1-4 1-5 1-6 1-6 1-7
iv
Chapter 2
Installing CONNECT:Direct for Windows NT

Step 1 - Gathering Installation Information ............................................. Step 2 - Starting the Installation Setup..................................................... Step 3 - Installing CONNECT:Direct for Windows NT .......................... Step 4 - Install Online Product Documentation........................................ Step 5 - Testing the Server Installation Setup .......................................... Starting the CONNECT:Direct Server.............................................. Automating Server Startup ........................................................ Verifying CONNECT:Direct Server Startup .................................... Connecting to the CONNECT:Direct Server from the Requester .... Starting CONNECT:Direct Requester for Windows ................. Inserting a CONNECT:Direct Requester for Windows Node Connection Definition................................................................ Attaching to the CONNECT:Direct for Windows NT Server ... Submitting the Sample Process ......................................................... Verifying the Success of the Sample Process ................................... CONNECT:Direct for Windows NT Program Items ............................... Post-installation Procedures ..................................................................... Define CONNECT:Direct Users....................................................... Local Users ................................................................................ Remote Users ............................................................................. Define Remote Node Information..................................................... Uninstalling CONNECT:Direct for Windows NT................................... Uninstalling CONNECT:Direct Requester for Windows ................. Uninstalling CONNECT:Direct Server for Windows NT ................ 2-1 2-6 2-6 2-7 2-7 2-7 2-8 2-9 2-10 2-10 2-10 2-11 2-12 2-13 2-14 2-15 2-15 2-16 2-16 2-17 2-17 2-18 2-18
Chapter 3
Automating CONNECT:Direct for Windows NT Installations

Preparing for Silent Installation ............................................................... Customizing CONNECT:Direct for Windows NT Initialization Information........................................................................................ CD_SRVR.INI File Contents..................................................... CD_REQ.INI File Contents ....................................................... 3-1 3-2 3-2 3-6
Contents
Customizing CONNECT:Direct for Windows NT Configuration Information ........................................................................................ Preparing for Rollout ......................................................................... Running a Silent Installation..................................................................... Support for SMS Silent Installations ........................................................ Package Definition File ..................................................................... Management Information File ........................................................... Unattended Uninstall .........................................................................
3-6 3-7 3-7 3-7 3-8 3-8 3-8
Appendix A Appendix B
Worksheets
OS/390 Network Map Example......................................................... A-4
VTAM 4.1 Example Definitions

Sample SNA Configuration ...................................................................... B-1
VTAM 4.1 Example Definitions............................................................... B-2 XCA Token Ring: Switched Net Definitions .................................... B-3 XCA Token Ring: Independent LU Definition ................................. B-4 XCA Token Ring: Major Node Definition ........................................ B-5 Sample CONNECT:Direct APPLDEF .............................................. B-6 Sample CONNECT:Direct MODEENTS (Mode Definitions).......... B-7 Sample VTAM Start Options (ATCSTRxx) ..................................... B-9 Sample CONNECT:Direct OS/390 Netmap Entries ......................... B-10 Accessing SNA Server Configuration Listing .......................................... B-10 Accessing Communications Server Configuration Listing....................... B-14
Glossary Index
vi
Preface
The CONNECT:Direct for Windows NT documentation library provides users with the information necessary to get started with the CONNECT:Direct product. This chapter provides a roadmap that guides CONNECT:Direct users in accessing information in the documentation library to perform CONNECT:Direct for Windows NT tasks. It also provides an overview of the manuals that comprise the library and information about using this Guide.
Using CONNECT:Direct for Windows NT Documentation

Refer to the following table for CONNECT:Direct for Windows NT tasks and where to find the information to perform those tasks. Note: For general, as well as platform-specific information about the CONNECT:Direct product, refer to the CONNECT:Direct Technical Overview.
Task Installing CONNECT:Direct for Windows NT Preparing to install CONNECT:Direct Reference Getting Started with CONNECT:Direct for Windows NT
Getting Started Guide Preparing for Installation and Worksheets Release Notes Important Notes Getting Started Guide Installing CONNECT:Direct for Windows NT
Installing the product
viii
Task Verifying the installation
Reference Getting Started Guide Installing CONNECT:Direct for Windows NT Getting Started Guide Installing CONNECT:Direct for Windows NT Getting Started Guide CONNECT:Direct for Windows NT Automated Installations
Uninstalling the product
Automating product installation
Setting up CONNECT:Direct for Windows NT operations Changing CONNECT:Direct for Windows NT settings Adding, changing, or deleting a CONNECT:Direct user Adding, changing, or deleting a remote CONNECT:Direct node definition Setting up Process notification Using user exits
CONNECT:Direct for Windows NT System Guide
System Guide Changing CONNECT:Direct for Windows NT Settings System Guide Defining and Managing CONNECT:Direct Users and Worksheets System Guide Defining and Managing the CONNECT:Direct Network and Worksheets
System Guide Configuring Process Notification System Guide Customizing CONNECT:Direct Operations
Using CONNECT:Direct for Windows NT
CONNECT:Direct for Windows NT System Guide CONNECT:Direct Requester for Windows Users Guide CONNECT:Direct Process Guide System Guide Interfacing with the CONNECT:Direct for Windows NT Server and Using the Admin Tool Utility System Guide Using the Command Line Interface Requester Users Guide Understanding the Fundamentals Requester Users Guide Performing Basic Tasks Requester Users Guide Performing Basic Tasks
Starting and stopping the server
Using server interfaces
Sending and receiving files Running batch jobs, programs, and system commands Using Processes
Requester Users Guide Performing Basic Tasks and Performing Advanced Tasks System Guide Using the Command Line Interface CONNECT:Direct Process Guide
Preface
ix
Task Managing CONNECT:Direct Processes
Reference System Guide Managing CONNECT:Direct Processes Requester Users Guide Monitoring Submitted Processes System Guide Reviewing CONNECT:Direct Statistics Requester Users Guide Examining Process Statistics System Guide Accessing CONNECT:Direct Messages and Troubleshooting
Accessing CONNECT:Direct statistics Troubleshooting
CONNECT:Direct for Windows NT Documentation

The following manuals make up the CONNECT:Direct for Windows NT documentation library: v CONNECT:Direct Technical Overview is an introduction to the CONNECT:Direct product family and its information transfer applications. v CONNECT:Direct for Windows NT Release Notes includes product updates and compatibilities. v Getting Started with CONNECT:Direct for Windows NT is a guide to getting started with the CONNECT:Direct for Windows NT product. This book includes preinstallation and installation information and tasks. v CONNECT:Direct for Windows NT System Guide is a guide to setting up and using the CONNECT:Direct for Windows NT product. This book also describes administrative concepts for CONNECT:Direct for Windows NT and stand-alone utilities that use Windows NT. v CONNECT:Direct Requester for Windows Release Notes includes product system and hardware requirements, as well as product updates. v CONNECT:Direct Requester for Windows Users Guide describes how to use the Windows-based graphical user interface. v CONNECT:Direct Process Guide provides you with the platform-specific information you need to write CONNECT:Direct Processes and provides examples of typical Processes for each platform. v CONNECT:Direct Compatibility and Connectivity Chart provides compatibility requirements between all supported platforms of the CONNECT:Direct product.
Using This Guide

The Getting Started with CONNECT:Direct for Windows NT uses certain notational conventions to denote special circumstances. The following table describes the conventions used in this guide.
This bold Represents Bold letters represent screen names, key names, and commands and values that you must type as stated. Italic letters are placeholders for information you must provide. For example, a reference to filename would require that you type the actual name of a file instead of the word shown in italic type. Italic letters are also used to show emphasis and to denote titles of publications. underlined letters | (vertical bar) Underlining indicates default values for fields. For example, Yes | No means that if a value is not specified, No is used. Vertical bars indicate that you can supply one of a series of values separated by the vertical bars. For example, Yes | No means either Yes or No is valid, but not both.
italic
Chapter 1
Preparing for Installation
Before you install CONNECT:Direct for Windows NT, you must first ensure that all of the system hardware and software (including third-party software, such as your SNA communications software or Microsoft SQL Server) are configured and operational. Pre-installation tasks include the following:
v v v v
Ensure that the system meets product hardware and software requirements Define users for Windows NT Configure and test TCP/IP or SNA (optional) connectivity Install and configure SQL Server for database support (optional)
Read Chapter 2, Installing CONNECT:Direct for Windows NT before you begin the installation.
1-2
Product Hardware and Software Requirements

Software Requirements (Minimum) CONNECT:Direct for Windows NT X CONNECT:Direct Requester for Windows X
Microsoft Windows NT Version 4.0 operating system with Service Pack 4 Microsoft Windows 95 operating system with Service Pack 1 Microsoft TCP/IP WinSOCK interface installed as part of the Windows NT system
Software Requirements (Optional)
CONNECT:Direct for Windows NT
CONNECT:Direct Requester for Windows
For SNA Connectivity (one of the following): Microsoft SNA Server Version 3.0 or 4.0 (for Alpha machines, you must have Version 3.0 with Service Pack 3 or Version 4.0 with Service Pack 2) Microsoft SNA Client Version 3.0 or 4.0 IBM Communications Server for Windows NT Version 6.01 (The SNA API client is not supported when installed on a stand-alone machine. The server and client components must be installed on the same machine.) X
For Automated (Silent) Installations using SMS: Microsoft Systems Management Server (SMS) Version 1.2 or 2.0 For CONNECT:Direct Process Notification using Microsoft Exchange: Microsoft Exchange Client Version 4.0 or 5.0 For SQL Server Database: SQL Server ODBC driver installed on the same system where you run CONNECT:Direct for Windows NT Local-domain access to SQL Server Version 6.5 or 7.0
Chapter 1 / Preparing for Installation
1-3
Hardware Requirements
CONNECT:Direct for Windows NT X X X X
CONNECT:Direct Requester for Windows X X X X
Intel or Alpha-based Windows NT system A minimum of 64 MB of memory CD-ROM drive supported by Windows NT A token ring or ethernet interface card for TCP/IP connectivity A total minimum of 29 MB of disk space for the following types of files: System (6 MB) Program (15 MB) Temporary (8 MB)
A total minimum of 16 MB of disk space for the following types of files: System (8 MB) Program (7 MB) Temporary (1 MB) X
Approximately 4 MB of RAM is required per session to other CONNECT:Direct servers
Microsoft SMS is not required for performing automated installations. Refer to the Preparing for Silent Installation section beginning on page 3-1 for more information about performing automated installations of CONNECT:Direct for Windows NT and CONNECT:Direct Requester for Windows. Refer to the Configuring Process Notification chapter of the CONNECT:Direct for Windows NT System Guide for more information about CONNECT:Direct for Windows NT Process notification.
Compatibility Requirements for CONNECT:Direct at Remote Nodes

Refer to the CONNECT:Direct Compatibility and Connectivity Chart for the required release level of the CONNECT:Direct product running on the remote nodes. The CONNECT:Direct Compatibility and Connectivity Chart is included in the CONNECT:Direct product documentation or you can download the latest from the CONNECT Support website at
http://commerce.csg.stercomm.com. Refer to the CONNECT:Direct for Windows NT Release Notes for more information about accessing the CONNECT Support website.
1-4
Configure Windows NT User Privileges

You must install CONNECT:Direct for Windows NT with an administrator account. This account can be any valid administrator account or an administrator account created specifically for CONNECT:Direct. Refer to the Microsoft Windows NT system documentation for specific instructions for setting up an administrator account. The following three user privileges must be assigned to the administrator account configured for CONNECT:Direct before you install the CONNECT:Direct for Windows NT product. Note: Theses privileges are stored locally, even if the machine is a member of a domain. As a result, privileges cannot be set on the domain controller and granted to all machines on the domain.
v
Act as part of the operating system - allows CONNECT:Direct to perform as a secure and trusted part of the operating system in order to authenticate and impersonate CONNECT:Direct users for commands and Process execution. Log on as service - allows a Windows NT service to run in the context of the specified user instead of running in the context of the local system account. Replace a process level token - allows CONNECT:Direct to submit Processes on behalf of logged on users.
v v
Configure Connectivity for Your System

Before installing CONNECT:Direct for Windows NT, you must configure connectivity for your TCP/IP or SNA environment.
TCP/IP Connectivity
For TCP/IP connectivity with CONNECT:Direct for Windows NT, your Windows NT machine must be configured with a valid IP address, IP subnet, and IP gateway. If the communications partner is on another subnet or network and a firewall is between the communications partner and the Windows NT machine, verify that the Access Control Lists (ACLs) are correctly configured to allow access to and from the IP address and IP ports specified during the CONNECT:Direct for Windows NT installation. Contact your
1-5
Firewall/Security Administrator for more information on configuring the ACLs for your firewall.
SNA Connectivity (Optional)

If you plan to use SNA network communications connectivity with CONNECT:Direct for Windows NT, you must correctly install and configure the SNA software before installing CONNECT:Direct for Windows NT. In addition, you must have an active connection between the local and remote nodes. CONNECT:Direct for Windows NT requires the following information for the local and remote SNA networks to configure a peer- or host-based partner SNA connection as follows:
v v v v v v
Network Name Mode Name (local system only) Control Point Name Node ID Network Address (remote system only) LU Name and LU Alias Name (these names may be the same value; CONNECT:Direct uses the LU Alias Name)
Note: CONNECT:Direct for Windows NT supports only independent LU6.2. Refer to the SNA Server/Host Configuration Worksheet section beginning on page A-3 when mapping SNA connection parameters between CONNECT:Direct for Windows NT and a host system. Note: Consult the SNA product documentation or contact your SNA vendor for any questions about configuring the SNA communications software you will use with CONNECT:Direct for Windows NT. The CONNECT:Direct Workstation Online Connectivity tool is an SNA configuration tool available on the CONNECT Support website at http://commerce.csg.stercomm.com. This tool generates sample SNA configuration information to assist you in configuring your SNA software and configuring CONNECT:Direct for SNA connectivity. The CONNECT:Direct Workstation Online Connectivity tool only generates example independent LU6.2 Token Ring SNA configurations at this time. Refer to the CONNECT:Direct for Windows NT Release Notes for more information about accessing the CONNECT Support website.
1-6
Install and Configure Microsoft SQL Server (Optional)

During the CONNECT:Direct for Windows NT installation, you are prompted to choose a database type: Microsoft Access or SQL Server. CONNECT:Direct uses the database to log Process statistics information, internal messages, and the Process control queue. If you will use SQL Server as the CONNECT:Direct database, you must perform the following tasks before you install CONNECT:Direct for Windows NT. Refer to the Microsoft SQL Server online documentation for specific instructions for performing these tasks. 1. 2. Install Microsoft SQL Server on the local machine, or a network drive or remote machine that is accessible from the locally installed CONNECT:Direct node. If you installed Microsoft SQL Server Version 6.5 as the CONNECT:Direct database, grant user permissions to the database through the SQL Enterprise Manager. If you installed Version 7.0, this step is not required. Set SQL Server to start automatically in the Services option of the Control Panel.
3.
Note: If your CONNECT:Direct database is Microsoft SQL Server Version 6.5, refer to the CONNECT:Direct for Windows NT Release Notes for important information regarding automated maintenance of the database. If you will use Microsoft Access as the CONNECT:Direct database, there is no preinstallation configuration required.
Automated CONNECT:Direct for Windows NT Installation

CONNECT:Direct for Windows NT supports automated installation. You can automate CONNECT:Direct for Windows NT and CONNECT:Direct Requester for Windows installations using initialization (INI) files provided on the CONNECT:Direct for Windows NT product CD. You can implement automated installations by specifying a path to INI files from the command line of the Windows setup or from within Microsoft Systems Management Server (SMS) unattended jobs. See Chapter 3, Automating CONNECT:Direct for Windows NT Installations for information about automating installations. For automated installations using Microsoft SMS, refer to the Product Hardware and Software Requirements section beginning on page 1-2 for the specific version(s) supported.
1-7
Prepare the CONNECT:Direct Installation Worksheet

Gathering information before beginning the CONNECT:Direct installation will assist you during the installation process. Record the installation information on the CONNECT:Direct for Windows NT Installation Worksheet section beginning on page 2-2 of Chapter 2, Installing CONNECT:Direct for Windows NT. After you have completed the installation worksheet, use it as a guide to install the CONNECT:Direct for Windows NT product components.
1-8
Chapter 2
Installing CONNECT:Direct for Windows NT
You can install CONNECT:Direct for Windows NT server or CONNECT:Direct Requester for Windows, or both. The CONNECT:Direct for Windows NT server is the component of the product that actually performs the functions issued from the user interface. The CONNECT:Direct Requester for Windows component is a graphical user interface to the CONNECT:Direct server. Note: You can also issue commands to the CONNECT:Direct for Windows NT server from the Command Line Interface (CLI). The CONNECT:Direct for Windows NT CLI is installed as part of the CONNECT:Direct for Windows NT server installation. Refer to the Using the Command Line Interface chapter of the CONNECT:Direct for Windows NT System Guide for information about using the CLI.
Step 1 - Gathering Installation Information

The following installation worksheet provides information to help you make the decisions necessary for installing CONNECT:Direct for Windows NTthe Requester or server component, or both. Go through the worksheet and record the information for your installation before you install the product.
2-2
CONNECT:Direct for Windows NT Installation Worksheet

Complete this worksheet before you install CONNECT:Direct for Windows NT. You will be prompted for the information on this worksheet during the CONNECT:Direct for Windows NT installation.
Choose CONNECT:Direct Software to Install
You can install the Requester, the server, or both.
q q
CONNECT:Direct Requester for Windows CONNECT:Direct Server for Windows NT
Install CONNECT:Direct Requester for Windows
1.
Choose the installation directory.
X represents the drive letter mapped to your Windows directory.
q q
Accept default installation directory - X:\Program Files\CDReq32 Change installation directory New installation directory: ___________________________________________
2. Name the program folder.
q q
Accept default program folder name - CONNECT Direct Requester for Windows Change program folder name New program folder name: ___________________________________________
3. Complete the Requester installation. The CONNECT:Direct Requester for Windows completion dialog box is dependent upon the components that you installed. w w Requester only Requester and server
Chapter 2 / Installing CONNECT:Direct for Windows NT
2-3
Install CONNECT:Direct Server for Windows NT
1.
Name this CONNECT:Direct node - The default local node name is the name of the Windows NT machine. You can keep this name for the local node name or change it. Local node name: ___________________________________________ Note: To change the local node name after the product is installed, you must re-install the CONNECT:Direct Server for Windows NT component.
2. Choose the installation directory.
X represents the drive letter mapped to your Windows directory.
q q
Accept default installation directory - X:\Program Files\Cdnt Change installation directory New installation directory: ___________________________________________
Note:
If you are re-installing CONNECT:Direct for Windows NT, you can choose to keep the current configuration. If you choose to keep the current configuration, the current configuration (network map, initialization, and user authority information) will be retained.
3. Choose the installation setup type (Intel only). If you are installing on an Alpha machine, skip to step 4.
Express - The Express option installs CONNECT:Direct Server for Windows NT with the following characteristics. w w w w w No SNA support; TCP/IP only Maximum number of sessions - 2 CONNECT:Direct Database - Microsoft Access TCP/IP Information - Default TCP/IP address of the machine; port number for node-to-node communications is 1364, port number for user interface to node communications is 1363 Process notification - NT Broadcast If you choose the Express installation, skip to step 8 on page 2-5 after choosing this option.
Note:
Custom
2-4
Note:
If you are installing CONNECT:Direct for Windows NT Workstation, you are not prompted for the maximum number of concurrent sessions.
4. Set the maximum number of concurrent sessions that this CONNECT:Direct node can participate in. Maximum number of sessions: ________ Note: The default maximum number of sessions is 2. Change this value only if you have purchased additional sessions for this node.
5. Choose the CONNECT:Direct database software.
q q
Microsoft Access (Intel only) SQL Server with Standard Security (Intel and Alpha) If Standard security is implemented, you must create a valid userid and password for the CONNECT:Direct installer and a CREATE TABLE privilege within the CONNECT:Direct database. SQL Server Name: __________________________________ User ID: ___________________________ Password: _________________________
SQL Server with Integrated Security (Intel and Alpha) If Integrated security is implemented, ensure that the NT user group that the CONNECT:Direct installer belongs to has CREATE TABLE privilege within the CONNECT:Direct database. SQL Server Name: ___________________________________
Note:
If you want to change the CONNECT:Direct database after installation, refer to the Using the Admin Tools Utility chapter of the CONNECT:Direct for Windows NT System Guide for step-by-step instructions.
6. Enter TCP/IP communication information. The installation program detects the IP address of the local machine and uses it as the default TCP/IP address for node-to-node communications and for user interface-to-node communications. Node-to-Node Communications IP Address: _____________________________ Port: __________
2-5
User Interface-to-Node Communications IP Address: _____________________________ Port: __________ Note: If you want to change the CONNECT:Direct TCP/IP information after installation, refer to the Changing CONNECT:Direct for Windows NT Settings or the Using the Admin Tools Utility chapter of the CONNECT:Direct for Windows NT System Guide for step-by-step instructions.
7. Choose additional optional installation components.
APPC Connectivity - SNA Refer to the Configuring SNA Properties section beginning on page 9-13 of the CONNECT:Direct for Windows NT System Guide for information about configuring CONNECT:Direct to listen for multiple incoming LUs.
Note:
LU Name: __________________________________ Net ID: _____________________________________ Mode Name _________________________________
Configure Process Notification
q q
Note:
NT Broadcast Microsoft Exchange
Exchange Profile: __________________________________ If you want to change the CONNECT:Direct notification type after installation, refer to the Changing CONNECT:Direct for Windows NT Settings chapter of the CONNECT:Direct for Windows NT System Guide for step-by-step instructions.
q q
Load an Existing Network Map Fully-qualified pathname for the MAP.CFG: ________________________________ Load Existing User Authorities Fully-qualified pathname for the USER.CFG: _______________________________
8. Verify installation setup information. 9. Complete the setup by clicking Finish to restart your computer. You can choose not to restart your computer at this time, but you must restart it before starting this CONNECT:Direct node.
2-6
Step 2 - Starting the Installation Setup

v If the Autorun option is enabled on your Windows NT machine for the CD-ROM drive, insert the CONNECT:Direct for Windows NT CD-ROM into the drive. The CONNECT:Direct for Windows NT installation setup detects the type of Windows NT operating system installed on your machine and automatically initiates. v If the Autorun option is disabled on your Windows NT machine, you must perform the following steps: 1. 2. 3. 4. 5. 6. 7. Insert the CONNECT:Direct for Windows NT CD-ROM into the CD-ROM drive. Click the Start button, and then click Run. The Run dialog box displays. On the Run dialog box, click the Browse button. The Browse dialog box displays. On the Browse dialog box, select the drive mapped to your CD-ROM drive from the Look in: field drop-down box. Select the folder for the type of Windows NT operating system installed on your machine: Alpha or Intel. Double-click Setup. The program returns to the Run dialog box. Click OK.
The installation setup initiates.
Step 3 - Installing CONNECT:Direct for Windows NT

Refer to the worksheet beginning on page 2-2 as you install CONNECT:Direct for Windows NT. During the installation process, you are prompted for the information that you recorded on the worksheet. The information on the installation worksheet corresponds to the installation screens for the following tasks: v Choosing the CONNECT:Direct software component(s) to install (Requester, server, or both) - 1 screen v Installing CONNECT:Direct Requester for Windows - includes multiple screens for installing the Requester. v Installing CONNECT:Direct Server for Windows NT - includes multiple screens for providing server installation and configuration information. The configuration screens that you see during installation are dependent upon whether you are installing on an Intel or Alpha machine and the type of third-party software installed (for example, your SNA communications software or Microsoft SQL Server).
2-7
Step 4 - Install Online Product Documentation

CONNECT product documentation is provided on a CD in Portable Document Format (PDF). To access the product documentation PDF files, you must: 1. 2. Verify that you have Adobe Acrobat Reader installed on your system. If not, download it from the Adobe website at http://www.adobe.com. Install the product documentation according to the instructions provided in the CD insert card.
For information about using Adobe Acrobat Reader to open, view, navigate, and print your product documentation, refer to the Acrobat Reader online Help or visit the Adobe website at http://www.adobe.com.
Step 5 - Testing the Server Installation Setup

After the installation is complete, perform the following tasks to verify that the server has been installed correctly: v Start the CONNECT:Direct Server v Verify CONNECT:Direct Server Startup from the NT Event Log v Log on to CONNECT:Direct Requester for Windows v Attach to a CONNECT:Direct node from CONNECT:Direct Requester for Windows v Submit the sample Process v Verify success of the sample Process
Starting the CONNECT:Direct Server

Perform the following steps to start the CONNECT:Direct for Windows NT server using the CD Admin Tool Utility. 1. 2. 3. 4. Click the Start button, and then point to Programs. Click the CONNECT Direct - NodeName program. Click the CD Admin Tool option. The CD Admin Tool main window displays. On the CD Admin Tool main window, click the stopped name of the server you want to start.
2-8
5.
Select Start from the Server menu, or click the green traffic light icon. The server icon will change to yellow, followed by green for a successful start. If the server did not start, the light will be red. You can also right-click your mouse and select Start from the pop-up menu.
Automating Server Startup

Perform the following steps to set the CONNECT:Direct for Windows NT server to start automatically each time the system is started. 1. 2. 3. Click the Start button, and then point to Settings. Click Control Panel. Double-click the Services icon. The Service dialog box displays.
4.
Select the CONNECT:Direct node that you want to set for automatic startup.
2-9
5.
Click the Startup button. The following dialog box displays.
6. 7.
Select Automatic. Click OK.
Verifying CONNECT:Direct Server Startup

Before you connect to the CONNECT:Direct server, you can verify that it started successfully by viewing the Windows NT Event Viewer Application Log. Complete the following steps to access the application log and verify successful server startup: 1. 2. 3. 4. Click the Start button, and then point to Programs. Click the Administrative Tools program. Select Event Viewer. The Event Viewer main window displays. From the Event Viewer main window, click the Log menu option and select Application to set the Event Viewer to view the application log.
If the server is successfully started, the event number is 1 for the most recent CONNECT:Direct entry listed in the application log. If the server is stopped, the event number is 20 for the most recent CONNECT:Direct entry listed in the application log.
2-10
Connecting to the CONNECT:Direct Server from the Requester

Before you can attach to a CONNECT:Direct node from CONNECT:Direct Requester for Windows, you must first define information about that node. To start CONNECT:Direct Requester for Windows, insert a node connection definition, and attach to the node, perform the following steps:
Starting CONNECT:Direct Requester for Windows

To start CONNECT:Direct Requester for Windows, perform the following steps: 1. 2. 3. Click the Start button, and then point to Programs. Click the CONNECT Direct Requester for Windows program. Select CD Requester for Windows. The CONNECT:Direct Requester for Windows program launches.
Inserting a CONNECT:Direct Requester for Windows Node Connection Definition

To create a CONNECT:Direct Requester for Windows node connection definition, perform the following steps: 1. 2. 3. Click the Node menu option from the CONNECT:Direct Requester for Windows main window. Click Connection Settings. Click the Insert Node option. The Node Properties dialog box displays:
2-11
4.
Enter the node information. Refer to the following table for field definitions.
Field Name Name Field Definition Name of the connecting node Type of operating system for the connecting node Valid Values Valid node name 116 alphanumeric characters.
Operating System
Automatic, Netware, OS/2 Warp, UNIX, and Windows NT/95. The default is Automatic which means that the Requester automatically detects the operating system for the connecting node. A valid TCP/IP address formatted as nnn.nnn.nnn.nnn
TCP/IP Support Address
TCP/IP address of the connecting node
5.
Click OK.
Attaching to the CONNECT:Direct for Windows NT Server

To attach to the CONNECT:Direct for Windows NT Server from CONNECT:Direct Requester for Windows, perform the following steps: 1. 2. 3. In the left-hand portion of the CONNECT:Direct Requester for Windows main window, click the name of the node that you want to connect to. Click the Node menu option from the CONNECT:Direct Requester for Windows main window. Click Attach. The CONNECT:Direct Attach dialog box displays:
4. 5.
Enter a valid Windows NT userid and password. Click OK.
2-12
Submitting the Sample Process

A sample Process, SAMPLE.CDP, is created during the installation so you can test the product without having to configure other remote nodes. You can also become familiar with the functionality of the CONNECT:Direct Requester for Windows. The sample Process is a loop back Process that copies the README.TXT file from the local node to the remote node (the same node as the local node) and creates a file called VERIFY.TXT. To submit the sample Process and monitor its outcome, perform the following steps: 1. 2. 3. 4. 5. 6. Click the File menu option from the CONNECT:Direct Requester for Windows main window. Click Open. From the Browse window, go to the CONNECT:Direct for Windows NT installation destination directory. The default installation directory is x:\Program Files\Cdnt. Open the process directory. Select the Sample.cdp file. Click Open. The sample Process opens.
2-13
7. 8.
Click the Process menu option from the CONNECT:Direct Requester for Windows main window. Click Submit. The Submit Process dialog box displays.
9.
Click OK.
The sample Process submits.
Verifying the Success of the Sample Process

To verify the success of the sample Process, perform the following steps: 1. 2. 3. 4. Click the Start button, and then point to Programs. Click Windows NT Explorer. Go to the CONNECT:Direct for Windows NT installation destination directory. The default installation directory is x:\Program Files\Cdnt. Find the file named, VERIFY.TXT. If it exists, the sample Process submitted successfully.
2-14
CONNECT:Direct for Windows NT Program Items

The CONNECT:Direct Server for Windows NT installation generates the following program items.
The following table describes the function of each item in the CONNECT:Direct program.
Program Item CD Admin Tool Description Used to start, stop, or administer any CONNECT:Direct server node installed on the same system where the Admin Tool utility is installed. Used to change the CONNECT:Direct Process notification method. Used to update connection settings in the Windows NT Registry for the client that will connect to the local CONNECT:Direct server. A simple text mode, command line interface to CONNECT:Direct for Windows NT. Used to edit, create, and validate configuration files for use with CONNECT:Direct for Windows NT. Used to change or configure the CONNECT:Direct databases (Microsoft Access or SQL Server).
CD Change Notification Utility
CD Client Connection Utility
CD Command Line Interface
CD Configuration Tool
CD Database Wizard
2-15
Program Item CD Message Import Utility
Description Used to import messages into the message database for recovery. Used to lookup CONNECT:Direct messages by message ID to access the short and long text explanations for an error message. A text file that contains supplemental information to the product manuals. Uninstalls CONNECT:Direct for Windows NT servers.
CD Message Lookup
Read Me
Uninstall CD Server
Post-installation Procedures
After you have installed and tested CONNECT:Direct for Windows NT, perform the following post-installation procedures to set up your CONNECT:Direct operations: v Define local and remote CONNECT:Direct users v Define remote node information in the Network Map
Define CONNECT:Direct Users

After you install the CONNECT:Direct for Windows NT server, you must grant authorizations for your local and remote users. Note: The installer of CONNECT:Direct for Windows NT needs to grant user authorizations in Windows NT for anyone who will use CONNECT:Direct for Windows NT. For more information about configuring user privileges in Windows NT, refer to Chapter 1, Preparing for Installation of this guide.
2-16
Local Users
The following information will aid you in granting authorization for local users:
Subject Defining and Managing CONNECT:Direct Users Reference CONNECT:Direct for Windows NT System Guide Description Defining, modifying, and deleting CONNECT:Direct local users (general and administrative privileges) using the CONNECT:Direct Requester for Windows Tool for defining user authorizations
User Functional Authorization worksheet
Remote Users
The following information will aid you in granting authorization for remote users:
Subject Defining and Managing CONNECT:Direct Users Reference CONNECT:Direct for Windows NT System Guide Description Defining, modifying, and deleting remote users using the CONNECT:Direct Requester for Windows Tool for defining user proxies and authorities for each remote user
User Proxy worksheet
2-17
Define Remote Node Information

After you install your CONNECT:Direct for Windows NT server, you must define Network Map entries for the remote CONNECT:Direct nodes that the local CONNECT:Direct node will communicate with. The following information will aid you in defining Network Map entries:
Subject Defining and Managing the CONNECT:Direct Network Reference CONNECT:Direct for Windows NT System Guide Description Defining, modifying, and deleting remote node information in the CONNECT:Direct for Windows NT Network Map using the CONNECT:Direct Requester for Windows Defining communication mode, communication path, and remote node information in the Network Map Network Map requirements of the remote CONNECT:Direct nodes with which you communicate
Network Map worksheets
Platform-specific CONNECT:Direct Admin Guides
See Table of Contents of the appropriate Guide
Note: Verify that the CONNECT:Direct administrators of the remote nodes have updated their Network Maps with the information required to identify your local node.
Uninstalling CONNECT:Direct for Windows NT

This section provides instructions for uninstalling the CONNECT:Direct for Windows NT components: CONNECT:Direct Requester for Windows and CONNECT:Direct Server for Windows NT. The Uninstall program completely removes the application, its components, Program folder, Program items, and all server and Registry settings.
2-18
Uninstalling CONNECT:Direct Requester for Windows

To uninstall the CONNECT:Direct Requester for Windows program, perform the following steps: 1. 2. 3. 4. 5. Click the Start button, and then point to Programs. Click the CONNECT Direct Requester for Windows program. Select Uninstall. The Confirm File Deletion dialog box displays. Click Yes to initiate the uninstall process. Before the uninstall starts deleting shared program files, the Remove Shared File? confirmation dialog box displays. Because the shared files may be used for another program, click No to All. After all of the CONNECT:Direct Requester for Windows program files, folders, directories, items, and registry entries are removed, click OK to complete the uninstallation process.
6.
Uninstalling CONNECT:Direct Server for Windows NT

To uninstall the CONNECT:Direct Server for Windows NT program and all of the server utilities, perform the following steps: 1. 2. 3. 4. 5. 6. Click the Start button and then point to Programs. Click the CONNECT Direct - NodeName program. Select the Uninstall CD Server program item. The CONNECT:Direct Uninstall dialog box displays. Select the Server Node you want to uninstall and click Uninstall. You are prompted to verify that you want to uninstall CONNECT:Direct for Windows NT. Click Yes to continue the uninstall process. After all of the CONNECT:Direct for Windows NT server program files, folders, directories, items, and registry are removed from your system, click OK to complete the uninstallation process.
Chapter 3
Automating CONNECT:Direct for Windows NT Installations
You can automate the installation and configuration of CONNECT:Direct for Windows NT for mass rollout across your enterprise by performing silent installations of the product. Silent installations require no user responses during the installation routine. Instead, configuration information is supplied by pre-defined initialization and configuration files that are accessed as part of the silent installation. You can perform silent installations of CONNECT:Direct for Windows NT by specifying a path to CONNECT:Direct Server and Requester initialization (INI) files in one of the following ways: v From the command line of the Windows setup utility (non-SMS) v From within Microsoft Systems Management Server (SMS) unattended jobs
Preparing for Silent Installation

The initialization (INI) file is the foundation of a silent installation because it contains the answers that would be provided by a user during a normal interactive installation. The INI files provided with CONNECT:Direct for Windows NT contain parameter values you can change to specify site-specific answers you want to supply to the installation routine. With SMS, the INI values are used for each SMS Package distributed to an SMS client. The administrator is responsible for ensuring that each package contains site-specific INI files.
3-2
In addition to providing site-specific initialization information during a silent installation, you can provide site-specific configuration information for the CONNECT:Direct Network Map and user authorizations. Refer to Customizing CONNECT:Direct for Windows NT Configuration Information section beginning on page 3-6 of this chapter for more information about using customized configuration files during silent installations.
Customizing CONNECT:Direct for Windows NT Initialization Information

The CONNECT:Direct for Windows NT server initialization file (CD_SRVR.INI) is located in the server installation directory specified during installation. The Requester initialization file (CD_REQ.INI) is located in the requester directory specified during installation. These INI files are also on the product CD in their respective directories. Update the parameter values in the INI files as follows: 1. 2. Open the INI file using any text editor, such as Windows Notepad. Specify site-specific values for the parameter variables. When updating the files, refer to the INI file content descriptions following these steps for information on the initialization parameter variables and syntax. 3. Save the file.
CD_SRVR.INI File Contents

The CD_SRVR.INI file contains the following variables. Underlined values are defaults.
Parameter Name LocalNodeName Parameter Definition specifies the local node name. If specified, the name must be 116 characters long consisting of numbers, letters, @, #, $, -, underscore (_), and a period (.) with no spaces or apostrophes (). Valid Values If this field is left blank, the LocalNodeName defaults to the first eight characters of the computer name of the machine where the server is being installed.
Refer to Customizing CONNECT:Direct for Windows NT Configuration Information section beginning on page 3-6 in this chapter for more information about how to use this parameter.
Chapter 3 / Automating CONNECT:Direct for Windows NT Installations
3-3
Parameter Name AdminUserID
Parameter Definition specifies the Windows NT Administrative userid to use for this installation. This is an optional parameter.
Valid Values A valid Windows NT administrator userid with rights defined for: 1) act as part of operating system, 2) log on as service, and 3) replace process level token. If no value is specified for this parameter, the installation will be performed using the System Account. A valid password for the specified Windows NT administrator userid. If no value is specified for this parameter and the AdminUserID parameter, the installation will be performed using the System Account.
AdminPassword
specifies the password associated with the Windows NT administrative userid to use for this installation. This parameter is only required if a value is specified for the AdminUserID parameter.
InstallDirectory
specifies the directory into which CONNECT:Direct for Windows NT will be installed. If the directory does not exist, it will be created, if possible. If it cannot be created, setup will exit with an error. specifies the type of installation for CONNECT:Direct for Windows NT: Express or Custom. Express is a limited installation and Custom provides more installation options. Refer to step 3 on page 2-3 of the CONNECT:Direct for Windows NT Installation Worksheet section beginning on page 2-2 of this guide for a description of the Express installation options. specifies the maximum total concurrent connections for this CONNECT:Direct for Windows NT server node.
X:\Program Files\CDNT | Any valid Windows directory
InstallType
Express | Custom
MaxSessInit
A numeric value from 2510. The default is 2. The workstation version of the product is limited to 2 sessions. Access | SQLServer
DatabaseType
specifies the type of database support to use. SQL Server is the only configuration option for Alpha installations.
3-4
Parameter Name SQLServerName
Parameter Definition specifies the name of a valid SQL Server. Note: This variable is required only if DatabaseType=SQLServer. specifies the SQL Server system administrators userid. Note: This variable is required only if DatabaseType=SQLServer and SQL Server standard security is in place. specifies the SQL Server system administrators password. Note: This variable is required only if DatabaseType=SQLServer and SQL Server standard security is in place. specifies the TCP/IP address of the destination machine. Any valid TCP/IP address may be specified.
Valid Values Valid SQL Server Name
SQLUserID
Valid SQL Server System Administrator Userid
SQLPassword
Valid SQL Server System Administrator Password
Server_Addr
Valid TCP/IP address. If blank, the IP address will be obtained by querying the destination machines IP address from the TCP/IP stack. Valid port number. The default is 1364.
HostPort
specifies the host port used to communicate with other CONNECT:Direct servers using TCP/IP. specifies the API port used to communicate with the CONNECT:Direct Requester for Windows, Command Line Interface, or any other application using the CONNECT:Direct Software Developers Kit (SDK). specifies whether to support SNA connectivity. specifies whether to support email notification of Process results when requested in Process definitions. specifies whether to include a customized Network Map configuration file for this installation of CONNECT:Direct.
Client_Port
Valid port number. The default is 1363.
SNA_Components
yes | no
MailComponents
yes | no
ConfigNetmap
yes | no
3-5
Parameter Name ConfigUser
Parameter Definition specifies whether to include a customized User Authorization configuration file for this installation of CONNECT:Direct. specifies the Local LU Name to be used during SNA communications. Note: This variable is required only if SNA_Components=yes. specifies the SNA network name to be used during SNA communications. Note: This variable is required only if SNA_Components=yes. specifies the SNA Mode name to be used during SNA communications. Note: This variable is required only if SNA_Components=yes. specifies the mail notification type you want to use. Note: This variable is required only if MailComponents=yes. This is the userid that will be the sender of notification. The recipient of the notification is specified in each Process definition. Note: This variable is required only if Mail Components=yes and NotificationType=Exchange. specifies the fully-qualified pathname to a customized Network Map configuration file to use for this installation of CONNECT:Direct. specifies the fully-qualified pathname to a customized User Authorization configuration file to use for this installation of CONNECT:Direct. specifies whether or not to keep the current configuration during a reinstall or upgrade.
Valid Values yes | no
LU_Name
Valid LU alias name
NetID
Valid SNA network name
ModeName
Valid SNA Mode name
NotificationType
NT Broadcast | Exchange
ExchangeProfile
Valid Microsoft Exchange Profile
NetMapPath
Fully-qualified pathname
UserAuthPath
Fully-qualified pathname
KeepCurrentConfig
yes | no
3-6
CD_REQ.INI File Contents

The CD_REQ.INI file contains the following variables.
Parameter Name InstallDirectory Parameter Definition specifies the directory where CONNECT:Direct Requester for Windows will be installed. If the directory does not exist, it will be created if possible. If it cannot be created, setup will exit with an error. specifies the name of the Program Folder where CONNECT:Direct Requester for Windows will be installed. Valid Values
X:\Program Files\CDREQ32 | Any valid Windows directory
Program Folder
CONNECT Direct Requester for Windows | Any valid Windows program folder name
Program folder names can be from 1255 characters, including spaces. The following characters are not allowed: slash (/), backslash (\), colon (:), asterisk (*), question mark (?), quotations ("), less than (<), greater than (>), and vertical bar (|).
Customizing CONNECT:Direct for Windows NT Configuration Information

After you have installed CONNECT:Direct for Windows NT on a master node, you can customize configuration information for mass rollout within your enterprise by using the CONNECT:Direct Requester for Windows to configure the NetMap and user authorizations on the master node. You can then extract those files using the Configuration Utility. Refer to the Using the Configuration Utility chapter of the CONNECT:Direct for Windows NT System Guide for more information about using the Configuration Utility. To apply the customized configuration files during a silent installation, you must set parameter values in the CD_SRVR.INI file: v To apply a customized Network Map file w w ConfigNetmap=yes NetMapPath=the fully-qualified pathname to a customized Network Map configuration file ConfigUser=yes UserAuthPath=the fully-qualified pathname to a customized User Authorization configuration file
v To apply a customized user authorization file w w
3-7
Preparing for Rollout

For silent installations from the command line (non-SMS), provide the CONNECT:Direct for Windows NT executables and the customized initialization and configuration files (if applicable), to sites within your enterprise. Users will then run the silent installation as described in the following section.
Running a Silent Installation

Perform the following steps to run a silent installation from the command line: 1. 2. 3. Click the Start button. Click Run. The Run dialog box displays. In the Open field of the Run dialog box, type the drive and pathname of the CONNECT:Direct for Windows NT executables, followed by the -inipath command, the drive and pathname of both of the customized initialization files (cd_srvr.ini and cd_req.ini), and the -s command as shown in the following example.
g:\intel\setup -inipath=X:\pathname -s
4.
Click OK.
The silent installation initiates.
Support for SMS Silent Installations

You can use Microsoft Systems Management Server (SMS) to silently install (and uninstall) CONNECT:Direct for Windows NT and CONNECT:Direct Requester for Windows on nodes within your enterprise. The following SMS features are supported: v Package Definition File (PDF) v Management Information File (MIF) Note: This section assumes knowledge of Microsoft SMS.
3-8
Package Definition File

CONNECT:Direct for Windows NT provides three Package Definition Files (PDFs) for use with SMS. The following three PDF files represent the master installation (installs both the server and the requester), and the stand-alone server and requester installations. v CDMASTER.PDF v CDNT.PDF v CDREQ32.PDF These PDF files contain the product components (in ASCII text format) necessary to invoke the CONNECT:Direct for Windows NT and CONNECT:Direct Requester for Windows setup and uninstall programs. To install CONNECT:Direct for Windows NT and CONNECT:Direct Requester for Windows, SMS extracts the contents of the PDF onto the remote destination system and executes the installation component. You must modify the PDF files to provide the correct pathname for the INI files. Note: The PDFs distributed on the CONNECT:Direct for Windows NT CD-ROM also contain definitions for creating SMS attended installations. If you have specific installation sites that cannot be configured for SMS unattended jobs, you can create SMS attended jobs that can be distributed to SMS clients who can then customize the CONNECT:Direct for Windows NT installation.
Management Information File

CONNECT:Direct for Windows NT uses the Management Information File (MIF) default form to report success or failure of a particular SMS job.
Unattended Uninstall
CONNECT:Direct for Windows NT also provides for an unattended uninstall by supplying SMS with the -s parameter, which is used with the CDUNINST.EXE program. Note: CONNECT:Direct for Windows NT does not use UninstallShield due to problems handling Registry keys. The CDUNINST.EXE program will not attempt to delete any SQL Server data, tables, or databases. Your Database Administrator should perform any cleanup after uninstalling CONNECT:Direct for Windows NT. UninstallShield can be invoked successfully by SMS to uninstall the CONNECT:Direct Requester for Windows product.
Appendix A
Worksheets
Use the worksheets in this appendix to gather and record information needed for the following tasks for SNA connectivity: v SNA software configuration v SNA Server/Host configuration
A-2
SNA Configuration Worksheet

You will be prompted for the values on this worksheet when you configure the SNA software that you will use with CONNECT:Direct. Refer to Chapter 1, Preparing for Installation on page 1-1 for supported SNA software. You may want to make copies of this worksheet for each SNA configuration you require. See Appendix B, VTAM 4.1 Example Definitions for SNA Server configuration examples.
Local Node SNA Information
CONNECT:Direct Node Name: ________________________________________________ LU Alias Name: ___________________________________________________________ The LU Alias name is a user-defined name that points to the LU name defined in the local SNA network. This value can be the same as the actual LU name. You can get the following information from your local SNA administrator. LU Name: _________________________ Mode Name: _______________________ Node ID: __________________________ Network Name: ____________________
Control Point Name: _________________
Remote Node SNA Information
CONNECT:Direct Node Name: ________________________________________________ LU Alias Name: ___________________________________________________________ The LU Alias name is a user-defined name that points to the LU name defined in the remote SNA network. This value can be the same as the actual LU name. You can get the following information from the SNA administrator of the remote system. LU Name: _________________________ Control Point Name:__________________ Network Address: ___________________ Network Name: ____________________
Node ID: __________________________
Appendix A / Worksheets
A-3
SNA Server/Host Configuration Worksheet

The information on this worksheet is required to setup and configure an SNA connection between the host and the SNA server on Windows NT. It will also assist Sterling Commerce Support in troubleshooting SNA problem issues. In the following table, record the parameter value mapped between SNA and VTAM for each parameter listed. The first column contains an alpha identifier for each parameter. These identifiers are used in the examples following the table to show how the parameter values are implemented in the network map.
Windows NT/SNA [a] [b] Local CONNECT:Direct Node Name Remote CONNECT:Direct Node Name Mode Session Limits Max RU Server Netname Server CPNAME Connection CPNAME Connection Netname Connection LOCALBLOCKNO Connection LOCALNODENO Connection REMOTENETADDR Local LU Name (APPCLU) Parameter Value = = = = Host/VTAM LOCAL.NODE ADJACENT.NODE
[c] [d] [e] [f] [g] [h] [i] [j] [k] [l] [m]
= = = = = = = = = = =
= = = = = = = = = = =
LOGMODE VTAM APPLID DSESSLIM LOGMODE RU Size VTAMNETID (owner of PU) VTAM PU Name VTAM SSCPNNAME VTAM NETID (owner of PU) VTAM PU DBLK VTAM PU IDNUM Remote Network Address VTAM LU Name (must be independent) VTAM NETID (owner of PU) VTAM APPLID VTAM NETID (owner of APPLID)
[n] [o] [p]
APPCLU Netname Remote Partner LU (APPCRLU) APPRCLU Netname
= = =
= = =
A-4
OS/390 Network Map Example

The following example illustrates the use of the VTAM parameters (identified by alpha character) in the OS/390 network map. LOCALNODE= (node name[b], communications name[o],, superuser password) TCQ=(tcxdsn, tcqdsn)) ADJACENT.NODE=( (node name[a], communications name[m],, LU62) PARSESS=(max[d], default) ENVIRONMENT=NT LOGMODE=logmode entry name[c])
Refer to the platform-specific CONNECT:Direct Installation and Administration guides for network map information on other host platforms.
Windows NT Network Map Example

The following example illustrates the use of the SNA parameters (identified by alpha character) in the Windows NT network map. CREATE_SNA_MODE Name(mode [c]) MAXRUsize (MaxRU [e]) MaxPacingSize(7) MaxNetSessLimit(8) CREATE_SNA_COMMPATH Name(commpathname) Transport(transport-type) Adapter(0) Address(000000000000) NetId(netid[f]) PUName() LUName(LUName [m]) ProfileName() LULocAddr(0) Mode(mode[c]) LUSessLimit(8) CREATE_REMOTENODE Name(remotenodename [b]) LRetry(10) LRetryTime(180) Sretry(10) SretryTime(10) SessPnodeMax(32) SessSnodeMax(32) DefaultClass(1) RemoteOSEnv(OS/390) NetName(NetName[f]) PartnerName(PartnerName[o]) TPName(NNV2DTF) Mode(mode[c]) CommPath(commpathname)
Appendix B
This chapter covers the following topics: v Sample SNA Configuration v VTAM 4.1 Example Definitions w XCA Token Ring: Switched Net Definition XCA Token Ring: Independent LU Definition XCA Token Ring: Major Node Definition Sample CONNECT:Direct APPLDEF Sample CONNECT:Direct MODEENTS (Mode Definitions) Sample VTAM Start Options (ATCSTRXX) Sample CONNECT:Direct for OS/390 Netmap Entries
v Accessing SNA Configuration Listings
Sample SNA Configuration

This section provides an example of how to configure your SNA software for connections to CONNECT:Direct for MVS or OS/390.
B-2
You will be prompted for the following SNA Resource Definitions during the Microsoft SNA configuration. These values are derived from VTAM definitions supporting connections between CONNECT:Direct for MVS or OS/390 and CONNECT:Direct for Windows NT. Contact your VTAM administrator for the values you need to specify during SNA configuration.
Windows NT Remote LU Name Local LU Name Network Name Mode Name Remote Control Point Name Local Control Point Name Local CONNECT:Direct Node Name Remote CONNECT:Direct Node Name Local Node ID Remote Network Address Parameter Value = M1CDXY2B = M1R01LUA = CSDNET = NDM624K = CSDSA01 = M1RPU01 = SS.DUB.USER1 OS/390 =APPLID =LU NAME =NETID =MODEENT =SSCPNAME =PU NAME =ADJACENT.NODE
= CDNT0001
=LOCAL.NODE
= 0716200D = 4000 7000 6200
=XID =MAC Address

The following section contains definitions for use in configuring your SNA software. The relevant resource name entries are in bold.
Appendix B / VTAM 4.1 Example Definitions
B-3
XCA Token Ring: Switched Net Definitions

The following values represent the Switched Net PU definitions for an XCA attached NT SNA server.
*************************************************** * * *XCA TR DEFINITION * * * * * *CHANGE LOG * * * *************************************************** M1R01PU VBUILD TYPE=SWNET, MAXGRP=1, MAXIMUM NUMBER OF UNIQUE GRPNM MAXNO=1 MAXIMUM NUMBER OF UNIQUE DIALNO * *** M1RPU01 PU ADDR=01, PUTYPE=2, ISTATUS=ACTIVE, DBLK=071, IDNUM=6200D, PASSLIM=8, DLOGMOD=NDM624K, MODETAB=DALLMTAB, SSCPFM=USSSCS, USSTAB=LSUSSTAB, PACING=7, VPACING=7, DISCNT=(NO), MAXDATA=521, MAXPATH=2, MAXOUT=8 * M1RPTH0D PATH GRPNM=M1XG516D, DIALNO=0011111111111D DUMMY *M1ROLUA LU LOCADDR=0, DLOGMODE=NDM6241C *3270 * M1R01LU2 LU M1R01LU3 LU * *LU 6.2 ILU *
X X
X X X X X X X X X X X X X X X
LOCADDR=2,DLOGMOD=D4A3290 LOCADDR=3,DLOGMOD=D4A3290
B-4
XCA Token Ring: Independent LU Definition

The following values represent the Independent LU definitions coded as Cross Domain Resources.
***************************************************************** * VTAM 3.4 CDRSC DEFINITIONS FOR INDEPENDENT LUS * * 6.2 ILU DEFINITION - XCA TR ACCESS * * * *CHANGE LOG: * * * ***************************************************************** M1R01CDS VBUILD TYPE=CDRSC * M1R01LUA CDRSC ISTATUS=ACTIVE, X ALSLIST=M1RPU01, ADJ LINK STATION X MODETAB=DALLMTAB, LOGON MODE TABLE X DLOGMOD=NDM624K, LOGON MODE TABLE ENTRY X RESSCB=5 SESSION CONTROL BLOCKS * M1R01LUB CDRSC ISTATUS=ACTIVE, X ALSLIST=M1RPU01, ADJ LINK STATION X MODETAB=DALLMTAB, LOGON MODE TABLE X DLOGMOD=NDM624K, LOGON MODE TABLE ENTRY X RESSCB=5 SESSION CONTROL BLOCKS * M1R01LUC CDRSC ISTATUS=ACTIVE, X ALSLIST=M1RPU01, ADJ LINK STATION X MODETAB=DALLMTAB, LOGON MODE TABLE X DLOGMOD=NDM622K, LOGON MODE TABLE ENTRY X RESSCB=5 SESSION CONTROL BLOCKS * M1R01LUD CDRSC ISTATUS=ACTIVE, X ALSLIST=M1RPU01, ADJ LINK STATION X MODETAB=DALLMTAB, LOGON MODE TABLE X DLOGMOD=NDM621K, LOGON MODE TABLE ENTRY X RESSCB=5 SESSION CONTROL BLOCKS *
B-5
XCA Token Ring: Major Node Definition

The following values represent the Major Node Definitions for an XCA device.
***************************************************************** * * * XCA MAJOR NODE * * * * CHANGE LOG: * ***************************************************************** M1XCA516 VBUILD TYPE=XCA XCA MAJOR NODE * M1XP5161 PORT MEDIUM=RING, TOKEN-RING X SAPADDR=4, SERVICE ACCESS POINT ADDRESS X ADAPNO=0, ADAPTER NUMBER X CUADDR=516 CHANNEL UNIT ADDRESS * M1XG516D GROUP DIAL=YES, SWITCHED PERIPHERAL NODE X CALL=IN, DIAL IN AS PER MCDATA X ISTATUS=ACTIVE ACTIVATED AT GEN * M1XL516D LINE ANSWER=ON PU CAN DIAL IN * M1X516PD PU * ***
B-6
Sample CONNECT:Direct APPLDEF

The following values represent the Application Definitions for CONNECT:Direct for OS/390.
ZZAPPGLP VBUILD TYPE=APPL ***************************************************************** * C:D OS/390 TEST LU6.2 ILU APPL DEFINITION * * ***************************************************************** * M1CDXY2B APPL ACBNAME=M1CDXY2B, VTAM APPLID X APPC=YES, LU 6.2 CAPABLE X AUTH=(ACQ,VPACE), VTAM AUTHORITY FOR THIS APP X AUTOSES=10, # OF AUTO CONT WINNER ACTIVATES X DDRAINL=ALLOW, DRAIN ALLOWED FOR CNOS 0 X DLOGMOD=NDMLM1K, DEFAULT MODE TABLE ENTRY X DMINWNL=10, MIN CONT WINNER FOR LOCAL LU X DMINWNR=10, MIN CONT WINNER FOR REMOTE LU X DRESPL=ALLOW, APPL WILL DO SESSION DEACTIVATES X DSESLIM=20, MAX # OF ALLOWED SESS FOR MODE X EAS=509, APPROX # OF CONCURRENT SESSIONS X MODETAB=DALLMTAB, MODE TABLE NAME X VPACING=7 DEFAULT RECEIVE PACING VALUE *
B-7
Sample CONNECT:Direct MODEENTS (Mode Definitions)

The following values represent the Mode Definition Entries for an Independent LU.
***************************************************************** * * * LU6.2 WITH 4K RUS * * * ***************************************************************** NDM624K MODEENT LOGMODE=NDM624K, * TYPE=1, * COS=NDMCOS1, * FMPROF=X13, * TSPROF=X07, * PRIPROT=XB0, * SECPROT=XB0, * PSNDPAC=X04, * SRCVPAC=X04, * SSNDPAC=X04, * COMPROT=XD0B1, * RUSIZES=X8989, * PSERVIC=X060200000000000000000300 * * 0 1 2 3 4 5 6 7 8 9 1011 ***************************************************************** * * * LU6.2 WITH 2K RUS * * * ***************************************************************** NDM622K MODEENT LOGMODE=NDM622K, * TYPE=1, * COS=NDMCOS1, * FMPROF=X13, * TSPROF=X07, * PRIPROT=XB0, * PSNDPAC=X04, * SRCVPAC=X04, * SSNDPAC=X04, * SECPROT=XB0, * COMPROT=XD0B1, * RUSIZES=X8888, * PSERVIC=X060200000000000000000300 * * 0 1 2 3 4 5 6 7 8 9 1011
Continued
B-8
***************************************************************** * * * LU6.2 WITH 1K RUS * * * ***************************************************************** NDM621K MODEENT LOGMODE=NDM621K, * TYPE=1, * COS=NDMCOS1, * FMPROF=X13, * TSPROF=X07, * PRIPROT=XB0, * PSNDPAC=X04, * SRCVPAC=X04, * SSNDPAC=X04, * SECPROT=XB0, * COMPROT=XD0B1, * RUSIZES=X8787, * PSERVIC=X060200000000000000000300 * * 0 1 2 3 4 5 6 7 8 9 1011
B-9
Sample VTAM Start Options (ATCSTRxx)

The following values represent the VTAM Start Option entries for NETID and SSCPNAME.
***************************************************************** * * * OS/390 VTAM START DEFINITION * * ***************************************************************** HOSTSA=01, X NODETYPE=NN, X CONNTYPE=LEN, X CPCP=YES, X GWSSCP=YES, X NETID=CSDNET, X SSCPID=15015, X SSCPNAME=CSDSA01, X LISTBKUP=DEFAULTS, X TNSTAT,NOCNSL,TIME=60, X PPOLOG=YES, X XNETALS=YES, X NCPBUFSZ=2048, X HOTIOTRM=50, X IOPURGE=5M, X MSGLEVEL=V4R1, X MAINTLVL=9311, X IOBUF=(750,320,50,,30,100,3000), X CRPLBUF=(500,,0,,25,1), X LFBUF=(300,,0,,32,1), X LPBUF=(80,,0,,12,1), X SFBUF=(40,,0,,34,1), X SPBUF=(32,,0,,32,1), X BSBUF=(600,,0,,25,50), X XDBUF=(55,,0,,5,1)
B-10
Sample CONNECT:Direct OS/390 Netmap Entries

The following values represent the CONNECT:Direct for OS/390 NETMAP entries for Windows NT SNA software running CONNECT:Direct for Windows NT.
***************************************************************** * * * CONNECT:DIRECT NETWORK MAP * * * ***************************************************************** * * ***************************************************************** * LOCAL NODE * ***************************************************************** LOCAL.NODE = ((SS.DUB.USER1 M1CDXX2B,, SUPERUSR) TCQ= (USER1.R210.TCX USER1.R210.TCQ) ) * ADJACENT.NODE = (PARSESS = (10 2) (CDNT0001, M1R01LUA, LU62) ENVIRONMENT=NT LOGMODE=NDM624K )
Accessing SNA Server Configuration Listing

Use the following Windows NT SNA Server command to list the configuration and redirect the information to a file:
snacfg /print>filename
The following values represent the Microsoft SNA Server configuration listing for a configured Windows NT Server using the values listed in the VTAM Sample Definitions.
B-11
MODE #INTER /ADD /SESSIONLIM:8 /CONWIN:4 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:Yes /PACESENDCNT:7 /PACERECVCNT:7 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"Interactive" MODE #INTERSC /ADD /SESSIONLIM:8 /CONWIN:4 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:Yes /PACESENDCNT:7 /PACERECVCNT:7 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"Interactive" MODE #BATCH /ADD /SESSIONLIM:8 /CONWIN:4 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:No /PACESENDCNT:3 /PACERECVCNT:3 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"Batch"
\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
Continued
B-12
MODE #BATCHSC /ADD /SESSIONLIM:8 /CONWIN:4 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:No /PACESENDCNT:3 /PACERECVCNT:3 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"Batch" MODE BLANK /ADD /SESSIONLIM:8 /CONWIN:4 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:No /PACESENDCNT:3 /PACERECVCNT:3 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"8 Blank chars" MODE QPCSUPP /ADD /SESSIONLIM:64 /CONWIN:32 /CONLOSE:0 /AUTOACT:0 /AUTOPARTNER:Yes /HIGHPRIORITY:Yes /PACESENDCNT:7 /PACERECVCNT:7 /MAXSENDRU:1024 /MAXRECVRU:1024 /MAXSENDRU:1024 /MAXSENDRU:1024 /COMMENT:"5250 Mode"
\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
Continued
B-13
MODE NDM624K /ADD /SESSIONLIM:20 /CONWIN:10 /CONLOSE:10 /AUTOACT:0 /AUTOPARTNER:No /HIGHPRIORITY:No /PACESENDCNT:7 /PACERECVCNT:7 /MAXSENDRU:4096 /MAXRECVRU:4096 /MAXSENDRU:4096 /MAXSENDRU:4096 /COMMENT:" " SERVER CSD-PUBS /ADD /CPNAME:M1RPU01 /NETNAME:CSDNET /COMMENT:"" LINK SNADLC1 /ADD /SERVER:CSD-PUBS /LINKTYPE:Token CONNECTION TOKEN1 /ADD /SERVER:CSD-PUBS /COMMENT:"802.2 Connection" /ACTIVATION:OnServerStartup /CALLDIRECTION:Both /LOCALBLOCKNO:071 /LOCALNODENO:6200D /CPNAME:CSDSA01 /NETNAME:CSDNET /REMOTEBLOCKNO: /REMOTENODENO: /LINKSERVICE:SNADLC1 /REMOTEEND:Host /CONNTYPE:802.2 /XIDTYPE:Format3 /REMOTENETADDR:400070006200 /REMOTESAPADDR:4 /MAXBTULEN:1929 /RECEIVEACKTHRESH:2 /NAKSENDLIMIT:8 /RETRYLIMIT:10 /XIDRETRIES:3 /T1TIMEOUT:Default /T2TIMEOUT:Default /TITIMEOUT:Default /ACTIVATEDELAY:Default /ACTIVATERETRYLIMIT:None
\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
Continued
B-14
APPCRLU M1CDXY2B /ADD /CONNECTION:TOKEN1 /NETNAME:CSDNET /LUNAME:M1CDXY2B /COMMENT:"" /UNINTERPNAME:M1CDXY2B /AUTOPARTNER:No /PARALLELSESS:Yes APPCLLU M1R01LUA /ADD /SERVER:CSD-NTSNA1 /LUNUMBER:0 /NETNAME:CSDNET /LUNAME:M1R01LUA /COMMENT:"" /AUTOPARTNER:No /DEFAULTPOOL:No /TPTIMEOUT:60 APPCLLU M1R01LUA /ADDPARTNER:M1CDXY2B,NDM624K,TOKEN1 APPCLLU M1R01LUB /ADD /SERVER:CSD-NTSNA1 /LUNUMBER:0 /NETNAME:CSDNET /LUNAME:M1R01LUB /COMMENT:"" /AUTOPARTNER:No /DEFAULTPOOL:No /TPTIMEOUT:60 APPCLLU M1R01LUB /ADDPARTNER:M1CDXX2B,NDM624K,TOKEN1 USER USER1 /ADD /DOMAIN:CSD-NTSNA1 /COMMENT:"" USER USER1 /INSERT:M1R01LU2 USER USER1 /INSERT:M1R01LU3 DIAGNOSTIC /AUDITLEVEL:10
\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
Accessing Communications Server Configuration Listing

The SNA configuration listing for IBM Communications Server are stored in a file with an extension of acg. The name for this file is defined by the user during Communications Server installation.
Glossary
A
Adjacent Node
An adjacent node is an entry in the Network Map that defines a CONNECT:Direct node with which the local CONNECT:Direct node can communicate. The adjacent node is also referred to as the remote node.
Advanced Program-To-Program Communication (APPC)

Advanced Program-To-Program Communication is the general facility characterizing the LU6.2 architecture and its various implementations in products.
C
Checkpoint Restart
The Checkpoint Restart feature eliminates the need to re-transmit an entire file in the event of a transmission failure. If a copy procedure is interrupted, CONNECT:Direct restarts that copy at the last checkpoint.
Glossary-2
Commands
CONNECT:Direct commands initiate and monitor activity within the CONNECT:Direct system.
Configuration Registry
A database of configuration information central to Windows NT operation. The Registry is the storage location for configuration settings for Windows NT applications. The Registry centralizes all NT settings and provides security and control over system, security, and user account settings.
L
Local Node
The local node is the CONNECT:Direct server.
Logical Unit (LU) 6.2

A type of logical unit that supports general communication between programs in a distributed processing environment. LU6.2 is characterized by (a) a peer relationship between session partners, (b) efficient utilization of a session for multiple transactions, (c) comprehensive end-to-end error processing, and (d) a generic application program interface (API) consisting of structured verbs that are mapped into a product implementation.
N
Network Map (Netmap)
The Network Map (netmap) identifies all valid CONNECT:Direct nodes in the network. One Network Map is associated with each CONNECT:Direct local node. The netmap has one entry for each of the other CONNECT:Direct nodes to which the local CONNECT:Direct node communicates. The netmap entries also contain the rules or protocol that the nodes use when communicating.
Glossary-3
Node
A node is any site in a network from which information distribution can be initiated.
P
Primary Node (Pnode)
The primary node, or Pnode, is the CONNECT:Direct node on which the Process is submitted. The primary node can be the local or the remote node. The primary node may be referred to as the controlling node or initiating node, but should not necessarily be interpreted as the sending node. The primary node can be the receiver. Every Process has one primary node and one secondary node.
Process
A Process is a series of statements that initiate CONNECT:Direct activity, such as copying files and running jobs.
Process Statements
Process Statements are instructions for transferring files, running operating system jobs, executing programs, or submitting other CONNECT:Direct Processes. They are used to build a CONNECT:Direct Process.
R
Registry
See Configuration Registry.
Remote Node
A remote node is an entry in the Network Map that defines a CONNECT:Direct node with which the local CONNECT:Direct node can communicate. The remote node is also referred to as the adjacent node.
Glossary-4
Retry Interval
The retry interval is the interval at which retries are performed as a part of the checkpoint-restart feature.
S
Secondary Node (Snode)
The secondary node, or Snode, is the CONNECT:Direct node that interacts with the primary node during Process execution. Secondary nodes may also be referred to as the participating (non-controlling) or partner node. Every Process has one primary node and one secondary node.
Statistics File
The statistics file holds CONNECT:Direct statistics records that document the history of a Process.
Statistics Facility
The CONNECT:Direct Statistics Facility records CONNECT:Direct activities.
Systems Network Architecture (SNA)

The description of the logical structure, formats, protocols, and operational sequences for transmitting information units through, and controlling the configuration and operation of networks.
T
Transmission Control Queue (TCQ)
The Transmission Control Queue (TCQ) holds information about CONNECT:Direct Processes that are currently executing or scheduled to execute in the future.
Index
A
AdminPassword variable CD_SRVR.INI file 3-3 AdminUserID variable CD_SRVR.INI file 3-3
C
CD_REQ.INI configuring 3-6 CD_REQ.INI file variables InstallDirectory 3-6 ProgramFolder 3-6 CD_SRVR.INI configuring 3-2
InstallDirectory 3-3 LocalNodeName 3-2 LU_Name 3-5 MailComponents 3-4 ModeName 3-5 NetID 3-5 NotificationType 3-5 Server_Addr 3-4 SNA_Components 3-4 SQLPassword 3-4 SQLServerName 3-4 SQLUserID 3-4 client_port variable CD_SRVR.INI file configuration user privileges 1-4 configuring the CD_REQ.INI answer file 3-6 3-4
CD_SRVR.INI file variables AdminPassword 3-3 AdminUserID 3-3 Client_Port 3-4 DatabaseType 3-3 ExchangeProfile 3-5 HostPort 3-4
configuring the CD_SRVR.INI answer file 3-2 configuring user privileges 1-4
D
DatabaseType variable CD_SRVR.INI file 3-3
Index-2
E
ExchangeProfile variable CD_SRVR.INI file 3-5
N
NetID variable CD_SRVR.INI file 3-5 NotificationType variable CD_SRVR.INI file 3-5 3-4
H
HostPort variable CD_SRVR.INI file
P
package definition file Systems Management Server PDF Systems Management Server ProgramFolder variable CD_REQ.INI file 3-6 3-8 3-8
I
installation worksheets 1-7 InstallDirectory variable CD_REQ.INI file 3-6 CD_SRVR.INI file 3-3
L
LocalNodeName variable CD_SRVR.INI file 3-2 LU_Name variable CD_SRVR.INI file 3-5
S
server uninstalling 2-18 3-4 Server_Addr variable CD_SRVR.INI file SMS compliance 1-6
M
MailComponents variable CD_SRVR.INI file 3-4 management information file Systems Management Server MIF Systems Management Server ModeName variable CD_SRVR.INI file 3-5 3-8 3-8
SNA_Components variable CD_SRVR.INI file 3-4 SQLPassword variable CD_SRVR.INI file 3-4
SQLServerName variable CD_SRVR.INI file 3-4 SQLUserID variable CD_SRVR.INI file Step Verify installation setup information. Systems Management Server compliance 1-6 2-5 3-4
Index-3
management information file 3-8 package definition files 3-8 unattended uninstall 3-8
U
unattended uninstall Systems Management Server uninstalling the CONNECT Direct for Windows NT server user privileges configuring for Windows NT 3-8 2-18 1-4
V
variables AdminPassword CD_SRVR.INI file 3-3 AdminUserID CD_SRVR.INI file 3-3 Client_Port CD_SRVR.INI 3-4 DatabaseType CD_SRVR.INI file 3-3 ExchangeProfile CD_SRVR.INI file 3-5 HostPort CD_SRVR.INI file 3-4 InstallDirectory CD_REQ.INI file 3-6 CD_SRVR.INI file 3-3 LocalNodeName CD_SRVR.INI file 3-2 LU_Name CD_SRVR.INI file 3-5 MailComponents CD_SRVR.INI file 3-4 ModeName CD_SRVR.INI file 3-5
NetID CD_SRVR.INI file 3-5 NotificationType CD_SRVR.INI file 3-5 ProgramFolder CD_REQ.INI file 3-6 Server_Addr CD_SRVR.INI file 3-4 SNA_Components CD_SRVR.INI file 3-4 SQLPassword CD_SRVR.INI file 3-4 SQLServername CD_SRVR.INI file 3-4 SQLUserID CD_SRVR.INI file 3-4
W
Windows NT user privileges configuration worksheets installation 1-7 1-4
Index-4
Product Enhancement Request Form

Company Name: _____________________________________________________________ Address: ____________________________________________________________________ City: _____________________________________ State: __________ Zip: _____________ Requester: ___________________________________ Telephone: ____________________ Product: q CONNECT:Direct for Windows NT q _______________________________________________________________________ Current Product Release Level:____________ Describe enhancement: ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ How will enhancement be used? ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ Over
Would you install a new release of this CONNECT product to get the enhancement? q Yes q No Enhancement priority: q Need ASAP q Have immediate plan to use when available q Good idea; nice to have Additional comments: ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ ___________________________________________________________________________ Mail or fax this completed form to: Sterling Commerce Communications Software Group Attention: Product Marketing 5215 North OConnor Boulevard, Suite 1500 Irving, Texas 75039-3771 Fax: (972) 868-5142 Thank you for your interest in the Sterling Commerce CONNECT Product Family.

CDNTGETSTARTED

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CDNTGETSTARTED

Uploaded by

Copyright:

Available Formats

PN 00194

Getting Started with CONNECT:Direct for Windows NT

Preparing for Installation

Getting Started with CONNECT:Direct for Windows NT

Installing CONNECT:Direct for Windows NT

Automating CONNECT:Direct for Windows NT Installations

3-6 3-7 3-7 3-7 3-8 3-8 3-8

VTAM 4.1 Example Definitions

Getting Started with CONNECT:Direct for Windows NT

Using CONNECT:Direct for Windows NT Documentation

Installing the product

Getting Started with CONNECT:Direct for Windows NT

Task Verifying the installation

Uninstalling the product

Automating product installation

CONNECT:Direct for Windows NT System Guide

Using CONNECT:Direct for Windows NT

Starting and stopping the server

Using server interfaces

Task Managing CONNECT:Direct Processes

Accessing CONNECT:Direct statistics Troubleshooting

CONNECT:Direct for Windows NT Documentation

Getting Started with CONNECT:Direct for Windows NT

Using This Guide

Preparing for Installation

Getting Started with CONNECT:Direct for Windows NT

Product Hardware and Software Requirements

Software Requirements (Optional)

CONNECT:Direct for Windows NT

CONNECT:Direct Requester for Windows

Chapter 1 / Preparing for Installation

CONNECT:Direct for Windows NT X X X X

CONNECT:Direct Requester for Windows X X X X

Approximately 4 MB of RAM is required per session to other CONNECT:Direct servers

Compatibility Requirements for CONNECT:Direct at Remote Nodes

Getting Started with CONNECT:Direct for Windows NT

Configure Windows NT User Privileges

Configure Connectivity for Your System

Chapter 1 / Preparing for Installation

SNA Connectivity (Optional)

Getting Started with CONNECT:Direct for Windows NT

Install and Configure Microsoft SQL Server (Optional)

Automated CONNECT:Direct for Windows NT Installation

Chapter 1 / Preparing for Installation

Prepare the CONNECT:Direct Installation Worksheet

Getting Started with CONNECT:Direct for Windows NT

Installing CONNECT:Direct for Windows NT

Step 1 - Gathering Installation Information

Getting Started with CONNECT:Direct for Windows NT

CONNECT:Direct for Windows NT Installation Worksheet

Choose CONNECT:Direct Software to Install

You can install the Requester, the server, or both.

CONNECT:Direct Requester for Windows CONNECT:Direct Server for Windows NT

Install CONNECT:Direct Requester for Windows

Choose the installation directory.

X represents the drive letter mapped to your Windows directory.

2. Name the program folder.

Chapter 2 / Installing CONNECT:Direct for Windows NT

Install CONNECT:Direct Server for Windows NT

2. Choose the installation directory.

X represents the drive letter mapped to your Windows directory.

Getting Started with CONNECT:Direct for Windows NT

5. Choose the CONNECT:Direct database software.

LU Name: ________________ Net ID: _ Mode Name _______________