All information in this file must adhere to the rules given in the file IBMPC RULES in the IBMPC database. File name: DCAF ANSWERS Conference: IBMPC Product: Distributed Console Access Facility Appendable: By owner only Owner: David Young (DEYOUNG at LSAVMIC1) Originator: David Young (DEYOUNG at LSAVMIC1) Purpose: This file is a parallel to the DCAF FORUM. Answers are provided for questions that constantly get asked or are of general interest to everyone. Discussion: Any discussion about an item in this file should be brought up in the DCAF FORUM. Corrections and suggestions for new entries should be sent directly to the owner. :title.DCAF ANSWERS - A companion file to DCAF FORUM :description. This file contains information about Distributed Console Access Facility that has been extracted from the DCAF FORUM, and from IBM Technical Support and Development. It is believed that the answers contained in this file are reasonably accurate and concise. If you see errors within these answers or wish to submit new questions or answers, append your correction or request to the DCAF FORUM on IBMPC. :end. ----- DCAF ANSWERS appended at 06:52:11 on 93/08/03 GMT (by DEYOUNG at LSAVMIC1) :ndx.APPC0001 :abs.What are the typical causes of some APPC Errors? :key.APPC ERRORS :QUESTION. What are the typical causes of some APPC Errors? :ANSWER. These are some of the typical APPC Errors you might encounter, and one of the posslble cause. There might be other reasons for the error, but this will give you the most common reason: o Command: 0100 / Return Code: 0003-00000004 is usually NORMAL *ONCE*. Retry and it will work. o Command: 1A00 / Return Code: F012-00000000 means Commu- nications Manager is not started. o Command: 1500 / Return Code: 0001-00000003 can be LU Alias name error in the DCAF Link Record. o Command: 1500 / Return Code: 0003-00000004 can be Part- ner LU Alias Name is OK, but the CP Name it is associ- ated with in the NDF is bad. o Command: 1500 / Return Code: 0001-0000015B can be Part- ner LU Alias Name is bad in the link record (Must be up- per case) o Command: 1500 / Return Code: 0003-00000005 can be the Link to the Partner LU is not active, or remote CM not active. If you can get the connection succesfully the first time then from the second attempt on you get this error you probably have the Free Unused Link parameter set to "YES" instaed of "NO" in the DLC adapter profile. o Command: 1600 / Return Code: 0002-00000509 can be that you need to reboot the target machine after installing DCAF. This error occurs also if there is something wrong in the TP definition (i.e. the TP path). If you can get the connection succesfully the first time then from the second attempt on you get this error you probably have the TP_OPERATION parameter in the TARGET DEFINE_TP section set to "QUEUED_AM_STARTED" instead of "NONQUEUED_AM_STARTED" o Command: 1B00 / Return Code: F004-00000000 can be that you forgot to start CM. :from.David Young, LSAVMIC1(DEYOUNG)/Lucio Bortolotti, ROMEPPC(BORTOLOT) :see. ----- DCAF ANSWERS appended at 04:50:46 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.SAMP0001 :abs.Are there some SAMPLE DCAF Installation Procedures? :key.INSTALL INSTALLATION CID :QUESTION. Are there some SAMPLE DCAF Installation Procedures? :ANSWER. If you are at all interested in setting up DCAF, read this note. You can use this diskette to install LAPS, CM/2 or ES, and DCAF, in less than an hour, and have a running configuration. To get the diskette and package: REQUEST DCAFSAMP FROM DEYOUNG AT LSAVMIC1 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) 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. 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. 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 EXAMPLE: Here is the procedure for installing with LAPS and CM/2: 1. Insert the DCAFSAMP diskette and run A:INSTALL 2A. To install the CONTROL system: - C:\DCAFSAMP\CTLLAPS to install/configure LAPS - C:\DCAFSAMP\CTLCM2 to install/configure CM/2 2B. To install the GATEWAY system: - C:\DCAFSAMP\GWLAPS to install/configure LAPS - C:\DCAFSAMP\GWCM2 to install/configure CM/2 3. Install DCAF, use the sample link records provided :from.David Young, LSAVMIC1(DEYOUNG) :see. ----- DCAF ANSWERS appended at 05:11:53 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.MODEM001 :abs.How do you set up CM for the IBM7855 Modem? :key.MODEM ACDI :QUESTION. How do you set up CM for the IBM7855 Modem? :ANSWER. To run DCAF with a DTE-to-modem speed of 19,200 bps and a modem-to modem speed of 12,000 bps with IBM 7855 Modems: 1. Configure ACDI communicaitons for your Com port. 2. Modifiy the Async Device Character string to: AT&F0&C1S0=0\Q2\N3&AP8\M14&I1\A3%C0| Explanation: &F0 : Reset to Factory Default settings &C1 : Carrier Detect when signal detected S0=0: Modem will not Auto-Answer \Q2 : needed to enable RFS flow control for the modem to tell the system to stop sending data. The default for ACDI is that it responds to RFS flow control. \N3 : calling modem will initiate an ECL connection. You must have an ECL connection to achieve a modem-to-modem speed of 12000 bps. &AP8: sets modems preferred telephone line speed to 12000 bps. \M14: sets modem to use a fixed DTE interface speed of 19,200 bps (or whatever it senses the DTE interface speed to be) regardless of what the modem-to-modem speed is. &I1 : needed so modem will return a "CONNECT 19200" message to the PS/2. ACDI reads the connect message from the modem and it will modify the system UART to the speed in the connect message. If you configure the modem to use a fixed speed of 19200 bps regardless of what the modem-to-modem speed is, you don't want the system to reconfigure the system UART to a different speed. \A3 : ECL Buffer size set to 256, use if you have clean phone lines. %C0 : Disable modem data compression (%C1 = MNP5, the default). 3. In the link record on the control specify 19200 line speed 4. On the Gateway specify EQNGWASY 1 19200 :from.David Young, LSAVMIC1(DEYOUNG) :see. ----- DCAF ANSWERS appended at 05:21:14 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.VTAM0001 :abs.What VTAM Logmode entries do I need for DCAF? :key.VTAM LOGMODE :QUESTION. What VTAM Logmode entries do I need for DCAF? :ANSWER. Below is a complete Logmode table that you could use for DCAF. You will at least need the SNASVCMG and DCAFMODE entries for DCAF to work. The #INTER entry is also a good idea as this is the default mode for CM. You need to have these entries in the logmode table that is defined for the DCAF LU at the host. Here is the LU definintion example: CONTROL LU LOCADDR=0,MODETAB=DCAFTAB,DLOGMOD=DCAFMODE And here is the DCAFTAB that contains the required entries: DCAFTAB MODETAB ********************************************************************** * * THIS MODE TABLE CONTAINS THE FOLLOWING ENTRIES : * * DYNAMIC - SNA DYNAMIC LOGMODE WITH QUERY FOR CM 3270 SESSIONS * SNASVCMG - SNA LU6.2 SESSION CONTROL * LU62 - SNA LU6.2 NULL TABLE ENTRY * LU62SYS1 - SNA LU6.2 NULL TABLE ENTRY * DCAFMODE - SNA LU6.2 NULL TABLE ENTRY FOR DCAF * #INTER - SNA LU6.2 DEFAULT for APPN * MLU62A - SNA LU6.2 For NETVIEW/DM * ********************************************************************** DYNAMIC MODEENT LOGMODE=DYNAMIC, X FMPROF=X'03',TSPROF=X'03',PRIPROT=X'B1', X SECPROT=X'90',COMPROT=X'3080',RUSIZES=X'87C7', X PSERVIC=X'028000000000000000000300' * *********************************************************************** *********************************************************************** * * MODE FOR *** SNA *** LU 6.2 SESSIONS * SNASVCMG MODEENT LOGMODE=SNASVCMG, X FMPROF=X'00',TSPROF=X'00',PRIPROT=X'00', X SECPROT=X'00',COMPROT=X'0000',RUSIZES=X'0000', X PSNDPAC=X'00',SRCVPAC=X'00',SSNDPAC=X'00', X PSERVIC=X'000000000000000000000000' LU62 MODEENT LOGMODE=LU62, X FMPROF=X'00',TSPROF=X'00',PRIPROT=X'00', X SECPROT=X'00',COMPROT=X'0000',RUSIZES=X'0000', X PSNDPAC=X'00',SRCVPAC=X'00',SSNDPAC=X'00', X PSERVIC=X'000000000000000000000000' LU62SYS1 MODEENT LOGMODE=LU62SYS1, X FMPROF=X'00',TSPROF=X'00',PRIPROT=X'00', X SECPROT=X'00',COMPROT=X'0000',RUSIZES=X'0000', X PSNDPAC=X'00',SRCVPAC=X'00',SSNDPAC=X'00', X PSERVIC=X'000000000000000000000000' DCAFMODE MODEENT LOGMODE=DCAFMODE, X FMPROF=X'00',TSPROF=X'00',PRIPROT=X'00', X SECPROT=X'00',COMPROT=X'0000',RUSIZES=X'0000', X PSNDPAC=X'00',SRCVPAC=X'00',SSNDPAC=X'00', X PSERVIC=X'000000000000000000000000' #INTER MODEENT LOGMODE=#INTER, X FMPROF=X'00',TSPROF=X'00',PRIPROT=X'00', X SECPROT=X'00',COMPROT=X'0000',RUSIZES=X'0000', X PSNDPAC=X'00',SRCVPAC=X'00',SSNDPAC=X'00', X PSERVIC=X'000000000000000000000000' MLU62A MODEENT LOGMODE=MLU62A, X FMPROF=X'13',TSPROF=X'07',PRIPROT=X'B0', X SECPROT=X'B0',COMPROT=X'50A1',RUSIZES=X'8585', X TYPE=0, X PSNDPAC=X'03',SRCVPAC=X'03',SSNDPAC=X'00', X PSERVIC=X'060200000000000000002400' *********************************************************************** MODEEND END :from.David Young, LSAVMIC1(DEYOUNG) :see. ----- DCAF ANSWERS appended at 14:32:30 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.INST0001 :abs.What are the typical causes of some DCAF Installation Errors? :key.INSTALLATION ERRORS :QUESTION. What are the typical causes of some DCAF Installation Errors? :ANSWER. Following are some typical error message that you may encounter when installing DCAF and their reason: o Error EQN0156 Return Code = 5391. Error EQN0156 Return Code = 4865. In both the situations the problem is that the DCAF Installation diskette is write-protected (a warning system pop up should be displayed before the DCAF error message) :from.Lucio Bortolotti, ROMEPPC(BORTOLOT) :see. ----- DCAF ANSWERS appended at 14:33:10 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.SEC00001 :abs.What are the typical causes of some Security errors ? :key.SECURITY ERRORS :QUESTION. What are the typical causes of some Erros setting up DCAF Security ? :ANSWER. If you get some DCAF error messages while setting up the DCAF sesuirity feature go to the Administrator wks. and edit the EQNADMN.LOG file. These are some of the errors you may find and the relative causes: o EQN0720: You must first log on to the workstation before transferring files. EQN0725: Error sending file=eqnsctrg.trn to the security authenticator=123456789. EQN0702: File transfer terminated partially. You must first LOG ON to DCAF, then try to start the File Transfer from the DCAF Administrator o EQN0725: Error sending file=eqnsctrg.trn to the security authenticator=123456789. EQN0702: File transfer terminated partially. One possible reason for this error is that your USER ID does not have the file transfer privilege. Another possible reason is that the "Security Data Path" specified on the Administrator component is different from the one specified on the Authenticator component. :from.Lucio Bortolotti, ROMEPPC(BORTOLOT) :see. ----- DCAF ANSWERS appended at 19:52:13 on 93/08/04 GMT (by DEYOUNG at LSAVMIC1) :ndx.VIDEO002 :abs.Is the 8514/A Display Adapter Supported? :key.Video xga vga bga 8514 :QUESTION. Is the 8514/A Display Adapter Supported? :ANSWER. The 8514/A adapter is NOT suported by DCAF 1.1, unless you are running in VGA mode. :from.David Young, LSAVMIC1(DEYOUNG) :see. ----- DCAF ANSWERS appended at 22:30:44 on 93/08/16 GMT (by DEYOUNG at LSAVMIC1) :ndx.DIR00001 :abs.How do you start the DCAF Directory Minimized? :key.directory minimized desktop :QUESTION. How do you start the DCAF Directory Minimized with OS/2 2.x? :ANSWER. First you have to delete the LAN Directory Object from the DCAF folder. It has an option set on it saying start at boot time. This was carried over from EE 1.3. The only way to get rid of it it to delete the object. Then in your STARTUP.CMD add this line: start "DCAF LAN Directory" /C /MIN c:\dcaf11\eqngwdir.exe :from.David Young, LSAVMIC1(DEYOUNG) :see. ----- DCAF ANSWERS appended at 06:25:25 on 93/08/22 GMT (by DEYOUNG at LSAVMIC1) :ndx.INST0002 :abs.How do you setup a CONTROL/GATEWAY system? :key.CONTROL GATEWAY APPC SETUP :QUESTION. How do you setup a CONTROL/GATEWAY system? :ANSWER. It is quite simple to setup one machine to be a Control/Gateway system. Also you typically have the Directory installed on this system. This will allow this one system to be the single APPC system on a LAN. The Targets can all have NETBIOS (LAN) target setups, thus not requiring ES or CM to be installed (just NTS/2 LAPS for the Netbios support). 1. Install DCAF, Controlling, Gateway and Directory. Make sure the Gateway and Directory are using the same Directory name, or use the default name (personalize does this). 2. Install CM/2 or ES, use the DCAFSAMP sample install diskette from MKTTOOLS. Install the Gateway configuration. The NDF file will look like this when you are finished: DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNSB.GATEWAY ) DESCRIPTION(Created on 05-06-93 at 11:53a) CP_ALIAS(GATEWAY ) NAU_ADDRESS(INDEPENDENT_LU) NODE_TYPE(EN) NODE_ID(X'66666') HOST_FP_SUPPORT(YES); DEFINE_MODE MODE_NAME(DCAFMODE) DESCRIPTION(DCAF 1.1 Session Values) COS_NAME(#CONNECT) DEFAULT_RU_SIZE(NO) MAX_RU_SIZE_UPPER_BOUND(1024) RECEIVE_PACING_WINDOW(8) MAX_NEGOTIABLE_SESSION_LIMIT(6) PLU_MODE_SESSION_LIMIT(6) MIN_CONWINNERS_SOURCE(1); DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) DESCRIPTION(Created on 05-06-93 at 11:53a) DEFAULT_MODE_NAME(BLANK) MAX_MC_LL_SEND_SIZE(32767) DIRECTORY_FOR_INBOUND_ATTACHES(*) DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED) DEFAULT_TP_PROGRAM_TYPE(BACKGROUND) DEFAULT_TP_CONV_SECURITY_RQD(NO) MAX_HELD_ALERTS(10); DEFINE_TP TP_NAME(IBM.DCAF.ADMIN.TRANSACTION.PROGRAM) DESCRIPTION(DCAF 1.1 Administration TP) FILESPEC(C:\DCAF11\EQNSCPPC.EXE) PARM_STRING(1) CONVERSATION_TYPE(BASIC) CONV_SECURITY_RQD(NO) SYNC_LEVEL(NONE) TP_OPERATION(QUEUED_AM_STARTED) PROGRAM_TYPE(FULL_SCREEN) INCOMING_ALLOCATE_QUEUE_DEPTH(5) INCOMING_ALLOCATE_TIMEOUT(60) RECEIVE_ALLOCATE_TIMEOUT(60); DEFINE_TP TP_NAME(IBM.DCAF.CONTROLLING.TRANSACTION.PROGRAM) DESCRIPTION(DCAF 1.1 Controlling TP) FILESPEC(C:\DCAF11\EQNCTRAM.EXE) CONVERSATION_TYPE(BASIC) CONV_SECURITY_RQD(NO) SYNC_LEVEL(NONE) TP_OPERATION(NONQUEUED_AM_STARTED) PROGRAM_TYPE(BACKGROUND) RECEIVE_ALLOCATE_TIMEOUT(INFINITE); DEFINE_TP TP_NAME(IBM.DCAF.GATEWAY.TRANSACTION.PROGRAM) DESCRIPTION(DCAF 1.1 Gateway TP) FILESPEC(C:\DCAF11\EQNGTWAM.EXE) CONVERSATION_TYPE(BASIC) CONV_SECURITY_RQD(NO) SYNC_LEVEL(NONE) TP_OPERATION(NONQUEUED_AM_STARTED) PROGRAM_TYPE(BACKGROUND) RECEIVE_ALLOCATE_TIMEOUT(INFINITE); DEFINE_TP TP_NAME(IBM.DCAF.TARGET.TRANSACTION.PROGRAM) DESCRIPTION(DCAF 1.1 Target TP) FILESPEC(C:\DCAF11\EQNTGAUT.EXE) PARM_STRING(LU62) CONVERSATION_TYPE(BASIC) CONV_SECURITY_RQD(NO) SYNC_LEVEL(EITHER) TP_OPERATION(NONQUEUED_AM_STARTED) PROGRAM_TYPE(PRESENTATION_MANAGER) RECEIVE_ALLOCATE_TIMEOUT(INFINITE); START_ATTACH_MANAGER; 3. Update the DCAF Link record (EQNCOMM.REC) To look like: // // 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 idencial (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 // 4. Run EQNSFPAR to parse the link record. 5. If you want you can add a CNOS statement to the NDF file to make sure you are setting up the proper session limits: CNOS LOCAL_LU_ALIAS(GATEWAY ) FQ_PARTNER_LU_NAME(USIBMNSB.GATEWAY ) MODE_NAME(DCAFMODE) SET_NEGOTIABLE(NO) PLU_MODE_SESSION_LIMIT(6) MIN_CONWINNERS_SOURCE(0) MIN_CONWINNERS_TARGET(0) AUTO_ACTIVATE(0); That is all. This all the setup you have to do for a Gateway, or to also use this system as an APPC Target. Since Implicit LUs are supported, you can have multiple controlling systems conntedt to this system. The session limits are set to 6 in this example, which will allow the controlling systems to have 3 concurrent targets under control PER CONTROLLING system. :from.David Young, LSAVMIC1(DEYOUNG) :see.