/*------------------------------------------------------------------*/ /* Created 06/04/93 - Dave Young */ /* Updated 08/19/93 - Dave Young - Added SDLC, VTAM/NCP defs, */ /* expanded Readme file instructions, */ /* and fast demo system setup instructions. */ /* Also Placed on MKTTOOLS */ /* */ /*------------------------------------------------------------------*/ The DCAFSAMP diskette contains sample configuration files for you to use in setting up two workstations: 1. DCAF Controlling 2. DCAF Gateway/Directory/Target (also has Controlling) *NOTE* The machine called GATEWAY on this diskette, and in this readme file, can also be a TARGET machine only. This same machine can also be a CONTROLLING/GATEWAY machine. Just read this file and it will tell you want to do. The intent of this diskette is to make it very simple for you to install Communications Manager (ES or CM/2) by providing these pre-configured systems. You can just point at these sample configuration files during the install and have a working system in a few minutes. The two sample systems are CONTROL and GATEWAY and the sample files are in the ES or CM2 directories on this diskette. During the ES or CM/2 install you can just point to these subdirectories and select the configuration file you want, it is that easy. Start now if you must, but I would suggest you read this file first. Additionally with CM/2 and LAPS there are CID command files and response files provided that can make the installation just feeding diskettes, or you can make some minor changes and make it unattended. If you are going to use SDLC connections, or have existing ES or CM/2 configurations, please see the appropriate sections below, there are special instructions for these setups. The sample files will allow for connection via: - LAN Token-Ring APPC - Async via 9600bps modems The Gateway/Directory machine can also: - Be a direct target for APPC or Async connections - Be a combined Controlling/Gateway/Directory station - Be a Netbios Target Sample configuration files are provided for: - Extended Services for OS/2 - NTS/2 LAPS - Communications Manager/2 Sample response files are provided for: - NTS/2 LAPS - Communications Manager/2 Note: The LAA for the CONTROL is 4000DCAFCCCC and for the GATEWAY it is 4000DCAF6666 (the 6 is as close to a G as I could get in Hex). You should change these after you get it working. You will have to change in the IBMCOM\PROTOCOL.INI file on both systems, and in the CONTROL.NDF file on the controlling (the link to the GATEWAY system has the Gateway's LAA in it). Also, the 3270 sessions have an IDNUM of 66666 and CCCCC that you will have to change, and a destination address of 400031728001 that you can change. The 3270 is not important or required for DCAF operation. Just handy to have. ------------------------------------------------------------------------- See the DCAF.ANS file for Answers to Common Questions (like error codes) ------------------------------------------------------------------------- Here is the procedure for installing with LAPS and CM/2, a response file install: 1. Insert the DCAFSAMP diskette and run A:INSTALL 2A. To install the CONTROL system: - C:\DCAFSAMP\CTLLAPS to install LAPS - C:\DCAFSAMP\CTLCM2 to install CM/2 2B. To install the GATEWAY system: - C:\DCAFSAMP\GWLAPS to install LAPS - C:\DCAFSAMP\GWCM2 to install CM/2 These procedures will use the A: drive for the source of the code. You can edit these .CMD files to change the source to a redirected drive if you are in that environment. You can also edit the response files to tailor for your installation (after you get it working once). An OPTIONAL way to install CM/2 would be to use CMSETUP without a response file, and point to the C:\DCAFSAMP\CM2 directory when prompted for the location of the configuration files. ------------------------------------------------------------------------- Here is the procedure for installing with Extended Services: 1. Insert the DCAFSAMP diskette and run A:INSTALL 2. Run ESINST 3. Choose Advanced Installation 4. Choose Install Communications Manager 5. Choose Configuration files/User Configuration Files 6. Enter a Path of C:\DCAFSAMP\ES for the configuration file location 7. Choose either GATEWAY or CONTROL sample configuration 8. Complete the installation ------------------------------------------------------------------------- Now on both machines install DCAF: 1. Insert DCAF Diskette 1 and enter A:INSTALL 2. On the Control: choose Control, Target and Packager components 3. On the Gateway: choose Control, Target, Directory and Gateway components NOTE: If you are running on a large LAN, it is wise to change the LAN Directory name. If you do, you have to change it for the Target component, Directory component AND Gateway component. All 3 of these have a separate place to personalize the directory name it is IMPERATIVE that you make all three of them match. Also be aware that these names are CASE SENSITIVE, so make them match. 4. Copy the sample link record file into your DCAF Directory: - C:\DCAFSAMP\CONTROL\EQNCOMM.REC for the Controlling - C:\DCAFSAMP\GATEWAY\EQNCOMM.REC for the Gateway 5. Run the parser EQNSFPAR to parse the link record file. That completes the install of all the components. You should be able to reboot and Test: - Start CM on both machines - Start the Netbios Target on the Gateway - Start the Controlling on the Control station - Select a Link record, Pick GATEWAY - You will probably get an error with 0003-00000004 return code, this just means try again. - You will connect on the second try. You can then select the target and test DCAF. - You can also test the other 3 link records: GATEWAY as a Target Async Gateway Async Gateway as a Target Note the Async requires a modem, also requires starting either the EQNGWASY program (see the LOOPACDI.CMD) or ACDI Target, depending on how you are going to connect. That should get you going enough to start with. You can install some additional targets, use the Packager function. The modem connection uses a standard Hayes 2400 AT command set. It is set to connect at 9600bps. I used an IBM7855 modem with factory reset values, and the AT command set. Your modem might vary. Be sure to set compression off for this sample file. Turn it on later after you have the setup working. ------------------------------------------------------------------------- SDLC Setup If you are going to do an SDLC setup, there are some sample SDLC configurations supplied. These are for Switched SDLC connections to a 3745/NCP/VTAM system. If you have a leased line configuration, you can use this as a starting point and change the SDLC DLC from Switched to Leased line connection. Only CM/2 files are supplied. Here is the procedure for installing CM/2 on two machines with a response file install: 1. Insert the DCAFSAMP diskette and run A:INSTALL 2A. To install the SDLC CONTROL system: - C:\DCAFSAMP\CTLSDLC to install CM/2 2B. To install the SDLC GATEWAY system (Can be a target only system): - C:\DCAFSAMP\GWSDLC to install CM/2 These procedures will use the A: drive for the source of the code. You can edit these .CMD files to change the source to a redirected drive if you are in that environment. You can also edit the response files to tailor for your installation (after you get it working once). An OPTIONAL way to install CM/2 would be to use CMSETUP without a response file, and point to the C:\DCAFSAMP\SDLC directory when prompted for the location of the configuration files. Now on both machines install DCAF: 1. Insert DCAF Diskette 1 and enter A:INSTALL 2. On the Control: choose Control, Packager components 3. On the Gateway: choose Control, Target, Directory and Gateway components (If this will only be a Target, just install TARGET) NOTE: If you are running on a large LAN, it is wise to change the LAN Directory name. If you do, you have to change it for the Target component, Directory component AND Gateway component. All 3 of these have a separate place to personalize the directory name it is IMPERATIVE that you make all three of them match. Also be aware that these names are CASE SENSITIVE, so make them match. 4. Copy the sample link record file into your DCAF Directory: - C:\DCAFSAMP\SDLC\EQNCOMM.REC for the Controlling 5. Run the parser EQNSFPAR to parse the link record file. That completes the install of all the components. You should be able to reboot and Test: - Start CM on both machines - Start the Netbios Target on the Gateway - Start the Controlling on the Control station - Select a Link record, Pick GATEWAY - You will probably get an error with 0003-00000004 return code, this just means try again. - You will connect on the second try. You can then select the target and test DCAF. ------------------------------------------------------------------------- If you already have CM/2 or ES installed, you can easily add the required DCAF defintions. 1. Edit your existing .NDF file and add: - C:\DCAFSAMP\DCAFNDF\DCAFTP.NDF - C:\DCAFSAMP\DCAFNDF\DCAFMODE.NDF (read the comments in those files as you include them) THEN ONLY ON THE CONTROL WORKSTATION: 2. Define a Peer Link with Partner LUs via CMSETUP: - CMSETUP, then Setup, then Use on this workstation - Select your Config file - Select your Workstation Configuration Type (TRN or Enet) - Select Feature type of APPC APIs - Click on Configure - Double click on SNA Connections - Partner Type: Peer, Click on CREATE - Adapter Type = same as above, Click on Configure - Enter: LAN Destination Address = Address of the GATEWAY system (Look in the \IBMCOM\LANTRAN.LOG on the gateway system for it's address). Partner Network ID = USIBMNSB Partner Node Name = GATEWAY (These two values come from the Gateway system, look in it's NDF file for: DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNSB.GATEWAY ) this is typically the first line, use your values for the node name.) - Click on DEFINE Partner LUs - Enter: LU Name = same as Partner Node Name above. Alias = same as Partner Node Name above. (this is what goes in your eqncomm.rec file as PLU name) - Click on ADD, then OK, then OK, then Close, then Close, then Close again which will verify your configuration. Finally Close again. You might be asked if you want to dynamically update, I always choose NO, and stop/start CM instead. THEN ONLY ON THE GATEWAY WORKSTATION: 2. Verify that Implicit LU support is configured. Look in the .NDF file and make sure you have: DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) 3. Install DCAF Components as outlined above. 4. Copy the sample link record file into your DCAF Directory: - C:\DCAFSAMP\CONTROL\EQNCOMM.REC for the Controlling - C:\DCAFSAMP\GATEWAY\EQNCOMM.REC for the Gateway Update the Link Record to match your Alias names: Alias Names are strictly internal to a system. So on the Control workstation, you need to find two alias names, one for your local node and one for the partner node (you just defined that. The local node alias name is in this section: DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNSB.CONTROL ) DESCRIPTION(Created on 05-06-93 at 11:53a) ------>>>>> CP_ALIAS(CONTROL ) The Partner LU alias would be: DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(USIBMNSB.GATEWAY ) ------>>>>> PARTNER_LU_ALIAS(GATEWAY) On the CONTROL workstation: The first entry is for a Gateway connection, the second for a Target connection (can be the Gateway or a separate Target). // // DCAF Link Record for the Gateway machine // :Link Record Name: Gateway // 1-60 characters :Link Record Type: 03 // 03=APPC v1.1 :LU Alias: CONTROL // 1-8 characters :Partner LU Alias: GATEWAY // 1-8 characters :Mode Name: DCAFMODE // 1-8 characters :Connection: 1 // 0=target,1=gateway :Security: 0 // 0=no, 1=yes (for Connection=1) // // // DCAF Link Record for the Gateway machine as/or a Target // :Link Record Name: Gateway_as_a_Target // 1-60 characters :Link Record Type: 03 // 03=APPC v1.1 :LU Alias: CONTROL // 1-8 characters :Partner LU Alias: GATEWAY // 1-8 characters :Mode Name: DCAFMODE // 1-8 characters :Connection: 0 // 0=target,1=gateway :Security: 0 // 0=no, 1=yes (for Connection=1) On the GATEWAY workstation: (This will allow this machine to be a Control/Gateway): On the Gateway the NDF file we care about looks like: DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNSB.GATEWAY ) DESCRIPTION(Created on 05-06-93 at 11:53a) ------>>>>> CP_ALIAS(GATEWAY ) // // // DCAF Link Record for the Gateway machine to allow Control and Gateway // to reside on the same machine. The only "trick" is that the LU Alias name // and the Partner LU Alias names are identical (the Local LU name). // :Link Record Name: CONTROL/GATEWAY // 1-60 characters :Link Record Type: 03 // 03=APPC v1.1 :LU Alias: GATEWAY // 1-8 characters :Partner LU Alias: GATEWAY // 1-8 characters :Mode Name: DCAFMODE // 1-8 characters :Connection: 1 // 0=target,1=gateway :Security: 0 // 0=no, 1=yes (for Connection=1) // 5. Run the parser EQNSFPAR to parse the link record file. 6. Test as above. ------------------------------------------------------------------------- Automatic session starting/session limiting on Control/Gateway If you want to automatically start LU 6.2 sessions between nodes, or limit the number of sessions started on a control/gateway system under CM/2 (there seems to be a problem there), you can include a CNOS (Change Number Of Sessions) section into your existing .NDF file: 1. Edit your existing .NDF file and add: - C:\DCAFSAMP\DCAFNDF\DCAFCNOS.NDF 2. Edit the names in the CNOS section to match your LU names, see the comments in the included file. 3. Run CMVERIFY "yourconfigfile" ------------------------------------------------------------------------- Fast Demo System Setup: Setup just the GATEWAY system. If you have CM installed already just include the DCAFTP.NDF and DCAFMODE.NDf files, and run CMVERIFY. Install DCAF Controlling/Gateway/Directory on this machine. Update EQNCOMM.REC file and run EQNSFPAR LU Alias and Partner LU Alias are identical names (see above) Install DCAF Target code on other machines. That is all you have to do. On the GATEWAY system the Directory and Gateway will startup at Boot time. Start the Controlling component, and then select the link record. The Gateway will get a list of Targets from the Directory and you can take them over. Takes just a few minutes to do this setup.. ------------------------------------------------------------------------- Detailed description of the contents of the DCAFSAMP Diskette: Directory of A:\ INSTALL.CMD - Installs the DCAFSAMP Diskette to C:\DCAFSAMP (XCOPY /s) GWLAPS.CMD - Response file install of LAPS for the GATEWAY CTLLAPS.CMD - Response file install of LAPS for the CONTROL GWCM2.CMD - Response file install of CM/2 for the GATEWAY CTLCM2.CMD - Response file install of CM/2 for the CONTROL GWSDLC.CMD - Response file install of CM/2 for the SDLC CGATEWAY CTLSDLC.CMD - Response file install of CM/2 for the SDLC CONTROL Directory of A:\ES CONTROL.CFG - ES configuration file for CONTROL CONTROL.NDF - ES APPC configuration file for CONTROL CONTROL.CF2 - ES parsed NDF file for CONTROL CONTROL.SEC - ES security configuration file for CONTROL CONTROL.INI - ES LAPS configuration file for CONTROL GATEWAY.CFG - ES configuration file for GATEWAY GATEWAY.NDF - ES APPC configuration file for GATEWAY GATEWAY.CF2 - ES parsed NDF file for GATEWAY GATEWAY.SEC - ES security configuration file for GATEWAY GATEWAY.INI - ES LAPS configuration file for GATEWAY Directory of A:\DCAFNDF DCAFTP.NDF - DCAF Transaction Program Defintions (can add to an NDF) DCAFMODE.NDF - DCAF Transmission Mode DCAFCNOS.NDF - DCAF Change Number of Sessions Verb README.NDF - Tells how to use these sample NDF files DCAF.ANS - Answers to Common Questions (DCAF ANSWERS file from IBMPC) Directory of A:\GATEWAY EQNCOMM.REC - DCAF Link Record for GATEWAY LAPS.RSP - NTS/2 LAPS Response file for GATEWAY CONFIG.ES - CONFIG.SYS of working GATEWAY for ES system CONFIG.CM2 - CONFIG.SYS of working GATEWAY for ES system LOOPACDI.CMD - DCAF Gateway Async loop program Directory of A:\CONTROL EQNCOMM.REC - DCAF Link Record for CONTROL LAPS.RSP - NTS/2 LAPS Response file for CONTROL CONFIG.CM2 - CONFIG.SYS of working CONTROL for ES system CONFIG.ES - CONFIG.SYS of working CONTROL for ES system Directory of A:\CM2 CONTROL.CFG - CM/2 configuration file for CONTROL CONTROL.NDF - CM/2 APPC configuration file for CONTROL CONTROL.CF2 - CM/2 parsed NDF file for CONTROL CONTROL.SEC - CM/2 security configuration file for CONTROL CONTROL.INI - CM/2 LAPS configuration file for CONTROL CONTROL.RSP - CM/2 Response file for CONTROL GATEWAY.CFG - CM/2 configuration file for GATEWAY GATEWAY.NDF - CM/2 APPC configuration file for GATEWAY GATEWAY.CF2 - CM/2 parsed NDF file for GATEWAY GATEWAY.SEC - CM/2 security configuration file for GATEWAY GATEWAY.INI - CM/2 LAPS configuration file for GATEWAY GATEWAY.RSP - CM/2 Response file for GATEWAY Directory of A:\SDLC SDLCCTL.CFG - CM/2 configuration file for SDLC Control SDLCCTL.NDF - CM/2 APPC configuration file for SDLC Control SDLCCTL.CF2 - CM/2 parsed NDF file for SDLC Control SDLCCTL.SEC - CM/2 security configuration file for SDLC Control SDLCCTL.RSP - CM/2 Response file for SDLC Control SDLCGW.CFG - CM/2 configuration file for SDLC Gateway SDLCGW.NDF - CM/2 APPC configuration file for SDLC Gateway SDLCGW.CF2 - CM/2 parsed NDF file for SDLC Gateway SDLCGW.SEC - CM/2 security configuration file for SDLC Gateway SDLCGW.RSP - CM/2 Response file for SDLC Gateway EQNCOMM.REC - DCAF Link Record for SDLC CONTROL ATCSTR00.VTA - VTAM startup file, contains host SSCP name you have to match in your connection to the host (NSBRM80 for sample) NCP3745S.VTA - NCP Gen for ALL of the connections in this diskette, also has SDLC leased line definitions that work/ DCAFSWL.VTA - VTAM Switched Major Node definitions for the Switched SDLC devices (actually looks just like LAN connections) MT3270.VTA - Log Mode Table, has all 3270 and LU 6.2 logmodes required.