no parameters are passed to the command file
2.8.10 RESTOR PACKAGE
A problem existed in the RESTOR package if you attempted to RESTOR a backup set under the following conditions:
o You first loaded the backup set's work index to disk;
o You restored the backup set using the pre-loaded index;
o Your system no longer contains the same tape controller as that used in the original backup.
Under the above conditions, the RESTOR option failed by prompting you to mount a tape volume on device "_ :" (the device name was
missing), and i t refused to accept any device you specified. Please see the June 1987 issue of the RSTS/E Software Dispatch for further details.
This problem has been corrected in V9.4.
2.8.11 SHUTUP.TSK Corrections
The following problems have been corrected in SHUTUP.TSK for V9.4:
o SHUTUP would send a shutdown message to an EMT logging utility (like EMTCPY) by issuing a "send by job number" SYS call. This failed if the EMT receiver was declared using a non-zero RIB.
SHUTUP has been corrected to use the "send by local object type" SYS call properly. This correctly sends the shutdown message to the EMT receiver, regardless of its RIB number.
o If PBS was running when you ran SHUTUP, and the OPSER package was not, SHUTUP would not allow you to back up to the PBS prompt from the "Minutes until system shutdown" prompt.
2.8.12 SYSTAT.TSK
o In the SYSTAT/D (disks) display of SYSTAT, the notations DLA (Date of Last Access) or DLWr (Date of Last Write) now print only for file structured disks.
o SYSTAT displayed the UP time "???:??:?" when the hours exceeded 999. Now, SYSTAT displays up to 9,999 hours, and
"????:??:??" when the hours exceed 9,999.
2.8.13 HOOK.SAV Correction
A problem where HOOK.SAV appeared to corrupt the pack label of a disk has been fixed. See section 2.3.6 for additional details.
2.8.14 BACKUP.TSK
RSTS/E v9.4 Release Notes Differences Between V9.4 and V9.3
Previously, when BACKUP produced a multi-volume backup set, i t
duplicated detail information about the source of the backup on each volume. This was done so that proper volume defaults could be applied when doing a restore, even if the first volume of the backup set was lost.
Unfortunately, VMS BACKUP was not coded to handle this duplication of information, and caused the file that was being restored at the time of the volume split to be restored incor~ectly.
For RSTS/E V9.4, BACKUP no longer writes the volume detail information on each volume. This means that the RESTORE command will be unable to provide meaningful defaults for initializing output disks when the first volume is not restored.
2.9.1 RMS-11 Access Methods
o RMS-II allowed an indexed file to be created that had
incompatible maximum record size and bucket size. Subsequent attempts to access the file returned ER$MRS. RMS-II has been modified to disallow this create.
This correction involved module R3WPLG of RMSLIB.OLB and the RMS resident libraries.
o RMS-II allowed temporary files to be created with a
declaration of shared write access. These programs would enter a sleep state in RMS during a subsequent record access.
Since temporary files are not intended to be write shared, RMS-II now overrides this request by clearing the write sharing request from the user's File Access Block (FAB).
This correction involved module ROCRFL of RMSLIB.OLB and the RMS resident libraries.
o The RMS-ll macros XBDOF$ and $GNCAL did not work correctly.
XBDOF$ attempted to use octal values for field lengths (they are decimal), and $GNCAL did not bring in the ORG$ and GSA$
macros as documented. RMSMAC.MLB has been modified to include these changes.
2.9.2 RMS-ll utilities RMSDES
o DES did not prompt correctly for packed decimal keys. It failed to request the key length. It now prompts for this value.
o There was no capability for superseding a file design. There are now two commands: SAVE SUPERSEDE and EXIT SUPERSEDE.
See the section on RMS-ll Documentation for detailed descriptions of these new commands.
o Indexed file alternate key data area assignments were
sometimes incorrect when user defaulted areas. When there was more than one alternate key, the data area for all subsequent keys would still be the same as for the first
alternate key. This was not as documented (RMS-ll utilities, Appendix B). RMSDES has been corrected to function as
documented.
o Alternate Index allocations were too large in many cases.
The calculations have been improved to match the expected needs of the file more closely.
o Indexed file allocations were not correct when duplicates were allowed and the anticipated number of duplicates would
result in continuation buckets on alternate keys. As an enhancement, RMSDES now issues a warning message when continuation buckets are required. These buckets are a
performance drain when the user requires deletion within the duplicate pointer array, or repositioning once having lost
record context on this key. Further, a new informational message will be issued if overflow occurs during calculations in this area, and the prompt "number of duplicates" has been expanded to read "number of duplicates per record on this key" to increase clarity.
o A user-friendly error message is now issued if the help file (LB:RMSDES.HLP) is not found. This is a feature for small systems that are extremely tight for disk space.
o DES displays the error message "Value out of legal range" if you attempt to use a file cluster size of 256. A workaround to this problem is to use a file cluster size of 255.
2.9.3 RMS-ll Documentation RMS-ll USER'S GUIDE
RSTS/E V9.4 Release Notes Differences Between V9.4 and V9.3
o Add new section 3.5.3.5 Block Mode versus Record Mode
Block I/O is recommended for file transfer applications. It provides a performance advantage over record mode due to a simplified code path for RMS-ll, less internal data movement and elimination of RMS-ll internal I/O buffer allocation.
However, in this case RMS-ll relies on the application to be responsible for End of File (EOF). Applications should write the last block of the file so that the Record Size field
indicates the valid bytes in the block, and ensures that the record buffer is padded with nulls beyond EOF.
NOTE
File transfer applications will observe that the READ operation returns the size of the valid portion of the last block in the RSZ field for all record formats except stream files. For compatibility purposes this value is rounded up to the block boundary and,
therefore, is not to be trusted as EOF. The EOF attribute can be obtained from the RFA field at the time of the block I/O CONNECT operation.
Current RMS-ll implementations performing record operations to stream files do not use the EOF attribute to determine the end of the file. However, future implementations may use it; therefore, applications should not rely on access to data beyond the logical EOF.
o Correction to section 5.4 paragraph 3, adding last sentence for increased clarity:
For FIND operations, RMS-ll uses the next record pointer to identify the target bucket. For GET operations, RMS-ll uses the next record pointer, if the GET operation was not
immediately preceded by a successful FIND operation. The current record pointer is used if the GET operation was immediately preceded by a successful FIND operation. An intervening FREE operation will cause RMS-ll to lose current record context.
o Add new section 7.4.5 RFA Access
This method can yield a record in one or two disk I/O's
(providing no duplicates on primary key). FIND and GET will report the unique address of each record. A table kept by the user in program space enables optimization of subsequent accesses.
NOTE
WARNING - RFA's are only valid for the life of the file. Invalid RFA's may cause RMS-ll to abort or return erroneous data.
RMS-ll UTILITIES GUIDE
o Additions for new commands
section 2.2.5 should be expanded to add the following:
EXIT SUPERSEDE
The EXIT_SUPERSEDE command stores your file design in the description file specified in the command string,
superseding any existing file by the same name. Then, i t terminates RMSDES, and the system prompt is returned.
Format
RSTSjE V9.4 Release Notes Differences Between V9.4 and V9.3
EXIT_S[UPERSEDE] filename[.typ]
filename[ .typ]
Names the description file in which the file design will be stored. The default file type is .DES.
If you do not wish to supersede an existing description file you must use the EXIT command.
In section 2.2.5 add to the discussion of the EXIT command:
To supersede an already existing description file, use the EXIT SUPERSEDE command.
Section 2.2.9 should be expanded to add the following:
SAVE SUPERSEDE
The SAVE SUPERSEDE command stores the file design in the descriptIon file specified in the command string,
superseding any existing file by the same name. If you have not defined areas when you issue the SAVE command, you will be prompted as to whether you want RMSDES to define areas.
Format
SAVE_S[UPERSEDE] filename[ .typ]
filename[ .typ]
Names the description file in which the file design will be saved. The default file typ is .DES.
If you want to design another file, you should issue a CLEAR ALL command to restore the attribute values in the design buffer to their defaults. If you do not wish to supersede an existing description file use the SAVE command.
In section 2.2.9 add to the discussion of the SAVE command:
To supersede an already existing description file, use the SAVE SUPERSEDE command.
The above items should also be added to Table 2-1.
o Other additions
Section 2.8 RMSDES MESSAGES - expand the description of
?DES-F-VOR by adding the following:
Or the values you entered resulted in a calculation which caused an overflow for RMSDES.
Section 2.6.2 File Section
o Modify paragraph 3 of the ALLOCATION field discussion to read as follows:
If you intend to create a single-area indexed file and do not request file placement, RMS-Il will use the allocation from the file section if no area section exists in your design buffer. If you are allowing RMSDES to define areas for an indexed file
o Modify paragraph 4 of the EXTENSION field discussion to read as follows:
If you intend to create a single-area indexed file and do not request file placement, RMS-Il will use the extension from the file section if no area section exists in your design buffer. If you are allowing RMSDES to define areas for an indexed file
o Modify paragraph 5 of the BUCKET SIZE field discussion to read as follows:
-If you intend to create a single-area indexed file and do not request file placement, RMS-ll will use the bucket size from the file section if no area section exists in your design buffer. If you are allowing RMSDES to define areas for an indexed file
RSTS/E v9.4 Release Notes Differences Between V9.4 and V9.3
by default, RMSDES will assign a bucket size value for each area i t defines. However, if you choose to define areas explicitly and specify a bucket size value for each area, you should accept the default in this section and set the bucket size attribute in each area section.
2.10 Layered Products 2.10.1 DECnet/E V4.0 Updating DECnet/E
To update DECnet/E to include changes on the RSTS/E V9.4 kit, run the DECnet/E: installation procedure after the RSTS/E V9.4 update is
complete. See the DECnet/E Installation and Update Guide for details on the installation process. When the installation completes, all new DECnet/E: components will exist in the appropriate accounts. No
network conversion or configuration procedures need to be carried out when updating existing DECnet/E V4.0 installations.
SET HOST Command Corrections
The following problems have been corrected in NET.TSK for RSTS/E V9.4:
o Under previous versions of RSTS/E, pressing CTRL/C while attempting to SET HOST to another node could cause the following message to be displayed:
Connection Established to 10 Node
1 Unsupported Remote Terminal Protocol - 0 This message no longer displays.
o Previously, if a logical link failure occurred during a
network session, no reason for the failure was indicated. In RSTS/E V9.4, the NSP reason code for the failure displays in the abort message.
RSTS/E Network File Transfer program (NFT) Corrections
The following problems have been corrected in NFT for RSTS/E V9.4:
o Remote copies involving a wildcarded ULTRIX file
specification would fail. This was due to NFT's incorrect handling of the ULTRIX directory symbol when parsing the resultant file specification.
o NFT did not correctly write the attributes of stream files transferred in block mode. It erroneously rounded up the End of File attribute.
DECnet/E File Access Listener (FAL) Corrections
The following problems have been corrected in FAL for RSTS/E V9.4:
o The DECnet/E FAL incorrectly handled repetitive use of a DECnet/E link to access more than one file on a RSTS/E node.
This problem could occur on i~ wildcard COpy command issued from a VAX/VMS V4.4 or later system, when three or more files were involved. In such cases, COpy would report an error
(ER$ORD) when accessing the second file matching the wildcard specification and abort the operation.
NOTE
The re-use of a DECnl~t link by VAX/VMS V4.4 and V4.S can still cause problems with other types of remote RSTS/E a~cesses. For
example, a VMS COpy command referencing more than one explicit file on RSTS/E will report
"DAP CODE
=
OlF7AOOl", referring to a synchronization error related to anunexpected Configuration Message sent by VMS.
In this case, the link is re-used following a search operation by VMS.
This problem is under investigation by both RSTS/E and VMS development.
o Remote accesses and remote directory operations would
occasionally result in FAL inappropriately setting the p-bit on a file. This caused the file to be non-deleteable
(protected). To restore files to their original state you previously had to use the DCL command "SET FILE/DELETE".
2.10.2 DECnet/E Documentation
DECnet/E utilities Guide
RSTS/E V9.4 Release Notes Differences Between V9.4 and V9.3
o Add to discussion of /ASCII switch, p.4-36:
NOTE
This switch is useful for copying ASCII text files from systems which have a different concept of non-attributed stream files than RSTS/E (e.g. DECnet-ULTRIX and DECnet-DOS use Line Feed as the standard record
delimiter, while RSTS/E non-attributed files use Carriage Return followed by Line Feed).
When this switch is applied, only the data portion of a record is transferred, so that RSTS/E can apply its own record delimiter.
2.10.3 DECmai1-11 v3.0 Updates on RSTS/E V9.4
This release of RSTS/E contains updates for DECmail-ll V3.0.
NOTE
Due to a change in RSTS/E V9.4, installation of the update is mandatory. If this update is not installed you may get n?Device not available" errors when
attempting to send mail.
Transfer" the DECmail-ll V3.0 update components to the PATCH account during the system upgrade from V9.3 to v9.4. Refer to the RSTS/E System Installation and Update Guide, Part IV:, Phase:3, Task:4, page 178 for more information about transfering updates for Layered
Products.
If you do not transfer DECmail-ll updates during the system upgrade, you will need to mount your RSTS/E Installation media during the DECmail-ll update. The RSTS/E Layered Product Update Procedure will transfer the DECmail-ll updates.
Requirements for this update:
Privileges:
Refer to the DECmail-ll Installation and System Manager's Guide for information about t~e privileges needed.
Programs:
SY:[1,2]LBR.TSK SY:[1,2]STK.TSK SY:[1,2]TKB.TSK SY:[1,2]MAKSIL.TSK Disk space:
960 blocks for update files in PATCH$:
5350 blocks for update work files in WORKS:
NOTE
The 5350 blocks of disk space in WORKS: will be returned to the system as free space after the update has completed.
1350 blocks for updated tasks in MAIL$:
NOTE
The tasks in MAIL$: should be contiguous for optimum performance.
The total number of free blocks needed to do this update is 7660 of which 1350 blocks should be contiguous. In order to reduce the need for disk space the MAIL update procedure deletes files as soon as they are no longer needed.
RSTS/E V9.4 Release Notes Differences Between V9.4 and V9.3
NOTE
Use of DECmail-11 during the update may cause unpredictable errors to occur.
Updating your DECmail-11 V3.0 software can be accomplished by invoking the RSTS/E software update procedure. The following is an example of a DECmail-11 update.
$ @[O,I]UPDATE LAYEREDPRODUCT MAIL Deleting all global symbols
Patch account <PATCH$:> :
The following will be updated:
Proceed? <yes>
please enter the name and unit number of the disk to which you want to update the software. This disk should be physically mounted and write-enabled.
Target disk? <SY:>:
Assigning system logicals 01-Dec-86 09:49 AM
01-Dec-86 09:49 AM
Please mount the MAIL Library media and enter the name and unit number of the device.
Valid device types are: 'MM', 'MS', 'MT', 'MU', 'DM' or 'DL' MAIL Library device? <MMO:> DLO:
The update procedure will complete without user intervention from this point. UPDATE. LOG is a log file of this update procedure, created in your account, and should be checked for possible update errors.
Disregard multiply defined symbol errors during the task rebuild phase.
The update should take between 3 and 4.5 hours, depending on your CPU and system disk.
Corrections
The following problems have been fixed in this update:
o Date and time values specified to the /AFTER qualifier were ignored when sending a message using the /EDIT qualifier, or if AUTO EDIT was enabled.
o The From: and Subject: fields are cleared out when sending a message with /EDIT or AUTO EDIT enabled.
o Batch Mail messages having To: and CC: lines greater than 255 characters would result in a "?Line too long" error and abort MAILQ.
o Entering PRINT<return> with no current message aborts MAIL with an "?Arguments don't match" error.
o DECmail-ll displays "?Integer error" when sending a message greater than 64 blocks in length via Message Router.
o MAILQ aborts with "?No room for user on device" when i t
encounters zero free blocks. MAILQ will now wait for blocks to become available before re-attempting the delivery.
o Users would sometimes receive multiple copies of the same mail message when sent via Batch Mail.
o Entering "NI" at the Send Menu replaces the CC: field with the To: field contents, if a CC: line had been entered.
o Files having records with trailing carriage returns, such as RNa and DSR files, do not print correctly when sent to users on other nodes.
o Users intermittently receive messages with an incorrect To:
field when sent via Batch Mail.
o DECmail-ll would abort with a Maximum Memory Exceeded error when attempting to send or FETCH Message Router mail to a
large number of users.
RSTS/E V9.4 Release Notes Differences Between V9.4 and V9.3
o Two errors which caused Batch Mail to send duplicate messages were corrected.
o Mail would not be delivered to a user who had exceeded logged out quota.
o The SELECT keyword was not properly cleared after unsuccessful SEARCH commands.
3 Documentation Changes in RSTS/E V9.4
The following documents have been revised or updated for V9.4:
o The RSTS/E Quick Reference Guide (AA-EZ13B-TC) has been revised to incorporate all changes that have occurred since V9.1 and to correct all known errors.
o The RSTS/E Programming
Manual
(AD-EZ09A-T2) has been updated to describe the Ethernet interface.o The RSTS/E System Directives Manual (AD-EZ10A-T2) has been
o The RSTS/E System Directives Manual (AD-EZ10A-T2) has been