Beruflich Dokumente
Kultur Dokumente
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
iv
Chapter 2
Chapter 3
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 .........................................................................
Appendix A Appendix B
Worksheets
OS/390 Network Map Example......................................................... A-4
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.
Getting Started Guide Preparing for Installation and Worksheets Release Notes Important Notes Getting Started Guide Installing CONNECT:Direct for Windows NT
viii
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
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
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
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
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
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
italic
Chapter 1
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
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
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
1-3
Hardware Requirements
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
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.
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
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
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.
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
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.
1-7
1-8
Chapter 2
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.
2-2
q q
1.
q q
Accept default installation directory - X:\Program Files\CDReq32 Change installation directory New installation directory: ___________________________________________
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
2-3
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.
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.
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.
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:
q q
Note:
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
2-7
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.
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.
4.
Select the CONNECT:Direct node that you want to set for automatic startup.
2-9
5.
6. 7.
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
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
5.
Click OK.
4. 5.
2-12
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.
2-14
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 Configuration Tool
CD Database Wizard
2-15
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
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
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
2-17
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.
2-18
6.
Chapter 3
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
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.
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.
3-3
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.
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.
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.
3-4
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.
SQLUserID
SQLPassword
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
SNA_Components
yes | no
MailComponents
yes | no
ConfigNetmap
yes | no
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.
3-5
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.
LU_Name
NetID
ModeName
NotificationType
NT Broadcast | Exchange
ExchangeProfile
NetMapPath
Fully-qualified pathname
UserAuthPath
Fully-qualified pathname
KeepCurrentConfig
yes | no
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.
3-6
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 (|).
3-7
4.
Click OK.
3-8
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
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: ____________________
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: ____________________
Appendix A / Worksheets
A-3
[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)
= = =
= = =
A-4
Refer to the platform-specific CONNECT:Direct Installation and Administration guides for network map information on other host platforms.
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
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
B-3
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
B-5
B-6
B-7
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
B-10
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
\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
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.
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.
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.
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
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.