DSNlink DSNA235 DSNlink for Tru64 UNIX V2.3E ECO Summary
TITLE: DSNlink DSNA235 DSNlink for Tru64 UNIX V2.3E ECO Summary
Modification Date: 13-OCT-1999
Modification Type: New Kit
Copyright (c) Compaq Computer Corporation 1999. All rights reserved.
PRODUCT: DSNlink for Tru64 UNIX
OP/SYS: Tru64 UNIX
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: DSNA235
ECO Kits Superseded by This ECO Kit: NONE
ECO Kit Approximate Size: 14,840 Blocks
DSNA235.TAR - 14,840 Blocks
Kit Applies To: DSNlink for Tru64 UNIX V2.3E
Tru64 UNIX V4.0b - 5.0
System/Cluster Reboot Necessary: No
Installation Rating: INSTALL_UNKNOWN
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for DSNlink for Tru64 UNIX V2.3E on Tru64 UNIX
4.0b through 5.0. The DSNlink Release Notes contain a complete
explanation of this release. Below is a brief description of problems
addressed in this kit:
PROBLEMS ADDRESSED IN DSNA235:
o X.25 Fixes
- DSNlink can now communicate through X.25 router nodes. The
local DTE address is now sent across as the first message.
This should bypass any network problems where routers remove
the address and/or subaddress.
o Modem Fixes
- The dsnmmgr show line command did not include information about
the HDLC layer.
- The dsnmmgr zero line command has been added to reset the counter
fields to zero in the HDLC statistics display for a modem line.
- Messages from using the modem with DSNlink have been improved.
- The dsnmmgr test wire command generated a device error message.
- Several of the modem scripts went into a loop between the script's
last two sections when the value 0 was not returned by the modem
after receiving the modem-specific commands.
- Modem script errors caused modem connections to fail because not
all result codes were trapped and interpreted.
- Links sometimes stuck on a modem line in the DONE or ABORT state.
This happened when the line was in the ONLINE or LISTENING states.
o File Copy Fixes
- When customers attempted to delete their copy of a file after
copying it to Compaq, the -d option was not recognized.
- The dsncopy command did not use the Support Center specified
in the -S option.
- File Copy server log files, /usr/lib/dsn/logs/dsn_file_server.log,
contained debugging information in addition to the file copy records.
- The Monitoring and Performance History (MPH) analysis tool did not
submit files for processing on the host.
- The Analysis Tool option did not work unless you supplied a service
request number.
- File Copy ignored the local authorizations file and allowed all
DSNlink users to use File Copy.
o Interactive Text Search Fixes
- The host software caused JACKETMSGCORRUPT errors.
- When customers with access to many databases entered the show
database command and then quit the listing, the quitting process
took a long time because the server continued to send the entire
database list.
- When exiting ITS, there was a long pause before the system prompt
appeared.
- ITS ignored the settings for pagination, view, and highlight.
o Network Exerciser
- The Network Exerciser measured the message transfer rate in
bytes per second (Bps).
o Service Request Application Fixes
- The Support Center option was ignored by dsnaug, dsncreate,
dsnfetch, dsnreview
- After successfully submitting a service request to the host, a
prompt appeared asking you to Click Mail for a confirmation
message. However, in the command line interface, there is nothing
to click on.
- If you attempted to fetch a list of closed service requests from
a host that does not provide such lists, an error message window
appeared and the process hung. The process had to be stopped from
the command line.
- In the local authorizations file, entries that allow access to
the Service Request application, dsn_sra, incorrectly produced
"You are not authorized to use this application" messages.
- In the DECwindows Motif interface, when errors occurred connecting
to the host followed by the user clicking on something in the window,
the application stopped and generated random application termination
errors.
o Multiple Application Fix:
- DSNlink could not start applications if there was a missing closing
quotation mark in the final entry of any of the following files:
o dsn_config.dat, the configuration file
o dsn_remote_auth.dat, the remote authorizations file
o dsn_local_auth.dat, the local authorizations file
The following are enhancements to DSNlink Version 2.3E:
o A new command displays the DSNlink Version Number.
o The modem scripts supplied in DSNlink Version 2.3 for Compaq's DIGITAL
UNIX have been updated to support additional Hayes and Hayes-compatible
modems, Multi-Tech modem script changes, and scripts have been added
o New mail parameters for cross-platform consistency now allow customers
who have DSNlink running on various operating systems to use the same
parameters on each system to specify who gets communique mail from
Compaq.
o You can now adjust the pipeline depth in the Network Exerciser using the
command dsnnetex -depth.
o Options have been added to the dsnmmgr test command. The dsnmmgr test
command allows you to test your modem line.
o Customers can mail themselves a copy of the confirmation message that
appears when they augment a service request.
o The ITS inactivity timer is suspended while customers are extracting
an article to a file.
o The DSNlink Version Number has been added to log files.
o When a modem line is initialized, the modem script is now recorded in
the logs or included in messages.
INSTALLATION NOTES:
If you have a previous version of DSNlink on your system, you must
deinstall it before installing DSNlink Version 2.3E. If the previous
subsets remain in place, the installation fails. For more details,
see the DSNlink Version 2.3E Installation Guide.
The deinstallation procedure removes the modem scripts in
/usr/lib/dsn/modem. If you modified DSNlink Version 2.3 scripts and
want to keep them, rename or move them before reinstalling DSNlink.
DSNlink Version 2.0 scripts are obsolete.
1. Become root and create a kit area on your disk by making a
kit directory and extracting the kit archive. For example:
# mkdir kit
# cd kit
# tar xvf ../dsna235.tar
.
.
.
2. Uncompress and print or display the DSNlink Version 2.3E
Installation Guide. This command uncompresses the PostScript
version of the guide:
# uncompress dsna235_iguide.ps.Z
The text version of the guide is dsna235_iguide.txt.Z.
3. Install the Version 2.3E kit using setld. Refer to the
instructions in the DSNlink Version 2.3E Installation
Guide.
During the installation, you will create an MD5 authentication
key. This is the key assigned by the Electronic Access Support
Team for your access number. Protect this key as you would a
password!
4. Complete the appropriate postinstallation tasks as
described in the DSNlink Version 2.3E Installation Guide.
The disk space requirements for loading DSNlink software subsets are as
follows. To determine if your system has enough disk space, use the df
command.
Size
After
Kit Size Installation /usr /var
7.3 MB 16.0 MB 14.0 MB 2.0 MB
The DSNlink installation procedure does the following:
1. Presents an Electronic Service Tools agreement. If you agree
to the terms, the installation procedure continues.
2. Checks for the supported versions of Tru64 UNIX, Versions
4.0b, 4.0d, or 5.0.
3. Verifies that you have sufficient disk space for DSNlink.
4. Checks for previously installed versions of DSNlink
5. Prompts you for a unique group for the DSNlink executables
and files
6. Sets the group ownership of the files or directories to the
group you created
7. Prompts you for your access number or numbers, the node's
name, your Customer Support Center, which transports you
want to use with DSNlink, the name of a person to contact
if Compaq must reach you by telephone, and your authentication
key
8. Adds entries to /etc/services and /etc/inetd.conf for
communications with the DSNlink host system, if you agree to
the additions
9. Prompts you for information necessary to configure each of the
transports
10. Runs the DSNlink Network Exerciser to test the connection to
the host system
DSNlink modem processes must be stopped during the DSNlink Version 2.3E
installation. DSNlink connections using DECnet, X2.5, or TCP/IP are not
stopped.
DECnet/OSI for Tru64 UNIX may hang the installation. We recommend shutting
down DECnet during the installation using the /usr/sbin/decnetshutdown
command. You can restart DECnet using the /usr/sbin/decnetstartup command.
The change to support X.25 router nodes requires that all customers who use
X.25 and the host run DSNlink Version 2.2E. If you use X.25, contact your
Customer Support Center to coordinate your DSNlink Version 2.2E installation
with their host DSNlink Version 2.2E installation.
A system reboot is not necessary.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
European Site
Files on this server are as follows:
dsna235.README
dsna235.CHKSUM
dsna235.CVRLET_TXT
dsna235.tar
dsna235.CVRLET_TXT
|
