Digital PDFs
Documents
Guest
Register
Log In
AA-DO15C-TE
March 1980
59 pages
Original
3.1MB
view
download
OCR Version
2.7MB
view
download
Document:
VAX/VMS Release Notes Version 2.0
Order Number:
AA-DO15C-TE
Revision:
0
Pages:
59
Original Filename:
OCR Text
dilgiltal VAX/VMS Release Notes Version 2.0 Order No. AA-DO15C-TE March 1980 This document contains information not included elsewhere in the documenta- tion set. Typically, this information covers software and/or documentation errors that were discovered or changes that were made late in the development cycle, plus hints concerning system installation and operation. This document should be read before the system is installed or used. VAX/VMS Release Notes Version 2.0 Order No. AA-D015C-TE SUPERSESSION/UPDATE INFORMATION: This revised document supersedes the VAX/VMS Release Notes (Order No. AA-D015B-TE) and VAX/VMS Version 1.6 Release Notes (Order No. AA-JO39A-TE). OPERATING SYSTEM AND VERSION: VAX/VMS V02 SOFTWARE VERSION: VAX/VMS V02 To order additional copies of this document, contact the Software Distribution Center, Digital Equipment Corporation, Maynard, Massachusetts 01754 digital equipment corporation - maynard, massachusetts First Printing, August February 1979 1978 Revised, Revised, The information in this document is subject to March change 1980 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 and software described in this document is furnished may only be used or copied in accordance with under a the terms 1license of such license. No responsibility equipment that is is assumed for the use or reliability of software on not supplied by DIGITAL or its affiliated companies. copyright (C) 1978, 1979, 1980 by Digital Equipment Corporation The postage prepaid READER'S COMMENTS form on the last document requests the wuser's critical evaluation preparing future documentation. The following are trademarks of Digital Equipment Corporation: DIGITAL DECsystem-10 MASSBUS DEC DECtape OMNIBUS PDP DIBOL 0S/8 DECUS EDUSYSTEM PHA UNIBUS FLIP RSTS COMPUTER COMTEX LABS DDT DECCOMM CHIP FOCAL page of to assist RSX INDAC TYPESET-8 LAB-8 DECSYSTEM-20 TYPESET-11 TMS-11 ASSIST-11 RTS-8 ITPS-10 VAX VMS SBI DECnet DATATRIEVE IAS PDT TRAX this us in CONTENTS Page HOW TO INSTALL VAX/VMS V2.0 1 Identifying the VAX/VMS V2.0 Kit VAX/VMS Optional Software Products Before Installing the V2.0 Kit Installing the VAX/VMS V2.0 Kit After Installing the VAX/VMS V2.0 Kit DIFFERENCES BETWEEN VAX/VMS V2.0 AND VAX/VMS 1.6 New Hardware Supported Changes to the Documentation Kit Command Language and System Messages Changes to DCL DIRECTORY Command Changes FORTRAN Command /WORK_ FILES Qualifier Now Ignored SET TERMINAL Command /LOCAL and /REMOTE Qualifiers System HELP Files Have Changed Program Development Tools VAX-11 Symbolic Debugger Features System Services and I/0 Use of Colon to Separate Name of Shared Memory from Name of Event Flag Cluster, Mailbox, or Global Section : Maghetic Tape Driver: Tapes Mounte 5 6 6 6 7 7 7 7 7 8 8 9 9 /FOREIGN 9 Run-Time Library Compatibility Between Different Versions of VAX/VMS Routine for Determining Setting of Lines-per-Page FORTRAN Default Logical Unit Assignments 10 User Stack Now Automatically Expanded 10 10 10 VAX-11 Record Management Services 11 12 RMSSHARE Utility RMSANLZ Unsupported 12 12 Utility Magnetic Tape Label HDR3 Sequential File Sharing Record Management Services (RMS-11) Compatibility Mode Change in P1 Parameter of 12 12 for the Changes to MCR Command PDP-11 IO.ATT Directives AME Emulation of QIOS$ Directives Unknown Devices MACRO-11 CRF Now Supported NN 1 3 3 4 5 13 for Language Interpreter LIBRARY/RSX1l1l Library Extractions Compatibility Mode Utilities Now Native Mode iii 12 13 13 13 13 13 14 CONTENTS Page System All Programming Drivers Must 14 Be Reassembled and Relinked 14 Buffered I/0 Count Interrupt Dispatch for More Than New Macro for Code Change Drivers 8 Quota Table Units Required Management System System System New a UNIBUS Datapath in Some V1.A Off "Last PO 1A and Operation Security: SET PASSWORD Security: Terminal Security: Privileged Command Allocation Device Name File Has Console for Importance of VMS-to-VMS Network Using the Capability Using the New Stand-alone 2.11.9 New Feature 2.11.10 New CRASH 2.11.11 New Method for ERRFMT Command to New Format Floppy v2.0 Command 2.11.8 VMB 19 20 Process 20 20 Default Lines21 File Manager Performance Enhancements 21 New 2.11.14 AUTOCONFIGURE AUTOCONFIGURE Device Support Lineprinter 22 Floppy Disks as Output System Generation 2.11.146 Use of Directory 2.11.17 SYS Parameter 2.12 Unsupported 2.12.1 DIGITAL from RSX-11S 22 [10,40] BUGCHECKFATAL 22 23 Software Standard 23 RUNOFF (DSR) Replaces e W N O . 25 N NDMDNOND B WwWwwwwwwwo e 25 25 SETNAME 25 SFA 25 TALK 25 USERS 25 WHO New 25 TECO-11 Manual RESOLVED 25 BY VAX/VMS RESTRICTIONS Command N s o Utilities SEARCH O b b DN 24 INFO O « Monitor Unsupported CURRENT o 23 Fault PROBLEMS . S WD NN RNO.EXE = 22 Errors Corrected Page 19 DSC2 Procedure Change 18 18 Terminal Value of 2.11.13 2.11.15 17 18 Authorization Effects 17 17 Images CTRL/Y per-Page 15 16 System User 1a 15 Purging PATCH Utility Turns Cluster" Option and Field Changes Can Be Set Languages DIRECTORY Command Restriction on AND and V2.0 2h PROBLEMS 27 System /EXCLUDE Use of Wild Messages Qualifier Card Characters Effect Devices of 27 Wild Mounted Incorrect 27 27 HELP iv Card Operations on Foreign Text for 27 MOUNT Command 27 CONTENTS Page Program Development Tools 27 LIBRARIAN Restrictions and Problems Using /NAMES and /LIST Qualifiers 27 28 Using /OUTPUT Qualifier LIBRARIAN Failures on Update 28 and 28 28 Insert <CTRL/Y> May Corrupt Library Broadcast Message Interrupts o N w d W NS o B o o S S, IS, o o G, N o o o o o ) WS NS IS o o « * o o o o ¢ o o s DD D SOS Alter 28 Screen Linker Restrictions and Problems LINKER Effect on Address Space of Executable Image Linking Multiple Shareable Images Shareable Images Linked with VMSRTL VAX-11 Symbolic Debugger Deposits of H floating DNata Long Literals Variables Short Floating-Point Real Variable Names Global Structures Condition Handlers MACRO Default [\ . PN e . 29 29 .IF 30 30 30 31 Arguments 1/0 31 Handlers and 29 29 Literals DEBUG Restriction When Using Condition LIBSADDX 28 29 String VAX-11 28 29 System Services and Run-Time Library * o ¢ DS D o s o D D D D BB BB WNDNDNDNDNDDNNDNDDNDDNN Mode LIBS$SSUBX Produce Length Incorrect Lowercase TPAS Symbols Not Recognized VAX-11 Record Management Services Restriction on Copying Relative and Indexed Files Device Characteristics Returned on Parse Incorrect BLISS-32 Definition in SYSSLIBRARY:STARLET.REQ Current File Access Sharing Problem Incorrect Status Return when File 31 31 31 31 32 32 32 32 Opened for Block I/O Magnetic Tape Restrictions and Problems MBA/TMO3 ECO Prevents Magnetic Tape 33 33 ACP Failures Magnetic Tape 33 Process to ACP Error Can Cause 33 Hang Appending Records Tape File to an ANSI Magnetic EOF3 Label Not Written on ANSI Magnetic 34 Tapes Continuation Tapes Run Away Initialized Foreign Tapes Initialized Support Level if Not 34 Run Away if Not for ANS X3.27-1978 Record Management Services PDP-11 34 (RMS-11) for the ‘ Restrictions on Use of RMSIFL Utility 34 35 CONTENTS Page 4.6.1.1 Records 4.6.1.2 May Lose Input Order Large Bucket and Record Containing Duplicate Key Values 35 Sizes Can Cause 4.6.2.1 Command Line Termination Restrictions to Use of RMSRST Utility Version Number Failures with /SE Switch 4.6.2.2 /RC 4.7 Compatibility 4.6.2 4.7.1 FLX and /RA Loops DEVICE Switch Usage Prohibited Mode after Receiving INVALID Message 34 System Programming SDA SET OUTPUT Command 4.8.2 4.8.3 PATCH Utility Problems Restriction on Using Interlocked 4,9 4.9.1 System Management and AUTOCONFIGURE Command 4,9.2 4.9.3 Generating Produces Error 4.10 EDT 36 37 Operation of SYSGEN Utility Parameters Not Supported RSX-11S and RSX-11M DECnet Computer-Assisted 37 37 37 37 Instruction Course 5.0 5.1 36 36 Queue Instructions SYSGEN 36 36 4.8 4.8.1 Two 35 35 35 38 NOTES TO PUBLISHED DOCUMENTATION VAX/VMS I/0 User's Guide 39 39 5.1.1 5.1.2 Foreign Magnetic Tape Skip DR780 Support Routines 5.1.3 5.2 Documentation VAX-11 Record Reference Manual ' VAX/VMS System Services Reference 41 5.3 Manual 41 5.4 VAX-11 PATCH Utility 5.5 VAX/VMS UETP User's Error Management Functions 39 39 41 Services Reference Manual Guide 42 42 5.6 VAX/VMS Command 43 5.7 VAX~-11 Utilities 43 6.0 INSTALLING AND 6.1 Installing 0.2 Verifying Language User's Guide Reference Manual TESTING VAX-11 COBOL-74 VAX-11 COBOL-74 Installation of vax-11 COBOL-74 A.O PATCHES MADE 44 44 45 AFTER MICROFICHE KIT MANUFACTURED 47 TABLE Table 1 VAX/VMS V2.0 Magnetic Tape Distribution Kit 2 VAX/VMS Kit Disk 3 4 VAX-11] Optional Software Suggested UETP Parameter V2.0 1 Cartridge Distribution 2 vi Products Settings 3 42 1.0 HOW VAX/VMS TO INSTALL V2.0 Current is a VAX/VMS major customers V2.0 release use the VAX/VMS V1.6 system to a distribution kit to install a This section is an overview of V2.0 of 1.1 Two Installation Guide Identifying VAX/VMS require require the information V2.0 kits are V2.0 components with customers you need system. upgrade to their use install can be new system of used this one for upgrading (new customers). the kits are VAX/VMS V2.0 Table 1 Magnetic Tape 25.1.5 Console floppy | RX listed Operating 1/11780 (or kit. is sent to in a system customers Tabhles 1 (current and Distribution Label VAX/VMS the Kit distributed: Component SPD to The definitions of and procedures upgrades are found in the VAX-11 provided VAX/VMS operating kit magnetic tape distribution, the other is sent to customers disk distribution. Except for media differences, the kits identical, and or installing a The the VAX/VMS V2.0 system. New VAX/VMS V2.0 systen. upgrade to) a VAX/VMS V2.0 system. for system installations and system Software the distribution LOCAL customers) 2. Kit Order System Version CNSL who who are Number 2.0 | AE-C770FE~-TE PKG AS-EA33I-YE diskette DSC floppy diskettes Upgrade STAND/ALONE 11780 DSC2 FLP1 AS-EB8Q8I-YE STAND/ALONE 11780 DSC2 FLP2 AS-J8 31A-BRE RX01l UPG floppy | VAX/VMS V2.0 AS-J803A-BE diskette V2.0 system VMS V20 BIN MT9 VMS V20 UPGRADE BB-D782C~BE magnetic tape Upgrade maghetic MT9 RB-J80OA-RBE tape Microfiche VAX/VMS V2.0 SRC LST VAX/VMS V2.0 DOC KIT RSX-11S UPDATE MCRF/XXX AH-H159B-SFE kit Documentation QEN001-GZ kit RSX-11S floppy| RX01l AS-J856A-BE diskette (continued on next page) VAX/VMS Release Notes Version Table VAX/VMS V2.0 Tape Distribution EDTCAI FLOPPY EDTCAI EDTCAI EDTCAI EDTCAI EDTCAI EDTCAI EDTCAI FLOPPY 2 FLOPPY 3 FLOPPY 4 FLOPPY 5 FLOPPY 5 FLOPPY 7 COURSE ADMIN EDTCAI STUDENT GUIDE VAX/VMS V2.0 1 Component SPD 25.1.5 System/upgrade | VAX/VMS disk cartridge floppy RX Operating V2.0 1/11780 AS-J814A~-BE AS-J815A-BE AS-J816A-BE AS-J817A~-BE AS-J818A-BE AS-J819A-BE AA-J823A-TE GUIDE AA-J824A-TE Distribution System Version BIN RKO7 LOCAL CNSL Kit Order Label VAX/VMS Number AS-J813A-B3 Table 2 Cartridge Disk Kit Order Label kit Console (Cont.) Magnetic Component EDTCAI 1 2.0 Number 2.0 | AE-C770E-TE AY-H020C-BE PKG AS-EG33I-YE diskette DSC floppy STAND/ALONE 11780 DSC2 FLP1 AS-E808I-YE STAND/ALONE 11780 DSC2 FLP2 AS-J8 31A-BE RX01l UPG diskettes Upgrade floppy VAX/VMS V2.0 AS-J803A-BE diskette VAX/VMS V2.0 SRC LST MCRF/XXX AH-H159B-SE Documentation kit VAX/VMS V2.0 DOC KIT QE001-GZ RSX-11S RSX-11S UPDATE Microfiche kit floppy AS-J856A-BE RXO01l EDTCAI kit EDTCAI FLOPPY Noa S W diskette EDTCAI COURSE ADMIN EDTCAI STUDENT EDTCAI FLOPPY EDTCAI FLOPPY EDTCAI FLOPPY EDTCAI FLOPPY EDTCAI FLOPPY EDTCAI FLOPPY GUIDE AS-J813A-BE AS-J814A-BE AS-J815A-BE AS-J816A-BE AS-J817A-BE AS-J818A~BE GUIDE AS-J819A-BE AA-J823A-TE AA-J824A-TE VAX/VMS Release Notes Version 2.0 1.2 VAX/VMS Optional Software Products This kit does not contain updates to any VAX-11 optional product and, with one exception, contains no information on optional product installation. That exception is the installation procedure for VAX-11 However, 1in Section A.0 of these release notes. contained COBOL-74, of overview an provide the VAX-11l Software Installation Guide does optional product installation. the products, software optional VAX-11 Table 3 lists the names of versions VAX/VMS by supported were that products these of versions V1l.5 and V1.6, supported versions the and VAX-11 Table 3 Optional Software Product Name V1.6 V2.0 1.1 l.2 1.3 1.2 1.3 2.0 1.0 1.0 2.0 -— 1.0 1.1 2.2 2.3 2.3 - PDP-11 BASIC-PLUS-2/VAX 1.5 1.5 1.6 PDP-11 DATATRIEVE/VAX 1.1 1.2 2.0 PDP-11 CORAL 66/VAX 3.0 3.0 3.0 VAX-11 -- 1.0 1.1 VAX-11 COBOL-74 4.0 4,1 4.1 VAX-11 BASIC -- - 1.0 Before Installing the V2.0 Kit FORTRAN VAX-11 BLISS-32 VAX-11 FORTRAN 2780/3780 Protocol IV/VAX to Emulator RSX Cross Compiler ensure 1. now Products vli.5 VAX-11 To are Version Supported by VAX/VMS DECnet-VAX 1.3 that products these of by VAX/VMS V2.0. PASCAL successful installation of the software: Read the VAX-11l Software Installation Guide. to how wunderstanding for document The Guide is the basic install, upgrade, or update VAX/VMS or its optional products. 2. Read this manual, This manual successful system. the VAX/VMS Release Notes contains 1installation information of (or you (Version 2.0). need upgrade to) to ensure a a VAX/VMS V2.0 VAX/VMS 3. Examine This the Release Notes Version VAX-11/780 read-only System register Bit Field Contains Processor type ECO level 18:15 ECO level for for 14:12 Manufacturing 11:0 Processor cannot a. Ensure be location serial that the in system command diskette >>> prompt, type HALT<KRET> d. After the >>> prompt, type EXAMINE/I e. A 31:24 the binary hardware contain and to) If any install the VAX-11 you are is (or the V1.6 value of bits is at values, the problem: a current a only VAX/VMS upgrade Software of the diskette is 1 The binary (processor 23:19 ECO 3E<RET> must level contact customer, ensure value of VAX-11/780) wequal If DIGITAL cannot is be 3). you to) VAX/VMS from V2.0 system will a V1.6 VAX/VMS these field install to 3 fields service (or upgrade system. V1.A that vyour VAX/VMS current V2.0 can bhe system. Kit VAX/VMS Installation customers perform a to system contents <CTRL/P> displayed. equal type hardware must use v2.0. upgraded To is be other report system 1Installing number must press the floppy the hexadecimal processor drive. After f. console, the print c. (the Current to At and will unless level for functional examine the SID, you console floppy code b. bits 1.4 ECO To language the the information: number installed command inserted following (SID). functional hardware changes nonfunctional hardware changes field contains a 1 and the changes field contains a 3. the console register: the Register information on: 31:24 V2.0 Identification contains 23:19 VAX/VMS 2.0 V2.0, Guide perform a follow that is system the instructions provided upgrade, installation. NOTE Instructions for installing the Computor-Assisted Instruction (the EDTCAI kit) are contained new EDT course in the Introduction to the EDT Editor, Course Administrator Guide provided with this kit. in with this kit. new customers VAX/VMS Release Notes Version 2.0 1.5 After Installing New customers VAX/VMS V2.0 should the VAX/VMS V2.0 install system has been optional Kit software products after the installed. After completing the system upgrade, current customers must reassemble and relink any user-coded software that had been linked with the V1.6 global symbol table of the operating system, [SYSEXE]SYS.STB, or that had been assembled using the V1.6 operating system macro library, [SYSLIB]LIB.MLB. For example, all wuser-coded drivers must be reassembled and relinked to the V2.0 version of SYS.STB. For more information on changes to user-coded software, refer to Section 2,10 of these release Current customers after completing superseded. If a product should be notes. should reinstall all optional software products the V2.0 wupgrade, if these products have not been product has been superseded, an update of that applied after the V2.0 upgrade is completed. CAUTION If you have installed VAX-11] COBOL-74 on an earlier version of VAX/VMS, do not reinstall it after upgrading to VAX/VMS v2.0. VAX-11 Continue to wuse the version of COBOL-74 already installed. VAX/VMS Release Notes Version 2.0 DIFFERENCES BETWEEN VAX/VMS V2.0 Because V2.0 are many highlight described 2.1 a major release of The the VAX/VMS 1.6 operating system, there V2.0 now Supported supports the following hardware supported, consult provided with this kit. 2.2 AND VAX.VMS changes and new features. The purpose of this section is to some of them: changes and new features are completely in the documentation for this release. New Hardware VAX/VMS of is is 2.0 e MA780 e RX02 floppy diskette e TS11 magnetic e LP25 line e DR780 Changes VAX/VMS revisions multiport the V2.0 to hardware. Software For Product complete list Description a that memory tape drive (used as a data device includes several new find information only) transport printer 32-bit to the parallel interface Documentation Documentation current Kit Kit manuals. To the manuals you need, and read the VAX-1l1l Information Directory and Index that is provided with this kit. The 1information directory describes the intended audience and features of each manual in the documentation kit and provides an index to major VAX/VMS operating system topics. Each manual that has been revised for VAX/VMS V2.0 contains a summary of technical changes. The purpose of these summaries is to point you quickly describe General to portions of the documentation new V2.0 features. information about VAX/VMS that V2.0 is were changed found 1in or the added to following documentation: e VAX-1ll Information e VAX/VMS Summary e VAX/VMS Primer e VAX/VMS Release Directory Description and and Index Glossary Notes 2.3 Command Language and System Messages This section Command contains Language describing DCL and notes on changes (DCL) and system messages e VAX/VMS Command e VAX/VMS Guide e VAX/VMS System Language to Using Messages and additions system message is found User's Command and the in: Procedures Procedures DIGITAL Documentation Guide Recovery ) to facility. Manual VAX/VMS Release Notes Version 2.0 to the Changes to DCL - There are many changes and additions Read the "Summary of Technical Changes" in the VAX/VMS Command 2.3.1 DCL. Language User's Guide for a list of them. 2.3.1.1 DIRECTORY Command Changes - The DIRECTORY command has been There are some incompatibilites between the way certain redesigned. these the way qualifiers worked in previous versions of VAX/VMS and are many new qualifiers. there Furthermore, now work. qualifiers the of II in Part Users should study the new command descriptions VAX/VMS Command Language User's Guide. in If you have used the DIRECTORY command of reprogramming desired results. 2.3.1.2 FORTRAN the procedures be may some procedures, necessary to achieve the Now Ignored - You Qualifier /WORK_FILES Command command no longer specify the number of work files for the compiler to should files. external work The VAX-11 FORTRAN compiler does not use use. files that specify this command 1if you currently have However, is the /WORK_FILES qualifier qualifier, they need not be changed; ignored. SET 2.3.1.3 TERMINAL Command /LOCAL Qualifiers /REMOTE and Removed - You can no longer specify the /LOCAL, /NOLOCAL, /REMOTE, or /NOREMOTE qualifiers with the SET TERMINAL command. VAX/VMS determines whether a terminal is remote or local automatically when the terminal comes on line. internal. All tracking of remote or local status is If you specify any of If you have used these qualifiers remove them to avoid the these qualifiers, in command an error occurs. procedures, you must error messages, 2.3.2 System HELP Files Have Changed - The format of the HELP files have changed for Vv2.0. All the help text files are now maintained in .EXE, SYS$SSYSTEM:CVTHELP program, A a library, SYSSHELP:HELPLIB.HLB. supplied to aid you in converting your site-specific help files to is the new format. When you run CVTHELP, you must have the old help files in your default Specify only the CVTHELP will ask for the V1.6 file name. directory. CVTHELP file name, as a default type of HLP is automatically applied. This is the key name that will be the key name. for ask also will When asked for the output entered into the index of the help library. A default type name, you may specify a full file specification. file of DAT is used if you do not supply one. After the help files have been converted, you can place help library by using the DCL $ them in the command: LIBRARY /HELP SYSSHELP:HELPLIB helpsource Note that all DIGITAL-supplied help files have been updated to include new features, VAX/VMS 2.4 Program This section components are contains wused documented in 2.0 Tools notes on changes to develop the following and software. additions The program VAX-11 Text e VAX-11 EDT e VAX-1l1l Utilities e VAX-11 SORT User's e PDP-11 SORT Reference ® VAX-11l MACRO User's e VAX-11 MACRO Language e VAX-11 Linker e VAX-11 Symbolic Debugger Reference Manual VAX-1l1 to Editor V2.0 Manual Reference Reference Reference ° SET . Special ) Scope ) SHOW SCOPE ° Modes for ° SET TYPE ° New command ) SET LOG o SET OUTPUT ° SHOW OUTPUT ° SHOW LOG ) Command procedures ) Support for Manual Manual Manual Reference Manual Manual Features Refer information Search on the - to command pathnames default command search rules and command modifiers command command command command VAX-11 BASIC The the new Rules SCOPE tools Guide Debugger ° system Manual debugger. for the Guide Reference Symbolic the Reference Editing to development mahuals: ® 2.4.1 new Development Release Notes Version typing following VAX-11 features. features Symbolic are Debugger VAX/VMS Release Notes Version 2.5 System Services This section and contains services and I/0. following manuals: 1I/0 notes The e VAX/VMS System e VAX/VMS I/0 2.0 on changes documentation Services User's and for Reference additions these to topics VAX/VMS system is in found the Manual Guide 2.5.1 Use of Colon to Separate Name of Shared Memory from Name of Event Flag Cluster, Mailbox, or Global Section - The colon serves the special function of separating the shared (multiport) memory name from the name of the common event flag cluster, mailbox, or global section. Therefore, any existing programs that include a colon in the name string will not work as they did previously (regardless of whether your system has a multiport For example, assume MBXNAM: .ASCID your memory program unit), contains these statements: /PROJECT5:BOX/ SCREMBX_ S . o o y LOGNAM=MBXNAM VAX/VMS will not attempt to create a mailbox named PROJECT5:B0X, but instead will attempt to create a mailbox named BOX in a shared memory unit named PROJECTS5. You will get the error message, "Shared memory not connected." To prevent the problem, change programs that include the colon in these name strings. 2.5.2 Magnetic Tape Driver: Tapes Mounted /FOREIGN - In V2.0, the 10$ SKIPRECORD and 1I0S$ SKIPFILE 1I/0 functions on magnetic tapes mounted foreign have changed. forward tape The The direction, now Both functions, when operating terminate upon encountering two in the consecutive marks. status prior actual to returned in the I/0 Status Block number of records the detection of high-order two bytes of remains positioned between (or files) the second tape (IOSB) is SS$ ENDOFVOLUME, skipped during the operation mark the first longword the two tape marks. is of returned the IOSB. in the The tape Subsequent skip record (or skip file) requests from this tape position will terminate immediately, producing no net tape movement and returning the SS$_ENDOFVOLUME status with a skip count of zero. To move the tape beyond the second tape mark, you must employ another I/0 function. For example, the I0$ READLBLK function, if issued after receipt of the SS$ ENDOFVOLUME status return, will terminate with an SS$ ENDOFFILE status second tape mark. and with the tape positioned just beyond the From this new position, other skip functions could produce forward tape motion (presuming that there is on the tape). be issued to additional data VAX/VMS Release Notes Version 2.0 If three consecutive tape marks are encountered during a forward skip function, you must issue two IO$ READLBLK functions; the first to get the SS$ ENDOFFILE return, the second to position the tape past the third tape mark. 2.5.3 User Stack Now Automatically Expanded - VAX/VMS now expands the user stack automatically, obviating the need for exactly specifying user stack size to the Linker and for user code to extend the stack. Note that there is no option to disable this automatic stack expansion. 2.6 Run-Time This section contains notes on changes and Common the Library Run-Time Run-Time Procedure Library. Library e VAX-1l e VAX-11 Guide is: Run-Time additions to the VAX-11 The documentation that describes Library Reference Manual to Creating Modular Library Procedures you Compatibility Between Different Versions of VAX/VMS - When 2.6.1 versions different between compatibility library, run-time link with a to of the operating system is only quaranteed from an earlier version a later version (upward compatibility) and not from a later version to an earlier one (downward compatibility). For example, a program linked on Version 1.6 will run on Version 2.0, but not vice versa. Note that any program that requires CMKRNL or CMEXEC be relinked to run on VAX/VMS V2.0. The reason privileges must is that programs not linked with the current system have their CMKRNL and CMEXEC privileges turned off at image activation time to prevent them from attempting to access symbols whose values have been changed in SYS.STB. In Version 1.6 systems, the information to determine whether an image privileges for image linked against SYS.STB activation time all and is not available. Version 1.6 restored at images image Therefore, are run-down. CMKRNL and CMEXEC turned off at 2.6.2 Routine compilers and for Determining Setting of Lines-per-Page - Many utilities produce output files formatted for the pages of a line printer. 1In V2.0, the Run-Time Library contains a routine, LIBSLP LINES, that native mode programs can call to determine the user setting of the number of lines on a printer page. The routine is documented in the VAX-11 Run-Time Library Reference Manual. Refer to Section 2.11.11 of these release notes information. NOTE Compatibility the the LIBSLP page cannot be mode LINES &size varied programs routine. for cannot For MACRO-11 conveniently. 10 use example, 1listings for related VAX/VMS Release Notes Version 2.0 2.6.3 FORTRAN Default Logical Unit Assignments - The implementation of VAX-11 FORTRAN default logical unit assignments has been changed to reduce the number of language-specific logical names in the VAX/VMS system logical name tabhle. VAX-11 FORTRAN, for example, provides the following correspondence between FORTRAN I/0 statements, FORTRAN-specific logical names, and system logical names: Statement FORTRAN Logical Name System Logical Name ACCEPT TYPE READ PRINT any on unit 5 any on unit 6 FORSACCEPT FORSTYPE FORSREAD FORSPRINT FOR0O05 FORO0OO0A SYSSINPUT SYSSOUTPUT SYSSINPUT SYSSOUTPUT SYSSINPUT SYSSOUTPUT In earlier versions of VAX/VMS, default logical unit assignments were implemented as system-wide logical names. These names were defined by ASSIGN/SYSTEM commands in the DIGITAL-supplied system start-up command procedure. In VAX/VMS V2.0, these logical names are not defined as system-wide logical names. Instead, the Run-Time Library contains code that provides logical unit defaulting. When the first I/0 operation Iis performed on any of these units, the FORTRAN-specific logical name is translated. If the logical name translation succeeds, the translated name is wused (as in earlier versions). However, if the logical name is not defined substituted, as (the default case), SYSSINPUT or SYSSOUTPUT is appropriate. Therefore, to the FORTRAN program, the default logical unit assignments appear to be the same as they were in. earlier versions of VAX/VMS. FORTRAN programs that were linked to the Version 1,6 Library (the default) will work without change. shared Run-Time However, programs returned is: that were linked using the /NOSYSSHR linker command qualifier may fail when they run under VAX/VMS V2.0. $FOR-F-OPEFAI, open The error message failure The appropriate logical name is also displayed. If the program used units 5 or 6, no error occurs, but the system attempts to use the files FOR0O0O5.DAT or FOROO0O6.DAT. To prevent problems with programs linked /NOSYSSHR, do one of the following: e Link the e Define running e program again on V2.0 the the required logical names at the process level before program Have the system manager insert ASSIGN/SYSTEM commands for the required 1logical names in the site-specific system start-up command procedure [SYSMGR]SYSTARTUP.COM 11 VAX/VMS 2.7 VAX-11l Record This section Release Notes Version Management contains notes Services that describe VAX-11 Record Management Services. found in the following manuals: e VAX-11l Record Management Services User's Guide e VAX-11l Record Management Services Reference RMSSHARE 2.7.2 they RMSANLZ RMSANLZ, has is to provide files. User's Utility are Record and Introduction 2.7.1 VAX-11 changes Documentation e utility; to 2.0 Changes described in Management have the been VAX/VMS additions to the on RMS is VAX-11 Services Manual made System to the Manager's RMSSHARE Guide. Unsupported Utility - An unsupported wutility program, been added to the V2.0 kit. The primary use of RMSANLZ an interactive, formatted dump of information in indexed Refer to Appendix B of the VAX-11 Guide for information about RMSANLZ. Record Management Services 2.7.3 Magnetic Tape Label HDR3 - A new label, HDR3, will appear on VAX/VMS ANSI-format magnetic tape. The 1label has been added to provide a place for some binary data that has been removed from HDR2. Until the tapes next with version both of binary version of VAX/VMS is in HDR2, and will information. VAX/VMS data in released, rely on Note that the magnetic tape version) will be able to read is released, HDR2 and HDR3 ACPs tapes 1in V2.0 produced There are no changes or additions as a component of VAX/VMS V1.6. the following manuals: RMS-11 User's e RMS-11 MACRO will After produce the next RMS 512 the next to V2.0. VAX/VMS now supports file byte records. sharing (RMS-11) to RMS-11 V1.8, which was Documentation for RMS-11] is Guide Reference RMS label. (and prior Record Management Services for the PDP-11 ® VAX-11 VAX-11] RMS will not place binary data HDR3 to contain VAX-11 RMS attribute 2.7.4 Sequential FIle Sharing - VAX-11] for sequential files with fixed-length, 2.8 a Manual 12 released found in VAX/VMS 2.9 Compatibility Mode This section affect notes on compatibility-mode system. found contains Release Notes Version Documentation changes and programming describing 2.0 additions on a to functions VAX/VMS compatibility-mode V2.0 that operating programming is in: ® VAX-11/RSX-11M User's e VAX-11/RSX-11M Programmer's 2.9.1 Change in Pl Guide Parameter of Reference IO.ATT Manual Directives - The meaning of the Pl parameter on an IO.ATT QIO RSX-11M directive has changed in V2.0. This change now makes the AME compatible with RSX-11M Version 3.2 but incompatible with previous versions of VAX/VMS. 2.9.2 AME Emulation of RSX-11M QIOS$ Directives for Unknown Devices - The AME QIO parameter mapping for unknown device types emulation of has changed. In V2.0, the equivalent to correspondence the VAX/VMS between QIO RSX-~11M parameters Pl QIO to parameters Pl to P6 1is P6. NOTE Unknown device device that line printer, tape. device. 2.9.3 MACRO-1ll1] A types 1s card null CRF Now Supported DEFINE/SYSTEM CRF a defined disk, reader, device is now supported. Add [SYSMGR]SYSTARTUP.COM; then, CRF qualifier in the MACRO-11 command $ are not - The 1s or an as any terminal, magnetic unknown RSX-11M V3,2 the following can be invoked string. program CRF.EXE DCL command by wusing the to /CR SYSSSYSTEM:CRF 2.9.4 Changes to MCR Command Language Interpreter Language Interpreter has been updated to include Version 3.2 of RSX-11lM. The MCR features Command found in 2.9.5 LIBRARY/RSX11 Library Extractions - When using the LIBRARY/RSX1ll command to extract compatibility-mode object modules from the macro 1library, you should specify the 1library type by including a file type in the library file specification. For example: LIBRARY/RSX11/0UTPUT=TT:/EXTRACT=macro Do not use the /OBJECT or incorrect example: /MACRO filename .MLB qualifiers, as LIBRARY/RSX11/0UTPUT=TT:/EXTRACT=macro/MACRO 13 1in the filename following VAX/VMS Release Notes Version 2.0 Compatibility Mode 2.9.6 versions of VAX/VMS, compatibility-mode image native-mode Utilities Now Native Mode - In previous the following commands invoked the PIP. In V2.0, these commands invoke images: RENAME UNLOCK CREATE CREATE/DIRECTORY SET PROTECTION DIRECTORY 2.10 System Programming This section contains notes that describe changes and additions to the The system programmers. VAX/VMS by used components system in found is documentation for system programming under VAX/VMS V2.0 the following manuals: e VAX/VMS Real-Time User's Guide e VAX/VMS Guide to Writing a Device Driver e VAX/VMS System Dump Analyzer Reference Manual e VAX-11 PATCH Utility Reference Manual 2.10.1 All Drivers Must Be Reassembled and Relinked - Current users must reassemble and relink all user-written drivers after VAX/VMS V2.0 has been installed. Because the executive has been reassembled and relinked, drivers also must be reassembled and relinked to ensure that the 1link with and definitions they use the correct data structure correct addresses of executive routines. version Note that drivers must be reassembled and relinked with every upgrade but not with version updates, because version updates include a patched executive, not a reassembled and relinked executive. 2.10.2 Buffered I/0 Count Quota Field Changes - In earlier versions of VAX/VMS, the PCBSW_BYTCNT, was field that contained the process byte-count quota, in the software Process Control Block (PCB). For VAX/VMS V2.0, that field has been moved to a Job Information Block new field (JIB) new structure, and has been given a longword value. the The is labeled JIBSL_BYTCNT. coding some Any driver using the byte-count quota field will require changes. For example, the code that adjusts a process's quota could have been: SUBW R1,PCBSW_BYTCNT (R4) ; 14 Adjust byte count quota VAX/VMS For V2.0 that code would Release Notes Version have to be changed MOVL PCB$L_JIB(R4),RO ; SUBL R1,JIBSL BYTCNT(R0O) ; 2.0 to: Get JIB address Adjust byte count quota NOTE It may addend When the changes have Typically, the only that perform buffered 2.10.3 1Interrupt earlier versions contained a effectively be in necessary Rl from to convert the longword. been made, reassemble and relink the drivers that need make this change are driver. drivers I/0. Dispatch of Table Can VAX/VMS, field, 1IDBSB limiting to word the UNITS, number Be the of eight. Set for More Interrupt that Than contained units 8 Dispatch attached Units Block the to one - In (IDB) value 8, controller to In VAX/VMS V2.0, that field has been changed to a word value, IDBSW_UNITS. Now, vyou can define the number of units allowed in the IDB by including the following qualifier in the Driver Prologue Table creation macro: DPTAB MAXUNITS=n,... Then, not reassemble specified, and it relink defaults After the number using the following of units the to is qualifier driver. the so 1If Version the 1.6 MAXUNITS=n value of value is 8. defined, in the you can override the value by SYSGEN utility CONNECT command: /MAXUNITS=n The qualifier is optional: wuse it only when you want maximum number of units from that specified in the DPT In V2.0, the a in each macro RKO6/RK07 Purging to driver call can driver similar to MOVL UCBSL_CRB(R5),R3 MOVL @CRBS$L BGEQ be code a used used Datapath UNIBUS to used a buffered purge to following: INTD+VECSL_ADP (R3) - adapter the purge earlier versions datapath had datapath. For the datapath ,R2 UNIBUS example, Get CRB Get config. Extract 208% was address reg. datapath INTD+VEC$B _DATAPATH (R3) ,R1 #UBASV _DPR BNE,#1,UBASL DPR(R2) [R1] #31-UBASV_DPR_ XMTER UBASL DPR(R2) [R1],R0 15 to datapath. #VECSV DATAPATH, #VECSS _DATAPATH, CRBSL In (UBA) We ASHL ASHL that UNIBUS e EXTZV the a purge we included for used W be code e New Macro VAX/VMS, W 2.10.4 of to change the creation macro. Purge datapath Transfer error? if GEQ none addr. VAX/VMS Release Notes Version 2.0 For V2.0, call and the an code error PURDPR BLBS that performs ; ; R0,20$ The PURDPR macro has been executive code the same function consists of a macro check: routine, Purge datapath, check and clear Branch if no datapath error included to allow TIOCSPURGDATAP, instead drivers to errors <call a new of having to contain the themselves. 2.10.5 Code Change Required in Some V1.6 Drivers - Any V1.6 drivers that use the status bits IRPSV PRIVIO or IRPSV_EXQUOTA in IRPSW_STS to check process privileges must be changed. A new IRP field, IRPSL ARB, has been defined that points to the process Access Rights Block (ARB) in the Process Control Block. The ARB contains both the ©process privilege mask and its UIC. Documentation for the ARB is contained in the VAX/VMS Guide to Writing a Device Driver. 2.10.6 PATCH Utility Turns Off "Last PO Cluster®TM Option - The PATCH utility can add patch area to an image file by finding the last virtual address used by the image and then creating an 1image section that uses the next available virtual address space. Both executable and shareable image files can have patch area added by this method. When you link an executable image that contains one or more shareable images, the 1linker gives the "Last PO Cluster" attribute to all the image sections from the shareable image that is positioned last in the virtual address space. This attribute tells the image activator that there are no image sections with higher virtual address ranges, thus allowing the image sections to grow without needing to relink the executable image. The image activator will automatically map any new space needed when the executable image is run., The earlier versions of the PATCH utility did not turn off the "Last PO Cluster" option when the patch resulted in new patch area. Thus, a new version of a shareable image having this option and growing in size (using more wvirtual address space) would result in the image activator over the first mapping the new new space and then mapping the patch area space. The V2.0 PATCH utility turns off the "Last PO Cluster" option for the last shareable 1image linked into an executable image when patch area is created for that executable image. The image activator checks that the "Last PO Cluster" option is off when it activates an executable image in which the shareable image has grown. By finding where the patch area begins, it can calculate that the shareable image is too large to fit into the virtual address space allocated to it, and returns the error message: SHARTOOBIG, Shareable image too big, please relink all images The executable image should be relinked against the new copy of the shareable image (and then repatched if necessary). When two or more shareable images are linked together into a new shareable image and an executable 1image is 1linked to the combined image, the combined shareable the image and the executable SHARTOOBIG message is returned. image both need to be 16 relinked if VAX/VMS 2.11 System Management This section contains and that describe affect VAX/VMS these features ® VAX-1ll1l Software e VAX/VMS System e VAX/VMS Operator's e VAX/VMS UETP 2.0 Operation notes system features that The documentation for 2,11.1 Release Notes Version changes and system management is found in: additions and to operations. Installation Guide Manager's Guide User's System Security: Guide Guide SET PASSWORD Command - One of the ways in which the security of a system can be improved is by allowing users to change their passwords. The SET PASSWORD command has been added to DCL for this purpose. To help maintain the secrecy of passwords, this command does not echo user input. To help ensure that a mistake is not made, _users must enter their password twice. 1In the following example, the text enclosed in angle brackets represents wuser input that is not echoed. $ SET PASSWORD 01d password: <old password> New password: <new password> Verification: <new password> Users can change their password manager can prevent users login flag LOCKPWD in the file. Refer to the at any time. from changing their user's record of VAX/VMS System Manager's However, the system passwords the user by setting the authorization Guide the for procedures used. NOTE All passwords will be encrypted using a new, more secure algorithm when set or changed using either AUTHORIZE or SET PASSWORD., 2.11.2 System nonprivileged currently One way to in Security: program use can prevent shareable, to cause the Terminal allocate a Allocation - The an interactive potential problem is non-filestructured to security protect devices. of that is a not problem, the The ability terminal allocation SET PROTECTION of non command format SET PROTECTION=code/DEVICE provides the capability to set the owner UIC and protection for a nonshareable device. The READ protection flag is used to allow or deny the desired allocation. Two new SYSGEN owner UIC of parameters all terminals have on been a added system: to set the TTY PROT and Currently, the protection does not restrict who terminal (due to the way the Job Controller and interact). Rather, the protection mask should be access to any <class. Since the Login procedure BYPASS privilege all users will be able to log in, able to randomly allocate the terminal. 17 protection and TTY_ OWNER. can 1log in at a the Login procedure set to allow no is started with the but none will be VAX/VMS Release Notes Version 2.0 Privileged Images and CTRL/Y - In earlier 2.11.3 System Security: at a terminal could disrupt a privileged user a VAX/VMS, versions of image by pressing <CTRL/Y> then entering commands, such as EXAMINE and DEPOSIT, that would affect the image before the image's exit handling routines could take effect, Now, 1images that have been installed privileged perform an unconditional rundown (with a call to the image's exit handlers) when a CTRL/Y interrupt is detected. The effect 1s to prevent casual interruption of a privileged 1image's exit handling routines when <CTRL/Y> is pressed. Note that the image can be installed with any privilege (not necessarily a "meaningful" one) to prevent these CTRL/Y interrupts. 2.11.4 User Authorization File Has New Format - The format of the user authorization file (UAF) has been changed in Vv2.0. The UAF file on the system disk (SYSUAF.DAT) is automatically converted to the new format during the upgrade process. If you have created other UAFs, you must convert them, using the [SYSUPD]CVTUAF command procedure, since all the VAX/VMS programs that access UAF files make the (LOGIN, conversion, AUTHORIZE, etc.) require the new format. To type: SET DEFAULT SYSSSYSTEM @[SYSUPD]CVTUAF $ $ The command procedure will prompt you for the device on which the old SYSUAF.DAT resides. You must have read access to the old SYSUAF.DAT and the ability to create files on SYSSSYSTEM. The scratch file SYSUAF.TMP 1is used to sort the old SYSUAF.DAT thereby compacting the initial population of the new SYSUAF.DAT. The AUTHORIZE utility has two commands that allow the system manager console floppy to display of a particular user's record in the UAF. The LIST command is used to create a file, SYSUAF.LIS, which then can be printed; the Both a display at the terminal. obtain to used is command SHOW System Manager's refer to the VAX/VMS commands have been enhanced; Guide for details. 2.11.5 diskette name The driver Name Device New for has been changed is now loadable. Console from DXAl Floppy - The to CSAl. To load the driver use the commands: SRUN SYSS$SSYSTEM:SYSGEN SYSGEN> CONNECT These commands the console is CONSOLE require the CMEXEC and CMKRNL not autoconfigured. privileges. Note that If you often configure the console floppy, you should protect it from unauthorized access by mounting it with the /FOREIGN and /SYSTEM qualifiers. 18 VAX/VMS Release Notes Version 2.0 2.11.6 Importance of Using the V2.0 VMB - The VAX/VMS primary bootstrap file, VMB.EXE, 1is in [SYSEXE}l on the V2.0 system binary distribution and on the console floppy diskette (label RX 1/11780 LOCAL CNSL PKG). When installing v2.0, use the V2.0 console floppy diskette. However, customers who have purchased a field service maintenance contract that includes the remote diagnosis service receive another console floppy diskette (AS-E989n-YE), which is to be used as the console If you floppy diskette have the remote after the diagnosis installation console is completed. floppy diskette, you may need to copy the [SYSEXE]JVMB.EXE file from the system, and the files DSCGEN, CRASH, and DSCBOO.CMD from the V2.0 console floppy diskette to the remote diagnosis console floppy diskette. After V2.0 has [SYSUPD]DXCOPY to the remote been [SYSUPD]BOOTUPD.COM to the remote installed, use the V2.0 command procedure to copy the ASCII files (DSCGEN, CRASH, and DSCBOO.CMD) diagnosis floppy, and the V2.0 command procedure to copy diagnosis [SYSEXE]JVMB.EXE from the V2.0 system disk floppy. NOTE V2.0 VMB, can be bootstrapped but system crash contain and the the contents V2.0 of using the V1.6 dumps will not shared memory stand-alone DSC will not boot. 2.11.7 VMS-to-VMS Network Command Terminal Capability - VMS-to-VMS Network Command Terminal capability is now available, The requirements To are: e DECnet-VAX V1.3 e REMDEVICE.DAT e RTTLOAD.COM bring up network is installed on each node in SYSSSYSTEM in SYSSSYSDISK:[SYSMGR] command terminals, execute this command: @SYSSSYSDISK: [SYSMGR]RTTLOAD This command procedure terminals process. To and runs REMACP will e DECnet-VAX e There e RTT remove RUN is is no driver REMACP, loads the RTT driver for network the not 1image SYSSSYSTEM:REMACP.EXE come up if: not up. as a command detached REMDEVICE.DAT. has not been loaded. type: SYSS$SYSTEM:STOPREM REMACP will delete itself when all network command terminates. 19 terminal activity VAX/VMS Release Notes Version 2.0 If the network is brought down, REMACP will automatically delete itself, as though STOPREM had been run. After the network is brought up, you must execute the SYS$SSYSDISK:[SYSMGR]RTTLOAD command procedure to bring up network command terminals again. If you press <CTRL/Y> repeatedly, you will be asked if vyou terminate the network command terminal session; otherwise, the session by logging out. If you intend installed. $ to The Note that SET HOST to install command, RTPAD the 1image RTPAD must the maximum number node is of inbound remote logins possible on Using the New Stand-alone DSC2 - utilities The operating procedures for 1is contained 1in the VAX-11 Utilities Reference Manual, In earlier write to versions of VAX/VMS, the error log file continually operator broadcast had to addition, operator and new restart is error intervene the to deletion account in 4. 2.11.9 New Feature for ERRFMT Process - The ERRFMT process deletes 1itself 1if it encounters too many errors while writing error log file. It also reports more specific error messages prints a warning message before deleting itself. the a 15. new version of stand-alone DSC2 are described in Section 2.2 of VAX-11 Software Installation Guide. More information on the DSC Chapter In be are: /OPEN/SHARED/PRIV=(NETMBX,TMPMBX,LOG IO) DECnet-VAX 2.11.8 the the the to RUN SYSS$SYSTEM:INSTALL RTPAD single use commands wish terminate fixed. stop command the the ERRFMT process would attempt to in spite of error conditions and would messages to ERRFMT now the and to the the procedure process To restart, be restarted. operator console,. The process. log ERFSTART.COM after in to the the problem system allows that the caused manager's type: @ [SYSMGR] ERFSTART The ERRFMT process will 2.11.10 New CRASH Command Procedure - V2.0 contains a new command procedure on the system console medium. CRASH enables you to halt the system in the event that the system hangs and does not respond to an orderly system shutdown. 20 VAX/VMS Release Notes Version To execute 1. this Press The 2. At <CTRL/P> system the The 3. command procedure, At the The system (SPR) to console, by console, then Save corresponding system by responds system console. the responds system system on type: following: the >>> prompt. HALT<KRET> displaying type: the >>> prompt. @CRASH the shutdown console file) for the console. displaying sends this dump DIGITAL perform 2.0 with 1listing a Software information to the and (and the send it Performance Report examination. 2.11.11 New Method to Change Default Lines-per-Page Value - Many native mode programs, such as VAX-11 MACRO, VAX-11 BASIC, the linker, and VAX-11 FORTRAN, paginate listing files. The default value for physical lines-per-page in VAX/VMS 1is A6, 1In earlier versions of VAX/VMS, installations that wanted to change this default value had to use the command procedure [SYSUPD]JLINEPAGE.COM to patch in a new default The and value. LINEPAGE.COM command procedure has been removed from the V2.0 kit, a new system-wide logical name has been defined: SYSSLP LINES. Assign a wvalue to this 1logical name to produce a physical lines-per-page value for native mode utilities to use in routines that calculate the number of lines to be printed on output listings. Refer to the VAX/VMS Run-Time Library Reference Manual for more information. 2.11.12 Effects of File Manager Performance Enhancements - The Files-11 file manager in VAX/VMS V2.0 contains several optional enhancements that more than double its performance. However, their presence requires that greater <care be taken in mounting and dismounting disks and in shutting down the systen. The optional performance enhancements are described in the VAX/VMS System Manager's Guide. CAUTION Because the optional caching features cause a mounted disk to appear inconsistent, running VFY2 on a disk that has been 1in wuse may result in a variety of consistent error messages. To get a report from VFY2, you must flush the caches by dismounting and remounting the disk (and making sure that no file activity occurs while VFY2 is running). 21 VAX/VMS Release Notes Version 2.0 2.11.13 New AUTOCONFIGURE Device Support - The table of UNIBUS devices recognized by AUTOCONFIGURE has been extended to include new peripheral devices manufactured by DIGITAL. Also, the CSR and vector assignments for the DR11B have been revised, Refer to Chapter 14 of the VAX/VMS Guide to Writing a Device Driver for a list of current CSR and vector assignments. Note the new devices expected by AUTOCONFIGURE in floating CSR and vector space may interfere with customer device assignments in floating space. 2.11.14 AUTOCONFIGURE Lineprinter Errors Corrected - In earlier versions of VAX/VMS, the AUTOCONFIGURE command assumed incorrect CSR addresses for all but the first line printer in a configuration. In V2.0, the SYSGEN AUTOCONFIGURE command has been corrected to look for a second line printer CSR at 774004 (instead of 764004). Also, three line printer CSRs have been added. The following table lists the CSRs and vectors for the five 1line printers: Line Printer CSR Vector 1 2 3 4 5 $0777514 $0764004 20764014 $0764024 20764034 %0200 %0170 $0174 %0270 %0274 2.11.15 Floppy Disks as Output from RSX-11S System Generation - If you perform RSX-11S system generations on your V2.0 system, either the console floppy device or an RX02 floppy device can be (among other media) the device to which the RSX-11S system image is written. If the console floppy device is used, an RX0l bootstrap is included in the RSX-11S system image. If an RX02 device 1is wused, an RX02 is the RX02 and image bootstrap is included in the RSX-11S system written in single density format. NOTE It is not prudent to use the console floppy device for these operations. DIGITAL recommends use of other output devices (such as RX02s) if possible. that an RSX-11S system image Note that the bootstraps are different: to the console floppy device cannot be bootstrapped from written was an RX02 device; an RSX-11S system image that was written to an RX02 device cannot be bootstrapped from an RX01l device. the directory use of [10,40] - Although Use of Directory 2.11.16 [10,40] has been allowed in earlier versions of VAX/VMS, it should not be used after V2.0 is installed. 1Instead, 22 use the [SYSEXE] directory. VAX/VMS The reason for this caution [10,40] will 2.11.17 8SYS Parameter enables or disables be Release Notes Version terminated is in that a support later BUGCHECKFATAL the making of for VAX/VMS - The all SYS In the default require places 2.12 This that an system into Unsupported section 2.12.1 RNO.EXE of was V2.0, the is off. fatal Thus, directory only a BUGCHECKFATAL bugchecks. 1In default was parameter BUGCHECKFATAL rebootstrapped; error notes Standard VAX/VMS, RNO.EXE for of parameter a fatal nonfatal (and the bugcheck will bugcheck just log. Software included unsupported be the contains DIGITAL versions In the entry setting setting) use parameter bugchecks versions of VAX/VMS, the BUGCHECKFATAL thereby making all bugchecks fatal. V2.0 the release. earlier set on, DIGITAL-supplied 2.0 has VAX/VMS RUNOFF the in pertaining [SYSEXE] replaced version of unsupported Replaces unsupported the been (DSR) to text software. RNO.EXE formatting - In utility earlier program directory. by DIGITAL the program Standard RUNOFF.EXE, Runoff an (DSR). NOTE Although a few exist, DSR 1is RNO.EXE. known incompatibilities mostly compatible with Please do not submit problem reports. Three To DSR are included in [SYSEXE]: Unsupported RUNOFF Table TCX.EXE Unsupported RUNOFF Two-column Index NDXDMP .EXE Unsupported RUNOFF Index utility use DSR, use type the DCL the utilities of Contents Dump utility utility command: RUNOFF /qualifiers... $ $ $ To files TOC.EXE $ To utility filespec,... provided with DSR, type the DCL RUN command: RUN SYS$SYSTEM:TOC RUN SYSS$SYSTEM:TCX RUN SYSSSYSTEM:NDXDMP obtain information about using DSR and its wutilities order the manual: DEC Note that kit, and Standard this must Runoff manual be is (DSR) not separately User's part of ordered. 23 Guide the (Order VAX/VMS No. V2.0 AA-J2A8A-TK) documentation VAX/VMS Currently, 1. there are some Restriction If you use on Release Notes Version khown using these problems the /SIMULATE qualifiers, nothing seems to happen. for a response. The work space, then will hang. 2. An You cannot a character is specify the .END feature generated the LIST number or .END of DSR by an of blank NOTE is .END lines command. .END LIST 0 no blank .END NOTE nine 9 specify any the LIST that accepts an <RET>, for underlining if you /UNDERLINE:NOSPACING. ability to or NOTE to .END be For control the and waiting type a RUNOFF have There number of command. generated, add a number to example: lines are generated blank value returned press just problem. this not you to work around qualifiers. that DSR is bug is to is no way program: however, for this or lines can If RUNOFF.EXE /PAUSE prompt Note, around <RET>. and /UNDERLINE:SEPARATE To You specify a the specified undocumented blank press with 2.0 lines would are generated be acceptable file produced to the .SKIP command. The NDXDMP utility input by the /INDEX qualifier in DSR and creates an output file with the type XMP. This file contains a dump of your index file similar to that produced by the /DEBUG:INDEX qualifier in DSR, but in an easier-to-read format. 2.12,2 Page Fault Monitor - The Page Fault Monitor is an unsupported facility that can be used to generate page fault information about a program. The following help file contains information about the use of the facilty: SYSSHELP:PFMON.HLP The procedures you use to insert HLP files into SYSSHELP:HELPLIB.HLB are found in the LIBRARIAN chapter of the VAX-11 Utilities Reference Manual. PFMOM requires the SETPRV, ALTPRI, and PSWAPM privileges. When page fault monitoring is enabled by an PFMFILWRT, 1s created. If the 1image exits fault monitoring, the PFMFILWRT subprocess does image, a subprocess, without disabling page not exit. NOTE On a heavily-loaded system, you can lose monitoring samples if the system takes a significant amount of time to create the PFMFILWRT subprocess. This is because the SSETPFM system service does not wait until the subprocess is created before returning to the calling 24 image. VAX/VMS Release Notes Version 2.12.3 Unsupported unsupported screen formatting Library. USERS, You with 2.12.3.1 Utilities utilities. use can the 1INFO - Included the screen the The in wutilities install required information about the first parameter - The package INFO.EXE so all program a process. When INFO specifies the name of V2.0 that common privileges the 2.0 kit perform in the are several video terminal VAX-11 wutilities, such users access have displays as Run-Time TALK to constantly is run as a the process and them. updated foreign command, to be displayed. While INFO is running, you can press the V key to display a map pages in the virtual address space of the process. Valid pages working set are represented by an asterisk (*); the current of in PC represented by return to INFO the first 2.,12.3.2 an SEARCH at sign (@). display. - The You INFO can requires SEARCH.EXE program press the CMEXEC space bar to the the is privilege. searches source files for a given 'string. When SEARCH 1is run as a foreign command, the first parameter specifies the name of the file(s) to search (wildcards are allowed) and the second parameter specifies the string to search for. If the parameters 2.12.,3.3 SETNAME name. When specifies the are - not The specified, SETNAME.EXE SETNAME is run as new process name. a SEARCH program foreign prompts sets for the command, them. current the first process parameter 2,12,3.4 SFA - The SFA.EXE program is a formatting file dump utility. There is a help file, SYSSHELP:SFA.HLP, that <can be added to SYSSHELP:HELPLIB.HLB, and that describes all the functions of SFA. 2.12.3.5 TALK - The video terminals to requires OPER, WORLD, 2.,12.3.6 USERS - The TALK.EXE program allows users on two different type messages interactively to each other. TALK and PRMMBX privileges. USERS.EXE program displays a 1list of all the interactive users currently logged into the system. When USERS is run as a foreign command, the first parameter specifies the user names to display; if unspecified, all wusers are displayed. USERS requires WORLD privilege. 2.12.3.7 WHO - The WHO.EXE program converts a UIC to a user name or a user name to a UIC. WHO has a help command for further information, WHO requires the SYSPRV privilege. 2.12.4 New TECO-11 Manual revised; its new order included in the kit. - The PDP-11 TECO User's Manual number is DEC-11-UTECA-B-D. The 25 has been manual is VAX/VMS Release Notes Version 3.0 PROBLEMS 2.0 RESOLVED BY VAX/VMS V2.0 All restrictions and problems noted in the V1.5 and V1.6 have been resolved, with Section 4.0 of these release notes. 26 release notes for VAX/VMS the exceptions mentioned in VAX/VMS Release Notes Version 2.0 4.0 CURRENT RESTRICTIONS AND This section lists restrictions 4.1 Command Languages known This section contains and PROBLEMS and problems. System Messages restrictions and problems known to exist in v2.0. 4.1.1 DIRECTORY Command /EXCLUDE Qualifier - The in the DIRECTORY command does not work with /EXCLUDE qualifier zero version numbers, A version number of zero should exclude the latest version of the file. Instead, specifying a version number of zero excludes all versions 4.1.2 of the file, Restriction on of Use characters are not allowed specification. The one exception (asterisk). If you enter an character (for example ;5*7), unpredictable results may Wild Card card Characters - Wild in the wversion field of a file allowed is a single character * invalid version using the asterisk an error |1is not returned and occur. 4.1.3 Effect of Wild card Operations on Devices Mounted Foreign - Any wild card operation on a device that has been mounted foreign causes an executive mode exception. If the SYS parameter BUGCHECKFATAL is set off, if BUGCHECKFATAL Refer to is set on, Section a 2.11.17 fatal of the process is deleted; bugcheck occurs. these release notes for related information. 4.1.4 Incorrect HELP Text for MOUNT Command - The HELP text for the exist 1in The text describes the command's syntax. incorrectly command MOUNT shows the device name and volume label lists enclosed in parentheses. The presence of parentheses with these parameters is incorrect. The the describes correctly User's Guide Language Command VAX/VMS command's 4.2 syntax. Program Development Tools This section contains restrictions and problems vV2.0. 4.2.1 LIBRARIAN Restrictions and Problems 27 known to VAX/VMS Release Notes Version 2.0 Using /NAMES and /LIST Qualifiers - Always use the /NAMES and 4.2.1.1 the /NAMES qualifier specify If you together, /LIST qualifiers LIBRARIAN will the the /LIST qualifier, specifying without also terminate abnormally. a Using /OUTPUT Qualifier - If you issue a command to modify the /OUTPUT specify always 1library, earlier) (or Vl.6 4,2.1.2 VAX/VMS qualifier. If you do not specify /OUTPUT, the LIBRARIAN will write the format library into the current default directory. new V2,0 be library will new the Use of the /OUTPUT qualifier ensures that written to the device and directory of the library you are modifying. LIBRARIAN Failures on Update and Insert - The LIBRARIAN 4.2.1.3 not insert will a zero-length object, help, or macro file into a library, and will give no indication of the failure. file an object One situation in which the failure can occur is when (for example, as a result of assembled been has 1length zero with this issuing CTRL/Y to the assembler). -Attempts to insert or replace object module in an OLB library will appear to be successful, while in fact, 4.2.2 the fail to do either. <CTRL/Y> May Corrupt Library - If modifying use LIBRARIAN will a library, the corrupted you 1issue the library may be corrupted. library will $LIBRAR-E-WRITEERR, result CTRL/Y a while Later attempts to in the message: error writing <filespec> -LBR-E-RFAPASTEOF, VBN in map block request past eof. Submit SPR 4.2.3 Broadcast Message Interrupts SOS Alter Mode Screen - When a broadcast message interrupts the altering of a line in SOS Alter Mode, the it did before as the screen is not restored properly (to look the character-at-a-time nature of the is The cause broadcast). terminal I/0 requests done by SOS in Alter Mode. To restore the screen to its correct state, Then, 4.2.4 you must eiter CTRL/R. the line is redisplayed up to its current position. Linker Restrictions and Problems vyou Image - If LINRER Effect on Address Space of Executable 4.2.4.1 data address relocatable creating a shareable image that contains are the equivalent), its or (using the VAX-11 MACRO .ADDRESS directive the shareable image position-independent by a mechanism linker keeps called deferred relocation (see the VAX-11 Linker Reference Manual for details). 28 VAX/VMS To guarantee shareable equal to that image the Release Notes Version the relocation to have middle 32 the bits is wvalid, default of the the global enforcing the rule be resolved 4.2.4.2 Linking independent executable that when all that shareable Multiple shareable image, link space 4,2.4.3 of the Shareable with VMSRTL, the relinked for V2,0, these shareable image these may shareable executable Images - be If The 4,2.5 VAX-1l1 The 4.2.5.1 using linker Symbolic expected, while DEPOSIT results in - Shareable images linked library, 1linked must be against did not the virtual place address = in v2.0. - Deposits of example, Data DEPOSIT H HVARIABLE will not to the if MOVQ H floating = 1.405 data will work are as work. accept literals 1longer LABEL truncation the low-order label was 32 defined bits and an appropriate as: XFFFFFFFFFFFFFFFF2,A 4.2.5.3 8String Variables debugger CALL 4.2.,5.4 Short are not correctly will decode as an command correctly. Literals - The debugger will not For example, the instruction: message LABEL: exist For H EXAMINE/INSTRUCTION diagnostic in LINK image. this H floating constants. Long the Debugger restrictions Deposits of bits. creating will prevent the problem of Library appearing in the Linked with VMSRTL does to 4.2.5.2 32 are together default run-time shareable image along with any executable 1images restricted than image images. V2.0 following time). with the thereby shareable you In previous versions of VAX/VMS, the Linker position-independent shareable 1images 1last in space. a bound images By doing so, you shared Run-Time creation the match created. 1Images that (the images linked 1is relinked, within is forces match image references Shareable images qualifier /NOSYSSHR. multiple copies of the address symbol shareable 1linker section This match forces relinking of all executable shareable image every time the shareable image must 2.0 - String variables cannot be passed 1in a command. Floating-Point MOVF decoded by Literals the ~ Short debugger. #18,RO. 29 floating-point For example, MOVF literals #4.0,RO VAX/VMS Release Notes Version 2.0 Real Variable Names - When you use the format 4.2.5.5 evaluate/addr "expression" and "expression" contains a real value is displayed. incorrect works name, an correctly: evaluate/addr "real variable" module Global Structures - Global structures declared at the 4.2.5.6 or variable (floating-point) Note however that the following format are 1level routine always not having structure as recognized attributes. You can circumvent this problem by specifying explicit the pathname desired: examine module\global structure [n] Condition Handlers - You may get unexpected behavior when you 4.2.5.7 debug a program that uses a condition handler that intercepts faults (for example, SSSOPCDEC and SSSACCVIO) and looks at the opcode whose fault. 1in the resulted execution breakpoint on such an opcode and then program's will execute a BREAKPOINT opcode in its handler condition 1f you set a In other words, your 1it, execute to attempt place. the this property: Three DIGITAL-supplied condition handlers have and FLT, LIBSFIXUP LIBSEMULATE, procedures Library Run-Time LIB$SIM TRAP. Note that LIBSFIXUP_FLT and LIBSSIM_TRAP are implicitly enabled by any compatibility-mode FORTRAN program routines ERRSET or that uses FORTRAN PDP-11 the ERRTST. The restriction does not prevent you from setting breakpoints on such it does prevent you from proceeding or stepping away instructions; from a breakpoint while the breakpoint is in effect. For example, consider a program which has LIBSEMULATE enabled a as This procedure emulates execution of G_floating, condition handler. and Octaword instructions by intercepting the fault H floating, (opcode reserved to DIGITAL) generated when these instructions are executed on VAX-1l processors which do not support them. You may set breakpoints at such instructions, and you may stop at the breakpoints, the handler but should you proceed or step away from the breakpoint, will not execute correctly. To work around this restriction, do either of the following: e wuse the When you reach a breakpoint on such an instruction, the past STEP breakpoint; the cancel to command BREAK CANCEL and use SET BREAK to reenable the breakpoint. instruction; e Use the command form SET This BREAK/AFTER:0 to set breakpoints. form clears the breakpoint once it is reached. You must reenable the breakpoint after stepping past the instruction. 30 VAX/VMS 4.2.6 +.IF VAX-1ll MACRO IDENTICAL they are or .IF .IF enclosed Release Notes Version Arguments DIFFERENT e Argument e User-defined delimiters will be considered 4.3 System Services are no The arguments directive do not of a function VAX-11] MACRO properly when in: (within known as Run-Time Library This section contains brackets) IDENTICAL ABC,abc will be properly the directive .IF IDENTICAL <ABC>,<abc> different. and I/0 restrictions 4.4 angle delimiters For example, the directive .IF resolved as identical, while There - 2.0 or restrictions problems. and problems known to exist in v2.0. 4.4.1 DEBUG Restriction When Using Condition Handlers - If you are using the Run-Time Library procedures LIBSEMULATE, LIBSFIXUP_FLT, or LIB$SIM_TRAP, there is a restriction on breakpoints in the Debugger. Refer to Section 4.2.5.7 of these release notes for details. 4.4.2 LIBSADDX and LIBSSUBX Produce Incorrect Default Length - The procedures LIBSADDX and LIB$SSUBX perform multi-longword addition and subtraction. Currently, they both incorrectly default the number of longwords to be processed if you omit the fourth parameter (length). To prevent argument function the problem, list. When correctly. the specify length the number parameter is of longwords specified, the in the procedures 4,4.3 Lowercase TPAS Symbols Not Recognized - When creating state tables for LIBSTPARSE, a VAX-11 MACRO problem can prevent TPAS symbols from being recognized if they are entered in lowercase characters. For example, the symbol TPAS EXIT 1is recognized, but the symbol tpa$_exit is not recognized. To prevent the problem, always - specify TPAS symbols in uppercase known to exist characters. 4.5 VAx—il Record Management Services This section contains restrictions and V2.0. 31 problems in VAX/VMS 4.5.1 Restriction the COPY command, only to to disk. To on Copying VAX-11l] RMS copy record-oriented CONVERT This target device in the command, also was present the DEV characteristics are field is a in with of files CONVERT MCR and Files files to - By use of can be copied magnetic utility tape should be or used. CNV. V1.6, on the the Parse device FAB. the DEV - A successful characteristics If process-permanent returned 2.0 Indexed indexed indexed Returned returns routine and and RMS-11 by service SYSSPARSE and the Device Characteristics SYSSPARSE the Relative relative relative devices, invoked restriction 4.5.2 the is Release Notes Version the target file, field to for the device however, of call the no FAB for device remains unchanged. This restriction 4.5.3 also 1Incorrect was present BLISS-32 SYSSLIBRARY:STARLET.REQ, protection XAB in V1.6, Definition in the BLISS-32 incorrectly VAX-11 defines these SYSSLIBRARY:STARLET.REQ file definition protection for - the access In file bits: XABSV_NOREAD XAB$V_NOWRITE XABSV_NOEXE XABSV_NODEL If you you in are <can the REQ VAX-11 file creating the L32 0,0,1,0%; = 0,1,1,0%; 0,3,1,0%; MACRO XABSV_NOEXE = MACRO XAB$V_NODEL = associated and Current VAX-11 access opened for is are (as XABs, definitions described in the UPI VAX-11] been (user record - VAX-11 independent RMS opened access provided NOREAD, owner, XABS$SM_NOWRITE, RMS currently access to has files that access. specified, have of the system, structures. XABSM Problem processes shared any data correct, either performing have values, are Sharing has that for Access other sharing and File allows processes and mask XABSM NODEL, that RMS protection correct 0,2,1,0%; definitions are used to reference or world subfields as independent the file use the documentation): = that that substituting XAB$V_NOWRITE problem I/0 programs by XABSV_NOREAD 4.5.4 RMS BLISS-32 problem before BLISS-32 XABSM_NOEXE, When this MACRO These a VAX-11 MACRO group, Note coding correct should for operations, interlocks) sharing. 32 file set restrict sharing access to using VAX-11 using Block or are and specify only read VAX/VMS Release Notes Version 2.0 Currently, there are two ways open a file that should be shared 4.5.5 an independent process can restricted to those processes improperly performing access: e A process using Block I/0 write to a shared file. e A compatibility-mode 1it. This and specifying program can presents a open or write for RMS the compatibility-mode program to correctly change the file. a UPI can open and shared file and read since there is problem, to synchronize 1Incorrect Status Return when File Opened for Block with 1I/0 no way VAX-11 - When you open a relative or ISAM file for Block I/0 (the BIO FOP option is specified), area and key XABs are not filled in. The status returned should be OK_NOP. However, the status SUC is returned, instead. Both SOPEN and the $DISPLAY, incorrect The XABs are not file's prologue, To prevent (the BRO allows the if the BIO FOP option is specified, will return status. the filled in because which is not read problem, open FOP option is file's prologue the the information required is in when Block I/Q is specified. file for Block the I/0 and Record 1I/0 file in this manner information to be specified). Opening a to be read and all XAB returned. 4.5.6 Magnetic Tape Restrictions and Problems - This restrictions and problems known to exist section contains in Vv2.0. 4.5.6.1 MBA/TM0O3 ECO Prevents Magnetic Tape ACP Failures - There are some magnetic tape ACP failures that have been caused by an MBA/TMO03 hardware problem, If a parity error occurs occasionally information on a data transfer from magnetic tape, will be written to the ACP address space outside of the data buffer. The result wusually 1is invalid MTAACP queue addresses, an unexpected system service exception, and a system failure. This problem can be following hardware prevented ECOs: by having field service apply ' the M8276-TW004 M8277-TW007 70-13627-TW003 4,5.6.2 Magnetic Tape ACP Error Can Cause Process to Hang - A problem in the magnetic tape ACP can occur when a bad tape causes an error immediately after a file has been accessed on the tape. 33 VAX/VMS Release Notes Version 2.0 The problem occurs when the ACP has cleared the I/0 packet address before it can reference the address to return the error to the user process. The ACP then takes an exception and disappears, resulting in the user process waiting for the ACP to complete the request., Because the ACP has exited without deaccessing the file, both the process and the If tape drive are hung. the problem occurs, process and free the you must tape reboot the system to eliminate the drive. 4.5.6.3 Appending Records to an ANSI Magnetic Tape File - There |is only one way to append records to an existing ANSI magnetic tape file:. you must open the file with put access, which positions the tape after the last record in the file. You cannot use the NEF bit of the ROP if you want to append a file (without truncating) because the NEF bit causes the records tape to to be positioned at the beginning of the file. If you then use GETs to position the tape at the end of the file, certain EOF conditions are latched, preventing you from putting into the file at that point. Unfortunately, vyou will not receive an error until a number of PUTs have been executed (VAX-11 RMS blocks records to the tape, and the error 1is not detected until a complete block is written). As a result, put 4.5.6.4 access is not allowed. EOF3 Label Not Written on ANSI Magnetic Tapes - A HDR3 label has been added to ANSI magnetic tapes written by VAX/VMS. Although HDR labels and EOF labels are supposed to be symmetric, no EOF3 label has been added. This could be a problem for tape volumes that are created for interchange with foreign (non-DIGITAL) systems that do not tolerate nonsymmetric labeling. To prevent such problems, use the MOUNT command's /NOHDR3 qualifier when mounting the volume. 1In this case, the HDR3 is not written and the labels within each file will be symmetric. 4.5.6.5 Continuation Tapes Run Away |if Not Initialized - When creating multivolume tape sets using new maghetic tapes, always initialize the continuation tapes before creating the tape set. I1f you do not initialize the tapes, continuation tapes may run away. The reason is that the magnetic tape ACP always information on magnetic tapes: if the tape has it may run away. validates protection never been written on, 4.5.6.6 Foreign Tapes Run Away if Not Initialized - Before mounting a cause runaway condition. new magnetic tape foreign, you should initialize the tape as an ANSI tape (as described in the VAX/VMS Command Language User's Guide, INITIALIZE command). If you do not first initialize the new tape, the MOUNT/FOREIGN command, which always attempts to read the tape, could a 34 VAX/VMS Release Notes Version 2.0 for support RMS X3.27-1978 - VAX-11 Support Level for ANS 4,5.6.7 structures is based on, but not strictly equivalent to tape magnetic the ANS X3.27-1978 "Magnetic Tape Labels and File Structure for Management Record VAX-1l1] the to Refer Interchange.” Information Services Reference Manhual, Appendix B for a description of the format supported. 4.6 Record Management Services This section contains for the PDP-11 restrictions and (RMS-11) problems known to exist in following two v2.0. Restrictions on 4.6.1 Use restrictions were known 4.6.1.1 Containing Records RMSIFL of problems Utility - The in VAX/VMS V1.6, Duplicate Key Order - RMS-11 routines maintain a first-in, of records containing duplicate key Values first-out values. May When Lose Input RMSIFL sorts (FIFO) ordering records, this order can change unpredictably, depending on how the records occur in the sort work files when the work files are merged. 4.6.1.2 Large Bucket and Record Sizes Can Cause Command Line Termination - RMSIFL does not limit bucket or record sizes for input or output files. However, unusually large bucket and record sizes may cause RMSIFL to terminate the command line (especially if RMSIFL must sort the 4.6.2 input file). Restrictions restrictions were 4.6.2.1 to Use discovered of RMSRST after V1.6 was Version Number Failures with /SE Utility - The following released. Switch - RMSRST interprets version numbers in the file specification as octal numbers., Thus, if you specify a number containing an 8 or a 9 in the file specification using the /SE switch, RMSRST terminates the command line with the error message: /RST —-- SYNTAX ERROR - NN For example, RST causes command line: *,*=MT:FILE.SKP/SE:DATA.DAT;19 the /RST the following —-- SYNTAX error message ERROR - to be returned: 19 One way to work around the restriction is to specify a wild card character for the version number. All versions of the file specified will be restored; you can then delete the unwanted files from the disk. 35 VAX/VMS Release Notes Version 2.0 4.6.2.2 switch use or /RA exist in /RC and /RA Switch Usage Prohibited - Use of the /RC cause can these RMSRST to fail to restore requested files., Do not switches. Compatibility Mode 4.7 This section contains restrictions and problems to known v2.0. 4.7.1 Loops FLX Receiving after INVALID DEVICE Message - Under certain conditions, FLX may loop after displaying the error message: FLX -- INVALID DEVICE and If this occurs, press <CTRL/C> to interrupt FLX execution to the command 4.8 return interpreter. System Programming This section contains restrictions and problems to known exist in VZCOI 4.8.1 SDA SET OUTPUT Command Produces Error - When using the System Dump Analyzer (SDA) SET OUTPUT command, an error is produced when a process-permanent file (such as SYSSOUTPUT) is specified. To reestablish your output stream to your terminal, use SET QUTPUT TT:. 4.8.2 PATCH Utility Problems - Currently, PATCH does not support some abbreviations allowed by the VAX-11 MACRO assembler. the error message it produces in these situations: Unfortunately, $PATCH-E-NOENCODE, cannot encode instruction <instruction> is the same message used when the instruction syntax is invalid. A common cause of this error is a displacement mode address that is not preceded by an explicit displacement size operator (B®, W*, or L."). For example, the operands 4(AP) and @4(AP) should be written B~4(AP) and @B"4(AP), respectively. Note that the assembler allows the operand @O0 (AP) to be abbreviated @(AP): this operand should be written as @B"0(AP). PATCH does not provide for the representation of long literals that are less than 64 in unsigned magnitude. PATCH will try to express (The I” and S° operators are not such numbers as short literals. supported by PATCH). Should an assembly/disassembly problem be encountered in PATCH, it can be circumvented by patching in noninstruction mode. 36 VAX/VMS Release Notes Version 2.0 4.8.3 exists Restriction on Using Interlocked Queue Instructions - A problem in the 11/780 microcode for the new queue instructions INSQTI, REMQHI, and REMQTI) that causes incorrect (INSQHI, if operation any page fault 1is incurred while referencing queue elements. The error manifests itself as a failure to correctly back up the PC to retry the instruction. be elements must To avoid this problem, all pages containing queue for valid guaranteed otherwise or set working the into locked For the DR780 this will mean that the reference without a page fault. buffer area must be locked in the working set by means of the command SLKWSET system service. 1In the case of MA780 shared memory global to lock those pages in the working set need no is there sections, to references and mapped since they are valid at the time they are them do not incur page faults. These new queue instructions are intended primarily for use with the DR780 and MA780. They should not be used in other applications until this problem is corrected. 4.9 System Management and Operation This section contains restrictions and problems known to exist in V2.0. 4.9.1 AUTOCONFIGURE Command of SYSGEN Utility - The AUTOCONFIGURE command of the SYSGEN utility can disrupt I/O activity on an active To controller if the command is used to reconfigure that controller. they when inactive are ensure that controllers prevent the problem, are autoconfigured. 1is autoconfigured during Because the system boot device controller system initialization, a device timeout error may be logged each time the system is bootstrapped. You can probably ignore a timeout error immediately following the is logged for the system volume that the device driver will correct the timeout mounting of that volume: error by retrying the I/0 operation. 4.9.2 Two SYSGEN Parameters Not Supported - The SYSGEN parameters BJOBLIM and NJOBLIM are not supported. To control the maximum number of batch jobs, adjust the job limits on the batch queues. To control amount of DECnhet-VAX activity, use the NCP maximum 1links the parameter. 4.9.3 Generating RSX-11S and RSX-11M DECnet - You cannot perform A RSX-11S or RSX-11M DECnet generations on a VAX/VMS host system. the prevents interpreter language command problem in the MCR successful execution of the indirect command files that are used. 37 VAX/VMS Release Notes Version 2.0 4.10 EDT Computer-Assisted Instruction Course There are two known EDTCAI problems. In module 2, Objective 1, Subobjective B ("Repetition of Insertions"), the cursor is not positioned as EDT will position it. When any section of the course is running, BROADCAST to the terminal is not allowed. The terminal is in PASSALL mode, which prohibits all broadcasts. 38 VAX/VMS 5.0 NOTES TO This section PUBLISHED contains Release Notes Version 2.0 DOCUMENTATION notes that correct or supplement published documentation. 5.1 VAX/VMS I/0 Users's Guide 5.1.1 Foreign Magnetic Tape supplements the material on Sections 4.4.4 and 4.4.5 of the Skip Functions - The following note skip file and skip record functions in VAX/VMS I/0 User's Guide, A skip file or skip record operation following conditions exist: e The tape is mounted e Two consecutive is terminated when both of the foreign tape marks are encountered 1in the forward direction The tape is left positioned between the two tape marks. Status Block (IOSB) returns the status SS$_ENDOFVOLUME and number of files (or records) skipped. The status returned of records (or detection bytes of between in the files) IOSB is SS$ skipped ENDOFVOLUME. during the The The 1I/O the actual actual number operation prior to the of the second tape mark is returned in the high-order two the first longword of the IOSB. The tape remains positioned the two Subsequent tape skip marks. record (or skip file) requests from this tape movement zero. postition will terminate immediately, producing no net tape and returning the SS$_ENDOFVOLUME status with a skip count of For more information, 5.1.2 DR780 the material see Section Support Routines in Chapter 11 of 2.5.2 of these - The following the VAX/VMS I/0O release notes. information supplements User's Guide, The documentation implies that the input queue of the DR32 can be preloaded (using a call to XFSPKTBLD) before starting the DR32 (using a call to XF$SSTARTDEV). Although this is true, note that at least one packet has must been be built and released onto XFSPKTBLD is the only support routine which notifies the DR32 that there queue the input queue after the DR32 started. that it must that sets the DR32 "go" are command packets on the bit, input process. Chapter 11 also refers to a "context array," an array that the wuser makes available to the support routines, which use it as a common storage area for information on the status of the current transfer, The information in the DR32 transfers. The copy of the fields of context array next eight longwords make up the by the driver to define ranges of parameters of the is useful when you are debugging first eight longwords of the context array are a the most recently completed command packet. The current command command transfer. 39 table, a and data data structure used memory and other VAX/VMS A useful memory and at address offset to know CTX$SL while CMDBLK FREEQ queue headers, DR32 and longwords Release Notes Version debugging in which the context Byte Offset array has the form the following the context the application program, of the command block. The is address array. The of command INPTQ, TERMQ, communication path between can be found in the the first six "go" bit format: Bits Contents 7:0 64:0 I/0 11:8 31:0 Device and 15:12 31:0 buffer size 19:16 31:0 Buffer address 23:20 31:0 Residual memory 27:24 31:0 Residual DDI 31:28 31:0 DR32 status 35:32 31:0 Size of 39:36 31:0 Address of 43:40 31:0 Size data 47:44 31:0 Address of data 51:48 31:0 Address of pre-AST 55:52 31:0 pre-AST parameter 31:16 Reserved 15:8 Flags 7:0 Data status block command byte byte count count longword command of control (DSL) block command block block block routine rate 59:56 31:0 Address 63:60 31:16 Event flag number 15:0 Number of buffers 67:64 31:0 Address of 71:68 31:0 Packet AST 75:72 31:0 Size 79:76 31:0 Address of IDEVMSG array 83:80 31:0 Address of ILOGMSG array 87:84 31:16 Size of IDEVMSG 15:0 Size of ILOGMSG 31:0 Address 91:88 2.0 of to receive packet AST address routine parameter each of the buffer free 40 in memory BARRAY list of the VAX/VMS 5.1.3 11 Documentation of the Release Notes Version Error VAX/VMS I/0 - There User's Device Control Message in Descriptions, should read: This function specifies transfer message field of directs this packet. the «controlling Control One byte ® One byte into the The device command 5.2 VAX-11 This section magnetic user tape code of device message 1length RMS to device Message following Code the message function information over XF$B_ PKT MSGLEN) (offset XFSB_PKT_ MSGLEN) packet message field Management (offset Services XFSB_PKT_DEVMSG) Reference information tapes are the on considered tape will write last successful operation as the context, VAX-11 RMS will record a 1into the Manual the handling of foreign the Note that than 18 5.3 VAX/VMS SPACE, both and you and size supplements first constant with of devices. data. when a file is closed only PUT, or WRITE. Any or from user the being with for written. both a example) block CREATE, size VAX-11 RMS the BLS and MRS fields an OPEN, VAX-11 RMS will from must reading GET, specifies tape size from tape with sizes both CREATE, REWIND, the The for be the MOUNT command. specified short as greater blocks. information word in the messages bytes 'without of expects format: the on the user message use of messages buffer the SSNDACC to the must be system accounting the symbolic ACCSK_INSMSG. remainder count that a information record problems The S$SSNDACC system service file to have the following The if access blocks System Services Reference Manual This section service. The EOFs) marks and record access the record block prevent (two tape of tape, but is responsible file information. READ, records When block size When you block to block non-file-structured collection operation was preventing size. will take the in the FAB. tape marks (OPEN, clears 132 Write packet treats other @ message the Control the (command supplements the Note send in Chapter the Control control Device to can write multiple files on the positioning and interpreting of e a contained in of tapes. when take Device command Record RMS VAX-11 and Write DR32 11-2, of is error documentation of command Foreign magnetic VAX-11 The documentation The Interconnect: e e Table the DR a Guide. This far-end the device. is 2.0 of that any the first are error. SSNDACC system service to buffer byte 133 is (just to 200 Messages a like counted an bytes longer string, .ASCIC long than will 200 return SSS_BADPARAM status 41 with the string). be truncated bytes in RO. cause to the VAX/VMS Release Notes Version 2.0 VAX-11l] PATCH Utility Reference Manual 5.4 PATCH has a command qualifier that is not documented in the manual. [=n] /VOLUME Requests that the output file be placed on a specified relative volume of a multivolume set. wvalue the n, for value If you specify /VOLUME without supplying a 1If relative volume number of the input image file. the to defaults an in is placed you do not specify the /VOLUME qualifier, the file arbitrary position within the multivolume set. VAX/VMS UETP User's Guide 5.5 This section supplements information on determining parameter settings for running UETP. on UETP running for settings Table 4 contains suggested parameter depend settings parameter The confiqgurations. VAX-11/780 average-size upon: the system disk size of e The e The VMS parameter file selected when the VAX system is booted e Physical memory size Note that the table also contains the suggested number of UETP to run, given the size of the system disk and physical memory. loads to not guaranteed The parameters represent a starting point and are increased in can be value The NPAGEDYN system. on every work UETP the during increments of 10000 if a larger confiquration hangs test. Table 4 Suggested UETP Parameter Settings RKO07-based Systems: System Memory Sizes Parameters (up) 256K 512K 748K 1024K PAR file 4USER.PAR 8USER.PAR 1AUSER.PAR 32USER.PAR UETP loads 4 12 18 22 Swapfile size 4000 5120 7168 8192 Pagefile size 5120 7000 10000 10000 NPAGEDYN 50000 70000 90000 130000 WSMAX 150 200 200 200 SYSDUMP .DMP 1028 2052 3076 4100 (continued on next page) 42 VAX/VMS Release Notes Version Suggested RP06/RM03-based Table UETP 4 (Cont.) Parameter 2,0 Settings Systems: System Memory Sizes Parameters PAR 256K 512K 768K 1024K 4USER.PAR 8USER.PAR 1AUSER.PAR 32USER.PAR 4 20 30 40 file UETP loads (up) Swapfile size 8192 24000 24000 24000 Pagefile size 16384 24000 24000 24000 NPAGEDYN 60000 use default 90000 130000 WSMAX 150 use default 500 500 SYSDUMP .DMP 1028 2052 3076 4100 5.6 VAX/VMS Command Language User's Guide The following information supplements the information on the COPY command. In general, set to the COPY command requires a minimum of A0 pages of working The larger the working set available for COPY, the more run, efficient COPY If large records size greater specified, 5.7 becomes. (greater than 512 bytes) than bytes 2048 a working set larger are being copied, (on magnetic than A0 tape input pages may be or or a block output) required. VAX-1ll1l Utilites Reference Manual The message incorrect. name defined in Section 8.3.1.3 Replace the definition with the (the Message utility) following: name Up to 31 characters, as long as the message symbol made up of the prefix and name does is combined with the definition to make not exceed 31 characters. defined prefix symbol up the message 43 symbol. This symbol name facility the in VAX/VMS Release Notes Version 2.0 6.0 INSTALLING This section VAX-11 AND TESTING describes COBOL-74 on a how VAX-11 to VAX/VMS COBOL-74 install V2.0 and verify operating the 1installation of system. CAUTION If you have installed VAX-11] COBOL-74 on an earlier version of VAX/VMS, do not reinstall it after upgrading to VAX/VMS v2.0. VAX-11 6.1 Installing The distribution diskettes You VAX-11 kit BIN RXO01 VAXC742 BIN RXO01 VAXC743 BIN RX01 use of COBOL-74 for VAX-11] COBOL-74 includes three floppy labeled: VAXC741 product Software Continue to use the version COBOL-74 already installed. these diskettes to install installation procedure Installation Guide. the product. described in Follow Section 6.2 the of optional the VAX-11 NOTE The release notes for VAX-11 are in the File C74UPD.DOC distribution floppy diskette VAXC741 BIN RXO01l. To install VAX-11 COBOL-74, perform the steps COBOL-74 on the labeled described in Section 6.2.1 of the VAX-11 Software Installation Guide. However, instead of performing step 2, assign the logical name SYSSLIBRARY to the disk and directory that contains v2.0 of VAX/VMS, The installation procedure runs under the control of the command procedure copied from the first diskette (VAXC741 BIN RX01l). The command procedure copies the files from the floppy diskette, and upon completion, dismounts the device and requests the next floppy diskette (VAXC742 BIN RXO01): Please put the second COBOL-74 44 kit floppy in the drive VAX/VMS Release Notes Version 2.0 Remove VAXC741 BIN RX01l. When The BIN RX01 following Are you ready you are ready, to from the drive, message is and replace displayed. it with VAXC742 continue? type Y<RET>. second the from files the copied After the command procedure has floppy diskette, the following message is displayed on the terminal: Please put the third COBOL-74 kit floppy in the drive Remove VAXC742 BIN RX01 from the drive and replace it with VAXC743 BIN RX01. The following message Are you ready When you ready, The installation are to is displayed. continue? type then Y<KRET> continues to completion without further intervention. When the procedure is completed, the following message is displayed: Installation of COBOL-74 The time required to install has completed VAX-1]1 successfully COBOL-74 is approximately 30 minutes. When the installation is completed, the messages described in Section 6.2.3 of the VAX-11 Software Installation Guide will be displayed. You can terminate the session, or install other optional software products, NOTE the places procedure The installation file C74LIB.EXE in SYS$SYSTEM. You can use this shared image as an alternative Linking with to SYSSLIBRARY:C74LIB.OLB. a shared 1image 1is described in the VAX-11 COBOL-74 User's Guide; described 1is installing a shared image in the VAX/VMS System Manager's Guide. 6.2 Verifying Installation of VAX-11 COBOL-74 been has compiler COBOL-74 VAX-11] the of After the installation completed, the following sample test programs should be run to verify that the compiler is operating correctly. ' There are three sample test programs in the distribution kit: I0001.COB I0002.COB I0003.COB 45 VAX/VMS Release Notes Version 2.0 I0001.COB creates disk. I10002.COB a sequential creates a disk file relative named PD1101 on the disk file named PD1102 system disk. 1I10003.COB reads PD1101 from the system the file in formatted form on the system disk. disk and system on the 1lists There is also a file named UETPC74.COM, the command procedure for the sample test programs. All four files are copied into the directory [SYSTEST] during the COBOL installation procedure. To use the sample l. Log 2. Issue to in test under the the SET DEF At the the perform privileged the following steps: system manager's following SET commands proper SET UIC 3. programs, to set account. the UIC and directory defaults: [1,4] [SYSTEST] terminal, type: QUETPC74 Each sample test program should run to a successful completion. NOTE The following your CVTTP If this your ECO message may appear on terminal: ECO not message local installed does DIGITAL representative. 46 appear, field contact service VAX/VMS Release Notes Version 2.0 A.0 PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED This appendix contains applied to the V2.0 listings system patches for files journal of the Microfiche Kit was source after the manufactured. 1. SYS.JNL;1 2. RMS.JNL;1 47 VAX/VMS PATCH Version 2,28 Release Notes Version 16=Nov=1979 IMAGE FILE BEING PATCHEDS JOURNAL FILES DATE/TIME OF PATCH3 " DBAYI[SYSEXE]SYS,EXEs1" ",DBAKE [SYSEXE]SYS,JNLL" TeAPR=198y Image does nmot contain local symbols Some or all global symbols not accessible PATCH>SET ECO | PATCH>DEPQSIT/AS 802up2ese="vea,2’ "X2QK* BOARV26SDY olds ’Ve,d* BRRR2650F news PATCH>DEPOQOSIT/AS BOB13FB2=’V2,d’ old:s BRR13FB28 ’XBGK* ‘ve,.,a’ BAQ13FB2: new! PATCH>»UPDATE Updating image 2.0 file ,DBAQs [SYSEXE]SYS,EXE2 PATCHEXIT 48 11118:20,46 VAX/VMS PATCH IMAGE Version FILE 2,28 BEING Release Notes Version 16=Nov=1979 PATCHED: ", DBAYS [SYSEXE]RMS ,EXEy 1" ,JUNLy LY "L DBAUS ISYSEXEIRMS JOURNAL FILES DATE/TIME OF PATCH: APATCH»I=NQLCL, APATCH=I=NQOGBL, PATCH»SET ECO 1 2.0 9=APR=1984 12:112128,96 1mage does mot contain local symbols some or all globe) symbols not accessible PATCH»SE PAT NEW>» “XQ@Q00FuUQ9 PATCH»RE LOC> /1 *X@QQ@a2s4ds OLD> OLD> NEW> NEW> NEW> *MOVL BTM"XQ0Q20001B8(RY),B ""X00d0a6B(RI)"’ EXIT *BLBS R, X1’ ?MQOVL. RQ,R2* ’BICB2 #1,B8"2A(R4)’ NEW» NEW» NEW>» NEW> *MOVL B"2@(R9),RD* °BICB2 #1,B"2A(RQ)* *"CLRL R@* NEW> NEW> NEW>» oldt olay news news news news news news news news! *BSBW QaACT7’ *BRW "X0000260D° X0 $MOVL B**X0@022018(R4),B*""XA000n06Q(R9)"* EXI PRPB2S54BT QAR0ess50: BRE025483 PP@AN2551: Have2sses 0025531 PAB: BLBS YOeAF4QBs NQOAF40Es VORAF412: MOV BISB2 JMP NOP NOP NOP B*18(RY4),B"6QA(R9) #02,B3A(RY) L*PaB RQ,Xd MOV, Ro,R2 BICB?2 21,8 0A(RY) MOVL B*22(R9),RY news news newt RRBF4168 QAPAF41ALY @e2aFuiCs BICB? CLRL JSB news news Xes MOVL guedrFaeDs B"18(R4),B8"60(R9I) BISB2 #22,B"RA(RY) news news PeOAF422s QRAAF431y symbol "X0" symbo) "X2" PATCH»RE /] LOC> OLD> JMP JMP #A1,B"RA(RY) R LTMD00n0aRnACY L*adne26eD L*22802554 defimed as 20202565 redefined from 20032565 to ANVWAF4LRB “X@RO@2BCF ‘BBS #TMXQ00000006,B8°"X20000n33(R9),*xannaeCuB’ OLD> °*RISB2 oLD> NEW> EXIT “BBC #"X00000206,8""X00030r33(R9), X1’ NEW> *BBC #TMXQ0000082,R""X¢avunE33(R9),"Xudve2CaBs’ ’X1 3BISB2 NEW> NEW> NEW>» NEW> #"XJQ0QBQYQQ1,B""XPRAQA033(R9)"* "MOVZWL #°XQ000B4SY4,Rp"* *POPR #"X2upun93C’* *RSH’ #TMXyRop2an1,B "XuQa00r33(R9)”’ 49 VAX/VMS Release Notes Version NEW> old? olds EXI vepeeBRCF: newt new?} BBS #26,8"33(RI),00P42C 01 pred2eD4s AvYReBCFY BlISHBe JMP #31,B°33(R9) L®BA0BFU37 Ap022B8D5: NOP new! dueoa2BD6: NOP news A¢0ee2B07: NOP new! new! BOQWFA37: POQAFA3Ce: ARBC BBS #26,B"33(R9),x1 #22,R"33(R9),Q209F447 news Q00AF 441y JMP L*2Qv02C 3B new} AARAF 447t MOVIWL K#AB4S4,R4 news WARAF44Ce: POROF 458y POPR RSB BA93C news news X{s news symbel "X1" symbol "X1" PATCH»RE /1 LOC> OLD>» OLD> OLD>» oLD>» NEW>» NEW> NEW> NEW> NEw> BISBZ BRARF 4553 2.0 #41,B%33(R9) JMP L"234322B08 defined as UA@I2BE?D redefineg from QVA22BE3 to WBVOBFUS] *XPAU22CHE *MOVC3 R1,(R3),(R2)* °*POPR &°XPR20Q93C"’ ‘RSB’ EXITY *MOVC3 R1,(R3),(R2)"* *MOVL #"X2Q0000081,R2"* ‘*POPR #"X@p22@93C”* *RSR’ EXI olds olds olds geQeeCches Ae@adece2:s MOVC3 POPR Ri,(R3),(RQ) #993C PEpr2Cees RSB news ABPV2CSEL news 20Q02C648 JMP NOP news news peae2c6S: Wenaecess NOP news APAOF4SB: news BRRAFUSFy MOVC3 MOVL Ri,(R3),(RW®) #B21,R0 #AQ3( L*0200F458 NOP news POAOF 4621 POPR new! dDNRF4661 RSB news PATCH>»U WRBRFUeTs JMP Non=contiguous image file XPATCHeJ=WRTFIL, updating L*roadece7 being image written file ,CBAQI[SYSEXE]JRMS,,EXEs2 PATCH»EXI 50 VAX/VMS Release Notes AA-DO15C~TE READER'S COMMENTS This form is for document comments only. DIGITAL will use comments submitted on this form at the company's discretion. If you require a written reply and are eligible to receive one under Software Performance Report (SPR) service, submit your comments on an SPR form. NOTE : Did you find errors page in this manual? If usable, so, and well-organized? specify the error and the number. Please indicate UOO000d Please cut along this line. Did you find this manual understandable, Please make suggestions for improvement. the Assembly type of language Higher-level Occasional reader that you most nearly represent. programmer language programmer programmer (experienced) User with little programming experience Student programmer Other (please specify) Name Date Organization Street City. State Zip Code or Country — — — Do Not Tear - Fold Here and Tape No Postage Necessary if Mailed in the United States BUSINESS REPLY MAIL FIRST CLASS PERMIT NO.33 MAYNARD MASS. POSTAGE WILL BE PAID BY ADDRESSEE BSSG PUBLICATIONS TwW/A14 DIGITAL EQUIPMENT CORPORATION 1925 ANDOVER STREET TEWKSBURY, MASSACHUSETTS — Do Not Tear - Fold Here Cut Along Dotted Line - 01876
Home
Privacy and Data
Site structure and layout ©2025 Majenko Technologies