home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ub10970.zip
/
UB10970A.AVL
< prev
next >
Wrap
Text File
|
1994-10-12
|
34KB
|
966 lines
UB09790 - README
________________
This readme file contains some solutions
for problems found during DCAF testing and updated information
that did not make the printed publications.
It is divided into the following topics:
o Configuring the APPC Communications More Easily
o Deinstalling DCAF Version 1.0 Automatically
o Deinstalling DCAF 1.2 Automatically
o Documentation Correction: Installing and Using DCAF, Express Setup
Scenario 1: Controlling and Gateway on the Same Workstation
o Enhancements for DCAF Security
o Identifying a Security Authenticator for a Secure
Target using the Lan Adapter Address (LAA)
o Installing the Corrective Service Diskette (CSD)
Fixes on a DOS Target
o Installing the CSD Fixes on a Windows Target
o Installing the CSD with the Corrective Service Facility
o Installing DCAF Components Directly and Using the
Packager on the Same Workstation
o Personalization for Secure Gateways
o Personalization Utilities
o Listing Fixes Included in This CSD
CONFIGURING THE APPC COMMUNICATIONS MORE EASILY
You do not have to define the
CNOS entry in the .NDF configuration file
for the Communications Manager.
Therefore, the paragraph "Updating the CNOS Definitions
Profile" on page 108 of the DCAF Installing
and Using manual (SH19-6838) is superfluous.
DEINSTALLING DCAF VERSION 1.0 AUTOMATICALLY
o When you use the DCAF Packager to upgrade
from DCAF Version 1.0 to DCAF 1.2 remotely,
you must first deinstall DCAF Version 1.0
from the workstation.
To optimize this process, this CSD enables
you to deinstall DCAF 1.0 automatically
with two OS/2 executable files,
EQNDST10.EXE and EQNINDST.EXE.
Note: This program does NOT deinstall the DCAF
Version 1.2.
To start deinstallation, do the following:
1. Copy the two OS/2 executable files,
EQNDST10.EXE and EQNINDST.EXE, onto the
workstation where you want to deinstall DCAF.
2. At the command prompt or in a command
file (.cmd), type:
EQNDST10.EXE.
Note: If you have the DCAF 1.03 French
version installed, type:
EQNDST10.EXE /F
3. When the program stops running,
restart the workstation.
4. To erase all trace of DCAF,
delete the EQNINDST.EXE file from the
boot drive of the workstation and
restart the workstation again.
EQNDST10.EXE detects DCAF Version 1.0, deletes the DCAF
group, updates the CONFIG.SYS file and deletes all
the DCAF files except the ones in use.
It also installs EQNINDST.EXE on the workstation.
EQNINDST.EXE, which runs automatically when
the workstation is restarted,
deletes the remaining DCAF files.
DEINSTALLING DCAF 1.2 AUTOMATICALLY
o The DCAF 1.2 deinstallation component has been improved so that
it can be run remotely without requiring any user intervention.
The new deinstallation procedure must be started with parameter
/n to run without prompting the user for confirmation.
If no parameter is specified, the deinstallation requires user
intervention to proceed.
DOCUMENTATION CORRECTION: INSTALLING AND USING DCAF, EXPRESS SETUP
SCENARIO 1: CONTROLLING AND GATEWAY ON THE SAME WORKSTATION
o In Phase 2, For Workstation 1, Task 1, substitute
steps 10 through 18 in the DCAF 1.2 publication
with the following steps:
10. The Local Node Characteristics window appears.
For Network ID, type your network ID (you can get it from you
system administrator).
For Local node name, type CONTROL.
For Local node ID (hex), type 00001.
Press the Options... push button.
11. For Local node alias, type CONTROL.Press the OK push button.
12. The Communications Manager Profile List Sheet window reappears.
From Profile Name, select SNA connections and
press the Configure... push button.
13. The Communications Manager Profile List Sheet window reappears.
From Profile Name, select SNA features and press the Configure... push
button.
14. The SNA Features List window appears.
From Features, select Local LUs.
Press the Create... push button.
(To update an existing LU definition, select the
LU definition from Definition, and choose
the Change... push button.)
Continue from step 19 in the Using and Installing guide.
ENHANCEMENTS FOR DCAF SECURITY
o Some utilities are provided for the security components:
1. Key-encrypting Key Update Utility
---------------------------------
This utility allows to update one or more Authenticators'
Key-encrypting keys at the Administrator and the Authenticators
workstations from the command line.
The utility consists of two modules: one is run on the
Administrator workstation, the another on the Authenticator
workstation.
Administrator module: EQNUTAD1.EXE
This utility takes as parameters the name of a text file which maps
authenticator names to new KEKs specified as 32 hexadecimal
characters (default eqnutad1.txt) , the column position of an
authenticator name in each line of the file (1-9999, default 1), the
size of the authenticator name (1-9999, default 12), and the column
position of a new KEK in each line of the file (1-9999, default 13).
The length of the new KEK must be 32 characters.
If a longer key is specified in the file, only the first 32 chars
are taken into account, the others being ignored. If the keys
specified are shorter than 32 chars, an error will be displayed.
The utility reads the information in the file, searches for the
authenticator name in the administrators authenticator's database,
and if found updates the KEK for the authenticator to the specified
new KEK.
Authenticator workstation (for workstations with an IBM 4755
cryptographic card):
When executed at the authenticator, this part of the utility
indicates to the authenticator that the KEK has been changed and
that it can be found in the 4755 crypto card key label DCAFKEK.NEW.
This needs to be executed at the authenticator's workstation AFTER
the KEK has been stored in the DCAFKEK.NEW label by the customer
through whatever means he chooses.
2. Change Retry Limit for Password
-------------------------------
This utility EQNUTAU2.EXE updates the retry limit on a security
Authenticator from the command line. The retry limit is the maximum
number of attempts to be authenticated with an invalid pass phrase
before the UserID is revoked. The utility takes the new retry limit
as a parameter, the valid range is 1-255. No default is provided.
IDENTIFYING A SECURITY AUTHENTICATOR FOR A SECURE TARGET USING THE
LOCALLY ADMINISTERED ADDRESS (LAA)
o Now you can use either the security authenticator
LAA or universally administered address (UAA)
to identify a security authenticator for any secure target.
o If, for a secure target, you enter an LAA for the
security authenticator, remember to define it
when you configure the Communications Manager
on the authenticator workstation.
o The Authenticator UAAs for Target window and the Security Data
window for the secure targets differ slightly from their
originals as shown in the DCAF publications.
The new Authenticator Adapter Address window and the Security
Data window contain the Primary and Secondary Authenticator
Adapter Addresses fields. You can enter either the LAA or
the UAA of the authenticators assigned to the secure target.
o If a secure target and a security authenticator reside on the
same workstation, you must define the same kind of adapter address
on the target for both the target and the security authenticator.
For example, if, when personalizing the DCAF LAN parameters for the
target, you select LAA for the target adapter address, you must
enter an LAA for its security authenticator on the Authenticator
Adapter Addresses window.
INSTALLING THE CSD FIXES ON A DOS TARGET
o The CSD diskettes update all DCAF modules
installed on any OS/2 workstation automatically, but
for a DOS target you must use the packager.
To update a DOS workstation, do the following:
1. Run the CSD on the OS/2 workstation where the
DCAF packager component is installed.
2. Make a package for a DOS target.
3. Install the package on a DOS workstation.
INSTALLING THE CSD FIXES ON A WINDOWS TARGET
o Diskette three of the DCAF CSD completely replaces diskette
four of the DCAF 1.2 diskettes.
INSTALLING CSD WITH CORRECTIVE SERVICE FACILITY
The Corrective Service Facility can be installed one of two ways. If
you want to install the CSD using the standard defaults,
a default response file has been created enabling you to
use diskette one and install the CSD.
If you want to change the default set of products or
the default set of directories, insert CSD diskette one in the
A: drive and type A:\SERVICE from an OS/2 command prompt. The main
window contains a list of products that are found on the system
which are eligible for service. Select those products you want to be
serviced by highlighting the appropriate entries in the products list.
All eligible products are initially selected.
NOTE: Before servicing the DCAF, you must close the existing
processes in order to avoid having some files remain
locked, such as the LAN Directory.
To view the current levels of the products on your system, select CURREN T
from the LEVELS menu. To view the new levels on the
corrective service diskettes, select NEW from the LEVELS menu.
The service utility updates files in a set of directories associated with
each selected product. To view or change the set of directories,
choose SELECT DIRECTORIES from the OPTIONS menu.
After you make all your selections, select SERVICE to start the service
process.
You cannot terminate the service process after it is started.
When the service process ends, restart the workstation.
Use the service log to verify the installation:
<BOOTDRIVE>:\OS2\INSTALL\SERVICE.LOG
where <BOOTDRIVE> is the partition from which you IPLed
Subsequent installations are appended to the service log.
LIMITATIONS: You can service the IBM model 9557 and ThinkPad only
through the command line using the command A:\SERVICE.
INSTALLING DCAF COMPONENTS DIRECTLY AND USING THE PACKAGER ON THE
SAME WORKSTATION
o When you install DCAF directly and, subsequently, install
DCAF components using the packager on the same workstation,
any original DCAF personalization options
can be substituted by the personalization options
in the DCAF package. This problem most likely occurs when
you install a security authenticator directly
and, subsequently, other components using the packager
on the same workstation.
To avoid this problem, install the components in the
following order:
1. Create a DCAF package with all the desired components.
2. Unpack the package on the workstation.
3. Restart the workstation.
4. Install the Authenticator component from the DCAF diskettes.
5. Restart the workstation.
6. Apply the DCAF CSD to the workstation.
PERSONALIZATION FOR SECURE GATEWAYS
o The Authenticator name in the personalization for a secure Gateway
is now case insensitive, while the DCAF Installing and Using manual
(SH19-6838) says it is case sensitive.
PERSONALIZATION UTILITIES
o The new DCAF contains some utilities to update some personalization
parameters from the command line. The utilities are the following:
1. Utility for updating the Authenticator name
-------------------------------------------
This utility EQNRPLAN.EXE updates the Authenticator name for
the following DCAF components:
- Secure Gateway
- Authenticator
Since the Authenticator name cannot be longer than 12 chars, if
a longer name is specified, it is truncated to 12 chars.
The string is case sensitive.
Invoke this program from the directory where the DCAF is installed.
When complete, remember to restart the workstation.
Example:
========
to change the Authenticator name to AUTHNEW, type:
<drive>:\<directory>\EQNRPLAN AUTHNEW
2. Utility for updating the LAN Directory name
-------------------------------------------
This utility EQNRPLLD.EXE updates the LAN Directory name for the
following components:
- Gateway
- Target for OS2
- LAN Directory
Since the LAN Directory name cannot be longer than 12 chars, if
a longer string is passed to the program, it is truncated to 12
chars. The string is case sensitive.
Invoke this utility from the directory where the DCAF is installed.
When complete, remember to restart the workstation.
Example:
========
to change the LAN Directory name to LANNEW, type:
<drive>:\<directory>\EQNRPLLD LANNEW
3. Utility for updating the Authenticator Adapter Addresses
on a secure OS2 target workstation
--------------------------------------------------------
This utility EQNRPLAA.EXE updates the Authenticator Adapter
Addresses for a secure OS2 Target workstation.
This program updates two parameters, the primary and secondary
Authenticator Adapter Addresses on the secure Target.
The first parameter is required, the second is optional;
if you specify only the first parameter, then the program
assumes that the second parameter matches the first.
If you include more than two parameters, the program takes
only the first two.
Parameters must be exactly 12 hexadecimal characters long.
if you enter a longer string, the program truncates it
to the 12th character.
The string(s) must be valid Adapter Address(es).
In order to be able to run this utility successfully, you
must type "***" for both the primary and secondary authenticator
adapter addresses when installing the Target or when creating
the package for it.
Notes:
======
- Make sure that the Target component is not running when you
run the utility
- Invoke the utility from the directory where the DCAF is installed
- This utility can be successfully run on the same target only
once.
Example:
========
to change the Authenticator Adapter Addresses to:
Primary AA: 10005AAE9167
Secondary AA: 400000000001
type:
<drive>:\<directory>\EQNRPLAA 10005AAE9167 400000000001
LISTING OF FIXES INCLUDED IN THIS CSD (UB10970)
o This CSD contains fixes for the following
APARs:
#IC06149
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNINST.EXE, EQNINSLD.EXE
PROBLEM SUMMARY: If you install a DCAF package on
a workstation where NDM/2 is running,
the following error occurs: "DCAFDEF.CMD
A program caused an integer divide by zero exception."
#IC06186
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNINST.EXE, EQNINSSV.EXE
PROBLEM SUMMARY: SYS3184 (divide by zero) error occurs
on the DCAF packager component, running on an OS/2
workstation with NDM/2 on. The trapping module is
EQNINSSV.EXE.
#IC06283
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNDD.EXE
PROBLEM SUMMARY: If you install the DCAF DOS target
code on a LAN server, redirect the DOS target to
a shared drive to access the DCAF target code, and start
the DCAF target code, the following problem occurs:
DCAF DOS attempts to write the error log to the
A drive. If a diskette is placed in the A drive, the
DCAF target starts correctly, and writes the error log
to the A drive on the local machine.
#IC06360
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSERV.EXE, EQNDISP.DLL
PROBLEM SUMMARY: From a DCAF Administrator transfer
the security files to the remote Authenticators.
If these data include an incorrect address for the
corresponding target, the following data transfer
causes the 673 (rc=7) error message to come up on
the Controlling/Administrator workstation, then
the file trasfer hangs.
#IC06371
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNGWDIR.EXE
PROBLEM SUMMARY: The DCAF Lan Directory component
traps while reading a nickname file. The same DCAF
component causes a random SYS2175 trap on OS/2 2.1
workstations.
#IC06372
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNSERV.EXE, EQNSVGRE.DLL, EQNRCUT.DLL,
EQNTGMAI.DLL
PROBLEM SUMMARY: From a DCAF Controlling start a DCAF
session with an OS2 DCAF Target and terminate it.
Repeat this operation up to 10 times. On
controlling and target an error message (cannot open
log file) appears and the target hangs.
#IC06379
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNCM01.DLL
PROBLEM SUMMARY: The second time you attempt
to start a DCAF direct APPC session from a
controlling DCAF Version 1.2 to a target DCAF
Version 1.03, the following error occurs:
"EQN0516E: An APPC error occurred. APPC command
text=100. APPC return codes text= 0003 00000004."
#IC06380
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNPR00.DLL
PROBLEM SUMMARY: The DCAF packager does not add
a section in the DCAF.INI file properly, thus
causing a trap in the EQNGWAUD module.
#IC06381
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGUI.EXE, EQNTGAUT.EXE
PROBLEM SUMMARY: This is an enhancement to the way the
DCAF target window is displayed when the EQNTGAUT is
called. You can now start the DCAF target window
minimized by specifying /m as second parameter for
the EQNTGAUT.EXE command.
#IC06382
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNMSG.DLL
PROBLEM SUMMARY: The display time parameter for DCAF
messages, selected during the initialization, was
ineffective for the controlling and
Target workstations in the OS/2 2.1 environment.
#IC06383
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNINGRP.DLL
PROBLEM SUMMARY: When you install the packager, the
EQNPMGRE.DLL that is copied onto the workstation is
always the one for 16 bits. The installation does not
check which level of the operating system is installed
on the workstation
IMPORTANT: To make the fix effective, replace the
EQNINGRP.DLL module on the DCAF installation diskette.
#IC06392
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGUI.EXE
PROBLEM SUMMARY: This is an enhancement to the way the
DCAF ACDI target acts when the Async. link drops.
Now the target goes back to the OPEN state, instead of
closing the communication.
#IC06422
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNINST.EXE
PROBLEM SUMMARY: Uncorrect updating of the CONFIG.SYS
file when the DCAF target installation is performed
by using the packager component.
IMPORTANT: To make the fix effective, replace the
EQNINST.EXE module on the first DCAF installation
diskette.
#IC06427
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNDD.EXE
PROBLEM SUMMARY: Force a remote reboot of a DOS
target workstation from the DCAF controlling component
("Restart target wks" option): sometimes the DOS
target does not return available in the list of the
available targets.
IMPORTANT: If the DOS target was installed with the
secure option, the EQNDD.EXE file must be replaced on
#IC06431
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: INSTALL.EXE
PROBLEM SUMMARY: This is a problem in the DCAF Windows
target personalization. Since only UAA addresses were
accepted, a formal check on the first digit in the
address was performed, that failed if it was different
from 1. Now the check accepts any valid address.
#IC06438
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGMAI.DLL, EQNRCUT.DLL, EQNRCKB.EXE
PROBLEM SUMMARY: Trap on the DCAF target workstation
at boot time if the MVDM support in not installed
(OS/2 2.1 environment).
#IC06522
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSERV.EXE
PROBLEM SUMMARY: By an application using the DCAF APIs,
establish a DCAF session, then start a file transfer
from the "File transfer" option of the command line.
The file transfer completes OK, but no message comes
up, and the buttons don't get reactivated.
#IC06529
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNRCKB.EXE
PROBLEM SUMMARY: During a DCAF session between a DCAF
controlling and a target, in active state, if you click
on the mouse BUTTON 2 in the target client area, the
mouse movements become extremely slow.
#IC06584
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNSF00.DLL, EQNSFPAR.EXE
PROBLEM SUMMARY: "280" Error message logged in the
EQNCOMM.LOG file if the link record file includes
more than 1000 link record items.
#IC06589
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNRCUT.DLL
PROBLEM SUMMARY: During a DCAF session between a
DCAF controlling and a DCAF target, enter the
WIN-OS2 Full Screen environment from the Command
Prompt folder: if the target workstation runs in
XGA mode, the controlling will display a white panel
instead of the "unsupported mode" black panel.
#IC06651
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNINST.EXE, EQNINCPY.DLL
PROBLEM SUMMARY: On a workstation having the DCAF target
and the packager installed, start both the components
and then try packaging a OS/2 target package: about at
the end of the packaging process, the error message:
"EQN0156: Internal processing error. Call: DosOpen, rc:32"
pops up. The package gets created OK, but there might be
impacts on the security environment.
#IC06697
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNRCKB.EXE
PROBLEM SUMMARY: Interference problems between DCAF
and DEC PathWorks.
#IC06811
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGUI.EXE
PROBLEM SUMMARY: When you use a tool to change the
attributes of the DCAF target entry in the task list,
the changes disappear when a DCAF session starts.
#IC06826
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGUI.EXE
PROBLEM SUMMARY: If you maximize, then minimize the
DCAF window on the controlling workstation during an
active session, you can not restore it again from the
task list.
#IC06875
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNMAIN.EXE
PROBLEM SUMMARY: If you close the DCAF controlling
component without terminating the DCAF session, the
DCAF controlling icon in the DCAF folder appears as if
the component were still running.
#IC06905
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNGWDIR.EXE
PROBLEM SUMMARY: The EQNGWDIR.DAT file on the LAN Directory
component loses target nickname information.
#IC07048
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNTGMAI.DLL
PROBLEM SUMMARY: The DCAF target file remains in use
after you close the target, if it is secure and an
attempt to start a DCAF session with that target has
been made through an illegal authenticator.
#IC07053
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNTGMAI.DLL
PROBLEM SUMMARY: A file transfer from controlling to
OS/2 target fails with error message "EQN0617E:
Insufficient disk space on the target workstation.
Correct it and retry." when there is enough space
on the specified destination drive but not enough on
the C: drive.
#IC07105
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNCD.DLL
PROBLEM SUMMARY: During a DCAF session, a SYS3175 error
occurs on the Controlling workstation during a refresh
of the target screen.
#IC07106
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSERV.EXE
PROBLEM SUMMARY: During a session, some OS/2 hot keys
(such as ALT-PF11 and SHIFT-ESC) do not have an effect
on the OS/2 target.
#IC07329
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSERV.EXE, EQNSVGRE.DLL
PROBLEM SUMMARY: When the controlling user sends the SHIFT-PF1
to the target workstation, there is no effect.
#IC07332
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSCNBG.DLL
PROBLEM SUMMARY: When you install the security authenticator
on a workstation without a DCAF target, the authenticator does not
allow any sessions.
#IC07384
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNCM00.DLL
PROBLEM SUMMARY: During an ACDI session, you receive the
message "Invalid Device Handle".
#IC07396
EXTERNAL SYMPTOM: Abnormal End.
COMPONENT: EQNINNEW.EXE
PROBLEM SUMMARY: The workstation ends abnormally at
boot time after you install any level of DCAF 1.2.
#IC07404
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSCADM.EXE
PROBLEM SUMMARY: The DCAF Administrator does not
update the expiration date when controlling users change
their pass phrases.
#IC07438
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNPROO.DLL
PROBLEM SUMMARY: In the access levels table of a non-secure
OS/2 target, selections for the options "Controlling user
sends file" and "Controlling user receives files" are swapped.
#IC07440
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSERV.EXE, EQNSVGRE.DLL
PROBLEM SUMMARY: The OS/2 2.1 Screen Lock appears while
the controlling user is working on the target session window.
#IC07443
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNSERV.EXE
PROBLEM SUMMARY: If an user who is not authorized to
transfer files to or from the target uses the DCAF APIs
DCAFXFer for a secure target, the file transfer starts
but then stops. The controlling user receives abnormal
end SYS3175.
#IC07445
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNGWDIR.EXE, EQNGWOPN.EXE
PROBLEM SUMMARY: On some 66 Megahertz workstations the
DCAF personalization parameters are lost everytime the
worsktation is booted if either the LAN directory or
the gateway are installed.
#IC07459
EXTERNAL SYMPTOM: Incorrect Output.
COMPONENT: EQNSCADM.EXE EQNSCLOG.DLL
PROBLEM SUMMARY: If the Security administrator is running
on a workstation that has an IBM 4755 cryptographic card
you receive processing error message "EQN0306E: Error
returned from Transaction Security System. Return code=8.
Reason code=12." when the Controlling user requests a
pass phrase change.
#IC07461
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNINST.EXE
PROBLEM SUMMARY: If there is not enough memory available,
the DCAF installation process terminates with a SYS3175
error.
#IC07464
EXTERNAL SYMPTOM: Abnormal end.
COMPONENT: EQNSCNBG.DLL
PROBLEM SUMMARY: The Authenticator fails with NetBIOS
error after it rejects many consecutive attempts to start
secure DCAF sessions.
