G06.26 Release Version Update Compendium

Database and Transaction Processing Products
G06.26 Release Version Update Compendium—529842-001
4-2
Fallback
Information about attributes set by these options is also available through the INFO
TMF and STATUS TMF commands.
•
Ability to use file-name patterns as input to the TMFCOM DUMP FILES, INFO
DUMPS, and RECOVER FILES commands. This feature is provided by the <file-
name> specifier, which identifies an Edit-format or C-data file that contains the file-
name patterns. These patterns, in turn, designate the files to be dumped, reported
on, or recovered by TMF. They enable you to supply many more file names as
command input than was previously possible. Another specifier, NOT <file-name>,
allows you to designate files to be omitted from the dump, information retrieval, or
recovery operation.
•
Ability of the TMFCOM STATUS TRANSACTIONS command to display
transactions in a specified order, provided through the SORT option.
•
Ability of the TMFCOM STATUS TRANSACTIONS command to display the name
of the backout process assigned to an aborting transaction, shown in the Backout
Assigned field.
•
Change of the default timer value for TMP work processing, from AUTO to OFF.
•
Change of the TMFCOM and TMFSERVE programs to RISC objects.
Fallback
If you do not use any new configurable features after migrating to TMF 3.3, falling back
to the release from which you migrated is not a problem. If you use the new TMF 3.3
feature that allows you to add auxiliary audit trails while TMF is started, however, you
need to first understand the impact of any subsequent fallback.
If you add one or more auxiliary audit trails while TMF is started, it is only possible to
fall back to G06.24 or a later RVU. This is because the TMF audit reading facilities
prior to G06.24 cannot handle auxiliary pointer (AUXPTR) records that specify a
variable number of audit trails. (The number of audit trails is, once configured,
assumed to remain constant.)
If you issue an ADD AUDITTRAIL AUXnn command while TMF 3.3 is started, the next
AUXPTR record generated contains information for a different number of audit trails
than did the preceding AUXPTR record. In the G06.24 RVU, the audit reading module
can handle such AUXPTR records.
TS/MP 2.1 (Controlled Availability)
HP NonStop TS/MP 2.1 provides Pathsend users higher link capacity to client
processes by replacing the link management functions of the LINKMON (ROUT)
process with functions provided by the Application Cluster Services (ACS) subsystem.
NonStop TS/MP 2.1 is intended solely for Pathsend users on S-series systems using
TS/MP 2.0. It does not apply to SCOBOL users or TS/MP 3.0 users.