DCAF Hints: Difference between revisions
No edit summary |
mNo edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Last Updated: June 18, 1996 | {{Article | ||
|Author=Bruce Morris | |||
|Date=1996-06-18 | |||
|OS=[[IBM OS/2 2.1]] | |||
|File=N/A | |||
|Source=[http://ps-2.kev009.com/pccbbs/misc/dcafhint.txt] | |||
}} | |||
Last Updated: June 18, 1996 | |||
The following DCAF hints are provided by Bruce Morris, SystemView Support Operations, Raleigh, NC. | The following DCAF (Distributed Console Access Facility) hints are provided by Bruce Morris, SystemView Support Operations, Raleigh, NC. I hope you find them useful. | ||
They are provided to help you resolve DCAF problems/questions and are provided "as is" without any warranty or guarantee. | They are provided to help you resolve DCAF problems/questions and are provided "as is" without any warranty or guarantee. The file will be updated when time permits and when new hints are identified. | ||
Any suggestions concerning this file or suggested additions should be sent to: | Any suggestions concerning this file or suggested additions should be sent to: | ||
VNET address: BAMORRIS at RALVM14 | VNET address: BAMORRIS at RALVM14 | ||
INTERNET Addr: BAMORRIS@VNET.IBM.COM | INTERNET Addr: BAMORRIS@VNET.IBM.COM | ||
;DCAF product Information:CompID: 562221200 FESN: 0968318 | |||
;DCAF product Information | |||
Previous Releases/Latest CSD (Unsupported releases): | Previous Releases/Latest CSD (Unsupported releases): | ||
:DCAF 1.1/UB10971 | |||
:DCAF 1.2/UB10970 | |||
Supported Releases: DCAF 1.3 | |||
Supported Releases | |||
Latest Release | Latest Release: DCAF 1.32 | ||
Latest Corrective Service | Latest Corrective Service: CSD UB31597 (SYSLEVEL UB09850) | ||
Note: DCAF 1.3 + CSD UB31597 is equivalent to DCAF release 1.32 and CSD UB31597 supersedes any previous CSD. | Note: DCAF 1.3 + CSD UB31597 is equivalent to DCAF release 1.32 and CSD UB31597 supersedes any previous CSD. | ||
---- | ---- | ||
APARs for high impact or pervasive problems not fixed in latest CSD: | APARs for high impact or pervasive problems not fixed in latest CSD: | ||
# None | |||
DCAF information (fixes, text files, programs, etc.) are available for download from the IBM PCCBBS via: | |||
# Phone: 919-517-0001 | |||
DCAF information (fixes, text files, programs, etc.) are available | # Internet: WWW.pc.ibm.com or FTP.pc.ibm.com | ||
for download from the IBM PCCBBS via: | |||
DCAF packages are accessible to IBM employees thru IBM VNET with the following command: REQUEST <package name> FROM DCAFLEV2 AT RALVM14" | |||
DCAF packages are accessible to IBM employees thru IBM VNET with the | |||
following command: REQUEST <package name> FROM DCAFLEV2 AT RALVM14" | |||
(Package Name of "LIST" will send you a current list of packages) | (Package Name of "LIST" will send you a current list of packages) | ||
{| | |||
OPERATING SYSTEMS | !OPERATING SYSTEMS||SUPPORTED APPLICATIONS | ||
|- | |||
|Dos||Full Screen text mode | |||
|- | |||
|Windows||Any but Full Screen Graphic apps | |||
|- | |||
|Windows for Workgroups||Windowed applications only, No full-screen graphical or DOS environments | |||
|- | |||
|OS/2 1.3||Presentation Manager and OS/2 Full Screen Text Mode | |||
|- | |||
|OS/2 2.1||Presentation Manager, OS/2 Full Screen Text Mode MVDMs Full Screen Text Mode Seamless Windows (1) | |||
|} | |||
(1)Support of 'seamless' Windows means only windows apps that run on the OS/2 desktop are supported. Win-OS/2 Full Screen is not. | |||
(1)Support of 'seamless' Windows means only windows apps that run on | |||
---- | |||
DCAF 1.3 CONFIGURATIONS: | DCAF 1.3 CONFIGURATIONS: | ||
---- | |||
1. Controlling------>Target (NEW WITH DCAF 1.3) | 1. Controlling------>Target (NEW WITH DCAF 1.3) | ||
Line 98: | Line 90: | ||
10.Controlling------>Target (NEW WITH DCAF 1.3 | 10.Controlling------>Target (NEW WITH DCAF 1.3 | ||
IPX | IPX | ||
Note: To run DCAF via Asynchronous modems a separate communications | Note: To run DCAF via Asynchronous modems a separate communications product is required. | ||
Several communications programs can provide this support (e.g., CM/2 ACDI, CM/2 SNA Phone, LAN Distance, TCP/IP SLIP, etc.). CM/2 ACDI does not support data rates greater than 19,200 bps or PCMCIA/MWAV modems. | |||
==Start of Hints== | ==Start of Hints== | ||
===General Section=== | ===General Section=== | ||
Installing DCAF 1.32 | |||
To bring a workstation up to DCAF 1.32 level, this is what has to be done: | |||
* Install DCAF 1.31 | |||
To bring a workstation up to DCAF 1.32 level, this is what has to be | * Reboot | ||
done: | * Apply the CSD | ||
* Reboot | |||
* Run EQNCONF | |||
Since new functions have been included, this CSD does not only | Since new functions have been included, this CSD does not only upgrade files but also modifies files as the DCAF.INI and upgrades product's Databases. | ||
upgrade files but also modifies files as the DCAF.INI and upgrades | |||
product's Databases. | |||
To automate the process you can use a product like NvDM where you | To automate the process you can use a product like NvDM where you can schedule the sequence of the different installations and personalization (including the reboot). | ||
can schedule the sequence of the different installations and | ---- | ||
personalization (including the reboot). | |||
Building Controller Directory | Building Controller Directory | ||
A package is available (DCAFCWD) which will allow you to build a | A package is available (DCAFCWD) which will allow you to build a DCAF 1.3 Controller workstation directory using a REXX CMD file instead of adding each workstation individually or writing a "C" program. | ||
DCAF 1.3 Controller workstation directory using a REXX CMD file | ---- | ||
instead of adding each workstation individually or writing a | |||
"C" program. | |||
Setting DCAF Targets to use Video Device Driver mode | Setting DCAF Targets to use Video Device Driver mode | ||
Issue command "EQNFRDDI /D" and then restart the Target. Verify | Issue command "EQNFRDDI /D" and then restart the Target. Verify mode by checking EQNPM.LOG. | ||
mode by checking EQNPM.LOG. | ---- | ||
DCAF Target starts in Monitor Mode and Active Mode greyed out: | DCAF Target starts in Monitor Mode and Active Mode greyed out: | ||
After CSD UB20924 is installed lose ability to establish session with | After CSD UB20924 is installed lose ability to establish session with TGT wks in Active mode. | ||
TGT wks in Active mode. | |||
DCAF.INI file is corrupted. | DCAF.INI file is corrupted. Delete DCAF.INI file and re-personalize the TGT wks to correct problem or get IC11618 fix. | ||
TGT wks to correct problem or get IC11618 fix. | ---- | ||
EQN0185 error message on Windows Target (1% displayed): | EQN0185 error message on Windows Target (1% displayed): | ||
APAR IC10084 is for Windows Target wks (INCLUDED in UB20924) | APAR IC10084 is for Windows Target wks (INCLUDED in UB20924) | ||
---- | |||
DCAF supported COMPAQ 1280P Display Adapter | DCAF supported COMPAQ 1280P Display Adapter | ||
New DCAF enabled Display Driver for the Compaq 1280p is available on | New DCAF enabled Display Driver for the Compaq 1280p is available on | ||
COMPAQ BBS in file named SP0964. (COMPAQ BBS: 1-713-378-1418) | COMPAQ BBS in file named SP0964. (COMPAQ BBS: 1-713-378-1418) | ||
---- | |||
How to determine Video hardware on DCAF workstation: | How to determine Video hardware on DCAF workstation: | ||
CMD: QSYSTEM (included with CM/2) | CMD: QSYSTEM (included with CM/2) | ||
CMD: SVGA STATUS (From DOS fullscreen) | CMD: SVGA STATUS (From DOS fullscreen) | ||
---- | |||
Things to look for to verify that DCAF is correctly installed: | Things to look for to verify that DCAF is correctly installed: | ||
# Check DCAF directory for files with .NEW extension (expect none) | |||
# Try to rename EQNPMGRE.DLL (Should be locked by OS/2) | |||
# Check OS2.INI file for PM_ED_HOOKS (Should be there) | |||
---- | |||
DCAF Target changes to the OS2.INI file: | DCAF Target changes to the OS2.INI file: | ||
Line 177: | Line 150: | ||
PM_ED_HOOKS MODULENAME EQNPMGRE | PM_ED_HOOKS MODULENAME EQNPMGRE | ||
SYS_DLLS Load EQNCLHOT | SYS_DLLS Load EQNCLHOT | ||
---- | |||
Mouse movement on WINDOWS target: | Mouse movement on WINDOWS target: | ||
To speed up the mouse movements add the PBA=0 parameter to the target | To speed up the mouse movements add the PBA=0 parameter to the target CONFIG.SYS. | ||
CONFIG.SYS. | |||
DEVICE=<drive>:\<path>\DXMT0MOD.SYS ........ PBA=0 | |||
DEVICE=<drive>: | ---- | ||
RESERVED message: | RESERVED message: | ||
Message appears when you do not have IEEE 802.2 support configured in | Message appears when you do not have IEEE 802.2 support configured in LAPS for the adapter you are using. (Should not occur after UB20924 CSD is installed) | ||
LAPS for the adapter you are using. | ---- | ||
CSD is installed) | |||
DCAF 1.3 CID install to wrong drive using NetView DM/2 | DCAF 1.3 CID install to wrong drive using NetView DM/2 | ||
In the "Section Install", the token $(TargetDir) in /T: parameter | In the "Section Install", the token $(TargetDir) in /T: parameter of Parms row is not defined; so DCAF assumed as default for targetdir c:\dcaf13. | ||
of Parms row is not defined; so DCAF assumed as default | ---- | ||
for targetdir c:\dcaf13. | |||
Device Independence for Controlling DCAF workstations: | Device Independence for Controlling DCAF workstations: | ||
A DCAF 1.31 controller can control both DCAF 1.31 and pre-DCAF 1.31 | A DCAF 1.31 controller can control both DCAF 1.31 and pre-DCAF 1.31 target workstations ... if the Controller workstation has a Video Device Driver which is DCAF enabled. (Use DCAFSVGA package to test - see start of file for where to get DCAF packages) | ||
target workstations ... if the Controller workstation has a Video | ---- | ||
Device Driver which is DCAF enabled. (Use DCAFSVGA package to test - | |||
see start of file for where to get DCAF packages) | |||
Unable to select COM port for ASYNC connection with WARP Connect | Unable to select COM port for ASYNC connection with WARP Connect | ||
Problem occurs when running WARP Connect with Fixpack #17 or later | Problem occurs when running WARP Connect with Fixpack #17 or later installed. | ||
installed. | |||
DCAF APAR IC13487 corrects problem (In DCAF CSD #2 UB31597) @ | DCAF APAR IC13487 corrects problem (In DCAF CSD #2 UB31597) @ | ||
---- | |||
Unable to write OS2.INI or OS2SYS.INI files with XGA, SVGA device | Unable to write OS2.INI or OS2SYS.INI files with XGA, SVGA device drivers on Warp Connect. See OS/2 APARS: | ||
drivers on Warp Connect. | APAR= PJ19564 SER= 011 MS WPSHLAPAR | ||
CANNOT WRITE TO INI FILES DUE TO EXCEEDING MAX FILE HANDLES. | |||
APAR= PJ19564 SER= 011 MS WPSHLAPAR | |||
CANNOT WRITE TO INI FILES DUE TO EXCEEDING MAX FILE HANDLES. | |||
APAR= PJ21815 SER= 009 IN VIDEOAPAR | APAR= PJ21815 SER= 009 IN VIDEOAPAR | ||
RUNNING OS/2 WARP, USING THE S3_864 BBS DRIVERS WHILE DECAF IS | RUNNING OS/2 WARP, USING THE S3_864 BBS DRIVERS WHILE DECAF IS | ||
LOADED SYSTEM CANNOT WRITE TO OS2.INI AND OS2.SYS INI IN SVGA | LOADED SYSTEM CANNOT WRITE TO OS2.INI AND OS2.SYS INI IN SVGA | ||
---- | |||
Deinstalling DCAF 1.2 with EQNINSDS /n command | Deinstalling DCAF 1.2 with EQNINSDS /n command | ||
DCAF 1.2 must be at UB09790 SYSLEVEL for this command to be supported. | DCAF 1.2 must be at UB09790 SYSLEVEL for this command to be supported. | ||
---- | |||
How to monitor without Target notification: | How to monitor without Target notification: | ||
On a OS/2 target, use OS/2 facilities to make use of a restricted | On a OS/2 target, use OS/2 facilities to make use of a restricted shell on the OS/2 Target workstation and make the DCAF Target window invisible. | ||
shell on the OS/2 Target workstation and make the DCAF Target | |||
window invisible. | For DCAF full-screen sessions, change the target personalization so that the status area is displayed on row Number 0. | ||
---- | |||
For DCAF full-screen sessions, change the target personalization so | |||
that the status area is displayed on row Number 0. | |||
Replacing a locked DCAF module on a remote system | Replacing a locked DCAF module on a remote system | ||
For example, EQNCM03.DLL cannot be replaced on the target wks, | For example, EQNCM03.DLL cannot be replaced on the target wks, during a DCAF TCP/IP session (the module is locked). | ||
during a DCAF TCP/IP session (the module is locked). | |||
There are at least two ways of replacing this module from controller: | There are at least two ways of replacing this module from controller: | ||
1)-put in the first row of startup.cmd something like that: | 1)-put in the first row of startup.cmd something like that: | ||
copy (path):/EQNCM03.DLL (path):/dcaf13 | copy (path):/EQNCM03.DLL (path):/dcaf13 | ||
Line 256: | Line 214: | ||
===Protocol Section (TCP/IP, NetBIOS, APPC...)=== | ===Protocol Section (TCP/IP, NetBIOS, APPC...)=== | ||
Releases of TCP/IP which should work with DCAF 1.31: | |||
Releases of TCP/IP which should work with DCAF 1.31: | * OS/2: | ||
** IBM TCP/IP V2.0 plus CSD UN64092 | |||
* OS/2 : | ** IBM TCP/IP V3.0 provided with WARP Connect | ||
* Windows: | |||
** IBM TCP/IP V2.1.1 or later | |||
** MS TCP/IP for Windows for Workgroup 3.11 | |||
* Windows : | ** Novell LAN WorkPlace for DOS version 4.2 or later | ||
---- | |||
Using Host names with DCAF 1.31 | Using Host names with DCAF 1.31 | ||
* If the customer uses the IP address it works | |||
* If the customer uses the hostname it needs the nameserver. | |||
---- | |||
TCP/IP Port number on Target | TCP/IP Port number on Target | ||
all Targets can use 2501 as local port number. | all Targets can use 2501 as local port number. | ||
You need to change it if locally there is another TCP/IP | You need to change it if locally there is another TCP/IP program that uses the same port number. | ||
program that uses the same port number. | ---- | ||
Termination Problem with TCP/IP using MPTS stack on LAN Server 4.0 | Termination Problem with TCP/IP using MPTS stack on LAN Server 4.0 | ||
Apply fixpack WR08150 for MPTS TCP/IP stack | Apply fixpack WR08150 for MPTS TCP/IP stack | ||
---- | |||
DCAF TCP/IP hangs in INITIATING when crossing Bridge/Routers: | DCAF TCP/IP hangs in INITIATING when crossing Bridge/Routers: | ||
Line 292: | Line 246: | ||
problem. | problem. | ||
Note: sometimes the size may have to be even smaller (e.g., 1490 for | Note: sometimes the size may have to be even smaller (e.g., 1490 for Ethernet) | ||
---- | |||
DCAF 1.3 TCP/IP DOS/WINDOWS Support | DCAF 1.3 TCP/IP DOS/WINDOWS Support | ||
DCAF 1.3 in DOS/WINDOWS environment supports TCP/IP that is | DCAF 1.3 in DOS/WINDOWS environment supports TCP/IP that is compliant with WinSocket architecture. | ||
compliant with WinSocket architecture. | |||
If your wks has the WINSOCK.DLL, then it should be compliant. | If your wks has the WINSOCK.DLL, then it should be compliant. | ||
---- | |||
CM/2 runs out of resources after starting and stopping DCAF sessions | CM/2 runs out of resources after starting and stopping DCAF sessions | ||
Line 307: | Line 259: | ||
This fix should be in CM/2 latest FixPac available on CM/2 BBS at | This fix should be in CM/2 latest FixPac available on CM/2 BBS at | ||
(919)543-8200 (Current latest fixpac is AP111 for CM/2 1.11). | (919)543-8200 (Current latest fixpac is AP111 for CM/2 1.11). | ||
---- | |||
APPC Error Cmd Txt=1600 RC=0002 SRC=00000509 - Unable to allocate | APPC Error Cmd Txt=1600 RC=0002 SRC=00000509 - Unable to allocate a LU6.2 conversation | ||
a LU6.2 conversation | |||
Check the following Define_TP parameters: | Check the following Define_TP parameters: | ||
# Change the NDF file on the Target to include the keyword PARM_STRING as follows: | |||
#:PARM_STRING(LU62 /m) (attention case sensitive) | |||
as follows: | #Check the FileSpec and make sure that the directory and path point to your current DCAF subdirectory. | ||
#Check the name (e.g., IBM.DCAF.TARGET.TRANSACTION.PROGRAM) and make sure that there are no misspelled words and that it is exactly as shown in the DCAF Installation Guide. | |||
---- | |||
point to your current DCAF subdirectory. | |||
sure that there are no misspelled words and that it is exactly as | |||
shown in the DCAF Installation Guide. | |||
CM/2 ACDI CMD TXT:02 RC:000C with PCMCIA modem | CM/2 ACDI CMD TXT:02 RC:000C with PCMCIA modem | ||
PCMCIA modems are not supported by CM/2 ACDI | PCMCIA modems are not supported by CM/2 ACDI | ||
PCMCIA modems are supported by SNA Phone in CM/2 1.11 or LAN Distance | PCMCIA modems are supported by SNA Phone in CM/2 1.11 or LAN Distance | ||
---- | |||
CM/2 ACDI CMD TXT:02 RC:00F1 | CM/2 ACDI CMD TXT:02 RC:00F1 | ||
Return Code 00F1 indicates that an OS/2 error was returned to CM/2. | Return Code 00F1 indicates that an OS/2 error was returned to CM/2. | ||
The OS/2 error log provides additional information on this error and | The OS/2 error log provides additional information on this error and | ||
Line 337: | Line 280: | ||
Control Programming Ref. Follow normal OS/2 problem determination | Control Programming Ref. Follow normal OS/2 problem determination | ||
procedures. | procedures. | ||
---- | |||
ACDI Return Code 00FF | ACDI Return Code 00FF | ||
You have not configured or started CM/2 ACDI support. Make sure you | You have not configured or started CM/2 ACDI support. Make sure you | ||
booted your workstation after configuring ACDI and that ACDI is | booted your workstation after configuring ACDI and that ACDI is | ||
started by a "CMQUERY" command at an OS/2 command prompt. | started by a "CMQUERY" command at an OS/2 command prompt. | ||
---- | |||
DCAF msg EQN0512 when attempting ACDI dial connection: | DCAF msg EQN0512 when attempting ACDI dial connection: | ||
This message indicates that you probably do not have your modem | This message indicates that you probably do not have your modem | ||
initialization strings properly defined in the DCAF controlling or | initialization strings properly defined in the DCAF controlling or | ||
target workstation. | target workstation. | ||
Normally the modem may dial and the lights "flash" several times, | Normally the modem may dial and the lights "flash" several times, | ||
the speaker goes off, but you never see the "receive data" light | the speaker goes off, but you never see the "receive data" light | ||
come on indicating that the screen image is being received. | come on indicating that the screen image is being received. | ||
Generally it helps to have the same brand and model of modem on both | Generally it helps to have the same brand and model of modem on both | ||
the controlling and target workstation. | the controlling and target workstation. | ||
Select the Hayes 2400 SmartModem in the CM/2 set-up then change the | Select the Hayes 2400 SmartModem in the CM/2 set-up then change the | ||
default modem initialization string to one supported by your modem. | default modem initialization string to one supported by your modem. | ||
Even though your modem may support the "Hayes AT command set" or is | Even though your modem may support the "Hayes AT command set" or is | ||
"Hayes compatible", you still must build the initialization string from | "Hayes compatible", you still must build the initialization string from | ||
the documentation provided by the modem manufacturer. | the documentation provided by the modem manufacturer. | ||
Start by getting a basic initialization string working, and then if | Start by getting a basic initialization string working, and then if | ||
you want to experiment to enhance you performance you can try different | you want to experiment to enhance you performance you can try different | ||
values. | values. | ||
Generally you should select a string which supports LOCAL HARDWARE FLOW | Generally you should select a string which supports LOCAL HARDWARE FLOW | ||
CONTROL and disables COMPRESSION. | CONTROL and disables COMPRESSION. A common string might be: | ||
General string: "AT&F&C1&D2&K3" | General string: "AT&F&C1&D2&K3" | ||
USRobotics Sportster: "AT&F1&C1&D2&K0&A0" | USRobotics Sportster: "AT&F1&C1&D2&K0&A0" | ||
ACDI is limited to 19.2 kbps, so set the DCAF speed to 19.2 regardless | ACDI is limited to 19.2 kbps, so set the DCAF speed to 19.2 regardless | ||
of the speed of the modem. | of the speed of the modem. | ||
---- | |||
VTAM mode definition for DCAF when using SNA BackBone network: | VTAM mode definition for DCAF when using SNA BackBone network: | ||
VTAM does not care about the contents of the mode, just that it | VTAM does not care about the contents of the mode, just that it should exist. | ||
should exist. | |||
So the MODEENT should look something like: | So the MODEENT should look something like: | ||
DCAFMODE MODEENT LOGMODE=DCAFMODE | DCAFMODE MODEENT LOGMODE=DCAFMODE | ||
Just that * no additional parameters. | Just that * no additional parameters. | ||
---- | |||
DCAF using NETBIOS over SNA using AnyNet | |||
The following APAR has been closed and is available to all customers: | |||
:APAR IC07956 for AnyNet/2 NetBEUI over SNA V1.0 | |||
Problems fixed by this APAR: | |||
AnyNet/2 NetBEUI over SNA V1.00 as shipped does not support LAN NetView Management Utilities for OS/2 (LMU/2) or Distributed Console Access Facility (DCAF). You must apply this fix if you wish to run these programs over SNA using NetBEUI over SNA 1.00. | |||
With this fix, AnyNet/2 NetBEUI over SNA V1.00 | |||
* will support LMU/2 and DCAF | |||
* will allow multiple processes on a machine to add the same group name. | |||
* will allow a process to call from a name that a different process had added (this should not be allowed, but some programs depend on it). | |||
* eliminates timing windows where data sent using very short-lived | |||
* will accept status queries with very large buffer sizes. | |||
---- | |||
DCAF 1.3 TGT on Warp Connect | DCAF 1.3 TGT on Warp Connect | ||
If using Novell Netware Requester 2.11, apply APAR IC09747. | If using Novell Netware Requester 2.11, apply APAR IC09747. | ||
===Performance Section=== | ===Performance Section=== | ||
NETBIOS Performance Problem with LAPS WRU7045 | NETBIOS Performance Problem with LAPS WRU7045 | ||
There a fix for the NETBIOS loopback connection performance problem | There a fix for the NETBIOS loopback connection performance problem (controlling a DCAF NETBIOS target on the same wkstn where DCAF GW/LAN Dir. is installed *IS* a NETBIOS loopback connection) for LAPS WRU7045 was suggested: | ||
(controlling a DCAF NETBIOS target on the same wkstn where DCAF | :Increase LOOPPACKETS (and perhaps SELECTORS as well), in the NETBEUI section of PROTOCOL.INI. | ||
GW/LAN Dir. is installed *IS* a NETBIOS loopback connection) | :The values I am using are 8 and 30 respectively, but others are running okay with 8 and 15. (may need to be increased to 50 to work). | ||
for LAPS WRU7045 was suggested: | ---- | ||
Increase LOOPPACKETS (and perhaps SELECTORS as well), in the NETBEUI | |||
section of PROTOCOL.INI. | |||
The values I am using are 8 and 30 respectively, but others are running | |||
okay with 8 and 15. (may need to be increased to 50 to work). | |||
Performance problems on CM/2 Emulator Sessions with DCAF installed: | Performance problems on CM/2 Emulator Sessions with DCAF installed: | ||
Basically the symptom is that large LU 6.2 data or file transfer | Basically the symptom is that large LU 6.2 data or file transfer from DCAF (it's true for NVDM/2 as well) blocks 3270, LUA, 5250 or other LU 6.2 traffic. The symptoms are independent of the connectivity but are more visible on slower links such as SDLC and X.25. | ||
from DCAF (it's true for NVDM/2 as well) blocks 3270, LUA, 5250 or | |||
other LU 6.2 traffic. | CM/2 APAR JR08131 fixes this problem by documenting a new function that was added to CM/2 1.11 (WR06150), that is the use of fixed pacing. We recommend the use of this CM/2 function in such cases. | ||
but are more visible on slower links such as SDLC and X.25. | |||
CM/2 APAR JR08131 fixes this problem by documenting a new function | |||
that was added to CM/2 1.11 (WR06150), that is the use of fixed | |||
pacing. | |||
===Security Section=== | ===Security Section=== | ||
;DCAF Multiprotocol Security added with DCAF 1.32 | ;DCAF Multiprotocol Security added with DCAF 1.32 | ||
Controller--(NetBIOS)-->LAN Directory--(NetBIOS)-->Target | Controller--(NetBIOS)-->LAN Directory--(NetBIOS)-->Target | ||
Controller--(TCP/IP)-->LAN Directory--(TCP/IP)-->Target | Controller--(TCP/IP)-->LAN Directory--(TCP/IP)-->Target | ||
---- | ---- | ||
;DCAF Security Administrator wks HANG | |||
If using an Alias/Nickname file, all of the entries must align under the first entry to be processed correctly. | |||
---- | |||
If using an Alias/Nickname file, all of the entries must align under | ;DCAF Security Administrator fails with sending Security files to multiple authenticators: | ||
the first entry to be processed correctly. | |||
; DCAF Security Administrator fails with sending Security files to multiple authenticators: | |||
Change the message timeout value on the Controlling/Administrator workstation to a low value (e.g., 5) so that the message will time out. Default is "99" which means the operator must clear the message. | |||
---- | |||
;Failures distributing security files to Authenticators | ;Failures distributing security files to Authenticators | ||
If your Authenticator files (.ath) are seven (7) bytes long, then they are the defaults and the security files have not been received from the Administrator. | |||
If | If you get rc=7 error messages in combination with message EQN0343, the security authenticator expected by the target workstation is not the one that is trying to manage it. Reinstall the DCAF Secure Target workstation. | ||
If you get rc=7 error messages without the EQN0343 message, then you have the wrong files on the authenticator. Try replacing the *.ath files and redistributing to clear the problem. | |||
[[Category:Software Articles]] | |||
If you get rc=7 error messages without the EQN0343 message, then | |||
you have the wrong files on the authenticator. | |||
the *.ath files and redistributing to clear the problem. | |||
Latest revision as of 14:12, 19 August 2025
Article Info | |
---|---|
Author | Bruce Morris |
Date | 1996-06-18 |
OS Version | IBM OS/2 2.1 |
Companion File | N/A |
Source | [1] |
Last Updated: June 18, 1996
The following DCAF (Distributed Console Access Facility) hints are provided by Bruce Morris, SystemView Support Operations, Raleigh, NC. I hope you find them useful.
They are provided to help you resolve DCAF problems/questions and are provided "as is" without any warranty or guarantee. The file will be updated when time permits and when new hints are identified.
Any suggestions concerning this file or suggested additions should be sent to:
VNET address: BAMORRIS at RALVM14 INTERNET Addr: BAMORRIS@VNET.IBM.COM
- DCAF product Information
- CompID: 562221200 FESN: 0968318
Previous Releases/Latest CSD (Unsupported releases):
- DCAF 1.1/UB10971
- DCAF 1.2/UB10970
Supported Releases: DCAF 1.3
Latest Release: DCAF 1.32
Latest Corrective Service: CSD UB31597 (SYSLEVEL UB09850)
Note: DCAF 1.3 + CSD UB31597 is equivalent to DCAF release 1.32 and CSD UB31597 supersedes any previous CSD.
APARs for high impact or pervasive problems not fixed in latest CSD:
- None
DCAF information (fixes, text files, programs, etc.) are available for download from the IBM PCCBBS via:
- Phone: 919-517-0001
- Internet: WWW.pc.ibm.com or FTP.pc.ibm.com
DCAF packages are accessible to IBM employees thru IBM VNET with the following command: REQUEST <package name> FROM DCAFLEV2 AT RALVM14"
(Package Name of "LIST" will send you a current list of packages)
OPERATING SYSTEMS | SUPPORTED APPLICATIONS |
---|---|
Dos | Full Screen text mode |
Windows | Any but Full Screen Graphic apps |
Windows for Workgroups | Windowed applications only, No full-screen graphical or DOS environments |
OS/2 1.3 | Presentation Manager and OS/2 Full Screen Text Mode |
OS/2 2.1 | Presentation Manager, OS/2 Full Screen Text Mode MVDMs Full Screen Text Mode Seamless Windows (1) |
(1)Support of 'seamless' Windows means only windows apps that run on the OS/2 desktop are supported. Win-OS/2 Full Screen is not.
DCAF 1.3 CONFIGURATIONS:
1. Controlling------>Target (NEW WITH DCAF 1.3)
TCP/IP
2. Controlling------>LanDirectory(NO GW|)---->Target (NEW WITH DCAF 1.3)
TCP/IP TCP/IP
3. Controlling------>Gateway/LanDirectory---->Target (ALSO WITH OLD DCAF
APPC-or-APPN Netbios - only APPN is new
4. Controlling------>Target (ALSO WITH OLD DCAF
APPC-or-APPN - only APPN is new
5. Controlling------>Gateway/LanDirectory---->Target (ALSO WITH OLD DCAF
ACDI Netbios
6. Controlling------>Target (ALSO WITH OLD DCAF
ACDI
7. Controlling------>LanDirectory (NO GW|)---->Target (NEW WITH DCAF 1.3
Netbios Netbios
8. Controlling------>Target (NEW WITH DCAF 1.3
Netbios
9. Controlling------>LanDirectory(NO GW|)---->Target (NEW WITH DCAF 1.3
IPX IPX
10.Controlling------>Target (NEW WITH DCAF 1.3
IPX
Note: To run DCAF via Asynchronous modems a separate communications product is required.
Several communications programs can provide this support (e.g., CM/2 ACDI, CM/2 SNA Phone, LAN Distance, TCP/IP SLIP, etc.). CM/2 ACDI does not support data rates greater than 19,200 bps or PCMCIA/MWAV modems.
Start of Hints
General Section
Installing DCAF 1.32
To bring a workstation up to DCAF 1.32 level, this is what has to be done:
- Install DCAF 1.31
- Reboot
- Apply the CSD
- Reboot
- Run EQNCONF
Since new functions have been included, this CSD does not only upgrade files but also modifies files as the DCAF.INI and upgrades product's Databases.
To automate the process you can use a product like NvDM where you can schedule the sequence of the different installations and personalization (including the reboot).
Building Controller Directory
A package is available (DCAFCWD) which will allow you to build a DCAF 1.3 Controller workstation directory using a REXX CMD file instead of adding each workstation individually or writing a "C" program.
Setting DCAF Targets to use Video Device Driver mode
Issue command "EQNFRDDI /D" and then restart the Target. Verify mode by checking EQNPM.LOG.
DCAF Target starts in Monitor Mode and Active Mode greyed out:
After CSD UB20924 is installed lose ability to establish session with TGT wks in Active mode.
DCAF.INI file is corrupted. Delete DCAF.INI file and re-personalize the TGT wks to correct problem or get IC11618 fix.
EQN0185 error message on Windows Target (1% displayed):
APAR IC10084 is for Windows Target wks (INCLUDED in UB20924)
DCAF supported COMPAQ 1280P Display Adapter
New DCAF enabled Display Driver for the Compaq 1280p is available on COMPAQ BBS in file named SP0964. (COMPAQ BBS: 1-713-378-1418)
How to determine Video hardware on DCAF workstation:
CMD: QSYSTEM (included with CM/2) CMD: SVGA STATUS (From DOS fullscreen)
Things to look for to verify that DCAF is correctly installed:
- Check DCAF directory for files with .NEW extension (expect none)
- Try to rename EQNPMGRE.DLL (Should be locked by OS/2)
- Check OS2.INI file for PM_ED_HOOKS (Should be there)
DCAF Target changes to the OS2.INI file:
Three section updated or created:
Application Key User Data
PMGRE DISPLAYHOOK EQNPMGRE PM_ED_HOOKS MODULENAME EQNPMGRE SYS_DLLS Load EQNCLHOT
Mouse movement on WINDOWS target:
To speed up the mouse movements add the PBA=0 parameter to the target CONFIG.SYS.
DEVICE=<drive>:\<path>\DXMT0MOD.SYS ........ PBA=0
RESERVED message:
Message appears when you do not have IEEE 802.2 support configured in LAPS for the adapter you are using. (Should not occur after UB20924 CSD is installed)
DCAF 1.3 CID install to wrong drive using NetView DM/2
In the "Section Install", the token $(TargetDir) in /T: parameter of Parms row is not defined; so DCAF assumed as default for targetdir c:\dcaf13.
Device Independence for Controlling DCAF workstations:
A DCAF 1.31 controller can control both DCAF 1.31 and pre-DCAF 1.31 target workstations ... if the Controller workstation has a Video Device Driver which is DCAF enabled. (Use DCAFSVGA package to test - see start of file for where to get DCAF packages)
Unable to select COM port for ASYNC connection with WARP Connect
Problem occurs when running WARP Connect with Fixpack #17 or later installed.
DCAF APAR IC13487 corrects problem (In DCAF CSD #2 UB31597) @
Unable to write OS2.INI or OS2SYS.INI files with XGA, SVGA device drivers on Warp Connect. See OS/2 APARS:
APAR= PJ19564 SER= 011 MS WPSHLAPAR CANNOT WRITE TO INI FILES DUE TO EXCEEDING MAX FILE HANDLES. APAR= PJ21815 SER= 009 IN VIDEOAPAR RUNNING OS/2 WARP, USING THE S3_864 BBS DRIVERS WHILE DECAF IS LOADED SYSTEM CANNOT WRITE TO OS2.INI AND OS2.SYS INI IN SVGA
Deinstalling DCAF 1.2 with EQNINSDS /n command
DCAF 1.2 must be at UB09790 SYSLEVEL for this command to be supported.
How to monitor without Target notification:
On a OS/2 target, use OS/2 facilities to make use of a restricted shell on the OS/2 Target workstation and make the DCAF Target window invisible.
For DCAF full-screen sessions, change the target personalization so that the status area is displayed on row Number 0.
Replacing a locked DCAF module on a remote system
For example, EQNCM03.DLL cannot be replaced on the target wks, during a DCAF TCP/IP session (the module is locked).
There are at least two ways of replacing this module from controller:
1)-put in the first row of startup.cmd something like that:
copy (path):/EQNCM03.DLL (path):/dcaf13 (where EQNCM03.DLL is the DCAF module and (path):/dcaf13 is the directory of DCAF and "/" is really a backslash) -add a line at the bottom of STARTUP.CMD in order to start the DCAF target from STARTUP.CMD -reboot the target and restart DCAF session.
2)-have a DCAF session via appc, acdi, netbios or ipx
-close the TCP/IP protocol from the target user interface (now the EQNCM03.DLL is not locked and can be replaced) -replace the EQNCM03.DLL -close the session and have a DCAF session via TCP/IP.
Protocol Section (TCP/IP, NetBIOS, APPC...)
Releases of TCP/IP which should work with DCAF 1.31:
- OS/2:
- IBM TCP/IP V2.0 plus CSD UN64092
- IBM TCP/IP V3.0 provided with WARP Connect
- Windows:
- IBM TCP/IP V2.1.1 or later
- MS TCP/IP for Windows for Workgroup 3.11
- Novell LAN WorkPlace for DOS version 4.2 or later
Using Host names with DCAF 1.31
- If the customer uses the IP address it works
- If the customer uses the hostname it needs the nameserver.
TCP/IP Port number on Target
all Targets can use 2501 as local port number. You need to change it if locally there is another TCP/IP program that uses the same port number.
Termination Problem with TCP/IP using MPTS stack on LAN Server 4.0
Apply fixpack WR08150 for MPTS TCP/IP stack
DCAF TCP/IP hangs in INITIATING when crossing Bridge/Routers:
If there are Bridges/Routers between DCAF workstations when attempting TCP/IP connection the Controlling workstation may hang in INITIATING because data traffic is not getting thru router.
Change MTU size from 4400 to 1500 on both workstations may solve this problem.
Note: sometimes the size may have to be even smaller (e.g., 1490 for Ethernet)
DCAF 1.3 TCP/IP DOS/WINDOWS Support
DCAF 1.3 in DOS/WINDOWS environment supports TCP/IP that is compliant with WinSocket architecture.
If your wks has the WINSOCK.DLL, then it should be compliant.
CM/2 runs out of resources after starting and stopping DCAF sessions
CM/2 SNASVCMG LU6.2 Session not released - CM/2 APAR JR08314 applies This fix should be in CM/2 latest FixPac available on CM/2 BBS at (919)543-8200 (Current latest fixpac is AP111 for CM/2 1.11).
APPC Error Cmd Txt=1600 RC=0002 SRC=00000509 - Unable to allocate a LU6.2 conversation
Check the following Define_TP parameters:
- Change the NDF file on the Target to include the keyword PARM_STRING as follows:
- PARM_STRING(LU62 /m) (attention case sensitive)
- Check the FileSpec and make sure that the directory and path point to your current DCAF subdirectory.
- Check the name (e.g., IBM.DCAF.TARGET.TRANSACTION.PROGRAM) and make sure that there are no misspelled words and that it is exactly as shown in the DCAF Installation Guide.
CM/2 ACDI CMD TXT:02 RC:000C with PCMCIA modem
PCMCIA modems are not supported by CM/2 ACDI PCMCIA modems are supported by SNA Phone in CM/2 1.11 or LAN Distance
CM/2 ACDI CMD TXT:02 RC:00F1
Return Code 00F1 indicates that an OS/2 error was returned to CM/2. The OS/2 error log provides additional information on this error and the OS/2 function call and return code can be looked up in the OS/2 Control Programming Ref. Follow normal OS/2 problem determination procedures.
ACDI Return Code 00FF
You have not configured or started CM/2 ACDI support. Make sure you booted your workstation after configuring ACDI and that ACDI is started by a "CMQUERY" command at an OS/2 command prompt.
DCAF msg EQN0512 when attempting ACDI dial connection:
This message indicates that you probably do not have your modem initialization strings properly defined in the DCAF controlling or target workstation.
Normally the modem may dial and the lights "flash" several times, the speaker goes off, but you never see the "receive data" light come on indicating that the screen image is being received.
Generally it helps to have the same brand and model of modem on both the controlling and target workstation.
Select the Hayes 2400 SmartModem in the CM/2 set-up then change the default modem initialization string to one supported by your modem.
Even though your modem may support the "Hayes AT command set" or is "Hayes compatible", you still must build the initialization string from the documentation provided by the modem manufacturer.
Start by getting a basic initialization string working, and then if you want to experiment to enhance you performance you can try different values.
Generally you should select a string which supports LOCAL HARDWARE FLOW CONTROL and disables COMPRESSION. A common string might be:
General string: "AT&F&C1&D2&K3" USRobotics Sportster: "AT&F1&C1&D2&K0&A0"
ACDI is limited to 19.2 kbps, so set the DCAF speed to 19.2 regardless of the speed of the modem.
VTAM mode definition for DCAF when using SNA BackBone network:
VTAM does not care about the contents of the mode, just that it should exist.
So the MODEENT should look something like:
DCAFMODE MODEENT LOGMODE=DCAFMODE
Just that * no additional parameters.
DCAF using NETBIOS over SNA using AnyNet
The following APAR has been closed and is available to all customers:
- APAR IC07956 for AnyNet/2 NetBEUI over SNA V1.0
Problems fixed by this APAR:
AnyNet/2 NetBEUI over SNA V1.00 as shipped does not support LAN NetView Management Utilities for OS/2 (LMU/2) or Distributed Console Access Facility (DCAF). You must apply this fix if you wish to run these programs over SNA using NetBEUI over SNA 1.00.
With this fix, AnyNet/2 NetBEUI over SNA V1.00
- will support LMU/2 and DCAF
- will allow multiple processes on a machine to add the same group name.
- will allow a process to call from a name that a different process had added (this should not be allowed, but some programs depend on it).
- eliminates timing windows where data sent using very short-lived
- will accept status queries with very large buffer sizes.
DCAF 1.3 TGT on Warp Connect
If using Novell Netware Requester 2.11, apply APAR IC09747.
Performance Section
NETBIOS Performance Problem with LAPS WRU7045
There a fix for the NETBIOS loopback connection performance problem (controlling a DCAF NETBIOS target on the same wkstn where DCAF GW/LAN Dir. is installed *IS* a NETBIOS loopback connection) for LAPS WRU7045 was suggested:
- Increase LOOPPACKETS (and perhaps SELECTORS as well), in the NETBEUI section of PROTOCOL.INI.
- The values I am using are 8 and 30 respectively, but others are running okay with 8 and 15. (may need to be increased to 50 to work).
Performance problems on CM/2 Emulator Sessions with DCAF installed:
Basically the symptom is that large LU 6.2 data or file transfer from DCAF (it's true for NVDM/2 as well) blocks 3270, LUA, 5250 or other LU 6.2 traffic. The symptoms are independent of the connectivity but are more visible on slower links such as SDLC and X.25.
CM/2 APAR JR08131 fixes this problem by documenting a new function that was added to CM/2 1.11 (WR06150), that is the use of fixed pacing. We recommend the use of this CM/2 function in such cases.
Security Section
- DCAF Multiprotocol Security added with DCAF 1.32
Controller--(NetBIOS)-->LAN Directory--(NetBIOS)-->Target Controller--(TCP/IP)-->LAN Directory--(TCP/IP)-->Target
- DCAF Security Administrator wks HANG
If using an Alias/Nickname file, all of the entries must align under the first entry to be processed correctly.
- DCAF Security Administrator fails with sending Security files to multiple authenticators
Change the message timeout value on the Controlling/Administrator workstation to a low value (e.g., 5) so that the message will time out. Default is "99" which means the operator must clear the message.
- Failures distributing security files to Authenticators
If your Authenticator files (.ath) are seven (7) bytes long, then they are the defaults and the security files have not been received from the Administrator.
If you get rc=7 error messages in combination with message EQN0343, the security authenticator expected by the target workstation is not the one that is trying to manage it. Reinstall the DCAF Secure Target workstation.
If you get rc=7 error messages without the EQN0343 message, then you have the wrong files on the authenticator. Try replacing the *.ath files and redistributing to clear the problem.