RELEASE NOTESTHRUnet V2.4-01

wheatauditorSoftware and s/w Development

Oct 30, 2013 (3 years and 10 months ago)

66 views


THRUnet
®



10/31/2013

V2.4


RELEASE NOTES
1



RELEASE NOTES

THRUnet
®

V2.4
-
01

Copyright © 1993, 1994, 1995, 1996, 1998 Software Partners, Inc. All rights reserved


Overview


Purpose

These release notes describe new features, enhancements, and bug fixes introduced
by THRUnet
®

V2.4, the Network Backup a
nd Restore System from Software
Partners, Inc.


Audience

THRUnet users upgrading from THRUnet V2.x to Version 2.4 should follow the
upgrade procedure covered in these release notes.




In these notes

These release notes discuss the following topics:


Topic

See Page

Supported Platforms

2

Upgrading to V2.4

4

Changes for Version 2.3
-
02

5

Changes for Version 2.4

8

Changes for Version 2.4
-
01

9


THRUnet
®




2

RELEASE NOTES


10/31/2013

V2.4







Supported Platforms


Introduction

This section describes the server systems, client systems, and TCP/IP pa
ckages
currently supported by THRUnet V2.4.


Supported
server systems

THRUnet currently supports




VAX/VMS systems with VMS 6.0 through 7.1 with any of the following TCP/IP
packages:


-

TCPware for VMS

from Process Software Cor
poration (V4.0)


-

MultiNet from TGV (V3.5, 4.0)


-

DEC TCP/IP Services for VMS V4.0 and 4.1.





ALPHA AXP systems with OpenVMS V6.0 through 7.1 with any of the following
TCP/IP packages:


-

TCPware for VMS

V4.0 from Process Software Corporation


-

Multi
Net V3.3, 3.5, 4.0 from TGV, and


-

NEW!

DEC TCP/IP Services for OpenVMS AXP V4.0 and V4.1.


Supported
client systems

The following client systems are supported
:




abC⁕iqofu
-
ofpC⁖㐮㈬‴⸲4Ⱐ㐮㌬‴⸴



punlp
pun㐮4
un㑣⁡rchitectureⰠ,unlp‴⸱⹸Ⱐ㔮〮,F



pun⁓潬aris
pun㐮4un㑣⁡rchitectureⰠ,unlp‵⸲




-
ru
em‹〰〬⁈m
-
ru⁁⸰㠮〷⁡n搠d⸰㤮〱⬩




-
ru
em‹〰〠 潤ol‸〰Ⱐ m
-
ru‹⸰⸱



fBM⁒p㘰〰⁁fu⁖㌮3

aigital⁕nix
abC⁁um″〰〠 潤ol″〰Ⱐ igital⁕kfu⁖㌮㈠3
n搠㐮〩

pdf⁉ofu


Working with
TCP/IP

Software Partners has written a booklet providing a brief introduction to TCP/IP and
internetworking. This booklet, "TCP/IP and Internetworking: a Primer," provides a
basic overview of TCP/IP protocols and internetw
orking. It is available upon
request from Software Partners/32.


Continued on next page


THRUnet
®



10/31/2013

V2.4


RELEASE NOTES
3



Supported Platforms,
Continued


Restriction:
cpio

and
ULTRIX

When using
cpio

on an ULTRIX client, the
cpio

-
c

option must be used. The
headers created by the ULTRI
X
cpio

utility are non
-
standard and not recognized
by THRUnet unless the
-
c

option is used.


Note
:

See the
cpio man

page for more information about the
cpio

utility.


THRUnet
®




4

RELEASE NOTES


10/31/2013

V2.4







Upgrading to V2.4


Introduction

This section details the procedure followed by those
THRUnet users upgrading from
THRUnet V2.x to THRUnet V2.4.



Procedure:
upgrading from
V2.x

To perform an upgrade from THRUnet V2.x to THRUnet V2.4, follow the steps
detailed in the table below.


Step

Action

1

Make sure existing THRUnet server is runnin
g.

2

Load the THRUnet V2.4 distribution media.

3

Follow the installation and configuration procedures as detailed in the
THRUnet V2.4 documentation, Chapter 2. THRUnet V2.4 has a new
database format that is not compatible with previous versions of
THRU
net. During the installation, you will be prompted to convert and
save your previous database. To save this data, respond “YES”.



THRUnet
®



10/31/2013

V2.4


RELEASE NOTES
5



Changes for Version 2.3
-
02


Introduction

This section details new features, enhancements, and bug fixes for THRUnet V2.3
-
02.


New feature

THRUnet now supports the BRU™ archive utility. BRU is a robust backup and
rest潲e⁵tility⁤ vel潰o搠dn搠dar步te搠批⁅nhance搠d潦tware⁔echn潬潧yⰠ,nc.


eist潲y⁦iles⁡re⁳u灰潲te搠d潲⁂or.


History file
specification
format

THRUnet history files no longe
r require VMS format file specification. History files
are now stored in native UNIX file specification format. This eliminates the need for
conversion routines and enhances backup performance when history processing is
enabled.


History file
naming
con
vention

The history file naming convention has been changed. All THRUnet history files are
now formatted as follows:


File type

Convention

the saveset history file

<machinename>_<username>.SETS_5R0

the files history file

<machinename>_<username>.FILES_
TN23


Note
:

When a user is defined with an owner field, the history is stored in a file
based upon the machine name and user name rather than the owner
name.


Database
format change

The THRUnet database format now allows longer media type string lengths.


Continued on next page

THRUnet
®




6

RELEASE NOTES


10/31/2013

V2.4







Changes for Version 2.3
-
02,
Continued


The TNTHIST
utility

A history processing utility is now included with THRUnet. This program, known as
TNTHIST is available for both VAX (HISTUTIL_VAX.EXE) and Alpha AXP
(HISTUTIL_AXP.EXE) p
latforms.


TNTHIST can be used to:




convert pre
-
V2.3
-
02 histories to the new format, and



clean or list the contents of a history file.


Note
:

You can still view history files with the TNT QUERY FILES command.
However, TAPESYS history query commands w
ill no longer work.


Media
compaction

A bug was reported in previous versions of THRUnet that prevented media
compaction from working in some instances.


This has been fixed.


Device
allocation error
message

If TAPESYS is running and you specify a volume
(with the TNT ALLOCATE
command), THRUnet uses the mediatype and location found in the TAPESYS
database to allocate a device. If, when specifying a volume, you also specify a
mediatype and location and it differs from those returned by TAPESYS, THRUnet
dis
plays an error message.


Device
allocation
location

Previously, THRUnet allocated a device if it exactly matched the mediatype and
location specified. It now will allocate for locations that exactly match the specified
“location” and any appended charact
ers formatted as “location...”. For example, if
the location name equals “Boston”, then THRUnet will attempt devices at “Boston1”
or “Boston2”.


Continued on next page


THRUnet
®



10/31/2013

V2.4


RELEASE NOTES
7



Changes for Version 2.3
-
02,
Continued


Additional
TAPESYS
support

The Allocate comma
nd now allows you to specify a Notes field and a Scratch Date.
THRUnet passes this information to TAPESYS and updates the media database.


To specify Notes:


VMS:

use the /NOTES=<notes> qualifier on the $TNT ALLOCATE
command


UNIX:

use option “N” and incl
u摥⁡潴es⁳tring⁩nⁱ 潴es⁦潲⁴he
c潲res灯p摩ng⁶alue


q漠o灥cify⁡⁓cratch⁄ate:


sMp:

use⁴he pCoAqCe㵹y
-
浭m
-
yyyyⁱ alifier ⁴he․ kq
AiilCAqb⁣潭mand


UNIX:

use option “s” on a first or third party tnt allocate command and include
the⁓cratch⁄ate

in⁴he⁦潲m⁤
-
浭m
-
yyyy⁦潲⁴he⁣潲res灯p摩ng⁶alue




















Changes for Version 2.4

THRUnet
®




8

RELEASE NOTES


10/31/2013

V2.4








Backup and
Restore

If a backup and/or restore completes successfully with zero bytes transferred, a
status of "no data transferred" is returned.


Machine nam
e
width

The machine name width has been increased from 31 to 128 characters.


DEC C Run
Time Library

THRUnet is now built with the
DEC C RUN TIME LIBRARY
.


UNIX
command

The UNIX command
'EU'

no longer requires options
'x'
or

'y'.
This
allows autoconfigu
re mode to work for UNIX client machines.


Help
information
displayed

The UNIX client now displays help information relating to command syntax. For
example:
'tnt Q?'
will display syntax of all Query commands and
'tnt ?'
will display syntax of all comman
ds.


Portmapper

The embedded portmapper has been removed since UCX now supports a
reasonably functional portmapper.


Diagnostic
routines

The server now has improved diagnostic routines.


Bug fix

The server would sometimes free volumes which could not be

mounted because the
user had no access to them.


This has been fixed.


Nounload
option

The nounload option has been fixed.





Changes for Version 2.4
-
01


THRUnet
®



10/31/2013

V2.4


RELEASE NOTES
9




tar Header
Format
Variations

The server has been modified to recognize additional variations in th
e tar header for
correct check sum generation.


Bytes
Transfered
Counter

The server has been modified to accurately report bytes transfered to 15 digits within
server log files. The server has also been modified to return Kbytes (1024 bytes)
transfered w
hen queried using the
TNT QUERY JOB

command.


Job
Comple tion
Status

Some failed jobs incorrectly reported a successful completion. The server has been
modified to correctly report job completion status.