G06.25 Release Version Update Compendium
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 G06.25 Overview
- 2 Operating System
- 3 Application Development Products
- 4 Database and Transaction Processing Products
- 5 Installation and Configuration Products
- 6 Manageability Products
- 7 Hardware Products
- 8 Networking Products
- A Sources for Migration Assistance and Information
Networking Products
G06.25 Release Version Update Compendium—529423-002
8-2
Fallback
•
The existing BIND 4.8.3 version of DNS will continue to be shipped with G06.25
and later RVUs. No further enhancements will be accepted for this product. Both
versions of DNS can coexist on the same system. However, they must be assigned
different IP addresses.
•
The OSS environment must be configured and running to use or migrate to DNS
9.2.3. The Name Server runs in the OSS environment.
•
DNS 9.2.3 is supported on G06.25 and later RVUs. DNS 9.2.3 is not supported on
D-series RVUs.
•
The DNS 4.8.3 configuration file must be converted to DNS 9.2.3 format. A shell
script tool (named-bootconf) is provided for this conversion.
Fallback
If the DNS server abends or domain names are not resolved, T6021AAO (DNS 4.8.3)
can be started and used as a fallback option:
•
A system load is not required as part of fallback.
•
Effect of falling back: T6021AAO does not support the additional features that are
provided in DNS 9.2.3.
SNAX/APN
A new attribute, SENDUNBIND01, has been added to the syntax of the ADD LU
command. SENDUNBIND01 specifies the type of UNBIND request that is sent when a
CLOSE request is received from the application on an LU of protocol type CRT. If the
SENDUNBIND01 attribute is set to YES, an UNBIND of type 01 is sent. Otherwise, an
UNBIND of type 0F is sent. An UNBIND of type 0F directs SNAX/APN to clean up the
resources associated with the terminating session without waiting for a response. An
UNBIND of type 01 directs SNAX/APN to perform the cleanup after waiting for a
response. While adding a remote LU of protocol type CRT, the SENDUNBIND01
attribute should be set to YES.
Fallback
Consider falling back to an earlier version when:
•
A processor halts as a result of the SNAX/APN product.
•
SNAX subobjects (PUs or LUs) cannot enter the STARTED state.
As an effect of the fallback, the initial VTAM screen on the CRT terminal is corrupted
when a number of sessions are continuously started and stopped between a CRT
terminal and an LU on the NonStop server.
The fallback process takes less than an hour. If fallback is successful, the SNAX
subobjects (LUs and PUs) are in the STARTED state, and no processor halts occur.