Digital PDFs

XX-E7406-BE

May 1986

4 pages

Original

0.3MB

Document:	SH Bulletin V4N6 Fall86
Order Number:	XX-E7406-BE
Revision:	0
Pages:	4
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/tsxPlus/sh_bulletin/SH_Bulletin_V4N6_Fall86.pdf

OCR Text

fall 1986

volume four, number six
New Release of COBOL-Plus v6.11
Changes to the ISAM utility
A new switch has been added to the ISAM utility to facilitate
batch verification of indexed files. The new /Q switch. when
used in conjunction with the /V switch. eliminates all output
if no ISAM verification errors are detected. This simplifies
location and identification of errors during verification of
multiple files. In addition, a BELL character is inserted
into the output for each file in which any verification error
occurred.
ISMBLD Program
A utility program is now provided with COBOL-Plus to rebuild the index structure for indexed organization (ISAM)
files. This program uses only information stored in the data
portion of the fiie (Le .. fiies with extension COn) and completely rebuilds the index portion of the file (Le .. files with
extension Cln).
There are two primary uses for the ISMBLD program: (1) to
repair files whose index structures have been corrupted: and

(2) to make it possible to back up only the data portions
of files and then recreate the index portions if the files are
restored fiOm backup. If one Oi more index files are missing
when ISMBLD is run. it creates the index files as required.
Corrections
The ISAM utility did not convert ISAM files from pre-6.0
format into the correct format if the index had a deieted
bucket chain. This delete chain only pertains to index buckets which were reclaimed and is not related to the delete
chain pointer displayed by a home block dump. Files which
have already been converted using the update (fU) switch
MUST be rebuilt with the ISMBLD utility to insure that no
future key errors will occur.
NOTE: For ISAM files previously updated successfully.
and even successful verification is no guarantee that
the file is correct. All files updated with prior versions
of the ISAM utility MUST be rebuilt!

MessageNet Released
We are pleased to announce that our new electronic mail
package. MessageNet. is ready for release for VAX/VMS.
After extensive field testing. MessageNet was first introduced at DEXPO West in San Francisco and was very well
received.
Briefly. MessageNet is a fully automated gateway to electronic mail services such as EasyLink. MCI Mail. Telex.
Mailgram. Telegram. Cablegram. and paper mail services.
MessageNet also provides direct transfer of messages and
files over ordinary telephone lines between computers equipped 'Nlth Messagef'.Jet.
Some of the new features we are adding are the following.
The editor will have the capability to do split screen display.
This can be used at any time but is primarily intended to
be used when replying to a message. The reply you are

composing is displayed in the top window of the screen and
the original message you are responding to is in the bottom
window separated by a line of dots. You can move around
in either window and can move text between the windows
by using the cut/paste function. MessageNet also allows
full screen editing when replying. if desired.
We are also adding a Calendar/Reminder feature that allows
you to send a memo to yourself or any other MessageNet
user at any time of the day or night. and can be scheduled
for years in advance. This has been found to be very useful
for callbacks. appointments. and personal reminders.
If you would like some more information. or a brochure on
MessageNet. please call our sales department. They will
gladly send you the latest product information and inform
you about our MessageNet demo.

s&h bulletin

VTCOM-F-Wrong version of Xl
Over the last few months we have had several calls from
people who were having problems with different aspects of
VTCOM. Because of this we thought it would be appropriate
to write an article on the subject.
There are several things about using VTCOM with
TSX-Plus that are less than obvious. First, you should use
the XM version of VTCOM (VTCOM.SAV), rather than the
SJ version (VTCOM.REl). Next you should generate your
TSX-Plus system with sufficient PlAS region space. This
is the resource necessary for virtual arrays and virtual overlays. For each simultaneous use of VTCOM, you should
have at least 25 blocks of PlAS swap file (SEGBlK=25.).
We have found that 100 blocks seems to be sufficient. The
system parameter 10ABT=1 should be set in TSGEN, or
the SET 10 ABORT command issued before running VTCOM. Failure to do this may cause you to be unable to exit
VTCOM, or cause it to hang after file transfers.
If you wish to use VTCOM, and you want to use the Xl
handler, you should make sure there is a DEVDEF for Xl,
and the file XL. TSX is on the system disk (S Y:). If the
handler does not load, it probably failed the installation
tests. While under TSX-Plus, you should issue the SET
Xl CSR=nnnnnn and SET Xl VECTOR=nnn commands
appropriate for your hardware, and then restart TSX-Plus.
Xl should now load. On the PRO computers, XC defaults
to the communication port, and should load without difficUlity. Keep in mind that neither Xl nor XC can be used on
a multiplexer port (DZ, DZV, DH, DHV, DHU, or QSl on
the PRO).
As an alternative to using Xl or XC with VTCOM. we recommend using a Cl unit. In this case. one should not use
a DEVDEF for Xl or XC in TSGEN. In the TSX-Plus Reference Manual section 14.3.7, there is an example of how
to use VTCOM with a Cl unit.
Now we come to the point you have all been waiting for. the
error message:

This error message occurs when the internal table used by
TSX-Plus to determine the correct Xl version number does
not return the proper number. If this happens. you need to
determine the correct version number. This may be done
by editing the XL.MAC handler source file. and searching
for the string "$$$VER". This string will be assigned the
appropriate version number. You may also use SIPP to
search the XL.SYS file for the value 012705. The Xl version
number is stored in the high byte of the word following the
word which holds 012705. A third method of obtaining this
number is by calling the Xl handler with .SPFUN 204. The
version number will be returned in the high byte of the status
word.
TSX-Plus uses the ClVERS parameter within TSGEN to
assign the appropriate version to CL. If ClVERS=O then
TSX-Plus automatically choses a version that should allow VTCOM to fuction normally. If ClVERS is not 0, then
TSX-Plus uses the assigned value as the Cl version number. If the automatic selection of the Cl version does not
work in your case, then you need to change the value of
ClVERS in TSGEN to the number which you found by looking at XL.
You may modify the value of ClVERS by using TSXMOD_:",'
if you have TSX-Plus v6.00 or later. See the TSX-P/~
Installation Guide for full instructions on how to do this.
This is not a permanent solution. because the next time
you regenerate TSX-Plus, the value of ClVERS will revert
to the old value specified in TSGEN. Note that this is the
only way it may be changed for PRO /TSX-Plus.
The permanent method of modifing ClVERS is by changing
its value in TSGEN. ClVERS is in the section not normally
modified by the user. Set ClVERS to the value you found
in the Xl handler. then rebuild TSX-Plus.
For further information on this subject. as well as other subjects, consult the S&H Bulletin Board Service at
615/320-5462.

?VTCOM-F-Wrong version of XL (or XC).

DECUS/DEXPO
At the San Francisco DEXPO held in October. we demonstrated the newest version of TSX-Plus and announced the
release of our first VAX product. MessageNet. It was a pleasure to meet all of the people who visited with us there. As
always, we believe in the importance of the exchange of information and ideas and we are always looking and listening
for ways to improve our products.

Our next participation will be at the Canadian DECUS in
Montreal. February 1987. Steve Brenner will present a sem-I
inar on Monday, February 16th titled TSX-Plus Technical
Overview. The spring DECUS will be held in our own corporate headquarters city of Nashville. Tennessee (alias Music City. USA). We look forward to seeing "Y'all" at our
DEXPO booth here.

s&h bulletin

RTSORT News
RTSORT version 2.0 introduced a problem when attempting to run using only the /MESSAGE switch (without a
/GETCXT). It would digest any messages sent. but not
perform any sorts nor send a return message. Programs
which called RTSORT in message mode would thus wait
for a return message until aborted. The following patch
corrects the problem:

.R SIPP

Base
011342
011342

.R SIPP
*SY:RTSORT
Segment? 3
Base?
11340
Offset? 1542

*SY:RTSORT
Segment? 1
Base?
11342
Offset? 26624
Segment
000001
000001

sort error)". Note that this error message can be received
for other valid reasons such as hardware failure. When the
error occurred in the case of the software failure. it was
reproducible given the same input file. The following patch
corrects the problem in RTSORT version 2.0:

Offset
026624
026626

Old
103374
105037

New?
103006
-Y

*-C
RTSORT version 2.0 and earlier had a problem when sorting
files which contained a large number of records. Certain files
(depending on the number of input records) would cause
TSORT to abort with a "Temp tiie iink faiiure (internai

Segment
000001
000001

Base
011340
011340

Offset
001542
001544

Old
000310
170610

New?
620

-Y

RTSORT version 2.1. currently in field test. incorporates
these corrections. It also corrects two other problems:
(1) once the /FILE switch was specified it remained in effect until RTSORT was restarted; and (2) records could be
incorrectly sorted to sequential files when they contained
blanks past the last key position,

DU-What, When and Where
The multitude of devices supported by the DU device handier generates frequent inquiries about hardware and version
compatibiiities. We wiii try here to summarize our experience.
The RT-11 DU handler was first released by DEC with VS.O
for the RDS1. RA80 and RC2S disks. Support for additional
MSCP class devices came in the following versions: RDSO
and RXSO in VS.1; RDS2 in VS.2; RA81 and RDS3 in VS.3;
RD31 and RX33 in VS.4. Handler bad block replacement
was included in VS.3.
TSX-Plus first included the DU handler in V4.0. TSX-Plus
VS.1C used the RT-11 VS.1C UU handler and thus supported the RDSO. RD51. RASO. RC25 and RX50 devices.
In order to use the RQDX2 or RQDX3 controllers. it was
necessary to copy the RT-11 V5.2 DUX.SYS to DU.TSX.
TSX-Plus V6.0. V6.01 and V6.16 used the RT-11 VS.2
DU handler and thus added support for the RDS2. Actual experience has shown that the handler shipped with
6.0. V6.01 and V6.i6 works satisfactoriiy on RDSO. RDSi.
-RDS2. RD53. RA80. RC2S. RX50. and the 11/S3 devices
RX33 and RD31 even though they are not nominally supported by RT-11 V5.2. However, handler bad block replacement is not included.

Since no patches to DU were necessary to make it work
with TSX-Plus. it was acceptable with older versions to
simply configure the RT-llXM handler DUX.SYS as necessary and copy it to DU.TSX. This may not be done
with the RT-11 VSo3 or VS.4 DU handlers. The new
DU handlers use features that require changes to TSX-Plus
that are not included prior to TSX-Plus V6.2. In addition.
patches to the VS.3 and VS.4 DU handlers will be mandatory for use with TSX-Plus.
Handler bad block replacement is not an issue for the RD
or RX series of disks. It is never done on RXSO or RX33
disks and is done by the controller for the RD series. Under RT-11. handler bad block replacement is only available
from the XM monitor and then only starting with VS.3. The
significance of this is that the larger disks like the RA80 and
RA81 must be initialized with the /BAD switch. and not the
/REPLACE switch. Thus, large disks may become fragmented as bad blocks appear. sometimes interfering with
the placement of very large files. It does not mean that
these devices are unusable until TSX-Plus V6.2 is released.
but only that they cannot use handler bad block replacement.

s&h bulletin

TSX-Plus v6.2

BBS

TSX-Plus version 6.2 is almost ready for release. It will
be compatible with RT-11 version 5.04. and will include
support for the MU handler (TK50 tape drive) on the Q-Bus
only. If you have a UNIBUS with a TK50 tape drive. and
would like to field test the MU handler. please contact the
Technical Support Department at 615/327-3670.

Due to some necessary maintenance and other activities on
our VAX system. our Bulletin Board Service (BBS) has not
been up and running with much consistency recently. That
now all seems to be behind us. So we would like to take
this opportunity to once again invite you to call in and see
what we have. The BBS phone number is 615/320-5462.

s&h computer systems, inc.
1027 17th Avenue South
Nashville, TN 37212-2288

FIRST CLASS
U.S. POSTAGE

PAID
PERMIT NO. 986
NASHVILLE, TN