<<< DCSNL::DCSDSK:[NOTES$LIBRARY]PDP-11_SIG.NOTE;1 >>> -< DECUS Holland PDP-11 SIG (ex. RSX SIG) >- ================================================================================ Note 15.0 Release Notes RSX-11M/11S V4.7 No replies DCSNL::BELGRAVER_J "Jan; Organon, Oss; 04120 - 6" 10786 lines 18-OCT-1993 21:13 -------------------------------------------------------------------------------- RSX-11M/RSX-11S_______________________________ Release Notes AA-2573N-TC February 1993 This revised manual contains technical changes made to the RSX-11M and RSX-11S operating systems since the previous version, corrections to the documentation since Version 4.2, a summary of layered products supported on the operating system, and additional information on RMS-11. Revision/Update Information: This revised manual supersedes the RSX-11M/RSX-11S Version 4.6 Release Notes Order Number AA-2573M-TC Operating System: RSX-11M/RSX-11S Version 4.7 Digital Equipment Corporation Maynard, Massachusetts  __________________________________________________________ 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. ) Digital Equipment Corporation 1979, 1982, 1983, 1985, 1987, 1988, 1989, 1990, 1991, 1992, and 1993. All Rights Reserved. The postpaid Reader's Comments form at the end of this document requests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: BASIC-PLUS-2, CXA16, CXB16, CXF32, CXY08, DATATRIEVE-11, DCX, DDCMP, DEC, DECnet, DECnet-11M, DEC/CMS, DEC/MMS, DECUS, DELUA, DFA01, DHF11, DHQ11, DHU11, DHV11, DIBOL, DLVJ1, F11ACP, FORTRAN-77, IP11, J-11 Processor, KJD11, KJD11-A, KDJ11-E Processor, KMV11- A, KW11-P Clock, LA50, LA75, LK201, LN01, LN03, LSI, LSI-11/73 MicroPDP-11, MicroPDP-11/23, MicroPDP-11/53, MicroPDP-11/73, MicroPDP-11/83, MicroPDP-11/93, Micro/RSX, MicroVMS, MRV11-D, MXV11-B2, MXV11-BF, PDP, PDP-11/84, PDP-11/94, Professional, Q-bus, RA70, RA71, RA72, RA82, RA90, RA92, RC25, RD31, RD32, RD50, RD52, RD54, ReGIS, RK07, RL01, RL02, RM03, RM05, RM80, RMS-11, RP04, RP05, RP06, RQDX1, RQZX1, RSTS, RSX, RSX-11, RSX-11M, RSX-11M- PLUS RSX-11S, RX33, RX50, RZ23L, RZ24L, TC11, TK25, TK50, TU56, TU81, TZ30, UNIBUS, VAX, VAX-11, VAXcluster, VAX DOCUMENT, VMS, VT, VT200, VT300, WPS-PLUS, and the DIGITAL logo. This document was prepared using VAX DOCUMENT, Version 2.1.  ________________________________________________________________ Contents Preface.................................................. xi 1 RSX-11M New Features, Restrictions, and Supplementary Information 1.1 Summary of New Features......................... 1-1 1.2 Changes in the Distribution Kit and System Generation...................................... 1-2 1.2.1 Disk Save and Compress Utility ............... 1-2 1.2.2 Copying Magnetic Tape Kits Standalone ........ 1-3 1.2.3 Copying Magnetic Tape Kits Online ............ 1-3 1.2.4 Online System Generation Restriction ......... 1-4 1.2.5 New AT. Task ................................. 1-4 1.3 Layered Product Files........................... 1-4 1.4 New Hardware Support in Version 4.7............. 1-5 1.4.1 Support for the KDJ11-E Processor ............ 1-6 1.4.2 RA71, RA72, and RA92 Disk Support ............ 1-6 1.4.3 Supplementary Hardware Information ........... 1-6 1.5 Software Enhancements for Version 4.7 .......... 1-6 1.5.1 Support for Year 2000 in Date Format ......... 1-6 1.5.1.1 Changes to the File Exchange Utility (FLX) for Year 2000 and Beyond................... 1-9 1.6 Software Problems Corrected in Version 4.7 ..... 1-9 1.6.1 Backup and Restore Utility (BRU) Corrections................................... 1-10 1.6.1.1 Invalid Date or Time Error with /REVISED... 1-10 1.6.1.2 BRU Error Message Contains Extraneous Text....................................... 1-10 1.6.1.3 BRU Aborted Following a Tape Error......... 1-10 1.6.2 Correction to SHUTUP ......................... 1-10 iii  1.6.3 Corrections to Peripheral Interchange Program (PIP)......................................... 1-10 1.6.3.1 Specifying Files Using a Wildcard.......... 1-10 1.6.3.2 PIP Did Not Give Correct Error for Command [34,477]/LI................................ 1-11 1.6.4 KW11-P Clock ................................. 1-11 1.6.5 FAL .......................................... 1-11 1.6.6 Support for RA82 Errors ...................... 1-11 1.6.7 Parity Problems with Terminal Multiplexers ... 1-11 1.6.8 Incompatibility Between VMS DIFFERENCES Command and RSX DCL DIFFERENCES Command....... 1-12 1.6.9 Enhancement to the DCL SORT Command .......... 1-12 1.6.10 Correction to FLX ........................... 1-12 1.6.11 Intermittent Problem When Getting Data Late Errors on RK06 or RK07 Drives................. 1-12 1.7 Software Problems and Restrictions in Version 4.7............................................. 1-12 1.7.1 Error Logging Restrictions ................... 1-13 1.7.1.1 Support for Error Logging History Summaries.................................. 1-13 1.7.2 BRU Restrictions ............................. 1-13 1.7.2.1 Use of Wildcards in BRU.................... 1-13 1.7.2.2 Problem with the /NEW_VERSION Qualifier.... 1-13 1.7.3 Tasks Hang When Attaching to Another Terminal Already Attached to a Task.................... 1-14 1.7.4 ELI/SH Reports No Errors if ELI/NOLIM Has Been Set........................................... 1-14 1.7.5 Problem with Unused Terminal Ports ........... 1-14 1.7.6 Task Builder (TKB) Restriction ............... 1-15 1.7.7 FCSRES Restriction ........................... 1-15 1.8 Supplementary System Generation, Programming, and Device Information.......................... 1-15 1.8.1 Supplementary Information on Changes in the Distribution Kit and System Generation........ 1-15 1.8.2 Using Logical Names in Performing a System Generation on a VAX-11 RSX Host............... 1-16 1.8.3 Copying the RSX-11M Distribution Tape on a VAX-11 RSX Host............................... 1-18 1.8.4 Selecting Printer Support During System Generation.................................... 1-19 1.8.4.1 Modifying Printer Support.................. 1-20 iv  1.8.5 System Generation Restrictions ............... 1-21 1.8.5.1 Minimum Requirements for System Generation and Installation........................... 1-21 1.8.5.2 SYSGEN Invokes VMR when Using a VAX-11 RSX Host....................................... 1-22 1.8.5.3 Copying the Distribution Tape to Disk...... 1-22 1.8.5.4 Saved Answer Files......................... 1-22 1.8.5.5 GBLDEF Enhancement......................... 1-22 1.8.6 System Generation Device Restrictions and Supplementary Information..................... 1-22 1.8.6.1 LPA-11K Device Restrictions for System Generation................................. 1-22 1.8.6.2 MSCP Device Restrictions for System Generation................................. 1-23 1.8.6.3 Indirect Command Processor Restrictions.... 1-24 1.8.7 Supplementary Information on Device Support .. 1-24 1.8.7.1 Device Support for RA70 and RA90 Disk Drives and for SA550 and SA650 Arrays...... 1-24 1.8.7.2 VT300-series Terminal Functions in VT200 Mode....................................... 1-24 1.8.7.3 CXF32/DHF11 Module Support................. 1-25 1.8.7.4 CXA16, CXB16, and CXY08 Multiplexer Support.................................... 1-25 1.8.7.5 Terminal Driver Support.................... 1-26 1.8.7.6 Asynchronous Terminal Interfaces Support... 1-26 1.8.7.7 J11-Series Processor Support............... 1-26 1.8.7.8 Large Disk Support......................... 1-26 1.8.7.9 BRU64K Device Support...................... 1-27 1.8.7.10 Network Command Terminal Support........... 1-27 1.8.7.11 Digital Storage Architecture Support....... 1-27 1.8.7.12 Devices and Products No Longer Supported... 1-28 1.8.8 Hardware Restrictions ........................ 1-28 1.8.8.1 RX50/RX33 Diskette Restriction............. 1-28 1.8.8.2 Transportability Among 22-Bit Systems...... 1-29 1.8.8.3 Bootstrapping a DB-, DM-, or DR-Based System..................................... 1-29 1.8.8.4 LK201 Keyboard Restriction................. 1-29 1.8.8.5 DLVJ1 Four-Line Terminal Interface Restriction................................ 1-29 1.8.8.6 RQDX1 Controller Restriction............... 1-30 1.8.8.7 TK50/TZ30 Restriction...................... 1-30 1.8.8.8 LSI-11/73 Processor Restriction............ 1-30 v  1.8.9 Micro/RSX File Transfer Utility Supplementary Information................................... 1-30 1.9 Executive Supplementary Information............. 1-31 1.9.1 Executive Code Changes ....................... 1-31 1.9.2 Executive Data Structure Changes ............. 1-32 1.9.3 I/O Data Structure Changes ................... 1-33 1.10 Supplementary Information on the MAKESTK.CMD Command File.................................... 1-33 1.10.1 FCSRES and FCSFSL ............................ 1-34 1.11 System Library Routines Supplementary Information..................................... 1-35 1.12 Device Drivers.................................. 1-35 1.12.1 DU Driver Enhancement ........................ 1-36 1.12.2 Device Driver Restriction .................... 1-36 1.12.3 TK50 Tape Subsystem Supplementary Information................................... 1-36 1.12.3.1 TK50 Performance when Using RSX Utilities.................................. 1-38 1.12.3.2 TK50 Indicators............................ 1-43 1.12.4 Supplementary Information on User-Written Device Drivers................................ 1-44 1.12.4.1 Asynchronous Buffered I/O.................. 1-44 1.12.4.2 Overlapped I/O Completion.................. 1-46 1.13 I/O Operations.................................. 1-47 1.13.1 Crash Driver Modification for 4Mb-Memory Systems....................................... 1-47 1.13.2 I/O Operations Restrictions .................. 1-47 1.13.2.1 Multibuffer Processing in Random Mode...... 1-47 1.13.2.2 Big Buffering in Random Mode............... 1-48 1.13.2.3 Block Size on Tapes Mounted with the /NOLABEL Qualifier......................... 1-48 1.13.3 I/O Operations Supplementary Information ..... 1-48 1.13.3.1 Support for Using FCS to Queue Files for Printing................................... 1-49 1.13.3.2 File Attribute Codes....................... 1-49 1.14 Error Logging Enhancements, Restrictions, and Supplementary Information....................... 1-49 1.14.1 Bad Block Replacement Enhancement ............ 1-50 1.14.2 Error Logging Restriction .................... 1-50 vi  1.14.3 Supplementary Information on Error Logging ... 1-50 1.14.3.1 Possible Error in Error Logging History Summary.................................... 1-50 1.14.3.2 Error Logging Support for a Non-Digital Device..................................... 1-51 1.15 Supplementary Software Information.............. 1-51 1.15.1 Disk Save and Compress Utility ............... 1-51 1.15.2 File Control Services Changes Supplementary Information................................... 1-52 1.15.3 TKB Restrictions and Supplementary Information................................... 1-53 1.15.3.1 OTS Fast Map Restriction................... 1-53 2 RSX-11S New Features, Restrictions, and Supplementary Information 2.1 Summary of New Features......................... 2-2 2.2 The Distribution Kit Media...................... 2-2 2.2.1 Supplementary Information on Device Support .. 2-2 2.3 Layered Product Files........................... 2-2 2.4 Restrictions.................................... 2-3 2.5 New Hardware Support in Version 4.7............. 2-3 2.5.1 Support for the KDJ11-E Processor ............ 2-4 2.5.2 RA71, RA72, and RA92 Disk Support ............ 2-4 2.5.3 Supplementary Hardware Information ........... 2-4 2.6 Software Enhancements for Version 4.7 .......... 2-4 2.6.1 Support for Year 2000 in Date Format ......... 2-5 2.7 Software Problems Corrected in Version 4.7 ..... 2-7 2.7.1 Correction to SHUTUP ......................... 2-7 2.7.2 KW11-P Clock ................................. 2-7 2.7.3 FAL .......................................... 2-7 2.7.4 OTL Returned an Error When Trying to Load NCP/EVC....................................... 2-8 2.7.5 Correction to FLX ........................... 2-8 2.7.6 Intermittent Problem When Getting Data Late Errors on RK06 or RK07 Drives................. 2-8 2.8 Software Problems and Restrictions in Version 4.7............................................. 2-8 2.8.1 BRU Restrictions ............................. 2-8 2.8.1.1 Use of Wildcards in BRU.................... 2-8 2.8.1.2 Problem with the /NEW_VERSION Qualifier.... 2-9 2.8.2 Tasks Hang When Attaching to Another Terminal Already Attached to a Task.................... 2-9 vii  2.8.3 Problem with Unused Terminal Ports ........... 2-10 2.9 Software Problems Corrected Since Version 4.5... 2-10 2.9.1 INITL Module Fails to Clear Certain Memory Locations on Boot............................. 2-10 2.9.2 OTL Corrupts System After Task Load Error in Undersized Partition.......................... 2-11 3 RMS-11 Version 2.0 Release Notes 3.1 RMS-11 Corrections.............................. 3-1 3.1.1 RMS-11 Local Access .......................... 3-1 3.1.2 Partial Block Writes with Block I/O .......... 3-2 3.2 Restrictions to RMS-11 Remote Access Methods (RMSDAP)........................................ 3-2 3.2.1 Incorrect Interpretation of Keysize Field Values........................................ 3-2 3.2.2 Using RMSDAP on Your System .................. 3-2 3.3 Corrections to RMS-11 Utilities................. 3-4 3.3.1 RMSIFL Correction ............................ 3-4 3.3.2 RMSDES Correction ............................ 3-4 3.3.3 RMSBCK Corrections ........................... 3-4 3.3.4 RMSRST Corrections ........................... 3-5 3.3.5 Additional Corrections to Three Utilities .... 3-6 3.4 RMS-11 Supplementary Information................ 3-6 3.4.1 Building Combined Supervisor Mode and Remote Access RMS Programs........................... 3-6 3.4.2 Enhancements to RMSDES Utility ............... 3-6 3.5 RMS-11 Restrictions............................. 3-7 3.5.1 Restrictions to RMS-11 Utilities ............. 3-7 3.5.1.1 RMSIFL Restrictions........................ 3-7 3.5.1.2 RMSCNV Restriction......................... 3-7 3.5.2 RMS-11 Version 2.0 Installation .............. 3-7 3.5.2.1 RL01/RL02 and RK06 Procedures.............. 3-8 3.5.2.2 Startup Command Procedures................. 3-8 3.5.2.3 Utility Configurations..................... 3-9 3.5.2.4 Utility Command and ODL Files.............. 3-9 3.5.2.5 Rebuilding the Utilities................... 3-10 3.5.3 Files and Placement on the Distribution Kit .. 3-11 3.5.4 Reporting Problems ........................... 3-14 viii  4 Documentation Corrections 4.1 IAS/RSX-11 System Library Routines Reference Manual.......................................... 4-1 4.2 RSX-11M Guide to Writing an I/O Driver.......... 4-5 4.2.1 Changes to System Data Structures ............ 4-5 4.2.2 I/O Packet Description ....................... 4-5 4.2.3 I/O Queue Description ........................ 4-5 4.2.4 Text for Driver Initiator Section ............ 4-5 4.2.5 MACRO-11 Command Line Error .................. 4-6 4.2.6 Building User-Written Drivers ................ 4-6 4.2.7 I.PRM Description ............................ 4-7 4.2.8 S.VCT Description ............................ 4-7 4.2.9 U.BUF Description ............................ 4-7 4.3 RSX-11M System Generation and Installation Guide........................................... 4-8 4.4 RSX-11M-PLUS I/O Operations Reference Manual.... 4-8 4.5 RSX-11M/M-PLUS Batch and Queue Operations Manual.......................................... 4-9 4.6 RSX-11M/M-PLUS Command Language Manual.......... 4-9 4.6.1 Corrections to /CREATED/BEFORE and /MODIFIED/BEFORE Qualifiers................... 4-9 4.6.2 BACKUP Command Qualifiers .................... 4-10 4.6.3 Underscore Character Permitted in BACKUP Command Qualifier............................. 4-10 4.6.4 ANALYZE/ERROR_LOG Command .................... 4-10 4.6.5 /HEADERS:n and /MAXIMUM_FILES:n Qualifiers in the DCL Command INITIALIZE.................... 4-11 4.6.6 Unloading Magnetic Tape ...................... 4-13 4.7 RSX-11M/M-PLUS Error Logging Manual............. 4-13 4.8 RSX-11M/M-PLUS Guide to Program Development..... 4-16 4.9 RSX-11M/M-PLUS I/O Drivers Reference Manual..... 4-16 4.10 RSX-11M/M-PLUS Indirect Command Processor Manual.......................................... 4-16 4.11 RSX-11M/M-PLUS MCR Operations................... 4-23 4.11.1 /BAD Option Keyword in the MCR Command INI ... 4-24 4.11.2 /TERM Qualifier in the MCR Command SET ....... 4-25 4.11.3 /TERM Qualifier in the MCR Command ASN ....... 4-25 4.11.4 DEFER Option in the MCR MOUNT and SET Commands...................................... 4-25 4.11.5 /HSYNC Command Keyword in the MCR SET Command....................................... 4-25 ix  4.11.6 /INF and /MXF Keywords in the MCR Command INI........................................... 4-25 4.12 RSX-11M/M-PLUS RMS-11 Macro Programmer's Guide.. 4-27 4.13 RSX-11M/M-PLUS RMS-11 User's Guide.............. 4-28 4.14 RSX-11M/M-PLUS RMS-11 Utilities................. 4-30 4.15 RSX-11M/M-PLUS System Management Guide.......... 4-36 4.15.1 The TDX Catchall Task ........................ 4-41 4.15.1.1 Installing TDX............................. 4-41 4.15.1.2 TDX Commands and MCR Translations.......... 4-41 4.15.1.3 Modifying the TDX Source File.............. 4-44 4.15.1.4 Installing Tasks Permanently............... 4-46 4.16 RSX-11M/M-PLUS Utilities Manual................. 4-46 4.16.1 Backup and Restore Utility (BRU) ............. 4-46 4.16.1.1 Selective Backups.......................... 4-47 4.16.1.2 Wildcards in Input Specifications.......... 4-47 4.16.1.3 Options Added to /COMPARE and /VERIFY Qualifiers................................. 4-48 4.16.1.4 BRU /COMPARE and /VERIFY Examples.......... 4-49 4.16.1.5 /ERROR_LIMIT Qualifier..................... 4-50 4.16.1.6 /IDENTIFICATION Qualifier.................. 4-51 4.16.1.7 Removal of IMAGE Backup and Restore Code from BRU64K................................ 4-51 4.16.1.8 Locating and Booting Standalone BRUSYS..... 4-51 4.16.1.9 Skipping Over a Bootable System Image...... 4-52 4.16.1.10 Using the MANUAL Option.................... 4-53 4.16.1.11 Tape Write Error Message................... 4-53 4.16.1.12 Executing Command Files.................... 4-53 4.16.1.13 Changes in the CNF Table for Standalone BRU........................................ 4-54 4.16.1.14 /NOSUPERSEDE Qualifier..................... 4-54 4.16.1.15 BRU Error Messages......................... 4-54 4.16.2 Disk Save and Compress Utility ............... 4-56 4.16.3 File Dump Utility (DMP) ...................... 4-56 4.16.3.1 New /LIM Switch............................ 4-57 4.16.3.2 Correction to /HF Switch Description....... 4-57 4.16.4 File Transfer Program (FLX) .................. 4-57 4.16.5 Disk Volume Formatter (FMT) .................. 4-59 4.16.6 Librarian Utility Program (LBR) .............. 4-59 4.16.6.1 User File Attributes....................... 4-60 4.16.6.2 Create Switch Error........................ 4-60 4.16.6.3 The /IN Switch for Macro Libraries......... 4-61 4.16.7 Object Module Patch Utility (PAT) ............ 4-61 x  4.16.8 Peripheral Interchange Program (PIP) ......... 4-61 4.16.8.1 The /DD Switch Format Error................ 4-61 4.16.8.2 The /TD Switch Format Error................ 4-62 4.16.9 Source Language Input Program (SLP) .......... 4-62 4.16.9.1 Error Message Format....................... 4-62 4.16.9.2 Maximum Number of Characters in File Names...................................... 4-62 4.16.9.3 Illegal Switch Error Message............... 4-62 4.17 RSX-11M/M-PLUS and Micro/RSX Crash Dump Analyzer Reference Manual................................ 4-63 4.18 RSX-11M/M-PLUS and Micro/RSX Debugging Reference Manual.......................................... 4-63 4.19 RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual.......................................... 4-63 4.20 RSX-11M/M-PLUS and Micro/RSX I/O Operations Reference Manual................................ 4-64 4.21 RSX-11M/M-PLUS and Micro/RSX Task Builder Manual.......................................... 4-64 4.21.1 Double Brackets .............................. 4-65 4.21.2 Manual References ............................ 4-65 4.21.3 Reference to "/" for the /MP Switch .......... 4-65 4.21.4 /SHAREABLE:LIBRARY Switch Description ........ 4-65 4.21.5 Incorrect Device Specification ............... 4-65 4.21.6 Errors in Overlay Capability ................. 4-65 4.21.7 TKB Combinations of the /-PI and /LI Switches...................................... 4-66 4.21.8 References to the /-CO and /-LI Switches ..... 4-66 4.21.9 Offsets ...................................... 4-67 4.21.10 New TKB Error Message ........................ 4-67 4.21.11 TKB Option - RNDSEG .......................... 4-67 4.21.12 Map Problem for Non-PIC Shared Region ........ 4-68 4.21.13 Cluster Libraries ............................ 4-69 4.21.14 Changing Values in an Installed Common ....... 4-69 4.21.15 Using the /SS Switch with the RSX11M.STB File.......................................... 4-69 4.21.16 Slow Task Builder (STK) Restriction for Layered Products.............................. 4-70 4.21.17 The /CL Switch and the /CODE:CLI Qualifier ... 4-71 4.21.18 The /FM Switch and the /FAST_MAP Qualifier ... 4-72 4.22 RSX-11S System Generation and Installation Guide........................................... 4-73 xi  A Reporting Problems Index Tables 1-1 Version 4.7 Layered Products ................. 1-4 1-2 Storage of Dates in RSX Systems after 1990 ... 1-7 1-3 TK50 Performance and RSX Utilities ........... 1-38 2-1 Layered Products for RSX-11S Version 4.7 ..... 2-2 2-2 Storage of Dates in RSX Systems after 1990 ... 2-6 4-1 Table 6-1 $EDMSG Routine Editing Directives .. 4-2 4-2 Table 6-1 $EDMSG Routine Editing Directives .. 4-3 4-3 Number of Index File Headers ................. 4-12 4-4 Default Number of Files - Approximation ...... 4-12 4-5 Number of Index File Headers ................. 4-26 4-6 Default Number of Files - Approximation ...... 4-26 xii  ________________________________________________________________ Preface Manual Objectives The RSX-11M/RSX-11S Release Notes contains important information for using the RSX-11M operating systems. Read this document before generating and using your system. This manual contains the following categories of information: o Descriptions of new software features, as well as changes to existing software features o Descriptions of software and hardware restrictions o Supplementary information, which appeared in previous release notes but is still applicable o Corrections to documentation errors and omissions o Software modifications, restrictions, and supplementary information for RMS-11 Version 2.0 o Correction files and restrictions for layered products Intended Audience This manual is intended for all users of the RSX-11M and RSX-11S operating systems. Document Structure Chapter 1 describes software features, software and hardware restrictions, and supplementary information for the RSX-11M operating system. xi  Chapter 2 describes software features, software and hardware restrictions, and supplementary information for the RSX-11S operating system. Chapter 3 describes software modifications, restrictions, and supplementary information for RMS-11 Version 2.0. Chapter 4 corrects errors and omissions in the RSX-11M, RSX-11S, and RMS-11 documentation sets. Appendix A describes the procedure for submitting a Software Performance Report (SPR). Conventions The following conventions are used in this manual: __________________________________________________________ Convention______________Meaning___________________________ MCR> A right angle bracket is the default prompt for the Monitor Console Routine (MCR), which is one of the command interfaces used on RSX-11M/S systems. All systems include MCR. $ A dollar sign followed by a space is the default prompt of the Digital Command Language (DCL), which is one of the command interfaces used on RSX-11M/S systems. Many systems include DCL. DCL> This is the explicit prompt of the Digital Command Language (DCL). xxx> Three characters followed by a right angle bracket indicate the explicit prompt for a task, utility, or program on the system. xii  __________________________________________________________ Convention______________Meaning___________________________ UPPERCASE Uppercase letters in a command line indicate letters that must be entered as they are shown. For example, utility switches must always be entered as they are shown in format specifications. command abbreviations Where short forms of commands are allowed, the shortest form acceptable is represented by uppercase letters. The following example shows the minimum abbreviation allowed for the DCL command DIRECTORY: $ DIR lowercase Any command in lowercase must be substituted for. Usually the lowercase word identifies the kind of substitution expected, such as a filespec, which indicates that you should fill in a file specification. For example: filename.filetype;version This command indicates the values that comprise a file specification; values are substituted for each of these variables as appropriate. /keyword, A command element preceded by a /qualifier, slash (/) is an MCR keyword; a or DCL qualifier; or a task, utility, /switch or program switch. Keywords, qualifiers, and switches alter the action of the command they follow. xiii  __________________________________________________________ Convention______________Meaning___________________________ parameter Required command fields are generally called parameters. The most common parameters are file specifications. [option] Brackets indicate optional entries in a command line or a file specification. If the brackets include syntactical elements, such as periods (.) or slashes (/), those elements are required for the field. If the field appears in lowercase, you are to substitute a valid command element if you include the field. Note that when an option is entered, the brackets are not included in the command line. [, . . . ] Brackets around a comma and horizontal ellipsis points indicate that you can use a series of optional elements separated by commas. For example, (argument[, . . . ]) means that you can specify a series of optional arguments by enclosing the arguments in parentheses and by separating them with commas. { } Braces indicate a choice among required options. You must choose one of the options listed. xiv  __________________________________________________________ Convention______________Meaning___________________________ :argument Some parameters and qualifiers can be altered by the inclusion of arguments preceded by a colon. An argument can be either numerical (COPIES:3) or alphabetical (NAME:QIX). In DCL, the equal sign (=) can be substituted for the colon to introduce arguments. COPIES=3 and COPIES:3 are the same. ( ) Parentheses are used to enclose more than one argument in a command line. For example: SET PROT = (S:RWED,O:RWED) , Commas are used as separators for command line parameters and to indicate positional entries on a command line. Positional entries are those elements that must be in a certain place within the command line. Although you might omit elements that come before the desired element, the commas that separate them must still be included. . Periods immediately following a number indicate a decimal number. For example, 600. would mean 600(10). xv  __________________________________________________________ Convention______________Meaning___________________________ [g,m] The convention [g,m] signifies a [directory] User Identification Code (UIC). The g is a group number and the m is a member number. The UIC identifies a user and is used mainly for controlling access to files and privileged system functions. This may also signify a User File Directory (UFD), commonly called a directory. A directory is the location of files. Other notations for directories are: [ggg,mmm], [gggmmm], [ufd], [name], and [directory]. The convention [directory] signifies a directory. Most directories have 1- to 9-character names, but some are in the same [g,m] form as the UIC. Where a UIC, UFD, or directory is required, only one set of brackets is shown (for example, [g,m]). Where the UIC, UFD, or directory is optional, two sets of brackets are shown (for example, [[g,m]]). Vertical ellipsis points show . where elements of command input or . statements in an example or figure . have been omitted because they are irrelevant to the point being discussed. xvi  __________________________________________________________ Convention______________Meaning___________________________ filespec A full file specification includes device, directory, file name, file type, and version number, as shown in the following example: DL2:[46,63]INDIRECT.TXT;3 Full file specifications are rarely needed. If you do not provide a version number, the operating system uses the highest numbered version. If you do not provide a directory, the system uses the default directory. Some system functions default to particular file types. Many commands accept a wildcard character (*) in place of the file name, file type, or version number. Some commands accept a file specification with a DECnet node name. . A period in a file specification separates the file name and file type. When the file type is not specified, the period may be omitted from the file specification. ; A semicolon in a file specifi- cation separates the file type from the file version. If the version is not specified, the semicolon may be omitted from the file specification. xvii  __________________________________________________________ Convention______________Meaning___________________________ @ The at sign invokes an indirect command file. The at sign immediately precedes the file specification for the indirect command file, as follows: @filename[.filetype;version] . . . Horizontal ellipsis points indicate the following: o Additional, optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. KEYNAME This typeface denotes one of the keys on the terminal keyboard; for example, the Return key. print and type As these words are used in the text, the system prints and the user enters. The symbol means that you are to press the key marked Ctrl while pressing another key. Thus, indicates that you are to press the Ctrl key and the Z key together in this fashion. Ctrl/Z is echoed on some terminals as ^Z. However, not all control ________________________characters_echo.__________________ xviii  1 ________________________________________________________________ RSX-11M New Features, Restrictions, and Supplementary Information This chapter describes new features and restrictions and provides supplementary information for the Version 4.7 operating system. Section 1.1 summarizes new features; Section 1.2 describes changes to the distribution kit and to system generation; and Section 2.5 deals with device support. Subsequent sections deal with operating-system components individually. The information on individual system components is divided into three categories: New features and Describes new features and enhance- enhancements ments to existing features for Version 4.7. Restrictions Describes restrictions to software performance. Supplementary Describes software changes that were information documented in previous release notes and other information that is not included in the RSX-11M Version 4.2 documentation set but is still applicable to the software. If no new information or restrictions are provided for a component, that component is unchanged in Version 4.7. 1.1 Summary of New Features The changes to the RSX-11M operating system for Version 4.7 and previous versions are described throughout this chapter by operating-system component. Version 4.7 changes are summarized here as follows: o Support for the year 2000 and beyond. RSX-11M New Features, Restrictions, and Supplementary Information 1-1  o Support for the RA71, RA72, and RA92 devices. o Support for the RQZX1 SCSI adapter. o KDJ11-E Processor (used in MicroPDP-11/93 and PDP-11 /94). 1.2 Changes in the Distribution Kit and System Generation The magnetic tape distribution kits that contain the files for generating the new system have been changed since RSX-11M Version 4.5. For Versions 4.5, 4.6, and 4.7, the distribution kits are supplied on the following media: o Five RL02 cartridge disks. o One TK50 magnetic tape cartridge. The tape contains BRU64K and the operating system files. BRU64K is at the beginning of the tape. o Two 9-track, 800-bpi, 2400-foot magnetic tapes. BRU64K is at the beginning of the first of the two numbered tapes. o One 9-track, 1600-bpi, 2400-foot magnetic tape. BRU64K is at the beginning of the tape. Note that BRU64K replaces BRUSYS. BRU64K has included support for MU devices since Version 4.4 and can now be used to copy the system files to any supported device. The Disk Volume Formatter (FMT) and BRU image mode functions are not included in BRU64K but are included in the operating system. Users requiring BRUSYS can create it using the information in Section 4.16.1.8. 1.2.1 Disk Save and Compress Utility RSX-11M Version 4.6 was the last release to have the Disk Save and Compress utility (DSC) included on the software kit. Any data currently saved on media by the DSC utility will have to be restored using the DSC utility and then resaved using the Backup and Restore Utility (BRU). Beginning with RSX-11M Version 4.7, users will have to use the save and compression features of BRU. 1-2 RSX-11M New Features, Restrictions, and Supplementary Information  1.2.2 Copying Magnetic Tape Kits Standalone Since Version 4.5, BRU64K has been placed at the beginning of the first or only tape (depending on which form of the distribution kit you have purchased) that contains the system files. When you load and boot the tape, it will bring up standalone BRU64K, which you can then use to copy the remainder of the tape to your system disk. This means that some information in your Version 4.2 RSX- 11M System Generation and Installation Guide is no longer applicable, as follows: o The first sentence at the top of page 2-5 should read "The BRU64K System - Each tape distribution kit contains a BRU64K system." The next two sentences should be deleted. o Item 1 on page 2-6 should begin with "Load the distribution tape on the appropriate tape drive" instead of "Load the BRU64K tape on the appropriate tape drive." The next sentence, which is enclosed in parentheses, should be deleted. o Item 2 on page 2-7 should say "Hardware bootstrap the distribution tape" instead of "Hardware bootstrap the BRU64K or BRUSYS tape." o Item 6 on page 2-8 should be deleted. 1.2.3 Copying Magnetic Tape Kits Online Version 4.6 and later magnetic tape kits can be copied (as indicated by the RSX-11M System Generation and Installation Guide, Section 2.3.2) on online systems that have been upgraded to at least RSX-11M Version 4.1 Update D, RSX-11M-PLUS Version 3.0 Update D, or VAX-11 Version 2.3. RSX-11M New Features, Restrictions, and Supplementary Information 1-3  1.2.4 Online System Generation Restriction When performing a Version 4.6 or later online system generation, SYSGEN will always install the Task Builder (TKB) supplied on the distribution kit. TKB is installed under the task name . . . TKL. ________________________Note ________________________ You must be a privileged user to perform an online system generation. _____________________________________________________ 1.2.5 New AT. Task Beginning with RSX-11M Version 4.7, ICX.TSK, which is a new version of the Indirect Command Processor, is used as the AT. task image on baseline systems. 1.3 Layered Product Files The following table lists the layered products that have been updated for this release. Table_1-1_Version_4.7_Layered_Products__________________________ Directories Backup Documentation Layered_Product_______Used_________Set__________File_Name_______ PDP-11 BASIC-PLUS-2 [211,200] BP2 [211,200]BP2.DOC Version 2.7 DATATRIEVE-11/RSX [222,200] DTR [222,200]DTRREL.DOC Version 3.3 DCX KMV11-A [224,200] DCX [224,200]DCX.DOC Development Tools Version 1.03 (continued on next page) 1-4 RSX-11M New Features, Restrictions, and Supplementary Information  Table_1-1_(Cont.)_Version_4.7_Layered_Products__________________ Directories Backup Documentation Layered_Product_______Used_________Set__________File_Name_______ DECnet-11M [230,200] DECNET [230,200]DECNET.DOC Version 4.7 [225,20] [230,20] KMV11-A HDLC [253,200] KMV11 [253,200]KMV11.DOC Framing Software Version 1.02 KMV11 X25 Link Level [322,200] KXI [322,200]KXI.DOC Version 1.03 PDP-11 FORTRAN-77 [246,200] F77 [246,200]F77.DOC ____Version_5.4_________________________________________________ In the Version 4.7 RL02 kits, all the layered product files are located on the disk labeled RMSV20. 1.4 New Hardware Support in Version 4.7 The following new devices are supported: o RA71 o RA72 o RA92 o RQZX1 SCSI adaptor: - RZ23L - RZ24L - TZ30 ______________________ Caution ______________________ ANSI tape processing for information interchange is not supported on the TZ30 cartridge tape drive. _____________________________________________________ o KDJ11-E Processor (used in MicroPDP-11/93 and PDP-11 /94) RSX-11M New Features, Restrictions, and Supplementary Information 1-5  1.4.1 Support for the KDJ11-E Processor Support for the KDJ11-E processor module has been added to Version 4.7. The following features are supported: o The module ID o The TOY clock (Time of Year clock) o On-board serial lines (as terminal driver option) Support has been added in SYSGEN, ACF, Error Logging, SAVE, the Executive, and the MCR SET TIME command for this processor. 1.4.2 RA71, RA72, and RA92 Disk Support Error logging support has been added for the RA71, RA72, and RA92 disk devices. 1.4.3 Supplementary Hardware Information For a complete list of hardware supported by Version 4.7, refer to the Software Product Description contained in your media kit. 1.5 Software Enhancements for Version 4.7 This section describes software enhancements added to Version 4.7. 1.5.1 Support for Year 2000 in Date Format The RSX operating systems have been changed to support dates beyond the year 2000. Generally, RSX treats the current year as a two-digit field. The following areas of the RSX system have been changed: o Input-All areas of the system that allow input of a date will now accept two different forms of date input. First, the traditional dates of the dd-mmm-yy format (or mm/dd/yy for TIM) will still be accepted. These dates will always be considered as occurring between the years 1900 and 1999. In addition, the date may now be specified as dd-mmm-yyyy or (mm/dd/yyyy for TIM only), to allow the system to recognize dates occurring after 1999. 1-6 RSX-11M New Features, Restrictions, and Supplementary Information  o Output-In order to preserve compatibility in appli- cations that parse the output of system commands, the format of date output will not be changed. All places that output the date as 2 digits will continue to do so, representing 2000 as 00, and so forth. Places that currently output the date as 4 digits will still output the date as 4 digits. o Internal representations-As documented for the GTIM$ directive, the year field of time vectors is the number of years since 1900. This is still accurate. This field will reach 100(10) in the year 2000. For example, Table 2-2 shows how dates between years 1900 and 2209 will be stored. Dates will be displayed as the lower two digits of the real year or as a four- digit year. However, ODS-I only provides a 7-byte ASCII field for creation and other dates. In order to accommodate this restriction in a way that is consistent with RSX date handling, the 2-bytes of year in the date attribute will be used to represent the year since 1900. The two bytes will be encoded as follows: - Low byte-Low order decimal digit of year, in ASCII. - High byte-Quotient of years since 1900 divided by 10, plus 60(8). This represents the ASCII high digit of the year from 1900 - 1999. In 2000, however, this will result in ":" being stored for the high digit of the year. For years 2010 through 2019, ";" will be stored, and so forth. This change should result in another 200 years or more of file representations. Table_1-2_Storage_of_Dates_in_RSX_Systems_after_1990______ Calendar_Year____Year_Field_Representation________________ 1990 - 1991 90 - 99 2000 - 2009 :0 - :9 (continued on next page) RSX-11M New Features, Restrictions, and Supplementary Information 1-7  Table 1-2 (Cont.) Storage of Dates in RSX Systems after __________________1990____________________________________ Calendar_Year____Year_Field_Representation________________ 2010 - 2019 ;0 - ;9 2020 - 2029 <0 - <9 2030 - 2039 =0 - =9 2040 - 2049 >0 - >9 2050 - 2059 ?0 - ?9 2060 - 2069 @0 - @9 2070 - 2079 A0 - A9 2080 - 2089 B0 - B9 2090 - 2099 C0 - C9 2100 - 2109 D0 - D9 2110 - 2119 E0 - E9 2120 - 2129 F0 - F9 2130 - 2139 G0 - G9 2140 - 2149 H0 - H9 2150 - 2159 I0 - I9 2160 - 2169 J0 - J9 2170 - 2179 K0 - K9 2180 - 2189 M0 - M9 2190 - 2199 N0 - N9 2200_-_2209______O0_-_O9__________________________________ The following features have been changed to accept or display the new date format: o BROADCAST utility o BRU utility o The following DCL commands: - SET TIME - DIR/SINCE - BACKUP o F11ACP 1-8 RSX-11M New Features, Restrictions, and Supplementary Information  o MACRO o PIP utility o RPT and the /DATE qualifier o QMG o MCR command line interface o The following MCR commands: - BYE command - HEL command - TIM command 1.5.1.1 Changes to the File Exchange Utility (FLX) for Year 2000 and Beyond FLX has been modified to correctly record and display the dates of RT-11 files created after the year 2003. A FLX directory listing of RT-11 files will now display the century as part of the year. The FLX utility correctly displays dates from 1970 to 2001 with the /DO switch set. A C is displayed when the date is not in the valid range. Additionally, the dates displayed are invalid. However, the files are intact and correct. FLX will display the date as: ACF.TSK 33.C 15-NOV-98 The following example shows how FLX will display a file with invalid date information if the year is greater than 2001 (The <233> is the protection code.): ACF.TSK 33.C 19-70 <233> 1.6 Software Problems Corrected in Version 4.7 This section describes software problems corrected in Version 4.7. RSX-11M New Features, Restrictions, and Supplementary Information 1-9  1.6.1 Backup and Restore Utility (BRU) Corrections The following corrections have been made to the BRU utility. 1.6.1.1 Invalid Date or Time Error with /REVISED When using the /REVISED switch, BRU issued the following error message on files that contained no revision date: BRU -- *WARNING* -- Invalid date or time (filename) This problem has been fixed. 1.6.1.2 BRU Error Message Contains Extraneous Text While running a BRU backup from one disk to (192,000 blocks) to another (13,000), you sometimes received the following warning: This disk will not contain a hardware bootable system 002300.DIR;1 The last part of this warning indicating a file directory name was misleading. This problem has been fixed. 1.6.1.3 BRU Aborted Following a Tape Error Tape errors during the disk-to-tape backup operations occasionally caused BRU to terminate with an error message of "odd address trap." This problem has been fixed. 1.6.2 Correction to SHUTUP SHUTUP.TSK did not complete properly if the CO: device was logged in. SHUTUP.CMD would not execute and the CPU would not halt. This problem has been fixed by changing SHUTUP to log out all users before turning off console logging. 1.6.3 Corrections to Peripheral Interchange Program (PIP) The following corrections have been made to the PIP utility. 1.6.3.1 Specifying Files Using a Wildcard PIP was ignoring input wildcard file specifications when reading files from an ANSI tape. PIP was selecting all files instead of just those that matched the wildcard file specification supplied by the user. This worked correctly prior to Version 4.6. This problem has been fixed. 1-10 RSX-11M New Features, Restrictions, and Supplementary Information  1.6.3.2 PIP Did Not Give Correct Error for Command [34,477]/LI Previously, issuing a command such as PIP [34,477]/LI resulted in the following incorrect error message, "Cannot find directory file." Now, issuing this command will result in the following correct error message, "Bad directory syntax". 1.6.4 KW11-P Clock When trying to use the KW11-P clock by means of a CINT$ routine, when the clock was not being used as the system clock, the following DSW error was returned: IE.RSU (Vector in Use) This problem has been corrected. 1.6.5 FAL On Version 4.6, FAL would hang if a remote node issued a directory command with a blank file specification. For example: DIR REMNOD"usernam password"::LB:[1,2] This problem has been corrected. 1.6.6 Support for RA82 Errors Previously, RPT trapped on RA82 SDI errors. The MSCP8x error log control module has been updated to include support for RA82 SDI errors. This problem has been fixed. 1.6.7 Parity Problems with Terminal Multiplexers Previously, unsynchronized access to terminal multiplexer CSRs in terminal driver module TTYHV caused parity to be set on incorrect terminal lines. This problem has been fixed. RSX-11M New Features, Restrictions, and Supplementary Information 1-11  1.6.8 Incompatibility Between VMS DIFFERENCES Command and RSX DCL DIFFERENCES Command The DCL DIFFERENCES command did not accept DIFF A.TXT, B.TXT but would accept DIFF A.TXT B.TXT. The description of the DIFFERENCES command in the RSX-11M- PLUS Command Language Manual shows only the blank space as a valid file delimiter. A comma (,) can now be used as a valid file delimiter. 1.6.9 Enhancement to the DCL SORT Command Previously, DCL did not allow use of the /INDEXED_ SEQUENTIAL qualifier to the input and the output file for the DCL SORT command. DCL has been modified to allow use of the /INDEXED_SEQUENTIAL qualifier to both the SORT input and output files. 1.6.10 Correction to FLX Previously, FLX did not display the maximum number of blocks on a tape if the number of blocks was too large. This problem has been fixed. 1.6.11 Intermittent Problem When Getting Data Late Errors on RK06 or RK07 Drives Previously, there was an intermittent problem that resulted in getting data late errors. Due to potential inaccuracies in the way the RK06 reports word count when a data late is declared, the retry logic in the driver would restart the read or write operation in the wrong block. This problem has been fixed. 1.7 Software Problems and Restrictions in Version 4.7 This section describes software problems and restrictions that have not been corrected for Version 4.7. 1-12 RSX-11M New Features, Restrictions, and Supplementary Information  1.7.1 Error Logging Restrictions This section describes restrictions to Error Logging. 1.7.1.1 Support for Error Logging History Summaries Error logging history summaries are no longer supported. See Section 4.7. 1.7.2 BRU Restrictions This section describes restrictions to the Backup and Restore Utility (BRU). 1.7.2.1 Use of Wildcards in BRU BRU supports the asterisk (*) character only as a replacement of an entire field in a file specification. BRU will issue the "Invalid value or name" fatal syntax error when an asterisk is used to replace part of a file specification field. 1.7.2.2 Problem with the /NEW_VERSION Qualifier A problem with the /NEW_VERSION qualifier occurred when used in a BRU command line during a disk-to-disk backup. From the input device, BRU backed up multiple versions of a file in the order that they appeared in a directory, instead of in ascending order by version number. As a consequence, when the files were restored to the output device, new version numbers were assigned when each file was restored, and the original order of the files was not preserved. Thus, the last version of a file on the output device may not have been the last version created on the input device. The following workarounds are suggested to avoid this problem: o Sorting files on the input device. o Purging files prior to backing up your files. RSX-11M New Features, Restrictions, and Supplementary Information 1-13  1.7.3 Tasks Hang When Attaching to Another Terminal Already Attached to a Task Tasks would occasionally hang when they attempted to attach a terminal that was already attached to another task. The attach QIO request never returned and the task had to be manually aborted. As a workaround, the Marktime directive (MRKT$) can be used to implement a timeout function within the application code. If the attach function is issued as a QIOW, you can precede it with a MRKT$ directive, specifying the same event flag number using the I/O status block to distinguish between timeouts (IS.PND) and I/O completion (other values). Alternatively, the MRKT$ directive can specify an AST routine to be entered at the expiration of the timer with a CMKT immediately following the QIOW. There are other workarounds such as using WTLO or WTSE with QIO and MRKT$ directives. In these workarounds, the expiration of the time interval without I/O completion would signal the need for an I/O kill to be issued. 1.7.4 ELI/SH Reports No Errors if ELI/NOLIM Has Been Set If error log limiting has been disabled with the ELI /NOLIM switch, then subsequent hard errors are not displayed by the ELI /SH switch even though a full report generated with RPT shows that device hard errors have been logged. This restriction still exists. 1.7.5 Problem with Unused Terminal Ports The system can crash if you have an unused terminal port with a cable connected to the port. This problem can be eliminated by either removing the unused cables or setting the unused ports to slaved ports. 1-14 RSX-11M New Features, Restrictions, and Supplementary Information  1.7.6 Task Builder (TKB) Restriction To obtain the long version of the memory allocation file (map) when building an I&D task, you should specify only the /-SH switch (the DCL /LONG qualifier) after the map file in the command line. The /MA switch (the DCL /MAP qualifier) should not be specified with the /-SH switch for I&D tasks. 1.7.7 FCSRES Restriction Because the File Control Services Resident Library Routines (FCSRES) enhancement adds approximately 60(10) bytes to the size of the directory parsing code, the code is included only in FCSRES. The system library routines do not include this change. If you want to use this feature in your task, you must reference the modules PARDIL and PRSDIL instead of PARDI and PARSDI in your Task Builder ODL file. 1.8 Supplementary System Generation, Programming, and Device Information The following sections contain useful information about system generation, programming, devices, and restrictions. 1.8.1 Supplementary Information on Changes in the Distribution Kit and System Generation The following changes were made in the distribution kit prior to Version 4.5: o The procedure for copying the baseline system from the distribution kits to a disk was simplified. The baseline system includes an indirect command file called TAPEKIT.CMD, which guides you through the copying process. o For standalone system generations, the default control and status register (CSR) address that the Standalone Configuration and Disk Sizing Program (CNF) expects for MT-type devices was changed. Also, default values were added for MU-type devices. RSX-11M New Features, Restrictions, and Supplementary Information 1-15  o References in a previous release to an RC25 disk kit and an RC25-specific big disk magnetic tape kit were incorrect. Support for system generations targeted to RC25 system disks is provided in the magnetic tape distribution kit. o References in a previous release to an RP07 big disk magnetic tape kit were incorrect. There is no support for system generation targeted to the RP07. 1.8.2 Using Logical Names in Performing a System Generation on a VAX-11 RSX Host Because physical device names on VAX VMS systems are longer than those on RSX systems, the complete physical device name is not recognized by the SYSGEN procedure or RSX utilities such as the Backup and Restore Utility (BRU). This limitation is overcome by using what is known as a $$n logical name to refer to the device. The $$n logical names are defined for the devices on your VAX VMS system or VAXcluster by VAX-11 RSX when it is started. Please see the VAX-11 RSX Installation Guide and the VAX-11 RSX Release Notes for additional information on how the $$n names for your system are defined. Section 2.7 of the VAX-11 RSX Compatibility Mode Reference Manual provides more detailed information on $$n logical names. The $$n logical name for a device should be used in place of the VMS physical device name wherever a device specification is required. You can determine which $$n logical names correspond to the devices you are using with the following command: >SHOW LOGICAL $$* The following example illustrates how $$n names are used to copy a magnetic tape distribution kit and to prepare to invoke SYSGEN on a VAXcluster. The tape used is a TA78 on an HSC controller and the disk used is a local RK07 on controller B. 1-16 RSX-11M New Features, Restrictions, and Supplementary Information  >SHOW LOGICAL $$* (LNM$PROCESS_TABLE) (LNM$JOB_803299A0) (LNM$GROUP_000301) (LNM$SYSTEM_TABLE) "$$0" = "ALEX$DMA0:" "$$12" = "ALEX$DMB1:" "$$11" = "BLKHOL$MUA1:" "$$13" = "SYS$SPECIFIC:" "$$14" = "SYS$COMMON:" "$$16" = "BLKHOL$MUA0" "$$2" = "ALEX$MMA0:" "$$3" = "BLKHOL$DUA0:" "$$4" = "BLKHOL$DUA4:" "$$5" = "BLKHOL$DUA5:" "$$6" = "BLKHOL$DUA6:" "$$7" = "BLKHOL$DUA7:" >MOU $$16:/FOR >MOU $$12:/FOR >BAD $$12:/LIST >BRU BRU>/DENSITY:1600/VERIFY/INITIALIZE/BAC:DMSYS From: $$16: To" $$12: BRU - Starting Tape 1 on $$16: BRU - End of Tape 1 on $$16: BRU - Starting verify pass Tape 1 on $$16: BRU - End of Tape 1 on $$16: BRU - Completed BRU>[CTRL/Z] >DMO $$12:/NOUNLOAD >MOU $$12:RSXM67 >SET DEF $$12: >SET /UIC=[200,200] >@TAPEKIT Although using the $$n logical name is recommended, because it allows the use of any device on the system, it is not necessary in all cases. RSX-11M New Features, Restrictions, and Supplementary Information 1-17  If the devices you are using to copy the distribution kit and perform the SYSGEN are on controller A (the first controller for that device type) and they are local to the system you are using (not on another system or HSC in a VAXcluster), you may simply use an abbreviated form of the device name that omits the controller letter and node name. For example, the devices that appear in the SHOW LOGICAL display above as ALEX$MMA0: and ALEX$DMA0: may be referred to as MM0: and DM0:, respectively. 1.8.3 Copying the RSX-11M Distribution Tape on a VAX-11 RSX Host When you use TAPEKIT.CMD to copy the distribution kit on a VAX-11 RSX host, the command procedure asks several questions regarding the target volume and the location of the distribution kit. The answers to these questions inform the system of the type of kit you are using and determine the actions TAPEKIT.CMD will take. The device $$12: in the example in the preceding section is an RK07 disk drive, and the device $$16: is a TA78 tape drive, which supports 1600 and 6250 bpi tape densities. Because TAPEKIT.CMD cannot determine the device type from the $$n: form of device mnemonic, you must supply that information. The following example is an excerpt from the execution of TAPEKIT.CMD on a VAX-11 RSX host illustrates the correct responses to the questions asked. > @TAPEKIT >; ; RSX--11M V4.7 BL67 tape distribution kit extraction procedure >; Started on 22-Mar-93 at 13:58:46 >; >* Enter device and unit for disk(s) [ddn:] [S]:$$12: >* Enter device type [dd] [S]:DM >* Enter disk type, RK06 or RK07[D:RK07] >; >* Enter drive and unit with tape distribution kit [ddn:] [S]:$$16: 1-18 RSX-11M New Features, Restrictions, and Supplementary Information  >* Enter device type [dd] [S]:MU >; >; Copying rest of RSXM67 to $$12: . . . >; This example shows that only one disk volume was needed to copy the distribution kit from a 1600 BPI tape. 1.8.4 Selecting Printer Support During System Generation You can select support for a specific printer while performing a system generation. This support is a task- build option for the Queue Manager (QMG) and the Line Printer Processor (LPP). The printer you select becomes the default. To use a printer, you set the printer type when you initialize the print processor by specifying a form type in the command line. The valid form types are as follows: __________________________________________________________ Form_Type_____Printer_Type________________________________ 124. LN03 125. LA50 126. LA100 127.__________LN01________________________________________ If you have an LN03 printer connected to terminal line TT6, use the command shown in the following examples to initialize the print processor: > QUE TT6:/SP/FO:124./FL:1/LOWER $ INITIALIZE/PROCESSOR TT6:/FORMS:124./FLAG:1/LOWER To print a file, select your desired printer mode by including one of the following form types in the command line: RSX-11M New Features, Restrictions, and Supplementary Information 1-19  __________________________________________________________ Form_Type_____Printer_Mode________________________________ 3. 132-column, draft quality; also landscape mode for LN01/LN03 4. 80-column, letter quality; also portrait mode for LN01/LN03 5. 132-column, letter quality; also landscape mode for LN01/LN03 6. 80-column, draft quality; also portrait mode ______________for_LN01/LN03_______________________________ To print a 132-column draft quality TEST.LST file (that is, a normal listing file) and the 80-column letter quality TEST.TXT file on an LA50 printer, use the commands shown in the following examples: > PRI /FO:3.=TEST.LST > PRI /FO:4.=TEST.TXT $ PRINT/FORM:3 TEST.LST $ PRINT/FORM:4 TEST.TXT ________________________Note ________________________ Before using these commands, you must assign the default print queue, PRINT, to the processor handling the LA50 printer. _____________________________________________________ 1.8.4.1 Modifying Printer Support The printer options are controlled by task-build parameters in the build files for QMG and LPP. These build files are, respectively, [1,20]QMGBLD.BLD and [1,20]LPPBLD.BLD on the distribution kits. You can modify these files prior to building QMG and LPP during system generation. You can modify these files in the following ways: o Change the form types that are used to represent printer types. 1-20 RSX-11M New Features, Restrictions, and Supplementary Information  To do this, modify the GBLDEF options that define the symbols Q$LSPS and Q$HSPS. The comments in the build files explain the values of the symbols. The normal defaults are from 124 to 127(10). o Change the form types that are used to represent document types. To do this, modify the GBLDEF options that define the symbols Q$LSPF and Q$HSPF. The comments in the build files explain the value of the symbols. The normal defaults are from 3 to 6(10). If you modify the range of form types, you must change the GBLPAT options that define the forms to include offsets appropriate for the new form types. (See the comments in the command file regarding form definition.) o Remove the support for these printers altogether. This may be necessary if you do not have any of these printers and if you use form types in the range of 3 to 6(10) or from 124 to 127(10). To remove the support, set the values of Q$LSPS and Q$LSPF to 1 and the values of Q$HSPF and Q$HSPS to 0. You may also wish to remove the four GBLPAT definitions for the form types from 3 to 6(10). 1.8.5 System Generation Restrictions The following sections describe restrictions that apply to performing a Version 4.7 system generation. For system generation information about specific devices, see Section 1.8.6 and Section 1.8.7. 1.8.5.1 Minimum Requirements for System Generation and Installation To meet minimum requirements, the host computer for system generation must: o Have at least 128Kb of memory for distributions other than the TK50 o Have at least 248Kb of memory for using the BRUSYS system o Be mapped and have a null device (NL) RSX-11M New Features, Restrictions, and Supplementary Information 1-21  1.8.5.2 SYSGEN Invokes VMR when Using a VAX-11 RSX Host VMR is invoked automatically by SYSGEN when using a VAX-11 RSX host to perform an RSX-11M system generation. 1.8.5.3 Copying the Distribution Tape to Disk You must mount the target disk with the /FOREIGN switch before using BRU to copy the distribution tape to the target disk with an RSX-11M-PLUS or VAX-11/RSX host. 1.8.5.4 Saved Answer Files A Version 4.6 saved answer file (SYSSAVED.CMD) can be used when generating an RSX-11M Version 4.7 operating system. These files are upwardly compatible. ________________________Note ________________________ If you are using Version 4.4 saved answer files and you want to use the IP11 layered product, you will need to modify the previous IP11 symbols to conform with the new symbols. _____________________________________________________ 1.8.5.5 GBLDEF Enhancement When you choose user-written driver support, SYSGEN includes, by default, the statement GBLDEF=$USRTB:0 in the task-build command file for the Executive. 1.8.6 System Generation Device Restrictions and Supplementary Information The following subsections contain information about restrictions applying to certain devices when performing system generation. 1.8.6.1 LPA-11K Device Restrictions for System Generation The following restrictions apply to the LPA-11K, an LA- type device: o SYSGEN does not support fully the use of saved answers for the LPA-11K; therefore, questions will be asked during SYSGEN that must be answered in order for the SYSGEN to continue. 1-22 RSX-11M New Features, Restrictions, and Supplementary Information  o When you use a VAX-11 host to generate systems that contain both Industrial Control System and Industrial Control Remote (ICS/ICR) support and LPA-11K devices, the task build of the ICS/ICR common fails because the symbol TKL, which is used to access the Task Builder, was deassigned when the LPA-11K device support was processed. To solve this problem, pause SYSGEN at the next end- of-section breakpoint and then task build the common manually. Alternatively, you can mount the distribution disk as shareable and then task build ICOM manually from another terminal. 1.8.6.2 MSCP Device Restrictions for System Generation The following restrictions apply to Mass Storage Control Protocol (MSCP) devices for RSX-11M Version 4.6 and later: o The partition PUCOM for the MSCP-type device driver common may be created in the SYSVMR.CMD file with an incorrect size. This occurs because the task image size that is required for the partition varies according to device configuration and the system options. To solve this problem, you must obtain the map for the PUCOM partition and examine the task image size to determine the partition size that is needed. You must then edit the SYSVMR.CMD file to use the correct size for the PUCOM partition. Then run VMR on the system image. It is suggested that you pause SYSGEN before running VMR to examine the SYSVMR.CMD file and the PUCOM.MAP file for differences in the task image size. o There is a restriction in the configurations for MSCP- type disk devices supported by SYSGEN. SYSGEN creates the device database by using the physical unit number 0 for the first unit on the first controller that is specified; then SYSGEN increments the physical unit number sequentially for all subsequent units and controllers. Because of this, the physical unit numbers are assigned sequentially in the order that the controllers are specified, starting with zero. Controllers must be specified in the order of the physical unit numbers attached, beginning with the RSX-11M New Features, Restrictions, and Supplementary Information 1-23  controller used by physical unit number 0. The physical unit number is often determined and displayed by a plug or thumbwheel switch attached to the device unit. 1.8.6.3 Indirect Command Processor Restrictions Some configurations of RSX-11M may require the use of the ICX variant of the Indirect Command Processor. If your configuration requires ICX and you do not use ICX when you generate your system, you will receive a symbol table overflow error. Note that baseline systems for Version 4.7 use the ICX variant as the default. For online system generations, remove AT. and then install INS $ICX. Note that ICX is a privileged task with executive mapping. It must be linked with the executive being used for the online SYSGEN. For this reason, ICX is built as part of all V4.7 SYSGENs. In order to use ICX with other, previous versions of RSX, it must first be manually rebuilt. 1.8.7 Supplementary Information on Device Support See the appropriate RSX-11M Software Product Description (SPD) for a list of supported devices on RSX-11M. 1.8.7.1 Device Support for RA70 and RA90 Disk Drives and for SA550 and SA650 Arrays The RA70 and RA90 disk drives in the SA650 disk array have been supported since Version 4.6. Both the SA550 disk arrays and the SA650 disk arrays are supported. The SA550 disk array contains RA70 and RA82 disk drives. The SA650 disk array contains RA70 and RA90 disk drives. Error logging support has been added for RA70 and RA90 disk drives (in SA550 and SA650 arrays only). 1.8.7.2 VT300-series Terminal Functions in VT200 Mode In RSX-11M Version 4.6 and later, the VT300-series terminal is supported in VT200 mode only. Note that you cannot specify VT300 as a terminal type with the MCR SET /VTxxx=TI: command or the DCL SET TERMINAL/VTxxx command. 1-24 RSX-11M New Features, Restrictions, and Supplementary Information  To set VT200 mode for your terminal, press the Set-Up key. Then press the Enter key until the display indicates VT300 mode. Use the right arrow key to light up the panel indicating VT300 mode. Then press the Enter key again until the panel indicates VT200 mode. Next, use the right arrow key to light up the panel indicating SAVE and press the Enter key. This will preserve the setting when you log out. To exit from the Set-Up Directory, press the Set-Up, or F3 key. 1.8.7.3 CXF32/DHF11 Module Support The CXF32/DHF11 32-line serial line unit is a quad- height asynchronous terminal interface using fiber- optic technology to link the computer to the terminal concentrator boxes. The CXF32/DHF11 device appears to the system as two separate 16-line devices, each emulating a CXA16 multiplexer. The device has two switch packs that enable you to select the starting control and status register (CSR) and interrupt vector addresses. The second set of CSR and vector addresses is automatically set by the device logic. For example, if the CSR address is set to 160500 for the first 16 lines, the CSR address for the second 16 lines is set automatically to 160520. The same principle applies to the vector addresses: if the first 16 lines have the interrupt vector set to 300, then the second 16 lines will have an interrupt vector address of 310. 1.8.7.4 CXA16, CXB16, and CXY08 Multiplexer Support The operating system includes support for CXA16, CXB16, and CXY08 multiplexers. However, although the CXY08 supports remote (dial-up) terminal lines, the system generation procedure (SYSGEN) does not assign these terminal lines automatically. If you require support for remote lines, use SYSGEN to include the CXY08 controller in your target configuration. Then use the Monitor Console Routine (MCR) or Virtual RSX-11M New Features, Restrictions, and Supplementary Information 1-25  Monitor Console Routine (VMR) command SET/REMOTE to assign the remote lines. 1.8.7.5 Terminal Driver Support RSX-11M supports additional terminal characteristics if you select support for the full-duplex terminal driver in the Terminal Driver Options section of Phase I of SYSGEN. The additional terminal characteristics include parity generation and checking, advanced video and editing options, ANSI-standard and Digital-specific escape sequences, ReGIS graphics, and block-mode transmission. 1.8.7.6 Asynchronous Terminal Interfaces Support RSX-11M supports the YV device for the DHV11 and DHU11 multiplexers. The DHV11 is a Q-bus multiplexer that handles 8 lines at speeds up to 19.2K baud with full modem control. The DHU11 is the UNIBUS equivalent of the DHV11. It handles up to 16 lines with full modem control. You must select the full-duplex terminal driver during system generation if you want support for the DHV11 or DHU11. RSX-11M also supports the YZ device for the DZQ11 Q-bus multiplexer. 1.8.7.7 J11-Series Processor Support RSX-11M supports the J11-series processors, the PDP-11/84, the MicroPDP-11/23, the MicroPDP-11/53, the MicroPDP-11 /73, and the MicroPDP-11/83. The LSI-11/73 processor is supported under the hardware restrictions indicated in Section 1.8.8.8. 1.8.7.8 Large Disk Support Large disk support has been included for the following RSX-11M tasks and utilities: o Backup and Restore Utility (BRU) o Files-11 Ancillary Control Processor (F11ACP) o File Structure Verification utility (VFY) o INITVOLUME (INI) o Peripheral Interchange Program (PIP) 1-26 RSX-11M New Features, Restrictions, and Supplementary Information  This support allows Files-11 initialization and access to disks that contain more than 1,044,480 logical blocks but fewer than 16,777,217 logical blocks. 1.8.7.9 BRU64K Device Support The support for MU-type devices was added to BRU64K in RSX-11M Version 4.4. 1.8.7.10 Network Command Terminal Support Network Command Terminal (NCT) must be selected during system generation if you want to execute the MCR command SET/HOST (DCL command SET HOST) to gain access to another RSX host system. NCT defines logical layers and peer protocols that provide physical and logical terminals in a distributed environment. These services are layered on top of the DECnet package to present a fully transparent remote command terminal facility across heterogeneous Digital operating systems. NCT implementation is limited to providing support for an RSX system to serve as either a host or server system to an RSX or a VMS system. Many of the NCT features, such as turning on/off terminal features, are also available to RSX systems without the DECnet package software. NCT requires that input flow control be present. 1.8.7.11 Digital Storage Architecture Support Digital Storage Architecture (DSA) is necessary to support the MU-type magnetic tape devices such as the TK50 tape cartridge. DSA replaces the previous support for DU-type disk devices such as the RD52 disk device. DSA breaks the host level into two independent layers: the class layer and the port layer. The class layer handles a class of devices, such as tapes or disks. The port layer is responsible for the actual transmission of packets between the host and controller. RSX-11M New Features, Restrictions, and Supplementary Information 1-27  1.8.7.12 Devices and Products No Longer Supported The operating system does not contain the IP11 driver software. This software has been unbundled from the operating system and is available only as a separate layered product. Unbundling the IP11 driver software allows Digital to provide IP11 customers with new releases of the driver software in a more timely manner. With the introduction of this new IP11 driver layered product, Digital will be providing services for this product separately from the RSX operating systems. Software Product Services contract customers are entitled to the following services: o Software licenses and distribution kits for the IP11 driver at a nominal charge o Support for the IP11 driver, at no extra charge, for the current term of their RSX contract For more information, please contact your Software Product Services representative. Other products no longer supported since Versions 4.5 and later of RSX-11M operating systems include the following: o The TC11-TU56 dual-drive DECtape cartridge tape subsystem o The DJ11 terminal interface o The User Environment Test Package (UETP) 1.8.8 Hardware Restrictions The following are restrictions to hardware supported by the RSX-11M Version 4.6 and later operating system. 1.8.8.1 RX50/RX33 Diskette Restriction The RX50 and RX33 diskettes do not have a Bad Block Replacement Control Task (RCT) area. This means that bad blocks on these devices are not replaced and blocks that become bad during the use of the disk are not written to the bad block file [0,0]BADBLK.SYS. 1-28 RSX-11M New Features, Restrictions, and Supplementary Information  1.8.8.2 Transportability Among 22-Bit Systems The RSX-11M operating system supports transportability among all 22-bit systems. These systems may differ: the Executive may handle nonprocessor request (NPR) transfers by performing memory management functions, or the hardware may have its own capabilities for 22-bit physical memory addressing. To make these systems transportable, you must boot your target system on the processor selected during system generation, and then save it. The saved system will then be hardware bootable and transportable among the different 22-bit systems. 1.8.8.3 Bootstrapping a DB-, DM-, or DR-Based System The MCR command BOOT can loop indefinitely when it boots a system from an RP04, RP05, RP06, RK07, RM03, RM05, or RM80 device. This problem occurs if the bootstrap driver encounters an error correction code (ECC) correctable error when reading the system image. The bootstrap driver is not large enough to include ECC logic. Therefore, it retries the read operation but it never succeeds. To recover from this error, use the Peripheral Interchange Program (PIP) to copy the system image to another area on the disk and retry the boot operation. Alternatively, you can copy the entire image to another disk and boot from that one. 1.8.8.4 LK201 Keyboard Restriction Some non-English LK201 keyboards do not have a backslash (\) character. To generate the CTERM enter-control-mode sequence on an LK201 keyboard, press Ctrl/4, and then press the Return key. The LK201 keyboard generates the American Standard Code for Information Interchange (ASCII) control characters 033 to 037(8) with Ctrl/3 to Ctrl/7. 1.8.8.5 DLVJ1 Four-Line Terminal Interface Restriction Due to hardware restrictions, errors may result when the DLVJ1 four-line terminal interface is configured with an RQDX1 controller or additional DLVJ1 modules. RSX-11M New Features, Restrictions, and Supplementary Information 1-29  1.8.8.6 RQDX1 Controller Restriction Only one RQDX1 controller is supported per system. 1.8.8.7 TK50/TZ30 Restriction If the TK50 or TZ30 magnetic tape cartridge is used with utilities other than the Backup and Restore Utility (BRU), degraded performance may result. 1.8.8.8 LSI-11/73 Processor Restriction The LSI-11/73 processor is supported only when used in the following two configurations: 1. (Not supported with the RQDX1 controller) o KDJ11-A processor module o MRV11-D memory module with a MXV11-B2 boot read-only memory (ROM) set o DLVJ1 4-line terminal interface 2. (Supports only one DL11-type interface when using half- duplex terminal driver) o KDJ11-A processor module o MXV11-BF multifunction module with MXV11-B2 multifunction module with MXV11-B2 boot ROM set 1.8.9 Micro/RSX File Transfer Utility Supplementary Information The Micro/RSX File Transfer utility (MFT) supersedes the Professional File Transfer (PFT) program. The utility is available with both the forms interface and the PFT Command Line Format (CFT). To execute the forms interface, use the MFT /FORM command or install MFT as an MCR spawnable task with the task name . . . PFT. To use MFT with CFT, substitute the command MFT for the command PFT on all command lines shown in the PRO/Communications User's Guide. For example, when you transfer a file from a Professional to a host, the CFT command is as follows: >CFT filespec/PRO=filespec 1-30 RSX-11M New Features, Restrictions, and Supplementary Information  The file before the equal sign is the output file specification; the file after the equal sign is the input file specification. The PRO qualifier (/PRO) identifies whether the Professional is sending or receiving the file. To transfer a file from a Professional to a host that is using MFT, substitute MFT in the command line, as follows: >MFT filespec/PRO=filespec For a complete description of the PFT and CFT command lines, see the PRO/Communications User's Guide. 1.9 Executive Supplementary Information The following sections contain supplementary information on the Executive. 1.9.1 Executive Code Changes The following changes have been made to the Executive: o Many Executive routines have been moved into the Executive commons (if you selected Executive common support). Therefore, it may not be possible for privileged code to reference these routines as they may have done in previous RSX releases. To determine if an Executive entry point is in an Executive common, consult RSX11M.MAP. The entry point is in a common if its address falls between 1200008 and 1400008. If the entry points are inaccessible to a task because they reside in the Executive commons, you can make them accessible by writing a transfer routine that will permanently reside in the mapped Executive address space. See module DRSUB for examples of transfer routines. Note that transfer routines are already provided for the most commonly called subroutines that have been moved into the commons. Their existence is transparent to any task referencing them. o The RSXMC.MAC symbol P$$D70, which indicated cache memory on a 22-bit processor, has been changed to C$$CHE. RSX-11M New Features, Restrictions, and Supplementary Information 1-31  1.9.2 Executive Data Structure Changes The following changes have been made to the Executive data structure: o To enhance asynchronous buffered I/O, bit T2.TIO, which allowed for only one buffered I/O per task, has been changed to the byte T.TIO. This byte enables a task to queue many buffered I/O requests simultaneously. o The word at offset O.STAT+2 of the Offspring Control Block (OCB) is used to contain a secondary exit status, the Task Termination Notification program (TKTN) abort code, which is filled in whenever the offspring task exits. Previously, only the word at O.STAT was used. Note that more words in the exit status region of the OCB may be used in the future and, therefore, should be considered as reserved for future expansion. o The addition of alternate command line interpreter (CLI) support has changed the way that CLIs are associated with individual users. On systems that include alternate CLI support, the word previously at offset U.CLI in the terminal Unit Control Block (UCB), (DV.TTY is set) has been redefined. On these systems, it is referred to as U.MUP since it currently contains a bit mask for various multiuser features. Bits 1 to 4 in this word are used to identify the CLI associated with that terminal. The bits form an offset into a table located at $CPTBL in the Executive module SYSCM. This module contains a pointer to the CLI Parser Block for the CLI (CPB). Since only 4 bits are used to form this offset, the system is limited to 16 CLIs. The bit used for the NOBROADCAST feature is also in this word, which is why this feature is available only on systems supporting alternate CLIs. 1-32 RSX-11M New Features, Restrictions, and Supplementary Information  1.9.3 I/O Data Structure Changes The following changes have been made to the I/O data structure: o The bit DV.MXD in offset U.CW1 of the UCB has been changed to DV.MSD. This bit is set for all mass- storage devices and must be turned on for all user- written drivers that want to support error logging. In addition, error logging devices must have four words preceding each UCB (negative offsets). o The bit DV.SWL in offset U.CW1 of the UCB (previously unused) is now used to maintain the software write-lock status of the device. o Prior to Version 4.0, two words were added to the end of each DH11 UCB to contain the vector and control and status register (CSR) of an associated DM11BB. In Version 4.0, these two words were eliminated. The information is contained in fork block offsets in the Status Control Block (SCB). 1.10 Supplementary Information on the MAKESTK.CMD Command File The command file MAKESTK.CMD uses the Task/File Patch Program (ZAP) to create a version of the Slow Task Builder (STK) in LB:[1,54] from the existing Task Builder file (TKB.TSK). When executed, the procedure checks the LB:[1,54]TKB.TSK image file to see if it was built against the File Control Services Resident Library Routines (FCSRES). Previously, the MAKESTK.CMD procedure required the parameter RES to indicate that the Task Builder (TKB) that was being used to make STK had been built against FCSRES. The new MAKESTK.CMD procedure automatically determines if FCSRES was used to build TKB and uses one set of values if FCSRES was used and another if FCSRES was not used. MAKESTK.CMD returns an informational message if it discovers that the version of TKB from which you are making STK has been built against FCSRES. If the version of TKB from which you are making STK has not been built against FCSRES, it returns the following message: RSX-11M New Features, Restrictions, and Supplementary Information 1-33  ZAP -- Verify failure This message is the result of MAKESTK.CMD using ZAP to test TKB and does not indicate a failure. MAKESTK.CMD also verifies that ZAP is installed and, if not, exits with an error message. 1.10.1 FCSRES and FCSFSL FCSFSL is not supported on RSX-11M. The following informa- tion applies to RSX-11M only if you are transporting tasks between RSX-11M and RSX-11M-PLUS systems. FCSRES and FCSFSL are merged into a single vectored-entry memory image that can be used in either of the user- mode libraries. This reduces both disk and memory space requirements. The [1,1]FCSRES.TSK image file installs under the library name FCSRES and is used to satisfy your library requests. Existing tasks that reference FCSRES are unaffected by this change and need not be rebuilt except to use new features. To use the new library, you must rebuild existing tasks that reference FCSFSL, whether they reference FCSFSL directly or reference a library (such as F77RES) that has been built to reference FCSFSL. The FCS resident library image ([1,1]FCSRES.TSK) has been built containing the supervisor-mode library completion routine. However, because the user-mode FCSRES library is a memory-resident overlaid library, it must be distinguished from the supervisor-mode library (because the completion routine cannot be overlaid). Thus, the files for FCSFSL must be used to build tasks using supervisor mode (the TSK file is needed for information contained in the label block; the STB file is needed for symbol values and overlay structure). To supply the two different descriptions but use the same library image, TKB has been changed to force references to FCSFSL to become references to FCSRES in the resulting executable task image. In other words, the build command for RSX-11M remains the same as it has been (LIBR=FCSRES), and the files remain in directory [1,1]. The FCSFSL.TSK file size is considerably reduced. 1-34 RSX-11M New Features, Restrictions, and Supplementary Information  ________________________Note ________________________ Like TKB, FTB also changes references to FCSFSL to FCSRES in the resulting executable task image. _____________________________________________________ 1.11 System Library Routines Supplementary Information A feature has been added to the directory parsing code in FCSRES.FCS. (FCSRES is the memory-resident version of the File Control Services (FCS) I/O routines.) This enhancement makes it possible to maintain the transportability of FCSRES-linked tasks between RSX-11M and RSX-11M-PLUS. You can obtain the directory string used in the parse. An extension has been created for the File Descriptor Block (FDB), which has the following format: .Byte Extension length .Byte Reserved .Byte Length of buffer for directory string .Byte Length of directory string (filled in by .PRSDI) .Word Address of directory string buffer The extension block and directory string buffer are allocated in your address space. First, you enter the address, the length of the buffer, and the length of the extension into the proper words in the extension block. Then you insert the address of the extension block at the offset F.EXT in the FDB. When the directory parsing code detects that F.EXT has a value, it uses the value as an address and moves the directory string into the buffer. It also puts the length of the actual directory string into the byte in the extension. This directory will always be filled except when the directory is obtained from the default name block. This occurs because the default name block does not contain the directory string. In this case, the directory length will be set to zero. 1.12 Device Drivers The following sections include information on enhancements to device drivers, a restriction, and supplementary information. RSX-11M New Features, Restrictions, and Supplementary Information 1-35  1.12.1 DU Driver Enhancement The DU device driver has been enhanced to return more information in the IO.RSN (Read Serial Number) function. The added information is useful to the Bad Block Replacement Control Task (RCT). In addition to the volume serial number, the information returned now includes the controller identification number, the hardware and software version numbers of the controller, the unit identifier (device identification number), and the hardware and software version numbers of the device. RCT sends this information to the Error Logger. For more information on RCT, see the RSX-11M/M-PLUS System Management Guide. A new subfunction, IO.SEL (Suppress Error Logging), allows you to prevent error messages from being sent to the Error Logger. 1.12.2 Device Driver Restriction The IO.EIO function will not work if your terminal has been set as a remote terminal (RT) to another system. After you enter the SET HOST xxxxx command and log in to an RT, the RT driver will reject a QIO that issues an extended I/O request from the RT. 1.12.3 TK50 Tape Subsystem Supplementary Information RSX-11M supports the TK50 tape drive. The TK50 is an integrated subsystem that consists of a controller (for the Q-bus and UNIBUS) and a TK50 tape drive. The controller handles all error recovery and correction and internally buffers multiple outstanding commands. The TK50 driver (MUDRV) reads and writes data on a 1/2-inch tape cartridge that is recorded at 6667 bpi on serial data tracks in a serial serpentine recording (modified frequency modulation) method. The tape speed is 75 inches per second. If I/O commands are not issued to the tape unit quickly enough, the tape unit enters start/stop mode. While in start/stop mode, each I/O command issued incurs a time penalty (about 1 second for the TK50). 1-36 RSX-11M New Features, Restrictions, and Supplementary Information  Because the tape unit expects the next I/O command to be ready for processing when the current command finishes, it keeps the tape moving in the forward direction. However, if the next I/O command is not ready, the tape unit moves past the position on the tape where the I/O operation was to be performed. As a result, the tape has to be repositioned; that is, rewound to the correct position on the tape. It is this reposition operation that takes approximately 1 second to complete before the next I/O command can be processed. This reposition time can severely impact the performance of tape utilities if they are unable to issue commands to the controller quickly enough. To alleviate the performance impact of the reposition time, a padding feature is available in the TK50 firmware. This allows the controller to issue up to a preset number of padding blocks during output to the tape. Before each pad block is written, the controller checks to see if the next I/O command is ready for processing. If it is, no more pad blocks are written and the host's I/O request is processed. If the next host command is not ready, the controller writes out another pad block until either an I/O command is ready for processing or the number of consecutive pad blocks written reaches a maximum specified by the controller. In the latter case, the tape unit enters start /stop mode. When the next write command is issued, the controller repositions back over the pad blocks that it wrote before actually doing the write operation. Because of this, tape capacity is not lost if the application cannot keep the unit in streaming mode. If the application does keep the unit partially in streaming mode, then some tape capacity will be lost due to the pad blocks. On input from the TK50, the controller does not return any of these pad blocks to the application program. Because of this, padding is transparent to the user's application. The following section describes performance and capacity impact when you use RSX utilities with the TK50. The performance indicated is to be used only as a guideline. The timings given will vary according to system load, the RSX-11M New Features, Restrictions, and Supplementary Information 1-37  type of disk used in disk/tape applications, and errors encountered on the tape. 1.12.3.1 TK50 Performance when Using RSX Utilities This section describes anticipated timings for various RSX utilities. These are guidelines only; the actual times will vary according to system load, disk usage, and tape error correction codes (ECC) errors encountered. ________________________Note ________________________ The time values specified in this section are estimated values only. On your operating system, the amount of time that a utility needs to complete an operation may differ from these values. _____________________________________________________ The information in Table 1-3 pertains to the use of the TK50 and RSX-11M utilities: Table_1-3_TK50_Performance_and_RSX_Utilities______________ RSX_Utility___TK50_Performance____________________________ (continued on next page) 1-38 RSX-11M New Features, Restrictions, and Supplementary Information  Table_1-3_(Cont.)_TK50_Performance_and_RSX_Utilities______ RSX_Utility___TK50_Performance____________________________ MOU The time required to mount a TK50 tape, either foreign or as an ANSI tape, is dependent upon the position of the tape when the MOUNT command is issued. If the tape is at or near the beginning of a track, the expected time for the mount operation is approximately 20 seconds. During this time the controller performs calibration functions on the tape. If the tape is near the end of a track, the time required to mount the tape can increase to as much as 2 minutes. This time is required for the actual rewind of the tape (approximately 1.6 minutes) followed by the calibration functions by the controller. When you insert a cartridge, the tape will be positioned at the beginning. Only rarely (for example, if the system crashes during a tape operation) is the tape left positioned near the end of a track. DMO When you dismount a tape, a REWIND command is generally issued to the tape unit as part of the dismount function. Depending on where the tape is positioned, this may take between 1 second (the tape is at the beginning of a track) and 1.6 minutes (the tape is at the end of a track). (continued on next page) RSX-11M New Features, Restrictions, and Supplementary Information 1-39  Table_1-3_(Cont.)_TK50_Performance_and_RSX_Utilities______ RSX_Utility___TK50_Performance____________________________ BRU This utility will generally keep the TK50 in streaming mode during backup and restore operations. The exceptions to this are as follows: o During the initial set-up phase (that is, when writing out the directory information to the tape), BRU will not be able to issue I/O commands to the TK50 quickly enough. As a result, the TK50 will run in start/stop mode during this phase of BRU's operation. The time required for this operation is dependent on the number of directories contained on the input disk. This process can take from 1 to 10 minutes, based on the number of directories written. o BRU generally does not stream if there is a load on the system at the time BRU is run. This load will slow down BRU sufficiently so that it will not be able to issue commands to the TK50 drive quickly enough to keep it streaming. o Any use of the disk from which BRU is backing up or restoring to generally causes BRU to run the TK50 in the start /stop mode. The extra disk head movements add to BRU's processing time sufficiently so that it is not able to issue I/Os to the TK50 controller quickly enough to keep it in streaming mode. o BRU does not stream consistently during its verification pass. Modifications have been made to both BRU and the MU device driver to improve performance in verify and compare operations. o BRU does not stream while it is sorting retrieval pointers. The number of such sort operations is dependent on the degree of disk fragmentation that exists 1-40 RSX-11M New Features,tRestrictions,.and Supplementary Information (continued on next page)  Table_1-3_(Cont.)_TK50_Performance_and_RSX_Utilities______ RSX_Utility___TK50_Performance____________________________ (continued on next page) RSX-11M New Features, Restrictions, and Supplementary Information 1-41  Table_1-3_(Cont.)_TK50_Performance_and_RSX_Utilities______ RSX_Utility___TK50_Performance____________________________ Once BRU begins copying data blocks out to the TK50, it will keep the TK50 unit in streaming mode provided that none of the five conditions listed previously occur. In a test case using a slow disk and running 40Mb of data, the save operation required 13 minutes, with the directory writes consuming 3 minutes of this time. Estimating from the amount of tape used in this operation, and assuming that there is sufficient information on the disk to back up, BRU would have utilized approximately 83 percent of the total capacity (94Mb) of the tape. Such a capacity rating would allow the backing up of a 75Mb disk (0.83 x 94Mb = 78Mb). In this test case, no verify operation was performed. However, the verify operation is estimated to take approximately 1 hour for this example. BRUSYS These utilities exhibit the same capacity /BRU64K and performance characteristics as online BRU. FLX This utility will not keep the TK50 streaming. FLX's internal design does not permit the issuing of I/O commands to the TK50 at the rate required to keep the tape streaming. Because it does not stream, the padding blocks added by the controller will be overwritten during the reposition operation. Tape capacity will not be diminished. A test case using 180 blocks contained in nine files was run, and FLX copied the files in 1.8 minutes. (continued on next page) 1-42 RSX-11M New Features, Restrictions, and Supplementary Information  Table_1-3_(Cont.)_TK50_Performance_and_RSX_Utilities______ RSX_Utility___TK50_Performance____________________________ PIP This utility will not keep the TK50 streaming. Its internal design does not permit the issuing of I/O commands to the TK50 at the rate required to keep the tape streaming. Because it does not stream, the padding blocks added by the controller will be overwritten during the reposition operation. Tape capacity will not be diminished. A test case was run using 180 blocks contained in nine files. PIP, using the TK50 as an ANSI tape, copied the information in 10.5 minutes. This time differs significantly from the FLX test case due to the overhead involved in ANSI tape processing. The default block size on ANSI tape was used for the test case. An optimization can be performed to increase throughput to an ANSI tape on the TK50 drive. This optimization does not result in streaming; it does result in fewer I/Os to the tape unit and therefore fewer repositionings. The size of the block written to ANSI tape can be increased by using the /BS switch in PIP. A value up to 8192(10) bytes can be specified (the default is 512(10) bytes). PIP should be installed with an increment if this value is used. If it is not, PIP may issue "Not enough buffer space" error messages during certain copy ______________operations_to_the_tape._____________________ 1.12.3.2 TK50 Indicators Because the actual TK50 tape recording surface is hidden from view, it is often difficult to determine what the tape unit is actually doing. Two lights on the front of the TK50 tape unit provide some information as to what is happening. RSX-11M New Features, Restrictions, and Supplementary Information 1-43  o The green indicator serves a dual role. When the light is on consistently, it indicates that the tape cartridge can be safely removed from the unit. If this indicator is blinking or if it is off, you cannot safely remove the cartridge. A blinking pattern indicates that the tape is in motion, either in a forward or reverse direction. o The red indicator serves a multiple role. If the indicator is on consistently, a tape cartridge is loaded into the drive. Should the indicator blink slowly (for example, on for 1 second and then off for 1 second), this indicates that the tape is in use and is currently rewinding. If the indicator blinks more rapidly, it indicates a drive error has occurred. This latter condition can be cleared by pressing the LOAD /UNLOAD switch twice. Note that this will cause a loss of tape position. 1.12.4 Supplementary Information on User-Written Device Drivers The following sections contain supplementary information on user-written device drivers. 1.12.4.1 Asynchronous Buffered I/O Data for input and output requests are usually trans- ferred directly to and from task memory. To allow for the successful transfer of data, the task cannot be checkpointed until the transfer is completed. For most high-speed devices, the transfer occurs quickly so that a task does not occupy memory for too long. For slow- speed devices, however, some mechanism must be available to avoid binding memory to a task while the task is performing I/O operations. By using the $TSTBF, $INIBF, and $QUEBF routines in the Executive module IOSUB, a driver can execute an I/O request for a slow-speed device and allow the task to be checkpointed while the request is in progress. To perform the I/O request, the driver buffers the data in memory allocated to the driver while the task is checkpointed and the I/O request is in progress. 1-44 RSX-11M New Features, Restrictions, and Supplementary Information  To test whether a task is in a proper state to initiate I/O buffering, the driver calls the $TSTBF routine and passes it the address of the I/O packet. By extracting the address of the task control block (TCB) from the I/O packet, $TSTBF can examine various task attributes. For example, if the task is checkpointable, buffered I/O can be performed. $TSTBF returns to the driver and indicates whether buffered I/O can be performed. If buffered I/O can be performed, the driver performs two operations. First, it establishes the buffering conditions. For an output request, it copies the task buffers to dynamically allocated pool space. For an input request, it allocates sufficient pool space to receive incoming data. Second, the driver calls the $INIBF routine to initiate the I/O buffering. The $INIBF routine decrements the task I/O count, increments the task's buffered I/O count in T.TIO, and then releases the task for checkpointing and shuffling. If the task is currently blocked, the task state is transformed into a stop state until the task is unblocked, buffered I/O is completed, or both. Checkpointing the task is subject to the normal requirements of an active or stopped state as described in the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual. After the driver transfers the data, it calls the $QUEBF routine to queue the buffered I/O for completion. $QUEBF sets up a KERNEL asynchronous system trap (KERNEL AST) for the buffered I/O request and, if necessary, unstops the task. When the task is active again, a routine in the Executive module SYSXT detects the outstanding AST and processes it. If the request is for input, the routine copies the buffered data to task memory. This mechanism occurs transparently to the task. The routine then calls the driver to deallocate the buffer from pool. The $IOFIN routine completes the processing. These routines are not always present in RSX-11M. If you selected the full-duplex terminal driver or networking support during system generation, they are included. To include them in systems without these options, add the RSX-11M New Features, Restrictions, and Supplementary Information 1-45  symbol A$$BIO=0 to RSXMC.MAC during Phase I of system generation. 1.12.4.2 Overlapped I/O Completion In general, overlapped I/O completion support causes the execution of the Executive's I/O completion code for each I/O request to be postponed until the next request has been initiated. If I/O requests are in the driver's queue, this action causes the Executive to complete the I/O processing while the physical device services the next request. A minor side effect of this feature is that multiple I/O requests to the same device may complete in an order other than the issued order. When a driver requests the Executive to complete the I/O, the Executive checks the queue for requests to the driver. If the queue is not empty, the Executive defers I/O completion by placing the current completion at the end of the fork list. Control returns to the driver, which assumes that the Executive has completed I/O processing. The driver can then initiate the next I/O operation. After the driver has initiated an I/O operation on the device, the driver returns to the Executive and fork processing begins. Thus, the I/O completion for the previous I/O can be processed to the end. When a hardware I/O operation completes, the driver receives an interrupt and then forks, which always causes the I/O completion to occur after the previously queued completion. The exception to sequential completion occurs when an I/O operation does not require a hardware operation. In this case, the driver processes the I/O and then calls the Executive's I/O completion routine. If there is an additional I/O waiting in the queue, this completion also goes at the end of the fork list, and sequential processing is maintained. Nonsequential completion occurs when the very last request in the queue is a non-hardware- oriented I/O request. In this case, the non-hardware- oriented I/O completes before any others waiting for completion. There are many types of non-hardware-oriented I/O operations, such as inquiries into device state, or attach and detach requests. 1-46 RSX-11M New Features, Restrictions, and Supplementary Information  This feature speeds up I/O operation in the case of actual hardware operations because the new hardware I/O is initiated and the transfer may occur parallel to the final completion of the previous operation. The I/O processing speeds up by the amount of time necessary to process the remaining instructions in the Executive I/O finish routine. There is one case where overlapped I/O completion does not occur. It does not occur when the last I/O request queued to the controller does not require a device interrupt to complete. 1.13 I/O Operations The following sections contain information, restrictions, and supplementary information on I/O operations. 1.13.1 Crash Driver Modification for 4Mb-Memory Systems The MU routine in the crash driver has been modified to control the size of the memory dump in systems with 4Mb of memory. The crash driver now monitors the amount of memory dumped and terminates the dump when it reaches 2044K words of memory. 1.13.2 I/O Operations Restrictions The following sections describe I/O operations restric- tions. 1.13.2.1 Multibuffer Processing in Random Mode Multibuffering can improve performance for I/O-bound tasks under certain circumstances. However, multibuffer processing in random mode is not very efficient. When using multibuffering in random mode, a user task record buffer is always required. If one is not supplied, the task's low memory may be overwritten and the task may abort. RSX-11M New Features, Restrictions, and Supplementary Information 1-47  1.13.2.2 Big Buffering in Random Mode When you use big buffering in random mode, a user task record buffer is always required. If one is not supplied, the task's low memory may be overwritten and the task may abort. Using big buffering with random GET$ and PUT$ operations can cause loss of data from the end of a file. In this case, a directory of the file indicates that it has more blocks in use than it has allocated. To prevent data from being lost, perform the following steps: 1. Allocate enough space to make writing an extension unnecessary. 2. Issue a .FLUSH directive after the highest numbered record is written by a PUT$ operation. 3. After a PUT$ operation, do not issue any GET$ operation that could cause the file to extend. 1.13.2.3 Block Size on Tapes Mounted with the /NOLABEL Qualifier Under certain conditions, if a file is written to a tape, its block size will be even and one more than the value specified in the MOUNT command. This occurs in the following circumstances: o The tape is mounted with the /NOLABEL qualifier. o The MOUNT command specifies an odd record size. o The MOUNT command specifies an odd block size. File Control Services (FCS) adds the padding character, an octal 136 circumflex (^), to odd-sized byte blocks due to a hardware restriction. Some tape drives will not allow an odd number of bytes to be transferred to or from tape. Therefore, blocks of data are padded with the circumflex character so that even blocks of data can be written to tape on any tape drive. 1.13.3 I/O Operations Supplementary Information The following sections contain supplementary information on I/O operations. 1-48 RSX-11M New Features, Restrictions, and Supplementary Information  1.13.3.1 Support for Using FCS to Queue Files for Printing File Control Services (FCS) provides facilities at both the macro and subroutine level to queue files for subsequent printing. Therefore, your task can queue a print job. There are several ways for your task to spool output for printing. You cannot control the printing from your task as you can with the PRINT command. However, you can alter the attributes of the print job once the job appears in the queue by using the DCL command SET QUEUE. A task issues the PRINT$ macro call to queue a file for printing on a specified device. The specified device must be a unit record, carriage-controlled device such as a line printer or terminal. The file is placed in the default queue PRINT. If the device is not specified, LP is used. The file to be spooled must be open when the PRINT$ macro is issued. PRINT$ closes the file. The PRINT$ macro call format is shown next. PRINT$ fdb,err,,dev,unit,pri,forms,copies,presrv The parameter fdb is the address of the associated File Descriptor Block (FDB). This parameter need not be present if the address of the associated FDB is already in R0. 1.13.3.2 File Attribute Codes The Magnetic Tape Ancillary Control Processor (MTAACP) supports new file attribute codes for the dates of creation, revision, expiration, and backup of the file. These new codes read and write the date in the file header, using a 64-bit date format. MTAACP performs a computation to convert the date between ASCII and 64-bit binary form. 1.14 Error Logging Enhancements, Restrictions, and Supplementary Information The following sections contain descriptions of an enhance- ment and a restriction and supplementary information on the Error Logging system. RSX-11M New Features, Restrictions, and Supplementary Information 1-49  1.14.1 Bad Block Replacement Enhancement Since Version 4.5, the Bad Block Replacement algorithm of the Error Logging system has been modified to support the latest Mass Storage Control Protocol (MSCP) Disk Storage Architecture specification. The number of bad block replacement messages that appear in the error log reports has been reduced, and the existing messages contain more information pertaining to the hardware and the block replacement status. In addition, the Bad Block Replacement Attempt message, which appears in the Entry Type column in brief- and full-format reports, has been changed to RCT Device Error. 1.14.2 Error Logging Restriction By moving the error logging routines into the Executive common, the following restriction is introduced. If a driver of an error logging device calls the $CRPKT routine to create an error logging packet, the data address for the data subpacket must not be an address within the driver. Specifically, the address must not be mapped by APR5 because that active page register (APR) is used to map the common. Any user-written driver that performs such a function must allocate a piece of pool, fill in the appropriate information, and pass the pool address to the create-packet routine. 1.14.3 Supplementary Information on Error Logging The following sections contain supplementary information on Error Logging. 1.14.3.1 Possible Error in Error Logging History Summary The History qualifier documents the History Summary Report in Section 3.3.3.4 of the RSX-11M/M-PLUS Error Logging Reference Manual, as the following: RPT generates a summary report sorted by device error history. It displays the hard and soft error count and QIO count for every volume on each device. 1-50 RSX-11M New Features, Restrictions, and Supplementary Information  The history summary database within the Report Generator (RPT), which is created by the /HISTORY qualifier, is updated by only a MOUNT, DISMOUNT, or ERROR_LOGGING RESET record. Errors were noted that were for devices showing errors that were not followed by such a RESET record within the specified date/time range to force updates of the counts. The omitted device was mounted before the range and remained mounted for the entire duration. Thus, there was no record created for the device in the history summary database even though the device reported errors during the selection range. Also, the QIO counts were wrong because they were not updated after the last MOUNT record. The use of a date/time range may make the history summary more prone to error. The history summary information is valid only when there is a MOUNT (or RESET) followed by device activity followed by a DISMOUNT (or RESET) with no activity outside that interval. It seems likely that devices mounted before Error Logging is activated, or left mounted when it is turned off, will not be properly displayed in the history summary. Also, any selection by date/time selection is likely to lead to more or less glaring errors in the history summary report. This problem may be fixed in a later release. 1.14.3.2 Error Logging Support for a Non-Digital Device You no longer need to add a record to the DEVICE_INFO table in the DEVSM1 module for the error logging system to recognize a user-written device level module. 1.15 Supplementary Software Information 1.15.1 Disk Save and Compress Utility Version 4.6 of RSX-11M was the last release to have the Disk Save and Compress utility (DSC) included on the software kit. Any data currently saved on media by the DSC utility will have to be restored using the DSC utility and then resaved using the Backup and Restore Utility RSX-11M New Features, Restrictions, and Supplementary Information 1-51  (BRU). Beginning with Version 4.7, customers will have to use the save and compression features of BRU. 1.15.2 File Control Services Changes Supplementary Information File Control Services (FCS) has been modified to support VMS ancillary control process (ACP) functions that are needed for compatibility with future RSX products and versions of VAX-11 RSX. These modifications increase the size of the FCS code that is included in the task image. Because the increase in FCS code size may affect the building of some large tasks, FCS routine versions that do not have VMS ACP support are included in the object library [1,1]NOVACPLIB.OLB and in the concatenated object module [1,1]FCSNOVACP.OBS. Some large tasks that have a complicated Overlay Description Language (ODL) may be affected by the internal reorganization of specific FCS modules. This situation is indicated by "multiply defined symbol" errors occurring in ODL structures that were previously valid. You must correct the situation by revising the ODL structure. The object library [1,1]NOVACPLIB.OLB can be used to build individual tasks that do not have VMS ACP support. The default routines in the system library remain unchanged. If you replace the routines in the system library (SYSLIB) with the routines from the concatenated object module [1,1]FCSNOVACP.OBS, you will affect all the tasks that are built using the system library, and you will be unable to build tasks with VMS ACP support. If this support is not desired, it can be removed from the system library. The concatenated object module [1,1]FCSNOVACP.OBS is included on the kits and contains the affected modules with the support removed. To remove this support from your system, replace [1,1]FCSNOVACP.OBS in the system library by using the following Librarian utility program (LBR) command: LBR>[1,1]SYSLIB/RP=[1,1]FCSNOVACP.OBS 1-52 RSX-11M New Features, Restrictions, and Supplementary Information  If you also want to remove extended logical name support from the system library by replacing [1,1]FCSNOLOG.OBS in the system library, you must first replace FCSNOVACP.OBS. Some of the same modules are affected by both extended logical name support and VMS ACP support, and the modules are included in both of the concatenated object modules. If FCSNOLOG.OBS is replaced first, some modules in the system library will contain extended logical name support when FCSNOVACP is replaced because the modules in FCSNOVACP.OBS contain extended logical name support. 1.15.3 TKB Restrictions and Supplementary Information The following section describes TKB restrictions and supplementary information. 1.15.3.1 OTS Fast Map Restriction The Object Time System (OTS) Fast Map routine uses the RSX-11M-PLUS fast-mapping facility, which means that the task must not use the IOT instruction for any purpose except fast mapping. (For more information on the fast- mapping facility, see the RSX-11M-PLUS and Micro/RSX Executive Reference Manual.) ______________________ Caution ______________________ Be sure to use both TKB and the system library supplied for your system to ensure that the correct OTS modules are incorporated in your task. If you use the Version 4.1 TKB with an incompatible (older) version of the system library to build an autoloaded overlaid task, the following new fatal error message is issued: TKB -- *FATAL* -- Incompatible OTS module Conversely, if you use the Version 4.1 system library with an older version of TKB, the OTS module FSTMAP is automatically included in any task built, but the module will not be accessible. The FSTMAP module will not affect the execution or performance of your task. _____________________________________________________ RSX-11M New Features, Restrictions, and Supplementary Information 1-53  2 ________________________________________________________________ RSX-11S New Features, Restrictions, and Supplementary Information This chapter describes new features, corrections and device support, restrictions and provides supplementary information. Supplementary information is data that has appeared in previous release notes but is still applicable to the operating system. Section 2.1 summarizes new features. Section 2.2 lists the media on which the operating system is available. Section 2.2.1 and Section 2.5 deal with the hardware devices supported. Subsequent sections provide supplementary information and describe restrictions on individual operating-system components. Information on individual system components is divided into three categories: New features and Describes new features and enhancements enhancements to existing features for Version 4.7. Restrictions Describes restrictions to software performance. Supplementary Describes software changes that information were documented in previous re- lease notes and other information that is not included in the RSX- 11S Version 4.2 documentation set but is still applicable to the software. If no new information or restrictions are provided for a component, that component is unchanged in Version 4.7. RSX-11S New Features, Restrictions, and Supplementary Information 2-1  2.1 Summary of New Features The changes to the RSX-11S operating system for Version 4.7 and previous versions are described throughout this chapter by operating-system component. Version 4.7 changes are summarized here as follows: o Support for the year 2000 and beyond. o Support for the RQZX1 SCSI adaptor. o KDJ11-E Processor (used in MicroPDP-11/93 and PDP-11 /94). 2.2 The Distribution Kit Media The RSX-11S Version 4.7 operating system is distributed on the following media: o One RL02 cartridge disk o One 9-track, 800-bpi, 2400-foot magnetic tape o One 9-track, 1600-bpi, 2400-foot magnetic tape o One TK50 tape cartridge 2.2.1 Supplementary Information on Device Support See the appropriate RSX-11S Software Product Description (SPD) for a list of supported devices on RSX-11S. 2.3 Layered Product Files Table 2-1 lists the layered products that have been updated for this release. Table_2-1_Layered_Products_for_RSX-11S_Version_4.7______________ Directories Backup Documentation Layered_Product_______Used_________Set__________File_Name_______ DECnet-11S [230,200] DECNET [230,200]DECNET.DOC Version 4.7 [225,20] [230,20] (continued on next page) 2-2 RSX-11S New Features, Restrictions, and Supplementary Information  Table_2-1_(Cont.)_Layered_Products_for_RSX-11S_Version_4.7______ Directories Backup Documentation Layered_Product_______Used_________Set__________File_Name_______ DCX KMV11-A [224,200] DCX [224,200]DCX.DOC Development Tools Version 1.03 KMV11-A HDLC [253,200] KMV11 [253,200]KMV11.DOC Framing Software Version 1.02 KMV11 X25 Link Level [322,200] KXI [322,200]KXI.DOC ____Version_1.03________________________________________________ On Version 4.7 RL02 kits, the layered product files are located on the disk labeled 11SKIT. 2.4 Restrictions The following restrictions apply to the RSX-11S Version 4.7 operating system: o RSX-11S, as a memory-resident system, does not provide directory or file support for any magnetic tape, disk, terminal, or print device. o RSX-11S does not support the loading of tasks by the Online Task Loader (OTL) from any Mass Storage Control Protocol (MSCP) fixed disk device. However, fixed disk devices are supported for standard I/O operations. 2.5 New Hardware Support in Version 4.7 The following new devices are supported: o RA71 o RA72 o RA92 o RQZX1 SCSI adaptor: - RZ23L RSX-11S New Features, Restrictions, and Supplementary Information 2-3  - RZ24L - TZ30 ______________________ Caution ______________________ ANSI tape processing for information interchange is not supported on the TZ30 cartridge tape drive. _____________________________________________________ o KDJ11-E Processor (used in MicroPDP-11/93 and PDP-11 /94) 2.5.1 Support for the KDJ11-E Processor Support for the KDJ11-E processor module has been added to Version 4.7. The following features are supported: o The module ID o The TOY clock (Time of Year clock) o On-board serial lines (as terminal driver option) Support has been added in SYSGEN, ACF, Error Logging, SAVE, the Executive, and the MCR SET TIME command for this processor. 2.5.2 RA71, RA72, and RA92 Disk Support Error logging support has been added for the RA71, RA72, and RA92 disk devices. 2.5.3 Supplementary Hardware Information For a complete list of hardware supported by Version 4.7, refer to the Software Product Description contained in your media kit. 2.6 Software Enhancements for Version 4.7 This section describes software enhancements added to Version 4.7. 2-4 RSX-11S New Features, Restrictions, and Supplementary Information  2.6.1 Support for Year 2000 in Date Format The RSX operating systems have been changed to support dates beyond the year 2000. Generally, RSX treats the current year as a two-digit field. The following areas of the RSX system have been changed: o Input-All areas of the system that allow input of a date will now accept two different forms of date input. First, the traditional dates of the dd-mmm-yy format (or mm/dd/yy for TIM) will still be accepted. These dates will always be considered as occurring between the years 1900 and 1999. In addition, the date may now be specified as dd-mmm-yyyy or (mm/dd/yyyy for TIM only), to allow the system to recognize dates occurring after 1999. o Output-In order to preserve compatibility in appli- cations that parse the output of system commands, the format of date output will not be changed. All places that output the date as 2 digits will continue to do so, representing 2000 as 00, and so forth. Places that currently output the date as 4 digits will still output the date as 4 digits. o Internal representations-As documented for the GTIM$ directive, the year field of time vectors is the number of years since 1900. This is still accurate. This field will reach 100(10) in the year 2000. For example, Table 2-2 shows how dates between years 1900 and 2209 will be stored. Dates will be displayed as the lower two digits of the real year or as a four- digit year. However, ODS-I only provides a 7-byte ASCII field for creation and other dates. In order to accommodate this restriction in a way that is consistent with RSX date handling, the 2-bytes of year in the date attribute will be used to represent the year since 1900. The two bytes will be encoded as follows: - Low byte-Low order decimal digit of year, in ASCII. RSX-11S New Features, Restrictions, and Supplementary Information 2-5  - High byte-Quotient of years since 1900 divided by 10, plus 60(8). This represents the ASCII high digit of the year from 1900 - 1999. In 2000, however, this will result in ":" being stored for the high digit of the year. For years 2010 through 2019, ";" will be stored, and so forth. This change should result in another 200 years or more of file representations. Table_2-2_Storage_of_Dates_in_RSX_Systems_after_1990______ Calendar_Year____Year_Field_Representation________________ 1990 - 1991 90 - 99 2000 - 2009 :0 - :9 2010 - 2019 ;0 - ;9 2020 - 2029 <0 - <9 2030 - 2039 =0 - =9 2040 - 2049 >0 - >9 2050 - 2059 ?0 - ?9 2060 - 2069 @0 - @9 2070 - 2079 A0 - A9 2080 - 2089 B0 - B9 2090 - 2099 C0 - C9 2100 - 2109 D0 - D9 2110 - 2119 E0 - E9 2120 - 2129 F0 - F9 2130 - 2139 G0 - G9 2140 - 2149 H0 - H9 2150 - 2159 I0 - I9 2160 - 2169 J0 - J9 2170 - 2179 K0 - K9 2180 - 2189 M0 - M9 2190 - 2199 N0 - N9 (continued on next page) 2-6 RSX-11S New Features, Restrictions, and Supplementary Information  Table 2-2 (Cont.) Storage of Dates in RSX Systems after __________________1990____________________________________ Calendar_Year____Year_Field_Representation________________ 2200_-_2209______O0_-_O9__________________________________ The following features have been changed to accept or display the new date format: o DCL SET TIME command o MCR command line interface o BROADCAST utility o MCR BYE command 2.7 Software Problems Corrected in Version 4.7 This section describes software problems corrected in Version 4.7. 2.7.1 Correction to SHUTUP SHUTUP.TSK did not complete properly if the CO: device was logged in. SHUTUP.CMD would not execute and the CPU would not halt. This problem has been fixed by changing SHUTUP to log out all users before turning off console logging. 2.7.2 KW11-P Clock When trying to use the KW11-P clock by means of a CINT$ routine, when the clock was not being used as the system clock, the following DSW error was returned: IE.RSU (Vector in Use) This problem has been corrected. 2.7.3 FAL On Version 4.6, FAL would hang if a remote node issued a directory command with a blank file specification. For example: DIR REMNOD"usernam password"::LB:[1,2] This problem has been corrected. RSX-11S New Features, Restrictions, and Supplementary Information 2-7  2.7.4 OTL Returned an Error When Trying to Load NCP/EVC The Online Task Loader (OTL) under RSX-11S Version 4.4 reported an error when attempting to load DECnet-11S Version 4.3 tasks. When attempting to load NCP or EVC from an RX50, OTL returned error code 42, "Not enough APRs for task image." This resulted when loading a privileged task that overmapped the I/O page, because the module OTLLB.MAC reserved an APR for mapping the I/O page. This problem has been fixed. 2.7.5 Correction to FLX Previously, FLX did not display the maximum number of blocks on a tape if the number of blocks was too large. This problem has been fixed. 2.7.6 Intermittent Problem When Getting Data Late Errors on RK06 or RK07 Drives Previously, there was an intermittent problem that resulted in getting data late errors. Due to potential inaccuracies in the way the RK06 reports word count when a data late is declared, the retry logic in the driver would restart the read or write operation in the wrong block. This problem has been fixed. 2.8 Software Problems and Restrictions in Version 4.7 This section describes software problems and restrictions that have not been corrected for Version 4.7. 2.8.1 BRU Restrictions This section describes restrictions to the Backup and Restore Utility (BRU). 2.8.1.1 Use of Wildcards in BRU BRU supports the asterisk (*) character only as a replacement of an entire field in a file specification. BRU will issue the "Invalid value or name" fatal syntax error when an asterisk is used to replace part of a file specification field. 2-8 RSX-11S New Features, Restrictions, and Supplementary Information  2.8.1.2 Problem with the /NEW_VERSION Qualifier A problem with the /NEW_VERSION qualifier occurred when used in a BRU command line during a disk-to-disk backup. From the input device, BRU backed up multiple versions of a file in the order that they appeared in a directory, instead of in ascending order by version number. As a consequence, when the files were restored to the output device, new version numbers were assigned when each file was restored, and the original order of the files was not preserved. Thus, the last version of a file on the output device may not have been the last version created on the input device. The following workarounds are suggested to avoid this problem: o Sorting files on the input device. o Purging files prior to backing up your files. 2.8.2 Tasks Hang When Attaching to Another Terminal Already Attached to a Task Tasks would occasionally hang when they attempted to attach a terminal that was already attached to another task. The attach QIO request never returned and the task had to be manually aborted. As a workaround, the Marktime directive (MRKT$) can be used to implement a timeout function within the application code. If the attach function is issued as a QIOW, you can precede it with a MRKT$ directive, specifying the same event flag number using the I/O status block to distinguish between timeouts (IS.PND) and I/O completion (other values). Alternatively, the MRKT$ directive can specify an AST routine to be entered at the expiration of the timer with a CMKT immediately following the QIOW. There are other workarounds such as using WTLO or WTSE with QIO and MRKT$ directives. In these workarounds, the expiration of the time interval without I/O completion would signal the need for an I/O kill to be issued. RSX-11S New Features, Restrictions, and Supplementary Information 2-9  2.8.3 Problem with Unused Terminal Ports The system can crash if you have an unused terminal port with a cable connected to the port. This problem can be eliminated by either removing the unused cables or setting the unused ports to slaved ports. 2.9 Software Problems Corrected Since Version 4.5 The software problems described in the following subsections were corrected since the release of RSX-11S Version 4.5. 2.9.1 INITL Module Fails to Clear Certain Memory Locations on Boot A problem was noted with the INITL module in system code. INITL failed to clear certain memory locations during a boot operation and failed to size memory correctly if a parity error occurred at a 2K boundary. A more specific description of the problem is as follows. INITL used the size of memory in 32K-word blocks that was contained in the location $SYSIZ. The value in $SYSIZ was obtained from a system generation query to the user about the size of memory. INITL then used this value as the location from which to start clearing memory. The problem occurred because some uncleared memory existed between the system image and the memory location specified in $SYSIZ. These memory locations could contain parity errors. The solution to the problem is as follows. The location $SYSIZ+10 contains the size of the system image in 256- word blocks if the system is booted by the BOO task or down-line loaded by DECnet. The value in this location is now used to ensure that all of memory is cleared. If the system was booted by other means, which does not place a value in $SYSIZ+10, the code in INITL uses the value stored in $SYSIZ as before. In this case, the user must ensure that the value specified in $SYSIZ matches the size of the system image to avoid a potential problem. 2-10 RSX-11S New Features, Restrictions, and Supplementary Information  2.9.2 OTL Corrupts System After Task Load Error in Undersized Partition A problem was noted with using the On-line Task Loader (OTL) to load a task in a partition too small to contain it. A more specific description of the problem is as follows. If you used OTL to load a task into a separate task partition too small to hold it, OTL reported the error Partition too small. Subsequent OTL requests for the same task get the error Partition not in system and then other privileged tasks (such as RSD) sometimes crashed the system. The problem related to the error cleanup routines that deallocated Partition Control Blocks (PCBs) for tasks in a system-controlled partition. The routines did not function correctly for separate task PCBs that had their pool space deallocated but still linked into the system PCB list. These routines were corrected for Version 4.6 of the system. RSX-11S New Features, Restrictions, and Supplementary Information 2-11  3 ________________________________________________________________ RMS-11 Version 2.0 Release Notes This chapter describes RMS-11 corrections to the software, restrictions, and supplementary information. RMS-11 Version 2.0 has not changed version numbers for this release of RSX-11M. Information in this chapter has not been incorporated into the RMS-11 manuals. 3.1 RMS-11 Corrections The following sections describe corrections for RMS-11. 3.1.1 RMS-11 Local Access RMS-11 applications, which performed multistreaming asynchronous record operations resulting in a high rate of competition for the same buckets, encountered the following set of problems: o Executing a breakpoint trap in RMS modules R0RLSB and R0RSET. o Looping indefinitely in RMS modules R0RSET and R0RLCH. o Stalling indefinitely while waiting for the RMS event flag. o Receiving "Dynamic Memory Exhausted" error (ER$DME) on a $FIND, $GET, $PUT, $UPDATE or $DELETE operations, which are operations that do not require new use of dynamic memory. o Receiving "Bucket Header Checkbyte" error (ER$CHK) when, in fact, the file does not have this problem. The problems in the preceding list have been corrected. RMS-11 Version 2.0 Release Notes 3-1  3.1.2 Partial Block Writes with Block I/O Applications based on RMS-11 that used block I/O and attempted to execute partial block writes to an RP03 drive previously failed when the data length was not double- word aligned. RMS-11 returned primary status (STS) as ER$WER (write error) and secondary status (STV) as IE.BYT (Illegal byte count for I/O). RMS-11 applications perform partial writes on the last block of a file in order to have RMS-11 properly record the end-of-file attribute. However, RMS-11 was not rounding up to the double-word boundary as required for the RP03. This problem, which affected the DECnet file transfer partners Network File Transfer (NFT), File Access Listener (FAL), and the RMS-11 utilities, has now been corrected. 3.2 Restrictions to RMS-11 Remote Access Methods (RMSDAP) The following sections describe restrictions to RMS-11 Remote Access Methods. 3.2.1 Incorrect Interpretation of Keysize Field Values RMSDAP does not interpret a keysize field value of zero correctly. This causes keyed access to a remote indexed file to fail. The application passes the value zero for access to a non-string key and issues the following error message: ER$RNF (Record not found) If your program is written in F77 or other high-level languages, you may have to use a USEROPEN routine in order to be able to set this value. 3.2.2 Using RMSDAP on Your System The RMSDAP provided on your system uses a 576 byte buffer for transfers between your program's record/user buffer and your DECnet-RSX system network buffer. This buffer must be large enough to hold the record and the DAP message overhead (approximately 36 bytes). In certain rare cases, this buffer length may be insufficient. 3-2 RMS-11 Version 2.0 Release Notes  In particular, if you access a sequential variable file with a Maximum Record Size (MRS) of zero (used when no maximum has been set), and the sum of the largest record length (LRL) and the DAP message overhead exceeds the 576 byte length, your record access will fail with the RMS error, ER$MRS. This occurs because RMSDAP functions at a DAP protocol level that does not allow reconfiguration of buffersize without actually closing and reopening the file (and that is an unacceptable alternative for RMSDAP). If it is within your control to create the remote file, then an explicit MRS should be used. If not, the local RMSDAP buffer can be lengthened by the system manager (prior to run time) depending on the following considerations: o If your program was built with in-task RMSDAP, consult your map to determine the location of the variable $BUF.M (current contents 1100 octal) in the module R0NFRT in your application. After saving a copy of your application, ZAP the desired buffer length (including DAP overhead) into your application. This change will only affect your application. o If your program was built against the DAPRES library, consult the map (LB:[1,34]DAPRES.MAP) and determine the location of $BUF.M in module R0NFRT. Remove the DAPRES from memory. After saving a copy of LB:[1,1]DAPRES.TSK, ZAP in the desired buffersize. Reinstall the DAPRES library. This change will affect all programs built and run against the DAPRES library. In both cases the increased size of the buffer will be reflected in the size of your RMSDAP applications. ________________________Note ________________________ Network transfers rely on configuration of local RMSDAP and DECnet-RSX network buffers as well as remote FAL and DECnet-RSX network buffers. In all negotiations, the smaller buffer length is used. If your local RMSDAP buffer size exceeds the local DECnet-RSX buffer, the remote FAL, or the remote network buffer size the excess will be unusable, thus effectively eliminating the workaround. _____________________________________________________ RMS-11 Version 2.0 Release Notes 3-3  3.3 Corrections to RMS-11 Utilities The following sections describe corrections to RMS-11 utilities. The corrections are listed by utility. 3.3.1 RMSIFL Correction RMSIFL failed to correctly report exit status when errors occurred while loading a file with more than one alternate key. Once the first alternate key had been loaded without errors, internal exit status was set to success. Any errors on subsequent keys were not reflected in the final exit status of the task. This could cause command files or batch jobs to function incorrectly. This problem has now been corrected. RMSIFL incorrectly determined exception records when the key was packed decimal and the value was negative. This problem has been corrected. 3.3.2 RMSDES Correction RMSDES incorrectly shared channels between several commands. This resulted in the GET and SAVE commands using improper default devices (where explicit devices did not exist in the design buffer or in the actual command). The default device would have been set to LB: if HELP had been requested, or to either SY: or an explicit device when a CREATE command had been issued. The lack of an explicit device should have resulted in the GET or SAVE command using the SY: device. This problem has been corrected. 3.3.3 RMSBCK Corrections RMSBCK failed to correctly back up more than one file to a tape container when the date qualifiers (/CD or /RD) were used. Task exit status reported failure; however, the summary listing for the file container reported no errors. Each file after the first file was not actually backed up (the header for the file was backed up, but no data was present). A summary listing would claim that all blocks were backed up. An ensuing restore operation would produce empty files. This problem has been corrected so that the date switch no longer interferes with the backup. 3-4 RMS-11 Version 2.0 Release Notes  The utility failed to query the user about continuation in some cases in which read/write errors were discovered. The query is now performed. RMSBCK skipped files whose attributes could not be backed up (due to I/O errors); however, these files were reported as fully backed up. These output files are now reported correctly as empty files. Backup sets created on RSX-11M, or octal-based RSX- 11M-PLUS systems, were restored with incorrect version numbers. Backup incorrectly assumed that the source file came from a system that used decimal-based version numbers. For example: file FOO.DAT;10 was restored as FOO.DAT;12 even though both the input and output systems used octal-based version numbers. When this same file was restored to an RSX-11M-PLUS system, which supported decimal-based version numbers, the version number remained FOO.DAT;10 rather than being converted to FOO.DAT;8. This problem did not exist if the input system supported decimal-based version numbers. This problem has been corrected. 3.3.4 RMSRST Corrections RMSRST failed to query the user about continuation where read/write errors were discovered. The utility did not count write errors in the summary listing. Exit status was reported as failure; however, the summary listing reported "no errors." RMSRST ignored certain information in backup when creating output files. This caused the files to misrepresent the Longest Record Length (LRL) for the file. Some applications depend on this field to set up minimum-sized buffers. RMS-11 (or remote RMS implementations) reported "record too big for buffer" when attempting record-mode access on the file. RMS-11 Version 2.0 Release Notes 3-5  3.3.5 Additional Corrections to Three Utilities RMSDSP, RMSBCK, and RMSRST have been fixed to accept extended logical names. Previously, these utilities did not accept logical names containing an underscore (_) or a dollar sign ($) if the logical name was not followed by a colon. They will now accept these characters as well as the dollar sign or a number as the first character of a logical name. The logical name need not be followed by a colon. Parsing problems were corrected across several utilities. 3.4 RMS-11 Supplementary Information The following section describes information that has been documented in the previous release notes. 3.4.1 Building Combined Supervisor Mode and Remote Access RMS Programs A new Overlay Description Language (ODL) file has been added to simplify the building of RMS programs that combine supervisor mode RMS with remote access RMS (DAPRES). The file is LB:[1,1]DAPSLX.ODL. 3.4.2 Enhancements to RMSDES Utility The following enhancements have been made to the RMSDES utility: o There are two additional RMSDES commands: SAVE_ S[UPERSEDE] and EXIT_S[UPERSEDE]. o RMSDES issues the warning message "%DES-W-CBK, Continuation buckets will be allocated for this key" when continuation buckets are required. (Continuation buckets may result in decreased performance; see the RSX-11M/M-PLUS RMS-11 User's Guide.) o The informational message "?DES-F-VOR, Value out of legal range" is issued if overflow occurs during calculations of indexed file area allocations. Also, the "Number of duplicates:" prompt has been expanded to "Number of duplicates per record on this key:" for clarity. 3-6 RMS-11 Version 2.0 Release Notes  o The new error message "%DES-F-NHF, Help file is not available. Check release notes for the location of RMSDES.IDX on your installation media." is issued if the help file LB:[1,2]RMSDES.IDX is not found. This is a feature for small systems that have limited disk space. 3.5 RMS-11 Restrictions The following sections describe software restrictions that apply to RMS-11 Version 2.0. 3.5.1 Restrictions to RMS-11 Utilities The following sections describe restrictions to the RMS-11 utilities for Version 2.0. 3.5.1.1 RMSIFL Restrictions RMSIFL uses a sort algorithm that, when called upon to sort on a key, does not preserve the first-in/first-out (FIFO) ordering of duplicates. For alternate keys, it is necessary to work around this problem by using RMSCNV. If the only concern is ordering of duplicates in the primary key, then as long as your input file is an indexed file or a file sorted on primary key, you can use RMSIFL /NOSO. 3.5.1.2 RMSCNV Restriction RMSCNV ignores user-provided area extension quantities when loading a file. The values that are used are large enough to reduce the number of file extensions in most cases. 3.5.2 RMS-11 Version 2.0 Installation On most RSX-11M systems, all RMS-11 files are automat- ically on your system after system generation. However, for systems that were generated using distribution kits on RL01/RL02 or RK06 disks or the magnetic tape versions of these kits, the RMS-11 files must be transferred after system generation. If your system was not generated using one of these kits, you may want to skip the next section and go to Section 3.5.2.2. RMS-11 Version 2.0 Release Notes 3-7  3.5.2.1 RL01/RL02 and RK06 Procedures To transfer RMS-11 files to RL01/RL02 and RK06 disks, you must execute the command procedure [1,2]RMSINSTAL.CMD. This procedure is fully documented in the RSX-11M System Generation and Installation Guide. 3.5.2.2 Startup Command Procedures If all the RMS-11 files have been transferred to your system, all you need to do is to install the resident libraries and RMS-11 utilities at system startup. To aid you in the installation process, the file LB:[1,2]STARTUP.CMD contains sample comments that can be edited to become system startup commands. You must allocate a partition for each resident library you specify by using the SET command. You must allocate a partition called RMSRES, and you must install in that partition either the full-function resident library (RMSRES) or the subset library (RMSRESSUB.TSK). If you always plan to use the same library (no alternating between the full-function and the subset library), and you want to save disk space, you can delete the task image that you are not using. If you delete the full-function RMSRES.TSK and you plan to use only RMSRESSUB.TSK, then rename RMSRESSUB.TSK to RMSRES.TSK. Renaming these files will ensure that your programs and RMS-11 utilities will always link against the task named RMSRES. ________________________Note ________________________ If you use the subset library and you rebuild the RMS-11 utilities in their resident library form, utility functions for indexed files will be invalidated. _____________________________________________________ You can include the SET commands in your startup command file, or you may want to include the RMSRES and DAPRES partitions permanently in your system by performing the following steps: 3-8 RMS-11 Version 2.0 Release Notes  1. Use the SET commands to include the necessary partitions. 2. Use the INSTALL commands to install the tasks in the running system. 3. Use the SAVE command to save RMSRES and DAPRES into the system image. See your RSX-11M/M-PLUS MCR Operations Manual for more information about these commands. 3.5.2.3 Utility Configurations The RMS-11 utilities that are provided on the distribution kit are built to use disk-overlaid RMS-11. 3.5.2.4 Utility Command and ODL Files For each utility, a command and ODL file is provided that can be used to build the utility using disk-overlaid RMS- 11. The names of the files are as follows: __________________________________________________________ Utility_____Files_________________________________________ RMSBCK BCKNON.CMD, BCKNON.ODL, and RMSODL.ODL RMSRST RSTNON.CMD, RSTNON.ODL, and RMSODL.ODL RMSCNV CNVNON.CMD and CNVNON.ODL RMSDSP DSPNRN.CMD, DSPNON.ODL, and RMSODL.ODL RMSDES DESNON.CMD and DESNON.ODL RMSDEF DEFNON.CMD, DEFNON.ODL, and RMSODL.ODL RMSIFL______IFLNON.CMD_and_IFLNON.ODL_____________________ For each utility, a command and ODL file are provided that can be used to build the utility with the resident library RMSRES. The names of the files are as follows: __________________________________________________________ Utility_____Files_________________________________________ RMSBCK BCKNRN.CMD and BCKNRN.ODL RMSRST RSTNRN.CMD and RSTNRN.ODL RMSCNV CNVNRN.CMD and CNVNRN.ODL RMS-11 Version 2.0 Release Notes 3-9  __________________________________________________________ Utility_____Files_________________________________________ RMSDSP DSPNRN.CMD and DSPNRN.ODL __________________________________________________________ Utility_____Files_________________________________________ RMSDES DESNRN.CMD and DESNRN.ODL RMSDEF DEFNRN.CMD and DEFNRN.ODL RMSIFL______IFLNRN.CMD_and_IFLNRN.ODL_____________________ For RMSCNV, two additional configurations are available if you want to use RMSCNV to access files on remote nodes. To build RMSCNV using the clustered RMS-11 and RMSDAP resident libraries, use files CNVNRR.CMD and CNVNRR.ODL. To build RMSCNV using disk-overlaid RMS-11 and RMSDAP, use files CNVNOO.CMD and CNVNOO.ODL. 3.5.2.5 Rebuilding the Utilities To rebuild the utilities, perform the following steps: 1. Log in to a privileged account. 2. Set your default account to directory [1,24] on the system disk. 3. Use the Task Builder (TKB) to build the utility or utilities. The utilities and the corresponding map files will be built in the current account. You may then want to put the utility in the system account ([1,54]). Each command file for a particular utility creates a utility of the correct name. For example, CNVNRN.CMD and CNVNON.CMD both produce task images called RMSCNV.TSK. One is built to use the resident library and one is built with disk-overlaid RMS-11. 3-10 RMS-11 Version 2.0 Release Notes  3.5.3 Files and Placement on the Distribution Kit The following list describes the contents of the RMS-11 Version 2.0 distribution kit: __________________________________________________________ File_Name________DestinationComments______________________ RMSMAC.MLB LB:[1,1] Can be deleted if you are not using MACRO-11 RMS-11 programs. RMSLIB.OLB LB:[1,1] Object library for RMS-11 local access. RMSDAP.OLB LB:[1,1] Object library for RMS-11 remote access. Can be deleted if you do not need remote access. RMSBCK.TSK LB:[1,54] RMSBCK utility; does not use RMSRES. RMSRST.TSK LB:[1,54] RMSRST utility; does not use RMSRES. RMSDEF.TSK LB:[1,54] RMSDEF utility; does not use RMSRES. RMSDSP.TSK LB:[1,54] RMSDSP utility; does not use RMSRES. RMSCNV.TSK LB:[1,54] RMSCNV utility; does not use RMSRES. RMSDES.TSK LB:[1,54] RMSDES utility; does not use RMSRES. RMSIFL.TSK LB:[1,54] RMSIFL utility; does not use RMSRES. RMSDES.IDX LB:[1,2] Indexed help file used by RMSDES. RMS11.ODL LB:[1,1] Prototype ODL file. R0RMS1.MAC LB:[1,1] For use with the prototype ODL. RMS11S.ODL LB:[1,1] ODL file for sequential file organization. RMS-11 Version 2.0 Release Notes 3-11  __________________________________________________________ File_Name________DestinationComments______________________ RMS12S.ODL LB:[1,1] ODL file for sequential file organization. RMS11X.ODL LB:[1,1] Standard indexed file ODL. RMS12X.ODL LB:[1,1] Indexed file ODL. RMSRLX.ODL LB:[1,1] ODL for use with RMSRES. DAP11X.ODL LB:[1,1] ODL for use with overlaid RMSDAP. DAPRLX.ODL LB:[1,1] ODL for use with DAPRES. RMSRES.TSK LB:[1,1] TSK image for linking against RMSRES. RMSRES.STB LB:[1,1] STB file for RMSRES. RMSRES.MAP LB:[1,34] Map file for RMSRES. RMSRESSUB.TSK LB:[1,1] Subset library. RMSRESSUB.MAP LB:[1,34] Map file for subset library. DAPRES.TSK LB:[1,1] Task image for RMSDAP resident library. DAPRES.STB LB:[1,1] STB file for DAPRES. DAPRES.MAP LB:[1,34] Map file for DAPRES RMSRES.CMD LB:[1,24] For rebuilding RMSRES. RMSRES.ODL DAPRES.CMD LB:[1,24] For rebuilding DAPRES. DAPRES.ODL BCKNON.CMD LB:[1,24] For rebuilding the overlaid BCKNON.ODL version of RMSBCK. BCKNRN.CMD LB:[1,24] For rebuilding the resident BCKNRN.ODL library version of RMSBCK. CNVNON.CMD LB:[1,24] For rebuilding the overlaid CNVNON.ODL version of RMSCNV. CNVNRN.CMD LB:[1,24] For rebuilding the resident CNVNRN.ODL library version of RMSCNV. CNVNOO.CMD LB:[1,24] For rebuilding the overlaid CNVNOO.ODL version of RMSCNV including the overlaid remote access code RMSDAP. 3-12 RMS-11 Version 2.0 Release Notes  __________________________________________________________ File_Name________DestinationComments______________________ CNVNRR.CMD LB:[1,24] For rebuilding the resident CNVNRR.ODL library version of RMSCNV including resident library remote access code DAPRES. DEFNON.CMD LB:[1,24] For rebuilding the overlaid DEFNON.ODL version of RMSDEF. DEFNRN.CMD LB:[1,24] For rebuilding the resident DEFNRN.ODL library version of RMSDEF. DESNON.CMD LB:[1,24] For rebuilding the overlaid DESNON.ODL version of RMSDES. DSPNON.CMD LB:[1,24] For rebuilding the overlaid DSPNON.ODL version of RMSDSP. DSPNRN.CMD LB:[1,24] For rebuilding the resident DSPNRN.ODL library version of RMSDSP. IFLNON.CMD LB:[1,24] For rebuilding the overlaid IFLNON.ODL version of RMSIFL. IFLNRN.CMD LB:[1,24] For rebuilding the resident IFLNRN.ODL library version of RMSIFL. RSTNON.CMD LB:[1,24] For rebuilding the overlaid RSTNON.ODL version of RMSRST. RSTNRN.CMD LB:[1,24] For rebuilding the resident RSTNRN.ODL library version of RMSRST. RMSUTL.OLB LB:[1,24] For rebuilding several RMSODL.ODL utilities. GSA.MAC LB:[200,1] Demonstration program included as an illustration of how to extend an RMS-11 task in the event of pool exhaustion. PARSE.MAC LB:[200,1] Demonstration programs for the SEARCH.MAC new directory and wildcarding RENAME.MAC facilities. ERASE.MAC PARSE.TSK SEARCH.TSK RENAME.TSK ERASE.TSK_________________________________________________ RMS-11 Version 2.0 Release Notes 3-13  ________________________Note ________________________ All RMSDAP files can be deleted if you are not using RMS-11 to access files on remote nodes. _____________________________________________________ 3.5.4 Reporting Problems Software Performance Reports (SPRs) allow you to report any software problems directly to Digital. Appendix A of this manual includes the general procedures for filling out SPRs. The following additional information should be submitted with SPRs for RMS-11 software: 1. Include the version number and patch level of the RMS- 11 that you are using. 2. Indicate whether you are using a programming language to process the file or files and, if so, include the version number and patch level of the language. 3. Include a Postmortem Dump (PMD) and a map of the task involved, if RMS-11 aborts (or if some other task crashes and RMS-11 appears to be the cause). 4. Include a copy or copies of the file or files involved, in RMSBCK format. 5. Include copies of the files that can cause the error if the errors are reproducible. If the problem is not reproducible, include a copy of the corrupt file if possible. 6. Include a description of the command line or lines or interactive session that led to the error (for RMS-11 utilities). 7. Include a listing of the actual error, if possible. 3-14 RMS-11 Version 2.0 Release Notes  4 ________________________________________________________________ Documentation Corrections This chapter describes errors and omissions in the RSX- 11M, RSX-11S, and RMS-11 documentation sets. The chapter is organized according to the titles of manuals, and the information that needs correction is listed by its section number in the manual. 4.1 IAS/RSX-11 System Library Routines Reference Manual Please make the following corrections to the manual: o The following program section names and SYSLIB routines should be added to Table 1-1 page 1-3, of the IAS/RSX- 11 System Library Routines Reference Manual: _______________________________________________________ Program Section Name_____________Module_Name______Routine_Name_________ PUR$D CAT5B (data) $CAT5B EDTMG (data) $EDTMG PUR$I CAT5B $CAT5B (instruction) EDTMG $EDTMG _________________(instruction)_________________________ o In Section 2.1, page 2-3, the box at the top of the page should enclose the "Return Address to $SAVAL" line. o In Section 6.2.2, page 6-4, the information under NOTE should be changed. The correct information is as follows: For HH, the $TIM routine always returns two characters for all values specified. Documentation Corrections 4-1  A documentation error occurs in the IAS/RSX Library Routines Reference Manual. The following is documented in error in Table 6-1 for the $EDMSG routine: Table_4-1_Table_6-1_$EDMSG_Routine_Editing_Directives_____ Directive___Form__Operation_______________________________ X %X Converts a Radix-50 filename string in ARGBLK to an ASCII string in the format name.typ; converts the octal version number, if present, to ASCII and stores the results in OUTBLK. X %nX Converts the next n Radix-50 filename strings in ARGBLK to ASCII strings in the format name.typ; converts octal version numbers, if present, to ASCII and stores the results in OUTBLK; inserts a tab between strings. X %VX Uses the value in the next word in ARGBLK as a repeat count, converts the specified number of Radix-50 filename strings to ASCII strings in the format name.typ; converts octal version numbers, if present, to ASCII and stores the results in OUTBLK; inserts a tab __________________between_strings.________________________ The documentation must be corrected as follows: 4-2 Documentation Corrections  Table_4-2_Table_6-1_$EDMSG_Routine_Editing_Directives_____ Directive___Form__Operation_______________________________ X X Converts Radix-50 filename string in ARGBLK to an ASCII string in the format name.typ; converts a version number, if non-zero, to an ASCII decimal string if decimal version support is selected in your system. Otherwise the version number is converted to an ASCII octal string. If the version number is zero, no version number is put into OUTBLK; stores the results in OUTBLK. X %nX Converts the next n Radix-50 filename strings in ARGBLK to ASCII strings in format "name.typ"; converts the version numbers, if non-zero, to ASCII decimal strings if decimal version support is selected in your system; otherwise version numbers are converted to ASCII octal strings. If a version number is zero, no version is put into OUTBLK for that filename string. Stores the results in OUTBLK and inserts a tab between strings. __________________________________________________________ Key ARGBLK = The argument block containing the binary data to be converted, the addresses of ASCII and extended ASCII characters or the address of a double precision value. OUTBLK = The output block in which $EDMSG is to store output. (continued on next page) Documentation Corrections 4-3  Table 4-2 (Cont.) Table 6-1 $EDMSG Routine Editing __________________Directives______________________________ Directive___Form__Operation_______________________________ X %VX Uses the value in the next word in ARGBLK as a repeat count, converts the specified number of Radix-50 filename strings to ASCII strings in the format "name.typ"; converts version numbers, if non-zero, to ASCII decimal strings if the decimal version support is selected in your system. Otherwise version numbers are converted to ASCII octal strings. If a version number is zero, no version is put into OUTBLK for that filename string. Stores the results in OUTBLK and inserts a tab between __________________strings.________________________________ Key ARGBLK = The argument block containing the binary data to be converted, the addresses of ASCII and extended ASCII characters or the address of a double precision value. OUTBLK = The output block in which $EDMSG is to store __output._________________________________________________ o In Section 8.2, page 8-6, add the following global symbol definition to the second bulleted list: $WRKPT The address of the FDB must be stored in the word $WRKPT before calling $INIVM. o In Section 8.4, page 8-16, the words "virtual address" should replace "disk address" in the seventh bulleted list item. o In Section 8.5.2, page 8-24, entitled "Convert Virtual to Real Address Routine ($CVRL)," please add the following information to the first paragraph. Virtual address units are words, and dynamic memory addresses are bytes. 4-4 Documentation Corrections  4.2 RSX-11M Guide to Writing an I/O Driver This section describes documentation changes to the RSX- 11M Guide to Writing an I/O Driver manual and directs you to the appropriate places in the manual to make corrections. 4.2.1 Changes to System Data Structures The system data structures (control blocks) changed in the RSX-11M Version 4.2 release. Changes to system data structures are normally documented in the RSX-11M Guide to Writing an I/O Driver. This manual, however, was not revised for the Version 4.2 release. The current information on control blocks has been incorporated in the RSX-11M/M-PLUS and Micro/RSX Crash Dump Analyzer Reference Manual. 4.2.2 I/O Packet Description In Section 2.3.4, page 2-8, please remove the DPB acronym in the second line from the bottom of the page. 4.2.3 I/O Queue Description In Section 2.3.5, page 2-9, please remove the DPB acronym in the second line of the paragraph entitled "The I/O Queue." 4.2.4 Text for Driver Initiator Section Please add the following text to the end of Section 2.4.2, entitled "Post-Driver Initiation Services," on pages 2-11 to 2-12: When the Executive enters the driver at any of the four entry points contained in the driver dispatch table, it accesses D.DSP, locates the appropriate address in the table, and calls the driver at that address. A zero table address indicates that the (loadable) driver is not in memory. For a loadable driver, this field must be initialized to zero. If the driver does not process a given function, this address points to a return instruction within the driver's code. Documentation Corrections 4-5  You must provide a driver dispatch table in the driver source. The label on this table is of the form $xxTBL; it must be a global label. The designation xx is the 2- character generic device name for the device. Thus, $TTTBL is the global label on the driver dispatch table for the generic device name TT. This table is an ordered, 4-word table containing the following entry points: o I/O initiator o Cancel I/O o Device timeout o Power failure When a driver is entered at one of these entry points, entry conditions are as follows: At initiator: If UC.QUE=1 R5 = UCB address R4 = SCB address R1 = address of the I/O packet If UC.QUE=0 R5 = UCB address 4.2.5 MACRO-11 Command Line Error In Section 3.2.1, page 3-9, the command line at the bottom of the page is incorrect. The correct command line should read as follows: MAC>xxTAB,xxTAB=LB:[1,1]EXEMC/ML,LB:[11,10]RSXMC,xxTAB 4.2.6 Building User-Written Drivers In Section 3.3, page 3-14, there is a section from SYSGEN Phase II regarding the building of user-written device drivers. Currently, the manual reads as follows: >; If you are not including a resident data base, >; add the line >; GBLDEF=$USRTB:0 >; to the file instead. 4-6 Documentation Corrections  The correct version should read as follows: >; Also, delete the line >; GBLDEF=$USRTB:0 >; If you are not including a resident data base, >; this line should be left in the file. 4.2.7 I.PRM Description In Section 4.1.1.1, at the bottom of page 4-5, please add the following lines to the I.PRM description: It is generally not recommended that drivers alter or use the I/O packet beyond the device-dependent parameters. Should you find it necessary to use the area beyond the device-dependent parameters, please clear them before calling $IODON. When the last word of the device-dependent parameters is nonzero, the value can have one of several special meanings to the Executive. For example, if the value is nonzero and could be an Executive address, the Executive assumes that the value is a block-locking word. Therefore, if the driver uses the word, it should restore its contents before calling $IODON. 4.2.8 S.VCT Description In Section 4.1.4.1, page 4-21, please add the following paragraph to the S.VCT description: If $xxINT is defined, only the vector pointed to by S.VCT is initialized. If $xxINP and $xxOUT are defined, the vector pointed to by S.VCT is initialized to point to $xxINP. The following vector (address + 4) is initialized to point to $xxOUT. 4.2.9 U.BUF Description In Section 4.1.4.1, page 4-32, please change the address description in U.BUF, which describes the address of NPR device drivers. Add the following sentence to the paragraph at the top of page 4-32: For a 22-bit machine without UMRs (PDP-11/23+), the high- order 6 bits of the address are placed in U.BUF+1. Documentation Corrections 4-7  4.3 RSX-11M System Generation and Installation Guide Please make the following changes to the manual: o The first sentence at the top of page 2-5 should read "The BRU64K System - Each tape distribution kit contains a BRU64K system." The next two sentences should be deleted. o Item 1 on page 2-6 should begin with "Load the distribution tape on the appropriate tape drive" instead of "Load the BRU64K tape on the appropriate tape drive." The next sentence, which is enclosed in parentheses, should be deleted. o Item 2 on page 2-7 should state "Hardware bootstrap the distribution tape" instead of "Hardware bootstrap the BRU64K or BRUSYS tape." o Item 6 on page 2-8 should be deleted. Note that the instructions for performing an RSX-11M system generation on a VMS host system running in VAX- 11 RSX compatibility mode have been added to Chapter 2 of the RSX-11M System Generation and Installation Guide. Also, the reference to RMS in Question 3 of the Executive Options section of SYSGEN Phase I has been removed. The Files-11 Ancillary Control Processor (F11ACP) supports file sharing and placement control, so SYSGEN asks this question if your system includes the F11ACP, regardless of whether your system also includes Record Management Services (RMS). 4.4 RSX-11M-PLUS I/O Operations Reference Manual Please add the following section after the first paragraph of Section G.5 of the RSX-11M-PLUS I/O Operations Reference Manual. When a volume switch is requested, you may, by using the Magnetic Tape Control Task (MAG), cause error codes to be returned to the program that is reading or writing. (Previously, it was necessary either to mount a magnetic tape or to abort the program.) The MAG task also allows a magnetic tape to be initialized if a new tape is 4-8 Documentation Corrections  needed for output and no previously initialized tape is available. 4.5 RSX-11M/M-PLUS Batch and Queue Operations Manual Please add the following changes to the manual: o In Section 2.2, page 2-6, in the description of the PRINT command qualifier /[NO]TRANSFER, please note that when a file is copied from a private device and then printed, the copy is deleted. The original file, however, is not deleted from the private device. o In Section 2.3, page 2-10, the format for the DCL command DELETE is incorrect. The correct format should read: DELETE/JOB queuename jobname[/FILE_POSITION:n] o In Section 2.6.1, page 2-15, please add the following description of the /ALL qualifier to the SHOW QUEUE command: Displays information on all entries in all queues. o In Chapter 3, Section 3.8, note the following addition: Any spooled output or maps are also appended to the print job that contains the log file. In addition, the print job also assumes the characteristics of the batch log. 4.6 RSX-11M/M-PLUS Command Language Manual The following sections contain supplementary information and a restriction on the Digital Command Language (DCL) described in the RSX-11M Command Language Manual. 4.6.1 Corrections to /CREATED/BEFORE and /MODIFIED/BEFORE Qualifiers On pages 5-73, 5-75, and 5-76, the /CREATED:BEFORE and /MODIFIED:BEFORE qualifiers to the BACKUP command are incorrect. The correct syntax is /CREATED/BEFORE and /MODIFIED/BEFORE. Documentation Corrections 4-9  4.6.2 BACKUP Command Qualifiers Two new arguments have been added to the /COMPARE and /VERIFY qualifiers to the DCL command BACKUP in Section 5.10, page 5-81 of the RSX-11M Command Language Manual. The format for the arguments is as follows: BACKUP/COMPARE[:SINGLE_BUFFER] BACKUP/COMPARE[:DOUBLE_BUFFER] BACKUP/VERIFY[:SINGLE_BUFFER] BACKUP/VERIFY[:DOUBLE_BUFFER] For a description of these arguments, see Section 4.16.1.3. 4.6.3 Underscore Character Permitted in BACKUP Command Qualifier In Section 5.10, page 5-79 of the RSX-11M Command Language Manual, the /SAVE_SET:name qualifier to the BACKUP command now permits the use of the underscore character (_) in the parameter name. 4.6.4 ANALYZE/ERROR_LOG Command Please add the following section immediately after Section 5.1.6 of the manual: The ANALYZE/ERROR_LOG command analyzes and formats information about errors and events that occur on your system hardware. It also generates reports that contain information that can be used to repair your hardware. The format and valid qualifiers are as follows: ANALYZE/ERROR_LOG[/keyword[ . . . ]] datafile Parameter keyword Specifies the following qualifiers: /BRIEF /COMMAND:n /DEVICES[:(ddnn:[, . . . ])] /DEVICES[ALL] /ENTRY /FULL /INCLUDE 4-10 Documentation Corrections  /NODETAIL /OUTPUT[:outfile] /PREVIOUS_DAYS=n /REGISTERS /SERIAL_NUMBER:snum /SINCE:(dd-mmm-yy[mm:ss]) or /SINCE:(dd-mmm-yyyy[mm:ss]) /THROUGH:(dd-mmm-yy[mm:ss]) or /THROUGH:(dd-mmm- yyyy[mm:ss]) /TODAY /VOLUME_LABEL:label /[NO]WIDE /YESTERDAY datafile Specifies the output data file. 4.6.5 /HEADERS:n and /MAXIMUM_FILES:n Qualifiers in the DCL Command INITIALIZE The following listed changes should be made to the /HEADERS:n and /MAXIMUM_FILES:n qualifiers in Section 5.9, which is the description of INITIALIZE command. Please make the following changes: o In place of the text that explains the /HEADERS:n qualifier, please add the following: Specifies the number of file headers to allocate initially in the index file. The five system files (INDEXF.SYS, BITMAP.SYS, BADBLK.SYS, CORIMG.SYS, and 000000.DIR) are not included in the value for INF. The value used for /HEADERS:n is derived from the maximum number of file headers specified by /MAXIMUM_ FILES:n, with consideration for pre-extending the index file if the maximum number of file headers will require a multiheader index file (see the description of /MAXIMUM_FILES:n for more information on multiheader index files). You can use Table 4-3 to determine an appropriate value to use for the /HEADERS:n parameter. Documentation Corrections 4-11  Table_4-3_Number_of_Index_File_Headers____________________ Maximum Number Number of of_Files______________Disk_Size__________File_Headers_____ Maximum files less Disks less than Headers=maximum/2 than 25588 209 Mb Maximum files Disks between Headers=25593 greater than 25588 210Mb and 419Mb and less than 51176 Maximum files Disks between Headers=25846 greater than 51176 420Mb and 423Mb and less than 51693 Maximum files Disks greater Headers=51693 greater than 51693 than 423Mb and_less_than_65500_______________________________________ o Please replace the first two paragraphs after the /MAXIMUM_FILES:n qualifier with the following paragraph and table: The maximum number of files varies according to disk size. You may want to use the values in Table 4-4 as the default approximations: Table_4-4_Default_Number_of_Files_-_Approximation_________ Disk_Size________Approximate_Number_of_Files______________ Up to 64Mb Calculate the maximum number of files using the formula following the table From 64Mb to Specify the number of blocks divided by 532Mb 16 as the maximum number of files Greater than Specify 65500 as the maximum number of 532Mb____________files____________________________________ The default used for the maximum number of files is the theoretical maximum possible number of one-block files, divided by eight. The following formula calculates the theoretical maximum number of files: MAXIMUM FILES = ((N-(((N+4095.)/4096.)+9.))*127.)/258. 4-12 Documentation Corrections  4.6.6 Unloading Magnetic Tape In the RSX-11M Command Language Manual, please add the following section to the DISMOUNT command, Section 5.8, after the last paragraph in the description of the /[NO]UNLOAD qualifier. The ANSI standard recommends unloading the ANSI magnetic tape as the default action for dismounting a tape. Depending on which model magnetic tape drive is in use, this will either take the drive off line or actually unload the tape. The DCL qualifier /[NO]UNLOAD causes a specific action other than the default. 4.7 RSX-11M/M-PLUS Error Logging Manual Please make the following documentation changes: o In Table 2-2, page 2-5, the following change must be made to the device entry for the control file module ETSV05: TSV05 /TK25 ETSV05 o In Section 3.3.3.4, the /HISTORY qualifier does not always work as described in the following text: "RPT generates a summary report sorted by device error history. It displays the hard and soft error count and QIO count for every volume on each device." The use of a date/time range may make the history summary more prone to error. The history summary information within the Report Generator (RPT) is valid only when there is a MOUNT (or RESET) followed by device activity, followed by a DISMOUNT (or RESET) with no activity outside that interval. It is likely that devices that are mounted before Error Logging is activated and that remain mounted for the duration, or are left mounted when Error Logging is turned off, will not be properly displayed in the history summary. No record will be created for those devices in the history summary database even if they reported errors during the selection range. This occurs because those devices were not followed by a RESET record within the specified date/time range to force updates of the Documentation Corrections 4-13  counts. The QIO counts may also be wrong because they were not updated after the last MOUNT record. o In Example A-1, page A-3, the following change must be made to the list of acceptable device names: ; TSV05 or TK25 o In Section 3.5, please add the following error message: ERLRPT-F-FORINVCHR, FORMAT error - Invalid character in string in !DP directive. Explanation: A control file module executed a WRITE_GROUP statement where the string in a !DP directive contained a nonprinting character. User Action: Correct the user-written module or submit a Software Performance Report (SPR) for Digital-supplied modules. o Please add the following information, which describes how to use the new error logging feature, to Section 4.5.3: After you write the device level module or modules for your devices, compile the module with the DSP2P1.SYM file. Next, insert your module or modules in ERRLOG.ULB. Note that the name of a user-written module must be in the following format: ExxUSR The parameter xx represents the device mnemonic. Do not use a Digital-supplied device mnemonic as your device mnemonic. Specify your module name in the MODULE statement in the following format: MODULE ExxUSR If there is a NOTES module, the NOTES module name must be in the following format: NxxUSR 4-14 Documentation Corrections  o Appendix C includes an example of the format of an error log packet in memory, as described in the system macro $EPKDF.MAC. Please replace the information under "Type and Subtype Codes for Fields E$HTYC and E$HTYS" with the following information: ; ; Type and Subtype codes for fields E$HTYC and E$HTYS ; ; Symbols with names E$Cxxx are type codes for field E$HTYC. ; Symbols with names E$Sxxx are subtype codes for field E$HTYS. ; E$CCMD ='B' 1 ; Error Log Control E$SSTA ='B' 1 ; Error Log Status Change E$SSWI ='B' 2 ; Switch Logging Files E$SAPP ='B' 3 Append File E$SBAC ='B' 4 ; Declare Backup File E$SSHO ='B' 5 ; Show E$SCHL ='B' 6 ; Change Limits E$CERR ='B' 2 ; Device Errors E$SDVH ='B' 1 ; Device Hard Error E$SDVS ='B' 2 ; Device Soft Error E$STMO ='B' 3 ; Device Interrupt Timeout (HARD) E$SUNS ='B' 4 ; Device Unsolicited Interrupt E$STMS ='B' 5 ; Device Interrupt Timeout (SOFT) E$CDVI ='B' 3 ; Device Information E$SDVI ='B' 1 ; Device Information Message E$CDCI ='B' 4 ; Device Control Information E$SMOU ='B' 1 ; Device Mount E$SDMO ='B' 2 ; Device Dismount E$SRES ='B' 3 ; Device Count Reset E$SRCT ='B' 4 ; Block Replacement E$CMEM ='B' 5 ; Memory Detected Errors E$SMEM ='B' 1 ; Memory Error E$CSYS ='B' 6 ; System Control Information E$SPWR ='B' 1 ; Power Recovery E$CCTL ='B' 7 ; Control Information E$STIM ='B' 1 ; Time Change E$SCRS ='B' 2 ; System Crash E$SLOA ='B' 3 ; Device Driver Load E$SUNL ='B' 4 ; Device Driver Unload E$SHRC ='B' 5 ; Reconfiguration Status Change E$SMES ='B' 6 ; Message Documentation Corrections 4-15  E$CCPU ='B' 10 ; CPU Detected Errors E$SINT ='B' 1 ; Unexpected Interrupt E$CSDE ='B' 11 ; Software Detected Events E$SABO ='B' 1 ; Task Abort 4.8 RSX-11M/M-PLUS Guide to Program Development In Chapter 6, Section 6.2.2, please make the following correction: DCL>LINK/TA:SUPLIB/MAP:SUPLIB FILE, USROBJ/INC:(TTREAD,TTWRIT) > 4.9 RSX-11M/M-PLUS I/O Drivers Reference Manual Please make the following correction to the RSX-11M/M-PLUS I/O Drivers Reference Manual: o In Section 2.4, the correct octal value for the terminal type T.V2xx is 36, not 35. o Add the terminal type LA75 to Table 2-8 with the following values: Octal Value 43 TC.SCP Symbol T.LA75 Terminal Type LA75 TC.LPP 66 TC.WID 80 TC.HFF 1 TC.HHT 1 4.10 RSX-11M/M-PLUS Indirect Command Processor Manual The following sections describe a restriction and supplementary information for the Indirect Command Processor (Indirect) Library. Please add these sections to the manual at the end of Chapter 1: 4-16 Documentation Corrections  Indirect Restriction If a module name referenced is greater than 6 characters, Indirect truncates the name to 6 characters. When a file name is truncated, Indirect returns the following error message: AT. -- File not found Indirect assumes that the module name you want to reference is only 6 characters long, because the module names are truncated to 6 characters by the Librarian Utility Program (LBR) when the files are included in the command library. To avoid this problem, always specify a module name of 6 characters or less when issuing the @/LB:module command line. Also, do not use the @/LB:module command line unless you plan to include command files in a command library. Using the Indirect Command Procedure Library To use the Indirect command procedure library, INDSYS.CLB (as documented in the RSX-11M/M-PLUS Indirect Command Processor Manual), you must copy it from the MCR source volume directory of the distribution kit to the system volume. On single-disk distribution kits (RP04/RP05/RP06 or RM03, for example), copy the file as follows: >PIP LB:[1,2]=LB:[12,10]INDSYS.CLB On multidisk distribution kits (RL01/RL02, for example), mount the MCR source volume (MCRSRC) and copy the file as follows: >PIP LB:[1,2]=dd:[12,10]INDSYS.CLB The drive on which the MCR source volume has been mounted is represented by the letters dd. For the RL01/RL02 kit, the file is located on MCRSRC. Documentation Corrections 4-17  Indirect Command Processor Versions RSX-11M Version 4.7 supports the following versions of the Indirect Command Processor: ICX Provides the full functionality of ICP using the overlay structure of ICQ built for a 12KB partition. This provides additional symbol space at the expense of possible additional overlay activity. ICX is the default for baseline systems. ICX is the only version shipped with baseline systems and is built but not installed automatically by Phase II of SYSGEN. ICP Contains the same functional parameters as the IND task released in Version 4.2. This version requires a 12Kb partition size and may be used for SYSGEN of configurations that do not require ICX. ICP is the default for production systems. ICP is the standard version of Indirect created during the Phase II privileged task build. Both ICX and ICP are included in the privileged task builds during Phase II of SYSGEN. ICP is automatically installed by SYSVMR as the default for production systems at the conclusion of SYSGEN. There is no File Control Services Resident Library Routines (FCSRES) version of this task. 4-18 Documentation Corrections  ICQ Specifies a version that is overlaid more heavily to fit in an 8Kb partition. ICQ cannot be used for SYSGEN under any circumstances. This version supports the minimum of functional parameters necessary to execute a command file that does not exceed the following parameters: o One concurrently open data file o One parallel .XQT directive o Two direct-access labels o One GOSUB nesting level o A 2-level depth of open command files o A 108(10)-byte command file input buffer It is designed for systems that lack sufficient memory space to support a 12Kb task. ICQ's execution time is slower than ICP's, and its symbol table space and functional parameters are insufficient to complete a system generation. ICQ is built during system generation only if the target system contains less than 24Kb of memory. Due to task size constraints on ICQ, enhance- ments and corrections made to Indirect for Version 4.3 do not apply to the ICQ version. ICQ has the same features that it had in Version 4.2 with the exception of the new symbol. The symbol is set to the null directory string ([]) for compatibility with RSX-11M-PLUS and Micro/RSX systems. Documentation Corrections 4-19  ICQRES Specifies the File Control Services Resident Library Routines (FCSRES) version of ICQ. It is also highly overlaid and is slower than ICP. It has the same functional parameters as ICP with approximately the same symbol table space. The task resides in an 8Kb partition and has the following parameters: o Four concurrently open data files o Sixteen parallel .XQT directives o Sixteen direct-access labels o Eight .GOSUB nesting levels o A 4-level depth of open command files o A 132(10)-byte command file input buffer This version is designed for systems that lack sufficient memory space to support a 12Kb task but still attempt to retain the full capabilities of the ICP task. It does not contain enough symbol table space to complete a full system generation procedure, and it must be built as a privileged task with FCSRES support by using the SYSGEN Phase III procedure. Due to task size constraints on ICQRES, enhancements and corrections made to Indirect for Version 4.3 do not apply to the ICQRES version. Except for a new symbol, , no new features have been added to ICQRES since Version 4.2. The symbol is set to the null directory string ([]) for compatibility with RSX-11M-PLUS and Micro/RSX systems. Please make the following documentation corrections to the manual in the designated sections: o In Section 2.4.1.2, the special symbol will have a value of 5 if Indirect is running on a VMS host under VAX-11 RSX. o Change the final sentence in Section 2.4.2 to read as follows: 4-20 Documentation Corrections  See Section 2.4.6.1 for more information. o Delete the following text in Section 2.6.22: Task not installed in system (.XQT, .WAIT) o In Section 2.6, "ticks" are not allowed with the .ASK, .ASKN, and .ASKS directives. o In Chapter 2, Section 2.4.5, add the following statement: The default radix will always be octal unless you specify the character "D" in the format control string. For example, ; NUMBER = 'NUMBER%D' o In Chapter 2, Section 2.6.2, please make the following correction: The format for timeout is nnu, where nn is the decimal number of time units to wait and u is S (seconds), M (minutes), or H (hours). o In Chapter 2, Section 2.6.3, please make the following correction: The format for timeout is nnu, where nn is the decimal number of time units to wait and u is S (seconds), M (minutes), or H (hours). o In Chapter 2, Section 2.6.4, please make the following correction: The format for timeout is nnu, where nn is the decimal number of time units to wait and u is S (seconds), M (minutes), or H (hours). o In Section 2.6.10, 24 hours is the maximum amount of time you can specify for the .DELAY directive. o In Chapter 2, Section 2.6.12, add the following statement: The initial setting of the .ENABLE directive for GLOBAL mode is disabled (not enabled). o In Chapter 2, Section 2.6.19.3, please add the following information: Documentation Corrections 4-21  The directives .IFDF symb and .IFT symb should not be used on the same line. Because the .IFDF symb directive evaluates to false, Indirect processes the remainder of the command line looking for a .OR directive. Instead, it encounters .IFT symb, but because the symbol is undefined, an error message is generated. The following example shows how to test whether a symbol is defined and how to then use that symbol: .IFNDF symbol .GOTO 10$ .IFT symbol . . . .10$: .IFNDF symbol .SETF symbol . . . o Replace the example in Section 2.6.26 with the following: The following example is from an interactive terminal session: >@ti: AT.>.enable substitution AT.>.sets a "1,2," AT.>.parse a "," b c d AT.>;'b' >;1 AT.>;'c' >;2 AT.>;'d' >; (null substring) AT.>.parse a "," b c 4-22 Documentation Corrections  AT.>;'b' >;1 AT.>;'c' >;2, AT.> >@ > o In Appendix A, Section A.2, add the following error message: AT. - File attributes not available Explanation: An attempt was made to obtain file- attribute information with the symbol before any files were opened. User Action: A file must be opened with a .OPEN(x) directive before can contain any information. o In Section A.1, the "AT. - Value not in range" error message can also indicate that the time specified for the .DELAY directive exceeded 24 hours. o In Section A.2, add the following error message: AT. - .EXIT without .END Explanation: After executing a .EXIT directive from within a BEGIN/END block, Indirect encountered end-of- file (EOF) before finding a .END directive. User Action: Edit the command file to ensure that every .BEGIN directive is paired with a .END directive. Then, execute the procedure again. 4.11 RSX-11M/M-PLUS MCR Operations The following sections describe the changes to be made to Chapter 3 of the manual. Documentation Corrections 4-23  4.11.1 /BAD Option Keyword in the MCR Command INI The description of the /BAD=[option] keyword of the MCR command INI[TVOLUME] is partially incorrect. Please add the following information to the section describing the INI/BAD command: To prevent bad blocks from being allocated to files in a volume, first run the Bad Block Locator Utility (BAD). BAD tests volumes for the number and location of bad blocks. (Refer to the RSX-11M/M-PLUS Utilities Manual for a description of the BAD utility.) Then when you initialize a volume with the INI command, INI creates a file named BADBLK.SYS and uses the data generated by BAD to allocate bad blocks to the BADBLK.SYS file. In this way, known bad blocks are not allocated to any other file. The way in which INI creates the BADBLK.SYS file depends upon the input it receives from the BAD utility. In turn, the data generated by BAD differs according to the type of device it is testing. On non-last-track devices, BAD records the addresses of bad blocks on the last good block of the device. This list of bad block addresses is called the Bad Block Descriptor File. INI then uses the Bad Block Descriptor File to create the BADBLK.SYS file. However, on last-track devices, the last track can contain a Manufacturer's Detected Bad Sector File (MDBSF), and a Software Detected Bad Sector File (SDBSF). BAD writes a record of bad blocks to the SDBSF. INI then creates the BADBLK.SYS file by combining the input from the MDBSF and the SDBSF. If you want BAD to treat a last-track device as a non- last-track device, specify the /OVERRIDE switch in the BAD command line. In response to the /OVERRIDE switch, BAD writes a Bad Block Descriptor File on the last good block before the last track. Then, when you initialize the volume, you must also specify the /BAD keyword with the [OVR] option (INI /BAD=[OVR]) so that INI can locate the Bad Block Descriptor File and use it to create the BADBLK.SYS file. 4-24 Documentation Corrections  If you do not specify the /BAD keyword with the INI command, the default action of the command is /BAD=[AUTO]. That is, INI automatically performs bad block processing. The other options of the /BAD keyword allow you to modify the default action of the command. Refer to the RSX-11M/M- PLUS MCR Operations Manual for a complete description of the INI keyword /BAD and its options. 4.11.2 /TERM Qualifier in the MCR Command SET Add LA75 to the list of terminal types for the SET /TERM command. 4.11.3 /TERM Qualifier in the MCR Command ASN Add the following information to the ASSIGN (ASN) command qualifier /TERM: You cannot use ASN/TERM to display information regarding a terminal that is not logged in to the system. 4.11.4 DEFER Option in the MCR MOUNT and SET Commands Add the option [NO]DEFER to the MOUNT and SET commands. 4.11.5 /HSYNC Command Keyword in the MCR SET Command Add the following sentence to the SET command keyword /HSYNC: For more information on type-ahead buffers, see the RSX- 11M/M-PLUS I/O Drivers Reference Manual. 4.11.6 /INF and /MXF Keywords in the MCR Command INI The following listed changes should be made to the /INF and /MXF keywords in Section 3.9, which is the description of INITIALIZE VOLUME command (INI). Please make the following changes: In place of the text that explains the /INF keyword, please add the following: Specifies the number of file headers to allocate initially in the index file. The five system files (INDEXF.SYS, BITMAP.SYS, BADBLK.SYS, CORIMG.SYS, and 000000.DIR) are not included in the value for INF. Documentation Corrections 4-25  The value used for /INF is derived from the maximum number of file headers specified by /MXF, with consideration for pre-extending the index file if the maximum number of file headers will require a multiheader index file (see the description of /MXF for more information on multiheader index files). You can use Table 4-5 to determine an appropriate value to use for the /INF parameter. Table_4-5_Number_of_Index_File_Headers____________________ Maximum Number Number of of_Files______________Disk_Size__________File_Headers_____ Maximum files fewer Disks fewer than Headers=maximum/2 than 25588 209Mb Maximum files Disks between Headers=25593 greater than 25588 210Mb and 419Mb and fewer than 51176 Maximum files Disks between Headers=25846 greater than 51176 420Mb and 423Mb and fewer than 51693 Maximum files Disks greater Headers=51693 greater than 51693 than 423Mb and_fewer_than_65500______________________________________ Please replace the first paragraph after the /MXF keyword with the following paragraph and table: The maximum number of files varies according to disk size. You may want to use the values in Table 4-6 as the default approximations: Table_4-6_Default_Number_of_Files_-_Approximation_________ Disk_Size________Approximate_Number_of_Files______________ Up to 64Mb Calculate the maximum number of files using the formula following the table (continued on next page) 4-26 Documentation Corrections  Table_4-6_(Cont.)_Default_Number_of_Files_-_Approximation_ Disk_Size________Approximate_Number_of_Files______________ From 64Mb to Specify the number of blocks divided by 532Mb 16 as the maximum number of files Greater than Specify 65500 as the maximum number of 532Mb____________files____________________________________ The default used for the maximum number of files is the theoretical maximum possible number of one-block files, divided by eight. The following formula calculates the theoretical maximum number of files: MAXIMUM FILES = ((N-(((N+4095.)/4096.)+9.))*127.)/258. 4.12 RSX-11M/M-PLUS RMS-11 Macro Programmer's Guide Please make the following corrections to the RSX-11M/M- PLUS RMS-11 Macro Programmer's Guide: o In Section 2.3, the argument for P$BUF is "bufcount." This is incorrect. The correct argument is "iopool- size," as discussed in Section 2.3.4. o In Section 5.19, the last paragraph incorrectly describes the use of the FID field in the NAM block. It should read as follows: "If this value is non-zero . . . " o In Section 6.2, Table 6-2, the 000002 value for XB$DAT should be changed to 000003. o In Appendix A, page A-8, please add the following sentence: An attempt to insert a record that is too small to contain the whole primary key field may also cause the error ER$KEY. o In Appendix A, Section A.1, add the following text to the description of the error ER$MRS: Or, the sum of the fixed length record size and the record overhead exceeds the bucket size. Or, No Span Blocks has been selected with an invalid total record size. Documentation Corrections 4-27  o In Appendix A, Section A.1, add the following text to the description of the error ER$NOD: Or, the remote node rejected the operation. (STV contains the Network Services Protocol (NSP) code and can be found in Appendix C of the DECnet-RSX Programmer's Reference Manual.) o In Appendix A, Section A.1, add the following text to the description of the error ER$FUL: ER$FUL, Device or File Allocation Failure Octal: 176360 Decimal: -784 The specified device or directory does not have enough room for file creation or extension. In the case of a contiguous request, it is also possible that there is not enough contiguous space on the device. 4.13 RSX-11M/M-PLUS RMS-11 User's Guide Please add the following corrections to the manual: o According to the RSX-11M/M-PLUS RMS-11 User's Guide, RMS-11 cannot perform an UPDATE operation on an alternate key with the key characteristics CHANGES and NODUPLICATES. This description is misleading. To increase the clarity of the description, please add the following information to Chapter 6, Section 6.2.5.2: Although RMS-11 does not support the CHANGES and NODUPLICATES combination, it does not prevent you from performing an UPDATE operation on an alternate key with these characteristics. When an update causes a duplicate of an alternate key, RMS-11 returns the completion code ER$DUP. However, it does not terminate the UPDATE operation. Instead, RMS-11 updates the primary data level for the record without updating the alternate index. As a result, the file contains duplicates of the alternate key. 4-28 Documentation Corrections  To prevent RMS-11 from creating duplicates when you make changes on alternate keys, modify your application as follows: 1. Create the file with the key characteristics DUPLICATES and CHANGES. 2. To disallow duplicates, perform a FIND operation on each alternate key. Then, perform an UPDATE operation on the modified record. o In Section 2.2.3.3, please add the following informa- tion to the discussion of deadlock: An application should use multistream rather than multichannel access to write to the same indexed file. When RMS-11 updates an RRV in a bucket that is currently locked, it must wait for that lock to be released. Control will not be returned to the program until this release occurs. Deadlock will occur when the lock is held on another channel within the same program; however, RMS-11 can update an RRV in a bucket that is locked on another stream within the same program. See your programming language documentation for details on the implementation of multistreaming. o In Section 6.2.4, the discussion of writing a record, please add the following note: In the event that the record includes a partial alternate key but is not large enough to include space for the full alternate key field, RMS-11 will treat the alternate key as if it were not present in the record, making no entry in the alternate key index structure. o In Section 6.3, the discussion of contiguity and areas, please add the following information: You will obtain a small benefit by setting areas to contiguous on a noncontiguous multi-area file, however, there is no means for RMS-11 to determine if those areas remain contiguous. Consequently, RMSDSP and RMSDES will display them as noncontiguous. As long as the areas are preallocated, they will behave like contiguous areas; as soon as they need to be extended, they will not behave like contiguous areas. Documentation Corrections 4-29  o In Section 8.1.2.1, the discussion of task building against the RMS-11 resident library, incorrect syntax is documented for the cluster option in the Task Builder command file. The correct syntax is as follows: CLSTR = RMSRES,DAPRES:RO o Modify Section 8.1.2.1, page 8-8, paragraph 2, sentence 3, to read as follows: To add remote access (DAP) support to a task that is built against the RMSRES in supervisor mode you must include the following modules: LB:[1,1]RMSLIB/LB:R0EXSY:R0IMPA-LB:[1,1]RMSDAP /LB:R0AULS and include DAPRES as a LIBR or CLSTR option in the Task Builder command sequence. ________________________Note ________________________ Unlike RMSRES the DAPRES cannot be used in supervi- sor mode. _____________________________________________________ o In Appendix B, the discussion of remote file and record access using the DECnet package, the documentation states that the RSTS/E FAL does not support remote record access to indexed files. This is no longer true. 4.14 RSX-11M/M-PLUS RMS-11 Utilities Please make the following corrections to the RSX-11M/M- PLUS RMS-11 Utilities manual: o In Chapter 2, Table 2-1, add the following commands: _______________________________________________________ Command____________Format_and_Function_________________ EXIT_S[UPERSEDE] EXIT_S[UPERSEDE] filename[.typ] Names the description file in which the file design is stored. SAVE_S[UPERSEDE] SAVE_S[UPERSEDE] filename[.typ] 4-30 Documentation Corrections  _______________________________________________________ Command____________Format_and_Function_________________ Names the description file in which ___________________the_file_design_is_saved.___________ o In Chapter 2, Section 2.2.5, add the new command EXIT_ S[UPERSEDE]. The EXIT_S[UPERSEDE] command stores the file design in the description file specified in the command string, superseding any existing file by the same name. EXIT_ S[UPERSEDE] then terminates RMSDES and returns the system prompt. The format for the EXIT_S[UPERSEDE] command is as follows: EXIT_S[UPERSEDE] filename[.typ] EXIT_S[UPERSEDE] names the description file in which the file design is stored. The default file type is DES. If you do not want to supersede an existing description file, use the EXIT command. o In Chapter 2, Section 2.2.5, add the following statement to the description of the EXIT command: To supersede an existing description file, use the EXIT_S[UPERSEDE] command. o In Chapter 2, Section 2.2.9, add the new command SAVE_ S[UPERSEDE]. The SAVE_S[UPERSEDE] command stores the file design in the description file specified in the command string, superseding any existing file by the same name. If you do not define areas when you issue the SAVE command, RMSDES prompts you for the areas. The format for the SAVE_S[UPERSEDE] command is as follows: SAVE_S[UPERSEDE] filename[.typ] SAVE_S[UPERSEDE] names the description file in which the file design is saved. The default file type is DES. If you do not want to supersede an existing description file, use the SAVE command. Documentation Corrections 4-31  If you want to design another file, issue a CLEAR ALL command to restore the attribute values in the design buffer to their defaults. o In Chapter 2, Section 2.2.9, add the following statement to the discussion of the SAVE command: To supersede an already existing description file, use the SAVE_S[UPERSEDE] command. o In Chapter 2, Section 2.6.2, add the following corrections: - 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 require RSX positioning, RMS-11 uses 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 by default, RMSDES will automatically calculate an allocation value for each area it defines. - 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 require RSX positioning, RMS-11 uses 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 by default, RMSDES will automatically calculate an extension value for each area it defines. - Modify paragraph 5 of the BUCKETSIZE field discussion to read as follows: If you intend to create a single-area indexed file and do not require RSX positioning, RMS-11 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 by default, RMSDES will assign a bucket size value for each area it defines. However, if you choose to define areas explicitly and specify a bucket size value for each area, you should accept the default 4-32 Documentation Corrections  for the file section and set the bucket size value in each area section. o In Chapter 2, Section 2.8, add the following correction to the explanation of the error message ?DES-F-VOR: You entered a value in response to an attribute prompt that was not in the valid range of values for that attribute, or the values you entered resulted in a calculation that caused an overflow for RMSDES. If the value was not within the valid range, the error message is followed by a display of the incorrect value. o In Chapter 4, Table 4-1, add the following switch and description to the table of RMSCNV switches: /ER[:filespecContinue processing after encountering an exception record. If a file specification is provided, then write the primary keys of exception records into the specified file. If no file specification is provided, then output the exception records to the terminal. Default: Stop processing and report RMS error code. o In Section 4.3, add the following information to the description of RMSCNV switches: /ER[:filespec] Directs RMSCNV to continue processing when it encounters an exception record in the input file that cannot be written to the output file (see Section 3.4). If you specify a file specification, the exception records will be written to that file. If you do not specify a file specification, the primary key of each exception record will be issued to the terminal. RMSCNV also issues exception record codes (see RMSIFL exception codes, Section 3.3.2). If you specify an exception file specification, RMSCNV will create the file as an RMS-11 Variable Fixed Control (VFC) sequential file upon encountering the first exception record. RMSCNV will then write the Documentation Corrections 4-33  exception record with a 4-byte exception code to the fixed control area of the record. By default, if you do not specify the /ER switch, RMSCNV will stop processing upon encountering the first exception record and will issue an error message indicating the type of exception record. o In Table 5-1, add the following information to the description of RMSDSP switches: /BR Briefly displays attributes. /SU Supersedes existing output file. o In Section 5.2, include the asterisk (*) and percent sign (%) in the description of wildcard characters permitted in the input file specification. o In Section 5.3, add the following information to the discussion of RMSDSP commands: /BR Directs RMSDSP to issue basic displays for indexed files (see Section 5.4, Example 5-3) and container files (see Section 5.4, Example 5-6). /SU Directs RMSDSP to supersede any existing output file with the same name and version number as the output file specification. If this switch is not supplied and the version numbers are the same, RMSDSP will issue the following error message: ?DSP-F_OPNINP, Error opening DDnn:file.dat as output -RMS-E-ER$FEX, File already exists o In Chapter 6, Table 6-1, add the following information to the table of RMSBCK switches: /NV Creates a new version of the output file. o In Section 6.3.2, add the following information to the description of RMSBCK output switches: 4-34 Documentation Corrections  /NV Directs RMSBCK to create a new version of the disk output file if a file currently exists with the same version number as the input file. The current file is not deleted. If you do not specify this switch and a file currently exists with the same file name and version number as the input file specification, RMSBCK will issue the following fatal error message: ?BCK-F-CREOUT, Error opening ddnn:file.dat;n as output -RMS-E-ER$FEX, File already exists o In Section 6.2, in the discussion of RMSBCK command line format, include the asterisk (*) and percent sign (%) in the description of wildcard characters permitted in the input file specification. o In Table 7-1, add the following information to the table of RMSRST switches: /NV Creates a new version of the output file. o In Section 7.2, in the discussion of the RMSRST command line format, include the asterisk (*) and percent sign (%) in the description of wildcard characters permitted in the input file specification. o In Section 7.3.2, add the following information to the discussion of RMSRST commands: /NV Directs RMSRST to create the next higher version number if the expanded input file has the same version number as an existing output file. If this switch is not used and the file name and version number are the same, RMSRST will issue the following error message: ?RST-F-CREOUT, Error opening ddnn:file.dat;n as output -RMS-E-ER$FEX, File already exists Documentation Corrections 4-35  4.15 RSX-11M/M-PLUS System Management Guide Please make the following corrections to the RSX-11M/M- PLUS System Management Guide: o Add the following message to Chapter 2: ACNT-Workfile-open file ACNT-IO error Explanation: The disk that has the account file is full or write-locked. User Action: Provide free space on the disk by deleting files. o Change the following lines in Chapter 6: - In Section 6.4, locate the line "FREEx=ddnn:, where x is a number from 0 to 3 and ddnn: is a device name and number." Change "0 to 3" to "1 to 4." - In Section 6.4, locate the line "RMD displays the number of free blocks on DM0: instead of the fourth Files-11 device in your configuration and replots the display every 3 seconds instead of every second." Change "fourth" to "third." - In Section 6.4, locate the line "To change the second and third Files-11 devices to DB1: and DB2: respectively, use the following MCR command line." Change "second and third" to "first and second." - In Section 6.7, locate the line ">RMD I, DEVICE0=DB1:,DEVICE1=DB2:." Change to "RMD I, DEVICE1=DB1:,DEVICE2=DB2:." - In Section 6.7, locate the line "DEVICE1=ddnn:- specifies the device to be displayed." Change "DEVICE1" to "DEVICE" (no number). o In Chapter 7, Section 7.2, add the following switch to the DCL command INITIALIZE/PROCESSOR (the MCR command QUE): 4-36 Documentation Corrections  /NOWARNINGS (/NM) Reduces the amount of information that is displayed on the console terminal when the system is bootstrapped and the STARTUP.CMD file is invoked. For example, if you use the MCR command QUE LPO:/CR/NM, the message "Queue already exists" is not displayed by the Queue Manager (QMG). The switch /NOWARNINGS (/NM) suppresses this message. o In Chapter 8, Section 8.7.1, please make the following correction: When the delay before system shutdown expires, SHUTUP performs the following functions: 1. Stops the Console Logger (if active) 2. Redirects the console terminal to the TI of SHUTUP 3. Logs out logged-in terminals (multiuser protection systems only) 4. Stops the Queue Manager (QMG) and holds all active batch and print jobs 5. Stops Resource Accounting (if active) 6. Checkpoints all read/write commons 7. Invokes the LB:[1,2]SHUTUP.CMD file (if present) 8. Stops the Error Logger task (ERRLOG) (if active) 9. Deallocates checkpoint space and dismounts devices 10.Halts the processor o In Chapter 9, page 9-3, replace Section 9.2 with the following section: Establishing Terminal Emulation To establish terminal emulation between a local RSX system and a host system, you can use the DCL command SET HOST/DTE or the MCR command DTE. $ SET HOST/DTE ttnn:[/option] > DTE ttnn:[/option] Documentation Corrections 4-37  Parameters ttnn Specifies the RSX device and unit specification of the terminal port used for terminal emulation. option Specifies one of the following options: /DIAL=" . . . Allows the specification of a dial command " string for the modem. The string may consist of any of the digits 0 to 9, and one of the following symbols: - Equal sign (=) - Asterisk (*) - Hyphen (-) - Uppercase A, B, C, D, P, T, and W - Lowercase a, b, c, d, p, t, and w - A space - Number sign (#) - Left parenthesis - Right parenthesis The equal sign indicates that another dial tone is expected (for example, when you dial from an internal telephone system to an outside telephone number). The other symbols provide information for the modem being used. See the manual that accompanies your modem for more information. Note that when you specify /DIAL for a DFA01 modem, the modem automatically changes the terminal speed, if necessary. 4-38 Documentation Corrections  /MUTE Specifies whether DTE should alter certain device characteristics prior to exiting. The default is to return all of the device characteristics to their original states. However, if the device is set to NOSLAVE and ECHO status, it is possible that noise characters can create intersystem echo loops, which can severely affect performance. Therefore, it is recommended that either the device be set SLAVE and NOECHO when it is idle (DTE will change these characteristics) or that the /MUTE option be specified, which will set the device SLAVE and NOECHO when DTE exits. /VERSION Displays the version of the DTE task for DCL only. /ID Displays the version of the DTE task for MCR only. o Please add the following message to Chapter 9, Section 9.4.1, of the manual: ? DTE-F-MODERR, Unable to determine modem type Explanation: The system is unable to determine the type of modem (DF03, DF112, or DF224) in use. User Action: This message may indicate faulty hardware. Check your equipment and repeat the operation. o In Chapter 10, the description of the switch /TYPEAHEAD is incorrect. The default for size is 66(10), not 86(10). o In Chapter 13, Section 13.3.3, please add the following information at the end of the first paragraph: RCT reads the user's disk data in a bad block four times. As a result, data is successfully recovered more often. o On Chapter 13, Section 13.3.4, please add the following information at the end of the section: Documentation Corrections 4-39  The bad block replacement algorithm includes a test that ensures the replacement of bad blocks. When a disk is formatted, a forced error bit is placed in the header of each replacement block. To ensure that the block was revectored correctly, RCT reads the block and checks for the forced error bit. If the block was revectored correctly, the read operation is directed to the replacement block and the forced error bit is found. If the block was not revectored correctly and the forced error bit is not found, RCT write-protects the volume and informs you that the disk is corrupted. The Bad Block Replacement Control Task (RCT) supports the latest Mass Storage Control Protocol (MSCP) Disk Storage Architecture specification. RCT is used with MSCP controllers, such as the UDA-50 and the RC25, which do not perform automatic revectoring of bad blocks. Instead these controllers call the RCT task, which performs revectoring for them. Revectoring is the redirection of data from a dysfunctional block to a block that is functional. A controller that performs its own revectoring creates a complete error log report on the I/O it handles and sends the report to the device driver. The device driver, in turn, sends a report to the Error Logger. In this way, all messages on bad blocks appear in the error log file generated when you enter an ANALYZE /ERROR_LOG command. When RCT performs revectoring, it creates the error log report and sends it to the Error Logger. The Bad Block Replacement Attempt message, which formerly appeared in the error log report in the Entry Type column in brief- and full-format reports, has been changed to RCT Device Error. In addition, an error message is issued by the Task Termination Notification program (TKTN), whose function is to send a message to the console terminal whenever a nonrecoverable hardware error occurs. The message is as follows: *** ddnn: -- Replace command failure 4-40 Documentation Corrections  4.15.1 The TDX Catchall Task Please add the following section and subsections as new sections to the RSX-11M/M-PLUS System Management Guide: The TDX facility has the following functions: o Enables you to run uninstalled tasks o Allows you to abbreviate command names 4.15.1.1 Installing TDX Any task installed with the task name . . . CA. is treated as a catchall task. If MCR receives an unrecognized command, it searches for a task with that name and passes the command line to this task. To use TDX as the catchall task for your system, install it by using the following MCR command line: >INS $TDX/TASK=...CA. 4.15.1.2 TDX Commands and MCR Translations When installed, TDX checks the specified command against its list of commands. If the commands match, TDX translates the command specified into a valid MCR command. The TDX commands and their MCR translations are as follows: __________________________________________________________ TDX_Command____MCR_Translation________Function____________ ATS ACT /ALL Displays the names of all active tasks in the system. ATS ttnn: ACT /TERM=ttnn: Displays the names of all active tasks of the specified terminal. CHD SET /UIC Displays the current default User Identification Code (UIC) for terminal TI. Documentation Corrections 4-41  __________________________________________________________ TDX_Command____MCR_Translation________Function____________ CHD g m SET /UIC=[g,m] Changes the default User File Directory (UFD) to the UFD specified. CLR None Clears the issuing terminal's screen and sets cursor to 0,0. Returns an exit status of EX$SUC if the terminal is a cathode-ray tube (CRT) and EX$WAR if it is not a CRT. CRE file PIP file=TI: Creates a new file without invoking an editor. CVT val None Evaluates an arithmetic expression, converts that expression into different formats, and then displays all the formats on your terminal. CVT accepts input in octal (nnn or nn,nn) or decimal (nnn. or nn.,nn.) words or bytes; hexadecimal numbers ($nnnn), Radix-50 (%ccc), or ASCII ('c or "cc) characters; or arithmetic expressions using +, -, /, *, and < >. 4-42 Documentation Corrections  __________________________________________________________ TDX_Command____MCR_Translation________Function____________ DEL PIP file[, . . . ]/DE Deletes the file[, . . . ] specified file or files. DIR PIP [file[, . . . ]] Displays a directory [file[, . . .]] /LI listing at the terminal. DLG DEV /LOG Displays information about all logged-in terminals on the system. DLN NCP SHOW KNOWN NODES Displays all known DECnet nodes. FRE PIP /FR Displays the amount of space available on SY, the largest contiguous space on SY, the number of file headers available, and the number of file headers used. FRE ddu: PIP ddu:/FR Displays the same information as the FRE command for a specified device. PUR PIP file[, . . . ]/PU Deletes all but the file[, . . . ] latest version of a file. SHQ QUE/LI Displays information about all entries in all print queues. Documentation Corrections 4-43  __________________________________________________________ TDX_Command____MCR_Translation________Function____________ SYS SET /SYSUIC Displays the current system UIC. TDX None Displays the current version of TDX. TYP PIP TI:=file[, . . . ] Prints the specified file[, . . . ] file or files on ______________________________________your_terminal.______ 4.15.1.3 Modifying the TDX Source File You may want to add other commands to TDX by modifying the source file in [24,10]TDX.MAC. The routines for the commands are at the end of the source file and serve as examples for user-tailored routines. To reassemble the source file after making additions, use the TDXASM.CMD file located in directory [24,20]. To rebuild TDX, follow the procedure in the Phase III section of the RSX-11M System Generation and Installation Guide. TDX comes preassembled ([1,24]TDX.OBJ) if you do not wish to make any changes. The following table shows the location of files on multivolume kits: __________________________________________________________ Distribution Kit____________TDX.MAC_____TDX.OBJ_TDXBLD.BLD_____________ RL01/RL02 HLPDCL EXCPRV All_others_____RSXM67______RSXM67_________________________ If the command you enter does not match any of TDX's commands, TDX attempts to issue one of two MCR command options. In the following examples, xxx represents the first three characters of your command. The option that TDX uses depends on whether the logical device ZZ1 or ZZ2 exists on your system. You can assign one of these devices in your LOGIN.CMD file. Note that the presence of the ZZ1 assignment masks the presence of the ZZ2 assignment. If no assignment is made, TDX will not exercise either option. 4-44 Documentation Corrections  MCR>RUN $xxx/TASK=xxxTNN/CMD="params . . . " Installs, runs, and removes a task. In the example, "params . . . " represents the command line that you enter. Your command line cannot exceed 39 characters because TDX adds other characters to this line. If you want this option, place the following command line in your LOGIN.CMD file: ASN SY:=ZZ1: MCR>@SY:[loginuic]xxx.CMD or MCR>@LB:[libuic]xxx.CMD or MCR>@SY:[loginuic]CATCHALL.CMD or MCR>@LB:[libuic]CATCHALL.CMD For this option, TDX searches for one of the @[ . . . ]xxx.CMD indirect command files in the order indicated. As soon as TDX locates one of these files, the search stops. You can design the indirect command file to perform a variety of functions, such as installing tasks, providing HELP, or issuing error messages. To use this option, place the following command line in your LOGIN.CMD file: ASN SY:=ZZ2: RSX-11M Versions 4.6 and later contain a sample indirect command file, [24,24]CATCHALL.CMD. The ZZn option may be controlled for all users by placing the following command line in the system startup file: ASN SY:=ZZn:/GBL The variable n equals 1 or 2, depending upon which ZZn option you prefer. Documentation Corrections 4-45  If your command does not match a TDX command or if TDX cannot locate the necessary task, TDX issues the following message: MCR -- Task not in system 4.15.1.4 Installing Tasks Permanently You may want to install some tasks permanently rather than invoking TDX to install them as you need them. It is advisable to install the following tasks permanently: o Those requiring a larger increment than the default (see the INSTALL command in the RSX-11M/M-PLUS MCR Operations Manual) o Those that are used frequently In the following instances, TDX may affect the execution of the command file when noninstalled tasks are invoked: o The command line's length exceeds 39 characters. o TDX has no means of returning the exit status of called tasks to the Indirect Command Processor. This problem occurs in systems without parent/offspring tasking. In this case, Indirect proceeds immediately to the next command line without waiting for the called task to finish. This has the same effect as preceding the command line with the Indirect directive .XQT. 4.16 RSX-11M/M-PLUS Utilities Manual The following sections describe changes and corrections to the RSX-11M/M-PLUS Utilities Manual. 4.16.1 Backup and Restore Utility (BRU) The following documentation changes and corrections should be added to the manual in the designated sections for the Backup and Restore Utility (BRU). 4-46 Documentation Corrections  4.16.1.1 Selective Backups In Chapter 7, Section 7.1.2, add the following informa- tion: During a selective backup, UFDs that do not contain selected files are not backed up and cannot be re-created during a full restore operation. 4.16.1.2 Wildcards in Input Specifications In Chapter 7, Section 7.2.2.1, the documentation states that BRU treats all omitted file specification elements as if they were wildcards. This is incorrect. BRU does not treat omitted file names or file types as wildcards. This behavior is consistent with other RSX utilities. BRU differs from other utilities in the following ways: o If the version number is omitted, the system automat- ically inserts a wildcard in that field. For example, NAME.EXT is equivalent to NAME.EXT;*. o If only the UFD is specified, the entire file specification will be treated as a wildcard. For example, [UFD] is equivalent to [UFD]*.*;*. BRU has been enhanced to improve its method of verifying or comparing data backed up from a disk to an MU-type tape device, such as the TK50. MUDRV, the driver for the MU-type devices, has also been enhanced to direct the hardware to perform a compare-host function. BRU uses both of its buffers to hold data from the disk, and a buffer created by the compare-host function in the hardware holds the data from the tape. BRU can load data into one buffer while the other is in use, thus requiring fewer starts and stops of the tape. These changes increase the efficiency of compare and verify operations. The behavior is the default for MU-type devices only. You may override this default by using the new SINGLEBUFFER option added to the existing BRU qualifiers /COMPARE and /VERIFY, which ensures that compare and verify operations are done as they were previously. Documentation Corrections 4-47  4.16.1.3 Options Added to /COMPARE and /VERIFY Qualifiers In connection with BRU's enhancement for MU-type devices, two options have been added to BRU's existing /COMPARE and /VERIFY qualifiers. The format for the options is as follows: MCR Format BRU/COMPARE[:SINGLEBUFFER] BRU/COMPARE[:DOUBLEBUFFER] BRU/VERIFY[:SINGLEBUFFER] BRU/VERIFY[:DOUBLEBUFFER] DCL Format BACKUP/COMPARE[:SINGLE_BUFFER] BACKUP/COMPARE[:DOUBLE_BUFFER] BACKUP/VERIFY[:SINGLE_BUFFER] BACKUP/VERIFY[:DOUBLE_BUFFER] ________________________Note ________________________ The Digital Command Language (DCL) format includes an underscore character (_) in the SINGLEBUFFER and DOUBLEBUFFER option names, but the MCR format does not. The MCR style is used in this manual for general references to the options. _____________________________________________________ The DOUBLEBUFFER option used with the /COMPARE qualifier to the BRU command can be used only when the input device is a disk and the output device is a single MU- type magnetic tape. If you want to compare more than one MU-type magnetic tape, you must specify SINGLEBUFFER. If you want to verify one or more MU-type magnetic tapes, you can use the DOUBLEBUFFER option. If one magnetic tape is the MU-type and one is not, you must specify SINGLEBUFFER. Otherwise, BRU issues a fatal, device- conflict error message. 4-48 Documentation Corrections  The default for devices other than the MU-type is SINGLEBUFFER. For examples, see Section 4.16.1.4. The options are defined as follows: DOUBLEBUFFER Uses the compare-host function in comparing data transferred from a disk to a single MU-type magnetic tape. Also uses the compare-host function in verifying data transferred from a disk to one or more MU-type magnetic tapes. The MU tape drive must include the compare-host function. This is the default for MU-type devices. Use of this option increases the efficiency of a verify or compare operation. The error messages that BRU returns are less explicit, however. For more information on error messages, see Section 4.16.1.15. SINGLEBUFFER Overrides the default for MU-type devices and ensures that BRU uses only a single buffer to hold information from the disk when performing compare and verify operations. Use of this option ensures that the error messages BRU returns are more explicit but that the operation will usually require more time to complete. SINGLEBUFFER is the default for devices other than the MU-type. 4.16.1.4 BRU /COMPARE and /VERIFY Examples >BRU/VERIFY:SINGLEBUFFER DR5: MU2: This example uses the MCR command BRU to back up the data on a DR-type disk and perform a verify operation between the disk and the MU-type magnetic tape without the use of the compare-host function. The SINGLEBUFFER option overrides BRU's default behavior of using the compare-host function. > BRU/COMPARE:DOUBLEBUFFER DR7: MU1: Documentation Corrections 4-49  This example uses the MCR command BRU and the compare-host function to perform a compare operation between a DR-type disk and the MU-type magnetic tape device containing the backup set. The DOUBLEBUFFER option is the default for MU-type devices. Note that compare operations, unlike verify operations, are performed separately from backup operations; that is, no data is backed up in a compare operation. $BACKUP/COMPARE:DOUBLE_BUFFER DR7: MU1: This example uses the DCL command BACKUP and the compare- host function to perform a compare operation between a DR- type disk and the MU-type magnetic tape device containing the backup set. The DOUBLE_BUFFER option is the default for MU-type devices. $BRU/COMPARE:SINGLEBUFFER DR5: MU2: This example uses the MCR command BRU to perform a compare operation between a DR-type disk and an MU-type magnetic tape without the use of the compare-host function. The SINGLEBUFFER option overrides BRU's default behavior of using the compare-host function on MU-type devices. $BACKUP/COMPARE:SINGLE_BUFFER DR5: MU2: This example uses the DCL command BACKUP to perform a compare operation between a DR-type disk and an MU- type magnetic tape without the use of the compare-host function. The SINGLE_BUFFER option overrides the command's default behavior of using the compare-host function. 4.16.1.5 /ERROR_LIMIT Qualifier Prior to Version 4.5, the /ERROR_LIMIT:n qualifier terminated a restore operation after the specified number of errors was reached. The default number of errors was 25. The qualifier could not be used on backup operations. Since Version 4.6, the behavior with restore operations is unchanged. However, the qualifier can now be used with double-buffered compare and verify operations on data backed up from a disk to an MU-type device. The default number of errors is 25. 4-50 Documentation Corrections  4.16.1.6 /IDENTIFICATION Qualifier In Chapter 7, Section 7.4, on page 7-17 of the manual, please add the following BRU qualifier: /IDENTIFICATION Directs BRU to identify itself by displaying its version number. The qualifier may be specified on a command line alone or in combination with other qualifiers. 4.16.1.7 Removal of IMAGE Backup and Restore Code from BRU64K Please add the following section to Chapter 7, immediately before Section 7.5.1, of the manual: Because BRU64K (standalone BRU) had reached its maximum size, and no further corrections or enhancements could be made to it, the IMAGE backup and restore code was removed from the Backup and Restore Utility (BRU) contained in BRU64K. This means that the /IMAGE qualifier is no longer valid, and that BRU64K does not support backup operations with more than one output disk. However, BRU64K continues to support copy operations from a single disk to another single disk. If you need to use the /IMAGE qualifier, you can use online BRU or you can create a hardware-bootable standalone BRUSYS system on magnetic tape. For information on creating a hardware-bootable standalone BRUSYS system, see Section 4.16.1.8. 4.16.1.8 Locating and Booting Standalone BRUSYS Please add the following section to replace the first paragraph and list of Chapter 7, Section 7.5.1, on page 7-23 and 7-24 of the manual: The BRUSYS system image and symbol table are located in directory [1,51] in the distribution kit. This BRUSYS system requires 124K words of memory. You can bootstrap the standalone BRUSYS in one of two ways, as follows: o Software bootstrap standalone BRUSYS by using the privileged command BOOT as follows: Documentation Corrections 4-51  >INSTALL $BOO >BOOT [1,51]BRUSYS o Hardware bootstrap standalone BRUSYS by following the hardware bootstrap procedure for your processor. To create a hardware-bootable, standalone BRUSYS tape from the distribution kit, use the Virtual Monitor Console Routine (VMR) command SAVE to write the system image to tape in bootable format, as follows: !Comments not included in commands >ASSIGN Dx: = SY: !Dx is the device on which directory [1,51] is located >ASSIGN Dx: = LB: >ALLOCATE Mx: !Mx is the magnetic tape unit on which BRUSYS is to be !written >SET /UIC=[1,51] >RUN VMR ENTER FILENAME: BRUSYS VMR>SAVE Mx:BRUSYS VMR> The magnetic tape now contains a hardware-bootable image of the standalone BRUSYS system. (See the RSX-11M/M-PLUS System Management Guide for information on VMR.) 4.16.1.9 Skipping Over a Bootable System Image Please add the following section to Chapter 7, page 7-24, immediately before Section 7.6: BRU detects and skips over a bootable system image when appending to or restoring from a magnetic tape. This feature allows you to load a BRU backup set onto a magnetic tape volume that contains a bootable system image at the beginning. There is no need for a separate magnetic tape containing the bootable system image. In using this feature, you may notice a short delay, which is caused by rewinding the tape and skipping over the bootable system image. 4-52 Documentation Corrections  4.16.1.10 Using the MANUAL Option In Section 7.6.3, page 7-25, please replace the last two paragraphs with the following information: To get a list of the LBNs you have typed so far, type a slash (/) or press the Return key. When you have finished entering bad blocks, type two slashes (//). BRU will then allocate the bad blocks that you have entered to the BADBLK.SYS file and continue processing. 4.16.1.11 Tape Write Error Message In Section 7.10, page 7-54, the "User Action" is incorrectly documented for the following message: BRU-*WARNING*-TAPE WRITE ERROR I/O ERROR CODE number The correct user action should read as follows: User Action: Replace the tape on which the error occurred with another tape. BRU will rewrite this replacement tape from the same point that the previous "bad" tape began. This "bad" tape is not a part of the backup set and, consequently, should not be used in later verify or restore operations. If the error recurs on the replacement tape, the problem might be the tape drive. If the problem is the tape drive, clean the heads on the tape drive or terminate BRU and start over on another drive. 4.16.1.12 Executing Command Files You can execute a command file from BRU by typing an at sign (@) followed by the file specification for the command file. (This is not stated anywhere in the documentation.) Documentation Corrections 4-53  4.16.1.13 Changes in the CNF Table for Standalone BRU The control and status register (CSR) and vector information has changed for device types MM, MS, and MT. The following table should replace the table in Section 7.5 of the RSX-11M/M-PLUS Utilities Manual. __________________________________________________________ Device_______CSR_______Vector____CSR_Status_______________ DB 176700 254 Present DK 177404 220 Present DL 174400 160 Not Present DM 177440 210 Present DP 176714 300 Present DR 176300 150 Present DU 172150 154 Not Present MM FOR=0 172440 330 Present MS 172522 224 Not Present MT 160000 320 Not Present MU___________174500____260_______Present__________________ 4.16.1.14 /NOSUPERSEDE Qualifier In Section 7.4, page 7-19, please add the following information: When an output file and an input file have identical file specifications but different version numbers, the /NOSUPERSEDE qualifier causes the input file to be copied without deleting the output file. 4.16.1.15 BRU Error Messages Please add the following messages to Section 7.10 of the manual: BRU-BRU version xx.xx RSX-11M Explanation: Identifies the version of BRU being used. User Action: No user action is required. This is an informational message. 4-54 Documentation Corrections  BRU-*FATAL* -Device conflict Explanation: You specified a /COMPARE:DOUBLEBUFFER or a /VERIFY:DOUBLEBUFFER option and your output device is not of the MU-type. When verifying or comparing mixed types of output devices (MU and non-MU), SINGLEBUFFER must be specified as an option. User Action: If you wish to mix types of output magnetic tapes (non-MU with MU), you must specify /COMPARE:SINGLEBUFFER or /VERIFY:SINGLEBUFFER. BRU-*WARNING*-Potential data record verify error File ID mmmmmm,nnnnnn LBN nnnnn Explanation: A data block on the input device did not match a data block on the output device. User Action: To obtain a list of actual errors listing the file IDs and LBNs, perform a compare operation using /COMPARE:SINGLEBUFFER. If you prefer, you can repeat the backup operation. If it fails again, repeat the backup operation with a different disk or tape. BRU-*WARNING*-Potential file header record verify error [mmm,nnn] filename.filetype;version Explanation: A header record on the input device did not match a header record on the output device. User Action: To obtain a list of actual errors list- ing the filenames, perform a compare operation using /COMPARE:SINGLEBUFFER. If you prefer, you can repeat the backup operation. If it fails again, repeat the backup operation with a different disk or tape. BRU-*WARNING*-Potential file ID area or data record verify error Documentation Corrections 4-55  File ID mmmmmm,nnnnnn LBN nnnnn Explanation: An error occurred in the file ID area. Potential errors are listed under the message. BRU cannot verify whether errors occurred in the data area of the record. Therefore, BRU lists all file IDs and LBNs in that block. User Action: To obtain a list of actual errors, perform a compare operation using /COMPARE:SINGLEBUFFER. If you prefer, you can repeat the backup operation. If it fails again, repeat the backup operation with a different disk or tape. BRU-*FATAL*-Continuation volumes cannot be double buffered Explanation: BRU does not support a double-buffered compare operation on a backup set that spans more than one tape. User Action: If you must compare a backup set that spans more than one tape, specify /COMPARE:SINGLEBUFFER in the BRU command line. BRU-*WARNING*-Double buffered compare or verify not supported Explanation: BRU cannot perform a double-buffered compare or verify operation, because the tape driver does not support double-buffered compare or verify operations. User Action: No user action is required. BRU continues the verify or compare operation using a single buffer. 4.16.2 Disk Save and Compress Utility Version 4.6 of RSX-11M and RSX-11S was the last release to include the Disk Save and Compress utility on the kit. This utility was used to save data on media and then restore the data. The Backup and Restore Utility (BRU) provides a similar function. Media saved with the DSC utility should be restored with DSC and then saved with BRU. 4.16.3 File Dump Utility (DMP) The following documentation changes should be added to the RSX-11M/M-PLUS Utilities Manual for the File Dump Utility (DMP). 4-56 Documentation Corrections  4.16.3.1 New /LIM Switch In Table 11-1, page 11-6, the following new switch should be added to the table: __________________________________________________________ Switch____Description_____________________________________ /LIM:n:m Specifies the range of bytes n through m of each record or block to be dumped. The /OCT switch is still the default if no format switches are __________specified.______________________________________ 4.16.3.2 Correction to /HF Switch Description In Section 11.4, page 11-6, replace the last sentence before the example with the following: Other blocks are output as a data dump in the format selected by /AS and /BY, in octal words by default. 4.16.4 File Transfer Program (FLX) The following documentation change should be added to the RSX-11M/M-PLUS Utilities Manual for the File Transfer Program (FLX): o At the end of Section 4.1, page 4-3, add the following: If an error occurs during a copy operation to an RT- 11 device, the partial file is not substituted for an existing file on the output disk. The partial file is no longer closed as a permanent entry, and the definition and contents of the existing file remain intact. o After the table at the top of page 4-2 add the following: When you use the File Transfer Utility Program (FLX), the following devices do not support DOS-11 format: o RC25 o RA60, RA80, and RA81 o RD32, RD51, RD52, RD53, and RD54 o RX33, RX50 Documentation Corrections 4-57  o In Table 4-1, page 4-5, the table entitled "FLX Transfer Mode Switches" should include the following additional information about the use of octal and decimal numbers with the switches listed: The following switches accept octal numbers by default: o /FA:n o /FB:n o /IM:n o /BL:n o /BS:n o /NU:n o /ZE:n If you want to assign decimal numbers to these switches, you must follow the value of n with a period (.). For example, to assign the decimal value 18 to the /IM:n switch, you type the following: /IM:18. The /DNS:n switch accepts decimal numbers by default. Therefore, you do not need to follow the value of the /DNS:n switch with a period (.) if the value is decimal. o In Section 4.2.2, on page 4-6, the file type CDA should be added to the list of default file types for the Image Mode switch. o In Table 4-2, on page 4-8, the last sentence of the first paragraph should read: The /ZE switch does not allow a file specification. o In Section 4.4.2, page 4-12, the file specification in the example at the top of the page, as well as the file specification in the following line, should be SYS1.MAC. o In Section 4.4.3, page 4-13, the last line in the paragraph following the example should read: 4-58 Documentation Corrections  This results in a total of 324(10) directory entries, each of which uses 9 words. o In Section 4.8, page 4-21, the following error message should be added: FLX-Device size exceeds 65K blocks Explanation: The DU device selected as an RT-11 device is not an RC25, RCF25, RD51, RD52, RD53, RX33, or RX50. Devices greater than 65K blocks cannot be supported with FLX. User Action: Reenter the command line, specifying a valid RT-11 device. 4.16.5 Disk Volume Formatter (FMT) Please make the following correction to the RSX-11M/M-PLUS Utilities Manual for the Disk Volume Formatter (FMT): After Table 5-2 on page 5-5 add the following: FMT formats RX33 diskettes. You use the /DENSITY, /VERIFY, and /NOVERIFY switches to format an RX33. The RX33 must be mounted foreign before you can use FMT. An RX33 diskette cannot be formatted to simulate an RX50 diskette, and an RX50 cannot be formatted to simulate an RX33. This is due to a difference in the magnetic properties on RX50 diskettes. Consequently, you may not be able to perform read or write operations on the diskette. FMT Unsupported Devices None of the DU-type devices except the RX33 are supported by FMT. In Section 5.4, page 5-9, add DL to the list of devices supported by the /WLT and /VE switches. 4.16.6 Librarian Utility Program (LBR) The following sections describe documentation changes to be added to Chapter 10 of the RSX-11M/M-PLUS Utilities Manual for the Librarian Utility Program (LBR). Documentation Corrections 4-59  4.16.6.1 User File Attributes In Figure 10-7, page 10-7, bytes 40(8) to the end of the header are referred to as "user file attributes." (The documentation does not state what these attributes are or what their relationship is with the File Descriptor Block (FDB) of the original file from which the module was created.) Please insert the following paragraph: The FDB of the original file from which the module was created has five sections of information, the first of which is the "user file attributes." These attributes are as follows: o Record type o Record attribute o Record size o Highest virtual block o End-of-file block number o Optional information When you create a file and insert it into a universal library, LBR copies the input file attributes to the module header. You can modify some of these attributes by using the /MH switch to modify the header. For more information, please see Sections 10.5.9 and 10.5.11 of the RSX-11M/M-PLUS Utilities Manual, and Section 1.7.1.2 (page 1-10) and Appendix A of the RSX-11M/M-PLUS and Micro/RSX I/O Operations Reference Manual. 4.16.6.2 Create Switch Error In Section 10.5.2, page 10-12, the Create switch (/CR) format is incorrectly documented. The equal sign (=) should be replaced with a colon (:). The correct format should read as follows: outfile/CR:size:ept:mnt:libtype:infiletype 4-60 Documentation Corrections  4.16.6.3 The /IN Switch for Macro Libraries In Section 10.5.8, page 10-19, delete the following sentence, which is no longer true: LBR only recognizes uppercase characters in macro directives. 4.16.7 Object Module Patch Utility (PAT) Please make the following addition to the RSX-11M/M-PLUS Utilities Manual for the Object Module Patch Utility (PAT): In Section 14.2.4, page 14-7, the following new error message should be added to the section entitled "PAT Messages": PAT-Unable to open file filename Explanation: There is insufficient work space in the internal File Storage Region (FSR) of the PAT utility. User Action: Install or run the PAT utility with an increment. 4.16.8 Peripheral Interchange Program (PIP) The following sections describe documentation errors that should be corrected in the RSX-11M/M-PLUS Utilities Manual for the Peripheral Interchange Program (PIP). 4.16.8.1 The /DD Switch Format Error In Section 3.2.2.4, page 3-17, the /DD switch format is incorrectly documented in the three examples. There should be an ampersand (&) before /LI when used with /DD. The correct examples are shown next. PIP>/DD:01-JAN-93:01-FEB-93&/LI PIP>/DD:*:1-JAN-93&/LI PIP>/DD:1-JAN-93:*&/LI Documentation Corrections 4-61  4.16.8.2 The /TD Switch Format Error In Section 3.2.2.25, page 3-40, the /TD switch format is incorrectly documented. There should be an ampersand (&) before /LI when used with /TD. The correct format is as follows: PIP>/TD&/LI 4.16.9 Source Language Input Program (SLP) The following sections describe documentation errors and omissions that should be corrected in the RSX-11M/M-PLUS Utilities Manual for the Source Language Input Program (SLP). 4.16.9.1 Error Message Format In Section 13.5.2, page 13-20, the example of the error message format is incorrect. The correct format example is as follows: SLP-*FATAL*-ILLEGAL SWITCH OR FILESPEC SHIRLEY.MAC;2/CF 4.16.9.2 Maximum Number of Characters in File Names In Section 13.5.2, page 13-21, under the error message "Illegal file name," the explanation indicates that file names can be a maximum of 30(8) characters long. This is incorrect. SLP file names can be a maximum of 19(10) characters long. 4.16.9.3 Illegal Switch Error Message In Section 13.5.2, page 13-22, the "Illegal Switch" error message is incorrect. It should read as follows: SLP-*FATAL*-Illegal switch or filespec command line segment Explanation: One of the following conditions results in this error message: o The switch was not a valid SLP switch. o A valid switch was used in an invalid manner. 4-62 Documentation Corrections  o A file specification could not be parsed. User Action: Reenter the command line, specifying the valid switch or correct file specification. 4.17 RSX-11M/M-PLUS and Micro/RSX Crash Dump Analyzer Reference Manual Chapter 2 of the RSX-11M/M-PLUS and Micro/RSX Crash Dump Analyzer Reference Manual includes a description of the new DCL ANALYZE/CRASH_DUMP command. If your terminal supports the Digital Command Language (DCL) command line interpreter, you can use the ANALYZE/CRASH_DUMP command to run CDA. Command qualifiers let you choose which report listings you want CDA to generate. You can also use qualifiers to specify the format of the CDA report listings. 4.18 RSX-11M/M-PLUS and Micro/RSX Debugging Reference Manual The IAS/RSX-11 ODT Reference Manual has been renamed to RSX-11M/M-PLUS and Micro/RSX Debugging Reference Manual. Information specific to IAS has been deleted. This manual also includes information about XDT. 4.19 RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual The RRST$ and TFEA$ directives are incorrectly documented in the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual for RSX-11M Version 4.2. These two directives apply to RSX-11M-PLUS systems only. Please make the following corrections to the RSX-11M /M-PLUS and Micro/RSX Executive Reference Manual: o In Chapter 3, Section 3.7.1, make the following correction: If the length-to-map field is not specified, the window length is not changed. o In Chapter 3, Section 3.7.2, add the following statement: Documentation Corrections 4-63  The MACRO-11 interface to the fast-mapping facility uses general purpose register 3 (R3) as a "scratch" buffer. Consequently, all data stored by the fast- mapping facility is destroyed. o In Chapter 3, Section 3.7.4, add the following status messages: _______________________________________________________ Status Code________Meaning____________________________________ IE.ITS Inconsistent task state SU$SUC______Success____________________________________ 4.20 RSX-11M/M-PLUS and Micro/RSX I/O Operations Reference Manual Please add the following information to the RSX-11M/M-PLUS and Micro/RSX I/O Operations Reference Manual: o In Chapter 4, Section 4.2.1, please make the following correction: R1 Contains the size (in bytes) of the default directory string in program section $$FSR2. If no default directory string descriptor words have been written, R1 equals 0. R2 Contains the address of the default directory string in program section $$FSR2. o Appendix C contains a summary of the I/O-related system directives in alphabetical order. o Appendix I includes a new QIOMAC.MAC module descrip- tion. 4.21 RSX-11M/M-PLUS and Micro/RSX Task Builder Manual This section describes documentation changes that have not been incorporated into the manual. 4-64 Documentation Corrections  4.21.1 Double Brackets The occurrence of double brackets in the manual is a typographical error. These double brackets occur in Chapters 1, 5, 6, and 8. The brackets currently appear, as follows: TKB>DB2:[[300,53]]=DB1:[[5,7]]OBJECT.OBJ The correct format is: TKB>DB2:[300,53]=DB1:[5,7]OBJECT.OBJ 4.21.2 Manual References References to the Executive Reference Manual are to the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual. These references occur in Chapters 2, 3, 4, 5, 7, 10, 11, and Appendix H. 4.21.3 Reference to "/" for the /MP Switch In Section 1.3.1, page 1-9, the reference to the "/" character is incorrect. You should refer to the discussion of the /MP switch in Chapter 10 instead. 4.21.4 /SHAREABLE:LIBRARY Switch Description Section 5.1.1 incorrectly documents the effect of using the /SHAREABLE:LIBRARY switch. If you use this switch when building a library, the region program section name for the library is the same as that of the library root. 4.21.5 Incorrect Device Specification In Section 5.2.3.5, the specification LB; is incorrect. It should be replaced with LB:. 4.21.6 Errors in Overlay Capability In Section 3.6.1, "Creating a .ROOT Statement by Using a Virtual Address Space Allocation Diagram," there are errors in steps 10 to 14. The steps should be as follows: 10. Step 3A: Write .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0- (B1)) 11. Step 3B: Write .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0- (B1,B2)) Documentation Corrections 4-65  12. Step 3C: Write .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0- (B1,B2)) 13. Step 3B: Write .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0- (B1,B2),C) 14. Step 3C: Write .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0- (B1,B2),C) In Section 3.6.2, entitled "Creating a .FCTR Statement by Using a Virtual Address Space Allocation Diagram," a factual error occurs in the .ROOT statement. The statement should read as follows: .ROOT CNTRL-(A0-(A1,A2-(A21,A22)),B0-(B1,B2),C) The root statement with AFCTR included (the last .ROOT statement in Section 3.6.2) should read as follows: .ROOT CNTRL-(AFCTR,B0-(B1,B2),C) Section 3.6.3, entitled "Creating an ODL Statement for a Co-Tree by Using a Virtual Address Space Diagram," contains two .ROOT statements. The first, without the co-tree, should read as follows: .ROOT CNTRL-(AFCTR,B0-(B1,B2),C) The second .ROOT statement in Section 3.6.3 should read as follows: .ROOT CNTRL-(AFCTR,B0-(B1,B2),C),CNTRL2-(CNTRLX,CNTRLY) 4.21.7 TKB Combinations of the /-PI and /LI Switches In Section 10.25, page 10-31, the manual incorrectly documents the effect of using the /LI switch in the Task Builder (TKB). If you use this switch when building a library, the region program section name for the library is the same as that of the library root. The name of the library is not .ABS as documented. 4.21.8 References to the /-CO and /-LI Switches In Section 5.1.1, pages 5-4 and 5-5, references are made to the /-CO and /-LI switches. These are implied defaults for not using the /CO and /LI switches, and they are not actual switch designations. 4-66 Documentation Corrections  4.21.9 Offsets In Appendix B, Figure B-5, the following offset changes should be added: o 772 contains the Second Task Flag Word o 774 contains the Label Block Revision Number o 776 contains a zero (always) for VAX-11 RSX compatibil- ity (the last word in Label Block 0) 4.21.10 New TKB Error Message The Task Builder (TKB) has the following new error message: Cluster library element element-name is not resident overlaid. Explanation: The listed cluster element has been built without memory-resident overlays. This kind of element cannot be used as a cluster library element. Cluster libraries 2 through 6 must be memory-resident and overlaid. The following sections contain restrictions and supplemen- tary information on the Task Builder. 4.21.11 TKB Option - RNDSEG Please add the following RNDSEG option description to a location immediately preceding Section 12.1.26 in the manual: The TKB option RNDSEG is a storage-sharing option that causes TKB to round the size of a named segment up to the nearest Active Page Register (APR) boundary while building a resident library. When you install a resident library, INSTALL makes an entry for the resident library in the Common Block Directory (CBD). The system loads the resident library when a task that uses it runs. The length parameter for the common block, as described in the label block for the task image, must match the corresponding parameter in the system CBD. If the task's label block data does not match the system data for that task, the task cannot be installed. Documentation Corrections 4-67  If you do not use RNDSEG and the common block length for the newly rebuilt library is not the same as the common block length previously recorded in the CBD, you have to relink the task with the new library before you can install it. Syntax RNDSEG=seg-name Parameter seg-name Specifies the 1- to 6-character Radix-50 name of the segment. Default None Notes o The RNDSEG option operates only during a library build. Attempting to use the option while building any other form of task will result in the following diagnostic error message: TKB -- *DIAG* - Library build not requested - ignoring option RNDSEG=SEG1 o If you attempt to specify a nonexistent segment name, the following diagnostic error will be generated and the build will continue: TKB -- *DIAG* - Segment not found to address round RNDSEG=NOSEG 4.21.12 Map Problem for Non-PIC Shared Region Please add the following to Section 11.28, page 11-49 as a restriction: A non-position-independent code (PIC) shared region's base address is displayed in the map as zero. The base address is not zero, but it has a true base address. This problem is a map-generation problem of TKB. 4-68 Documentation Corrections  4.21.13 Cluster Libraries Please add the following note after the fifth paragraph in Section 12.1.5, Page 12-9, of the manual: ________________________Note ________________________ Clustering read-only and read-write libraries is not supported on RSX-11M Version 4.6 or later software. _____________________________________________________ 4.21.14 Changing Values in an Installed Common Please add the following section to Section 12.1.7 at the end of the note at the bottom of page 12-12 in the manual: Changes made in the common are made only in the memory image of the common. If the common is subsequently removed, reinstalling the common presents a fresh image in memory and the previously changed values are no longer present. 4.21.15 Using the /SS Switch with the RSX11M.STB File Please add the following section to Section 10.35, Page 10-48, in the manual at the end of the text in the heading Effect: When you use the RSX11M.STB file as an input file to TKB, the /SS switch should always be appended to the file specification. This allows only those symbols referenced to be included in the STB file. Otherwise, the STB file contains so many symbols that, potentially, TKB could exhaust its virtual memory tables. You must include the required library modules on the command line before you specify the Executive symbol definition file RSX11M.STB. Documentation Corrections 4-69  4.21.16 Slow Task Builder (STK) Restriction for Layered Products Please add the following section to page F-11 in the manual: Some RSX layered products require the Slow Task Builder (STK) for installation. STK is not supplied with the RSX- 11M operating system as a separate task image; STK and the Task Builder (TKB) are included together in one task image on the distribution kit. Please consult the release notes or installation guide for your layered product to determine if you need STK to install your layered product. To create a default STK for RSX-11M, you must copy the MAKESTK.CMD file to the LB:[1,2] directory. MAKESTK.CMD is located in the [1,20] directory on the following disk volumes: Tape kit RSXM67 RK07 kits RSXM67 RL01 kit RLUTIL RL02 kit PRVBLD Before you invoke the command procedure MAKESTK.CMD, you must boot your new system. Ensure that there is enough space on the system, and then invoke SYSGEN3.CMD to build ZAP. After SYSGEN3.CMD has completed, you can invoke MAKESTK.CMD. STK Supplementary Information The Slow Task Builder (STK) and TKB are included together in one task image in the distribution kit. Use the /SB switch or the /SLOW qualifier to select STK. Use the command line format shown next for the MCR switch /SB. file.TSK/SB,,=file.OBJ 4-70 Documentation Corrections  Default /-SB Use the command line format shown next for the DCL qualifier /SLOW. LINK/TAS/SLOW/MAP/SYM inputfile Default /NOSLOW 4.21.17 The /CL Switch and the /CODE:CLI Qualifier In the manual locations listed next, add the text following the list. o Immediately after Section 11.6, page 11-14 o Immediately after Section 10.4, page 10-7 The MCR switch /CL and DCL qualifier /CODE:CLI indicate to TKB that the task is a command line interpreter (CLI). Use the /CL switch when you build the DCL task or any other CLI task. ________________________Note ________________________ The Fast Task Builder (FTB) supports neither the /CL switch nor the /CODE:CLI qualifier. _____________________________________________________ Use the command line format shown next for the MCR switch /CL. file.TSK/CL,,=file.OBJ Default /-CL Use the command line format shown next for the DCL qualifier /CODE:CLI. LINK/TAS/CODE:CLI/MAP/SYM inputfile Default /NOCODE:CLI. Documentation Corrections 4-71  4.21.18 The /FM Switch and the /FAST_MAP Qualifier Please add the following section to the manual in the following locations: o Immediately after Section 10.12, Page 10-17 o Immediately after Section 11.20, Page 11-32 The MCR switch /FM and the DCL qualifier /FAST_MAP inform TKB that space must be allocated in memory between the task and the external header for use by the fast- mapping feature. The /FM switch corresponds to the INSTALL processor switch /FMAP=YES. ________________________Note ________________________ The /FM switch and the /FAST_MAP qualifier can only be executed on an RSX-11M-PLUS system. Therefore, you can only use the fast-mapping feature if you are transporting tasks between RSX-11M and RSX-11M-PLUS systems. Also, FTB does not support the /FM switch or the /FAST_MAP qualifier. _____________________________________________________ Use the command line format shown next for the MCR switch /FM. file.TSK/FM,,=file.OBJ Default /-FM Use the command line format shown next for the DCL qualifier /CODE:FAST_MAP. LINK/TAS/CODE:FAST_MAP/MAP/SYM inputfile Default /NOCODE:FAST_MAP 4-72 Documentation Corrections  4.22 RSX-11S System Generation and Installation Guide Section 2.5 of this manual, entitled "The SETTIM Callable Subroutine," contains incorrect information on the FORTRAN callable routine SETTIM. Please substitute the following information for Section 2.5: SETTIM is a subroutine that can be called with FORTRAN to set the system's internal time. It is supplied to allow a running program to set the time in a configuration that does not include either a console terminal or basic MCR. A new version of the FORTRAN callable subroutine SETTIM is available and is located in LB:[1,1]SYSLIB.OLB. Its module name is .STTIM. The interface to this routine is documented in the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual under the STIM$ directive. The format of the FORTRAN call is shown next. CALL SETTIM (ibufn [,ibufp [,ids]]) Parameters ibufn Specifies an 8-word integer array; new time-specification buffer. ibufp Specifies an optional 8-word integer array; returns the previous time. ids Specifies an optional directive status. Note that all the boundary checking is done within the directive itself and the status codes (documented under STIM$ in the RSX-11M/M-PLUS and Micro/RSX Executive Reference Manual) are returned in the Directive Status Word (DSW) if specified. Please make the following additional corrections to the manual: o In Section 5.1.1, the documentation omits the commands for manually copying 11SGEN2.CMD from the distribution media to the target disk. Documentation Corrections 4-73  The command to copy 11SGEN2.CMD from a distribution disk is as follows: > PIP ddnn:[200,200]=ddnn:[2,20]11SGEN2.CMD The command to copy 11SGEN2.CMD from a distribution tape is as follows: > FLX ddnn:[200,200]=mmnn:[2,20]11SGEN2.CMD o In Chapter 6, Section 6.1.1, please make the following corrections: - The example that describes how to use the Peripheral Interchange Program (PIP) utility to copy files is incorrect. It should be as follows: > PIP ddnn:[2,200]=ddnn[2,20]11SGEN.CMD - If you are using a blank target disk with a tape kit, you need to perform the following steps before using the File Transfer Utility Program (FLX) to copy files: 1. The target disk must be initialized, as follows: ALL ddnn: MOU/FOR ddnn: INI ddnn:11SKIT DMO ddnn:/LOCK=V 2. The tape containing the new kit must be mounted foreign, as follows: MOU/FOR mmnn: 3. Before you copy the file 11SGEN.CMD, the directory [2,200] must be created on the target disk, as follows: MOU ddnn:11SKIT SET /UIC=[1,1] UFD ddnn:[2,200] SET /UIC=[2,200] 4-74 Documentation Corrections  A ________________________________________________________________ Reporting Problems This appendix describes the procedure for submitting a Software Performance Report (SPR). An SPR allows you to report any problems with or questions about your system directly to Digital. An SPR can be used for: o Software errors o Documentation errors (when the Reader's Comments form is not appropriate) o Follow-up on a previous SPR o Questions o Suggestions An SPR cannot be used for: o Software license and price policies o Obvious hardware problems o Logistical or clerical problems with kits, such as blank media, or failure to receive the Software Dispatch o Problems with user-written software In general, when you complete an SPR, use the following guidelines: o Describe only one problem per form. This will facilitate a more rapid response because it allows the person answering the problem to concentrate more fully on that particular problem. One problem per form also helps simplify record-keeping. Reporting Problems A-1  o Define as accurately as possible the state of the system and circumstances when the problem occurred. o Illustrate the problem with specific examples. o If you report a documentation error, specify the title of the manual, and include the section and page number where the error occurred. Include a table or figure number if appropriate. SPRs are assigned a priority of 1 to 5. An SPR that is assigned a priority of 1 receives the highest priority. Priorities are described as follows: 1. Most production work cannot be run. - Major system functions are unusable. - You cannot boot the system. - Necessary peripherals cannot be used. 2. Some production work cannot be run. - Certain functions are unusable. - System performance has declined. - Installation does not have excess capacity. 3. All production work can be run with some user impact. - Significant manual intervention is required. - System performance has declined. - Installation has excess capacity. 4. All production work can be run with no significant impact on user. - Problem can be patched or easily bypassed. 5. No system modifications are needed to return to normal production. - Suggestions are supplied. - Consultations are requested. - Errors in documentation are noted. A-2 Reporting Problems  You can submit the following categories of SPRs: o Problem/Error SPR This type of SPR contains a software problem. It is assigned a priority of 1 to 5. You receive an answer to this report. o Suggested Enhancement This type of SPR contains a suggestion. It is assigned a priority of 5. You do not receive an answer to this report. o Other This type of SPR contains a question or suggestion. It is assigned a priority of 5. You may or may not receive an answer to this report. Please supply the following information (in machine- readable form where applicable) when you report a problem: o CRASH-Supply a copy of the Executive task-build map, output from the console terminal, the SYSGEN saved- answer file, the Executive STB file, and the crash dump. If the crash is reproducible, accurately describe the details and supply a hard copy or user source code when necessary. o DRIVERS-Supply controller/device information, software options, error log output, a copy of device registers, and a sample program. o UTILITIES-Supply a copy of your terminal output, showing setup commands, before and after effects, and relevant file information. o TASK BUILDER-Supply a copy of your terminal output command files, the task map, and a dump of the first few blocks of the task image. o FILE SYSTEM-For a corrupted volume, supply output from the File Structure Verification Utility (VFY) and dump of the volume. For improper results, supply the error code, a file header dump, and a sample program. Reporting Problems A-3  o ERROR LOG REPORT GENERATOR (RPT)-Supply a copy of the report file generated by RPT, either on a hardcopy listing or on machine-readable media. If a failure occurs when you are running privileged, add- on software (for example, the DECnet package), try to reproduce the failure without the additional software. Then, when you write the SPR, indicate how the system operated with and without the add-on software. The SPR process is sometimes lengthy. Therefore, if you have a critical problem, contact your local Digital office. In the meantime, read the Software Dispatch for news on the operating system, which includes changes and problems other people have found and solved. A-4 Reporting Problems  ________________________________________________________________ Index A Bad block replacement ___________________________ control task ANALYZE (DCL) command See RCT /CRASH_DUMP, 4-63 Baseline system /ERROR_LOG, 4-10 to 4-11, copying, 1-15 4-40 Batch and Queue Operations ASN (MCR) command Manual /TERM, 4-25 corrections, 4-9 Asynchronous buffered I/O, DELETE, 4-9 1-44 to 1-46 log files, 4-9 /NOTRANSFER, 4-9 B__________________________ SHOW QUEUE/ALL, 4-9 BACKUP (DCL) command BROADCAST utility /CREATED:BEFORE, 4-9 year 2000 support, 1-8, /MODIFIED:BEFORE, 4-9 2-7 /SAVE_SET qualifier BRU, 4-46 to 4-56 support for underscore corrections, 1-10 ( -) character, on files with no 4-10 revision date, 1-10 /SAVE_SET:name, 4-10 tape errors, 1-10 /VERIFY[:DOUBLE_BUFFER], to error messages, 4-10 1-10 /VERIFY[:SINGLE_BUFFER], to using the /REVISED 4-10 qualifier, 1-10 year 2000 support, 1-8 detecting bootable system Backup and Restore Utility image, 4-52 See BRU examples, 4-49 BAD (MCR) command executing command files, /OVERRIDE, 4-24 4-53 identification message, 4-54 large disk support, 1-26 messages, 4-54 to 4-56 Index-1  BRU messages (cont'd) C__________________________ error, 1-10, 4-53 Catchall task identification, 4-54 See TDX qualifiers CFT command /COMPARE, 4-48 format, 1-30 /COMPARE[: Copying SINGLEBUFFER], 4-48 distribution tape, 1-18 to 4-50 tape kit, 1-3 /COMPARE[:DOUBLEBUFFER] tape to disk, 1-22 , 4-48 to 4-50 Crash driver /ERROR_LIMIT:n, 4-50 modification, 1-47 /FOREIGN Crash Dump Analyzer copying with a Reference Manual RSX-11M-PLUS or corrections, 4-63 VAX-11 RSX host, CXA16 multiplexer support, 1-22 1-25 /IDENTIFICATION, 4-51 CXB16 multiplexer support, /NOSUPERSEDE, 4-54 1-25 /REVISED, 1-10 CXF32/DHF11 Module Support, /VERIFY, 4-48 1-25 replacement for DSC, 1-51 CXY08 multiplexer support, replacement for DSC 1-25 utility, 1-2, 4-56 restrictions, 1-13, 2-8 D__________________________ /IMAGE qualifier, 4-51 Data late error correction, /NEW_VERSION qualifier 1-12, 2-8 , 1-13, 2-9 Data Terminal Emulator use of wildcards, 1-13, 2-8 See DTE wildcard support, 4-47 DATATRIEVE-11/RSX with a TK50 tape, 1-40 correction file year 2000 support, 1-8 for RSX-11M, 1-4 BRU64K, 1-2, 1-3 DB-based system boot, 1-29 device support, 1-27 DCL, 4-9, 4-48 removal of IMAGE backup commands and restore code, 4-51 ANALYZE with a TK50 tape, 1-42 /CRASH_DUMP, 4-63 BRUSYS, 1-2 /ERROR_LOG, 4-10 to standalone, 4-51 4-11, 4-40 system requirements, 1-21 BACKUP with a TK50 tape, 1-42 /COMPARE[:DOUBLE_ BUFFER], 4-10 Index-2  DCL DCL commands commands BACKUP (cont'd) SET (cont'd) /COMPARE[:SINGLE_ TERMINAL/VTxxx, BUFFER], 4-10 1-24 /CREATED:BEFORE, TIME, 1-8, 2-7 4-9 SHOW QUEUE /MODIFIED:BEFORE, /ALL qualifier, 4-9 4-9 SORT/INDEXED_ /SAVE_SET:name, SEQUENTIAL, 1-12 4-10 DCL manual support for corrections, 4-9 underscore ( -) BACKUP /CREATED:BEFORE character, 4-10 , 4-9 year 2000 support, BACKUP /MODIFIED:BEFORE 1-8 , 4-9 DELETE, 4-9 DCX KMV11-A Development DIFFERENCES, 1-12 Tools DIRECTORY correction files /SINCE, 1-8 for RSX-11M, 1-4 DISMOUNT for RSX-11S, 2-3 /[NO]UNLOAD, 4-13 Debugging Reference Manual INITIALIZE corrections, 4-63 /HEADERS:n, 4-11 to DECnet-11M correction file 4-12 for RSX-11M, 1-5 /PROCESSOR DECnet-11S correction file /NOWARNINGS, for RSX-11S, 2-2 4-36 DELETE (DCL) command, 4-9 MOUNT Device /NOLABEL KDJ11-E processor, 1-2, restriction, 1-5, 1-6, 2-2, 2-4 1-48 list of supported devices PRINT , 1-6, 2-4 /[NO]TRANSFER RA71 disk drive, 1-2, qualifier, 4-9 1-5, 1-6, 2-3, 2-4 SET RA72 disk drive, 1-2, HOST, 1-27 1-5, 1-6, 2-3, 2-4 HOST/DTE, 4-37 to RA92 disk drive, 1-2, 4-39 1-5, 1-6, 2-3, 2-4 restriction on RQZX1 SCSI adapter, 1-2 VT300-series RQZX1 SCSI adaptor, 2-2 terminals, 1-24 SCSI, 1-5, 2-3 RQZX1 adaptor, 1-5, 2-3 Index-3  Device Disk support SCSI (cont'd) large, 1-26 RZ23L, 1-5, 2-3 Disk Volume Formatter RZ24L, 1-5, 2-4 See FMT TZ30, 1-5, 2-4 DISMOUNT (DCL) command support /[NO]UNLOAD, 4-13 supplementary, 2-2 Distribution kit TK25 cartridge tape, 4-13 media, 1-2, 2-2 Device driver DJ11 support, 1-28 remote terminal DJ11 terminal interface, restriction, 1-36 1-28 TK50 tape subsystem, 1-36 DM-based system boot, 1-29 to 1-44 DMO (MCR) command Device support with a TK50 tape, 1-39 DU-type device, 1-27 DMP utility, 4-56 for LA75, 4-16 DR-based system boot, 1-29 for T.V2xx, 4-16 DSA, 1-27 MU-type device, 1-15, DSC, 1-2, 1-51, 4-56 1-27 DTE, 4-37 RA70, 1-24 command RA90, 1-24 format, 4-37 see the Software Product /ID option, 4-39 Description (SPD), parameters, 4-37 1-24 error messages, 4-39 Dial command string DTE (MCR) command, 4-37 to for modem, 4-38 4-39 /DIAL option DU driver enhancement, SET HOST/DTE command, 1-36 4-38 DIFFERENCES (DCL) command, E__________________________ 1-12 Echo loops Digital Command Language intersystem, 4-38 See DCL ELI task Digital Storage restrictions Architecture /NOLIM switch, 1-14 See DSA /SH switch, 1-14 DIRECTORY/SINCE (DCL) Error Logging command error messages, 4-14 year 2000 support, 1-8 format of packets, 4-15 to 4-16 Disk Save and Compress restrictions, 1-13 utility creating error logging See DSC packets, 1-50 ELI Index-4  Error Logging Executive restrictions code changes, 1-31 to ELI (cont'd) 1-32 /NOLIM switch, 1-14 data structure changes, /SH switch, 1-14 1-32 /HISTORY qualifier, I/O data structure 1-50, 4-13 changes, 1-33 to history summaries, Executive Reference Manual 1-13, 4-13 corrections, 4-63 support MACRO-11 fast map, for a non-Digital 4-64 device, 1-51 RRST$ directive, 4-63 for RA71 disk drive, TFEA$ directive, 4-63 1-6, 2-4 for RA72 disk drive, F__________________________ 1-6, 2-4 F11ACP for RA82 devices, 1-11 large disk support, 1-26 for RA92 disk drive, year 2000 support, 1-8 1-6, 2-4 FAL, 1-11, 2-7 for TK25 cartridge FCS tape, 4-13, 4-14 code size, 1-52 for TSV05, 4-13, 4-14 support for queue files system, 1-49 to 1-51 for printing, 1-49 Error Logging Manual VMS ACP function support, corrections, 4-13 1-52 device entry ETSV05, FCSRES 4-13 restriction, 1-15 error log packet, 4-14 system library routines, error logging, 4-14 1-35 error messages, 4-14 Features TK25, 4-13 summary of new TSV05, 4-13 for 11M, 1-1 Error messages for 11S, 2-2 BRU, 4-53, 4-54 to 4-56 File DTE, 4-39 saved answer, 1-22 Error Logging, 4-14 File Access Listener Indirect, 4-23 See FAL RMS-11, 4-33 File attribute codes, 1-49 RMSRST, 4-35 File Control Services system management, 4-36 TKB, 4-67 See FCS Errors File Dump utility data late correction, See DMP utility 1-12, 2-8 Index-5  File Exchange Transfer See FLX I__________________________ File Transfer Program I/O See FLX asynchronous buffered, FLX, 4-57 to 4-59 1-44 to 1-46 copying RT-11 devices, overlapped completion, 4-57 1-46 to 1-47 correction on displaying restrictions the maximum number big buffering in of blocks on a tape, random mode, 1-48 1-12, 2-8 multibuffering, 1-47 DOS-11 device support, I/O Drivers Reference 4-57 Manual support for year 2000 and corrections, 4-16 beyond, 1-9 LA75 terminal type using with a TK50 tape, value, 4-16 1-42 T.V2xx terminal type FMT, 4-59 value, 4-16 device support, 4-59 I/O Operations Reference RX33 diskette support, Manual 4-59 corrections, 4-64 $$FSR2, 4-64 G /ID option ___________________________ DTE command, 4-39 GBLDEF enhancement, 1-22 Indirect, 4-16 Guide to Program command processors, 4-18 Development Manual ICP version, 4-18 corrections ICQ version, 4-18 LINK, 4-16 ICQRES version, 4-19 Guide to Writing an I/O ICX version, 4-18 Driver default radix, 4-21 corrections, 4-5 .ENABLE directive building user-written settings, 4-21 drivers, 4-6 error messages, 4-23 data structures, 4-5 format for timeout, 4-21 driver initiator, 4-5 restriction, 4-17 I.RPM, 4-7 restrictions I/O packet, 4-5 .DELAY directive, 4-21 I/O queue, 4-5 .IFDF directive, 4-22 MACRO-11 command line, .IFT directive, 4-22 4-6 on .ASK directive, S.VCT, 4-7 4-21 U.BUF, 4-7 on .ASKN directive, 4-21 Index-6  Indirect IP11 layered product restrictions (cont'd) for RSX-11M, 1-28 on .ASKS directive, 4-21 J__________________________ on ticks, 4-21 J11-series processor using the command support, 1-26 procedure library, 4-17 K__________________________ Indirect Command Processor KDJ11-E processor, 1-6, See Indirect 2-4 corrections, 4-16 to 4-23 Kit new ICX.TSK, 1-4 changes, 1-15 restrictions copying with $$n logical in SYSGEN, 1-24 name, 1-16 Indirect Command Processor media, 2-2 Manual tape, 1-3 corrections, 4-16 KMV11 X25 Link Level AT. error message, correction files 4-23 for RSX-11M, 1-5 .ENABLE GLOBAL, 4-21 for RSX-11S, 2-3 error messages, 4-23 KMV11-A HDLC Framing .IFDF and .IFT, 4-21 Software SYSTEM symbol, 4-20 correction files ticks in .ASK type for RSX-11M, 1-5 directives, 4-21 for RSX-11S, 2-3 timeout, 4-21 KW11-P clock, 1-11, 2-7 INI (MCR) command /BAD=[AUTO], 4-25 L /BAD=[option], 4-24 to ___________________________ 4-25 LA75 printer support, 4-16 /BAD=[OVR], 4-24 Layered product large disk support, 1-26 correction files, 1-4 /MXF, 4-25 to 4-27 Layered products INITIALIZE (DCL) command correction files /MAXIMUM_FILES:n, 4-11 to for RSX-11M, 1-4 4-12 DATATRIEVE-11/RSX, /PROCESSOR/NOWARNINGS, 1-4 4-36 DCX KMV11-A INITL module Development correction, 2-10 Tools, 1-4 Intersystem echo loops, DECnet-11M, 1-5 4-38 KMV11 X25 Link Level, 1-5 Index-7  Layered products MAKESTK.CMD command file, correction files 1-33 to 1-34 for RSX-11M (cont'd) Mass Storage Control KMV11-A HDLC Protocol Framing Software, See MSCP 1-5 MCR, 4-48 PDP-11 BASIC-PLUS-2 command line interface , 1-4 year 2000 support, PDP-11 FORTRAN-77, 1-9, 2-7 1-5 commands for RSX-11S, 2-2 ASN disk location, 1-5 /TERM, 4-25 file location, 2-3 BAD for RSX-11M /OVERRIDE, 4-24 IP11 software, 1-28 BYE Layered Products year 2000 support, correction files 1-9, 2-7 for RSX-11S DMO DECnet-11S, 2-2 with a TK50 tape, KMV11 X25 Link 1-39 Level, 2-3 DTE, 4-37 to 4-39 KMV11-A Development HEL Tools, 2-3 year 2000 support, KMV11-A HDLC 1-9 Framing Software, INI 2-3 /BAD=[AUTO], 4-25 LBR, 4-59 to 4-61 /BAD=[option], 4-24 Librarian Utility Program to 4-25 See LBR /BAD=[OVR], 4-24 Load error correction, /INF, 4-25 to 4-27 2-11 large disk support, LPA-11K device restriction, 1-26 1-22 MOU LSI-11/73 processor /[NO]DEFER, 4-25 restriction, 1-30 with a TK50 tape, 1-39 QUE M__________________________ /CR/NM, 4-36 MACRO SET year 2000 support, 1-9 /HOST, 1-27 Magnetic Tape Ancillary /HSYNC, 4-25 Control Processor /[NO]DEFER, 4-25 See MTAACP Index-8  MCR MTAACP commands support for new file SET (cont'd) attribute codes, 1-49 restriction on MU-type device support, VT300-series 1-27 terminals, 1-24 Multiplexers /TERM, 4-25 parity correction, 1-11 /VTxxx=TI:, 1-24 /MUTE option TIM SET HOST/DTE command, year 2000 support, 4-38 1-9 MCR Operations Manual N__________________________ corrections, 4-23 to 4-27 $$n logical name, 1-16 ASN, 4-25 NCT, 1-27 /BAD, 4-23 DECnet package, 1-27 INI, 4-24 Network Command Terminal MOUNT [NO]DEFER, 4-25 See NCT SET [NO]DEFER, 4-25 NL: device, 1-21 SET/HSYNC, 4-25 Media for kit, 2-2 O Memory clearing, 2-10 ___________________________ Memory-resident system, Object Module Patch Utility 2-3 See PAT MFT command, 1-30 Online Task Loader format, 1-31 corrections Micro/RSX File Transfer to loading DECnet-11S Utility tasks, 2-8 See MFT command OTL Modem See Online Task Loader dial command string, 4-38 OTL system error correction MOU (MCR) command , 2-11 /[NO]DEFER, 4-25 OTS Fast Map routine with a TK50 tape, 1-39 IOT restriction, 1-53 MOUNT (DCL) command Overlapped I/O completion, /NOLABEL 1-46 to 1-47 block size restriction , 1-48 P__________________________ MOUNT command, 1-38 Parity MSCP, 1-50, 4-40 with multiplexers, 1-11 restriction in SYSGEN, PAT, 4-61 1-23 restrictions on support in RSX-11S, 2-3 Index-9  PDP-11 BASIC-PLUS-2 correction file, 1-4 Q__________________________ PDP-11 FORTRAN-77 QUE (MCR) command correction file /CR/NM, 4-36 for RSX-11M, 1-5 Queue Manager Peripheral Interchange year 2000 support, 1-9 Program See PIP R__________________________ PIP RA70 support, 1-24 corrections, 1-10, 4-61 RA71 disk drive, 1-5, 2-3 to issuing the PIP/LI RA72 disk drive, 1-5, 1-6, command, 1-11 2-3, 2-4 to wildcard support, RA90 support, 1-24 1-10 RA92 disk drive, 1-5, 1-6, large disk support, 1-26 2-3, 2-4 qualifiers RC25 disk kit, 1-16 /LI, 1-11 RCT, 4-39 support enhancements, 4-40 for wildcards, 1-10 Record Management Services switches See RMS-11 /DD, 4-61 Report Generator Task /TD, 4-62 /HISTORY qualifier, 4-13 using with a TK50 tape, Reporting problems, A-1 1-43 information to be year 2000 support, 1-9 supplied, A-3 to A-4 PRINT (DCL) command RMS-11, 3-14 /[NO]TRANSFER qualifier, REWIND command, 1-39 4-9 RMS-11, 3-1 PRINT$ macro call, 1-49 access methods, 3-2 Printer support areas, 4-29 form types, 1-19, 1-20 combining supervisor mode modifying, 1-20 and remote access RMS selecting, 1-19 programs, 3-6 Problem reporting, A-1 commands information to be EXIT, 4-31 supplied, A-3 to A-4 EXIT_SUPERSEDE, 4-30 Problems to 4-32 corrected since V4.5, SAVE, 4-32 2-10 to 2-11 SAVE_SUPERSEDE, 4-30 PUCOM partition, 1-23 to 4-32 contiguity, 4-29 deadlocks, 4-29 Index-10  RMS-11 (cont'd) RMS-11 (cont'd) distribution kit files, RMSDSP 3-11 to 3-14 /BR switch, 4-34 error messages, 4-33 correction, 3-6 ER$FUL, 4-28 /SU switch, 4-34 ER$KEY, 4-27 RMSIFL ER$MRS, 4-27 correction, 3-4 ER$NOD, 4-28 restriction, 3-7 RMSRST, 4-35 RMSRST extended logical names correction, 3-5, 3-6 support, 3-6 /NV switch, 4-35 fields wildcard support, 4-35 ALLOCATION, 4-32 startup procedure, 3-8 to BUCKETSIZE, 4-32 3-9 EXTENSION, 4-32 startup SET commands, 3-8 installation, 3-7 supplementary information Macro Programmer's Guide , 3-6 corrections, 4-27 to task building, 4-30 4-28 UPDATE operations, 4-28 remote access methods, to 4-29 3-2 User's Guide corrections, remote access support, 4-28 to 4-30 4-30 using RMSDAP, 3-2 for indexed files, utilities, 3-4 4-30 command and ODL files, reporting problems, 3-14 3-9 resident libraries, 4-30 configuration, 3-9 resident library corrections, 4-30 to partition, 3-8 4-35 restrictions, 3-7 rebuilding, 3-10 RK06 in, 3-8 restrictions, 3-7 RL01 in, 3-8 RMSCNV, 3-7 RL02 in, 3-8 RMSIFL, 3-7 RMSBCK Utilities Manual, 4-30 to correction, 3-4, 3-6 4-35 /NV switch, 4-34 wildcard support, 4-34 wildcard support, 4-35 writing a record, 4-29 RMSCNV RMS-11 Macro Programmer's configuration, 3-10 Guide /ER switch, 4-33 corrections, 4-27 restriction, 3-7 ALLOCATION field, 4-32 RMSDES BUCKETSIZE field, 4-32 correction, 3-4 ?DES-F-VOR, 4-33 enhancements, 3-6 ER$FUL error, 4-28 Index-11  RMS-11 Macro Programmer's Routines (cont'd) Guide Convert Virtual to Real corrections (cont'd) Address ($CVRL) routine ER$KEY error, 4-27 , 4-4 ER$MRS error, 4-27 $CVRL, 4-4 ER$NOD error, 4-28 $EDMSG EXIT command, 4-31 editing directives EXIT_S command, 4-30, corrections, 4-2 4-31 errors, 4-2 EXTENSION field, 4-32 $EDTMG, 4-1 FID field, 4-27 SETTIM, 4-73 P$BUF, 4-27 $TIM, 4-1 record too small for $WRKPT, 4-4 primary key field, RP07 disk, 1-16 4-27 RPT RMSBCK switches, 4-34 /DATE qualifier RMSBCK wildcards, 4-35 year 2000 support, 1-9 RMSCNV switches, 4-33 RRST$ directive RMSDSP commands, 4-34 restriction, 4-63 RMSDSP switches, 4-34 RSX-11M SYSGEN manual RMSRST switches, 4-35 corrections, 4-8 RMSRST wildcards, 4-35 RSX-11M-PLUS I/O Operations SAVE command, 4-32 Reference Manual SAVE_S command, 4-30, corrections, 4-8 4-31 RSX-11S wildcards, 4-34 restrictions, 2-3 XB$DAT value, 4-27 RSX-11S SYSGEN manual RMS-11 User's Guide corrections, 4-73 to 4-74 corrections, 4-28 to 4-30 copying 11SGEN.CMD, adding DAP support, 4-74 4-30 copying 11SGEN2.CMD, CHANGES, 4-28 4-73 contiguity and areas, FLX with blank disk, 4-29 4-74 indexed file, 4-29 PIP example, 4-74 NODUPLICATES, 4-28 SETTIM, 4-73 record writing, 4-29 RX33 restriction, 1-28 remote access, 4-30 RX50 restriction, 1-28 task building resident libraries, 4-30 UPDATE, 4-28 Routines $CAT5B, 4-1 Index-12  SHOW QUEUE (DCL) command S__________________________ /ALL qualifier, 4-9 Saved answer file, 1-22 SHUTUP utility SCSI correction, 1-10, 2-7 support, 1-5, 2-3 Slow Task Builder supported devices, 1-5, See TKB 2-3 SLP, 4-62 to 4-63 RQZX1 adaptor, 1-5, Software Performance Report 2-3 See SPR RZ23L, 1-5, 2-3 SORT command RZ24L, 1-5, 2-4 /INDEXED_SEQUENTIAL TZ30, 1-5, 2-4 qualifier, 1-12 SET (DCL) command Source Language Input HOST Program /DTE, 4-37 to 4-39 /DIAL option, 4-38 See SLP /MUTE option, 4-38 SPR parameters, 4-37 category, A-3 /VERSION option, completing, A-1 4-39 priority, A-2 selecting NCT during SYSGEN SYSGEN requirement, corrections, 4-8 1-27 distribution kit, 1-2 /TERMINAL/VTxxx for RSX-11S restriction on VT300- corrections, 4-73 to series terminals, 4-74 1-24 FLX correction, 4-74 TIME PIP correction, 4-74 year 2000 support, invoking VMR when using a 1-8, 2-7 VAX-11 RSX host, 1-22 SET (MCR) command minimum system /HOST requirements, 1-21 selecting NCT during $$n logical name, 1-16 SYSGEN requirement, on a VAX-11 RSX host, 1-27 1-16 /HSYNC, 4-25 requirements /[NO]DEFER, 4-25 selecting NCT, 1-27 /TERM, 4-25 restrictions, 1-21 /VTxxx=TI: LPA-11K devices, 1-22 restriction on VT300- on Indirect Command series terminals, Processor, 1-24 1-24 on MSCP devices, 1-23 online generation, 1-4 Index-13  SYSGEN (cont'd) System transportability, selecting printer support 1-29 , 1-19 SYSVMR.CMD file, 1-23 standalone, 1-15 using logical names, 1-16 T__________________________ SYSGEN manual changes, 1-3 Tape SYSLIB copying distribution See System library tape, 1-18 routines, 1-35 copying distribution to System corruption disk, 1-22 correction, 2-11 distribution, 1-22 System generation kit, 1-3 See SYSGEN Task System library .AT task image, 1-4 using with TKB, 1-53 hanging when attaching to System library routines, a terminal, 1-14, 2-9 1-35 ICP.TSK, 4-18 FCSRES, 1-15, 1-35 ICQ.TSK, 4-18 RX50/RX33 devices, 1-28 ICQRES.TSK, 4-19 System Library Routines ICX.TSK, 1-4, 4-18 Reference Manual Task Builder corrections, 4-1 See TKB added program sections Task Builder Manual , 4-1 corrections, 4-64 to 4-72 added SYSLIB routines, /-CO switch, 4-66 4-1 /-LI switch, 4-66 $TIM routine, 4-1 /-PI switch, 4-66 $WRKPT, 4-4 double brackets, 4-65 System Management Guide double_quote character corrections, 4-36 to 4-46 , 4-65 ACNT message, 4-36 error messages, 4-67 DTE error message, label block offsets, 4-39 4-67 establishing terminal LB; specification, emulation, 4-37 4-65 INITIALIZE/PROCESSOR /LI switch, 4-66 /NOWARNINGS, 4-36 manual references, RCT, 4-39 4-65 RMD, 4-36 .ROOT statement, 4-65 SHUTUP, 4-37 /SHAREABLE:LIBRARY /TYPEAHEAD, 4-39 switch, 4-65 Index-14  Task load error correction, TKB 2-11 /-SH restriction, 1-15 TC11 support, 1-28 cluster libraries, 4-69 TC11-TU56 tape subsystem, compatible library 1-28 requirement, 1-53 TDX corrections, 4-64 to 4-72 commands, 4-41 to 4-44 creating the Slow Task functions, 4-41 to 4-44 Builder, 1-33 to 1-34 installing, 4-41, 4-46 error messages, 4-67 MCR translations, 4-41 to Fast Map routine 4-44 restriction, 1-53 modifying source file, Fast Task Builder, 4-71 4-44 to 4-46 FCSFSL, 1-34 task, 4-41 to 4-46 FCSRES, 1-34 Telephone non-PIC shared region, dial command string, 4-38 4-68 Terminal driver support, offsets, 4-67 1-26 qualifiers Terminal interface support, /CODE:CLI, 4-71 1-26 /FAST_MAP, 4-72 Terminals /SLOW, 4-70 unused ports, 1-14, 2-10 RNDSEG Option, 4-67 TFEA$ directive Slow Task Builder, 4-70 restriction, 4-63 to 4-71 TK25 tape, 4-13 switches TK50 /-CO, 4-66 with BRU, 1-40 /-LI, 4-66 with BRU64K, 1-42 /-PI, 4-66 with BRUSYS, 1-42 /CL, 4-71 with PIP, 1-43 /CO, 4-66 with the FLX utility, /FM, 4-72 1-42 /LI, 4-66 TK50 tape, 1-21 /MP, 4-65 restriction, 1-30 /SB, 4-70 subsystem, 1-36 to 1-44 /SHAREABLE:LIBRARY, dismounting the tape, 4-65 1-38 /SS, 4-69 mounting the tape, using system library, 1-38 1-53 performance using RSX TZ30 tape utilities, 1-38 restriction, 1-30 tape indicators, 1-43 Index-15  U__________________________ V__________________________ UETP support, 1-28 /VERSION option User Environment Test SET HOST/DTE command, Package 4-39 See UETP VFY Utilities Manual large disk support, 1-26 corrections, 4-46 to 4-63 VMR and VAX-11, 1-22 BRU, 4-46 VMS ACP function support BRU command files, FCS, 1-52 4-53 VT300-series terminal CNF table, 4-54 restriction, 1-24 DMP, 4-56 DMP/HF, 4-57 Y__________________________ DMP/LIM, 4-57 Year 2000 support, 1-1, FLX, 4-57 2-2 FMT, 4-59 BROADCAST utility, 1-8, LBR, 4-59 2-7 LBR/CR, 4-60 BRU, 1-8 LBR/IN, 4-61 date format, 1-6, 2-5 MANUAL option, 4-53 DCL commands /NOSUPERSEDE, 4-54 BACKUP, 1-8 PAT, 4-61 DIRECTORY/SINCE, 1-8 PIP, 4-61 SET TIME, 1-8, 2-7 PIP/DD, 4-61 F11ACP, 1-8 PIP/TD, 4-62 FLX, 1-9 selective backups, MACRO, 1-9 4-47 MCR SLP, 4-62 command line interface SLP error messages, , 1-9, 2-7 4-62 commands SLP file name length, BYE, 1-9, 2-7 4-62 HEL, 1-9 SLP illegal switch, TIM, 1-9 4-62 PIP, 1-9 tape write error Queue Manager, 1-9 message, 4-53 RPT wildcards, 4-47 /DATE qualifier, 1-9 Index-16  Z__________________________ ZAP used with the MAKESTK.CMD command file, 1-33 to 1-34 Index-17