Digital PDFs
Documents
Guest
Register
Log In
AD-L034A-26
July 1985
176 pages
Original
16MB
view
download
OCR Version
14MB
view
download
Document:
VAX/VMS
Order Number:
AD-L034A-26
Revision:
000
Pages:
176
Original Filename:
ad-l034a-26.pdf
OCR Text
VAX/VMS July 1985 AD-L034A-26 SQHWOre VAX/VMS SYSTEMS DISPATCH Published by Corporate Administrative Services Group, Software Services Digital Equipment Corporation 129 Parker Street (PKO2/E49) Maynard, MA 01754 The VAX/VMS Systems Dispatch contains new and revised Software Product Descriptions, programming notes, software problems statements and responses. Much of the material is developed from Software Performance Report (SPR) answers significant to the general audience and is printed here to supplement the maintenance updates. DECnet-VAX VAX-11 CORAL-66 VAX-11 SPM DECtype/VMS VAX-11 DATATRIEVE VAX-11 TDMS ReGIS Graphics Library VAX-11 DBMS VAX-11 2780/3780 Protocol RTEM-11 VAX-11 DECalc VAX-11 ADE VAX-11 DECOR VAX-11 BASIC VAX-11 DIBOL VAX-11BLISS VAX-11 DSM VAX-11C VAX-11 FMS (Cross Compiler) VAX-11 CDD VAX-11 FMS VAX-11 SORT/MERGE VAX-11 COBOL VAX-11 FORTRAN VAX-11 COBOL/74 VAX-11 MUX200 Emulator VAX-11 3271 Protocol Emulator ( FORTRAN IV/VAX to RSX VAX PDP-11 DATATRIEVE/ VAX-11 PASCAL VAX VAX-11 PL/I DISTRIBUTION The VAX/VMS Systems Dispatch is directed to one software contact for each software product. No mailing will be made to addresses without a software contact name. Address change requests should be sent to the nearest DIGITAL field office. Include the new address and mailing label from the most recently received publication. Software binary and sources are provided under licenses only. The standard Terms and Conditions, OEM Agreement, and/or Quantity Discount Agreement contain the licenses for all binaries other than DECsystem-10. Ernie Savoie, Associate Editor Copyright © 1985 Digital Equipment Corporation believes the information in this publication is accurate as of its publication date; such information is subject to change without notice. Digital is not responsible for any inadvertent errors. Comments on the contents of this publication should be directed to your local Digital Field Office. TRADEMARKS of DIGITAL EQUIPMENT CORPORATION Maynard, Massachusetts DEC DECUS DECnet DECsystem-10 DECSYSTEM-20 DECwriter DIBOL EDUsystem 1AS MASSBUS PDP PDT RSTS RSX RT ULTRIX UNIBUS VAX VMS vT “ Owd The material is this document is for information purposes only. Digital VAX/VMS Systems Dispatch, July 1985 TABLE OF CONTENTS Page HELPFUL HINTS FOR WRITING SPRS 1 KNOWN PROBLEMS AND RESPONSES Component/ Product Seq. No. VAX/VMS (V3.n) SYS CPU TIME LIMIT IS NOT DEDUCTIBLE HIGH AST LATENCY 1.2.42 1.2.43 17 19 4,44 21 T.1.11 23 7.5.41 T.5.42 25 26 8.18.2 27 11.4.10 1411 29 30 11.15.8 31 11.36.8 33 11.42.1 35 20.2.6 20.2.7 20.2.8 37 38 39 20.11.4 Ll 20.14.2 43 LOGINOUT ACCESS VIOLATION DURING SUBSEQUENT BATCH JOBSTEPS F11AACP INDEX FILE ALLOCATION FAILURE RMS SEARCH LOSES PLACE ON RMS$_PRN ERRORS INVALID %RMS-W-RTB ERROR ON STREAM FILE XWDRIVER POINT-TO-POINT BSC MODIFIER TO $QIO LIBRARIAN LONG MODULE NAMES CONFUSE LIBRARIAN/LIST LBR$GET_HELP RETURNS WRONG FLAG TO OUTPUT ROUTINE SET TERMINAL START-UP PROCESS HANGS DOING SET TERMINAL VMSINSTAL VMSINSTAL IGNORES DEVICE ALLOCATED ERROR [31) CDU DOES NOT ALLOW DEFAULTS ON LISTS DECnet REMOTE PROCESS NOT DELETED PROBLEMS WITH DLM OVER PERMANENT VIRTUAL CIRCUITS REMOTE LOGIN FACILITY PROBLEM RMS RSTS FILESPEC INCOMPATIBILITY RTPAD RTPAD AND CTRL/O RTPAD SINGLE STREAMS TERMINAL $QIOs 20.14.3 4 VAX/VMS Systems Dispatch, July 1985 TABLE OF CONTENTS (cont.) Component/ Product Seg. No. VAX/VMS_(V4.n) SYS F$GETDVI INFORMATION INVALID IF DISK NOT MOUNTED u7 EXCESSIVE MODIFIED PAGE LIST WRITING GETJPI PROC_INDEX VALUE SHUTDOWN WITH REBOOT CHECK CAN FAIL ug 49 51 TODR DEFINITION REMOVED IN VAX/VMS VERSION 4.0 SCREEN MANAGEMENT SYMBOLS DEFINED INCORRECTLY 52 TEMPORARY MAILBOX LOGICAL NAMES 55 ACCOUNTING PROBLEMS WITH ACCOUNTING SELECTION BY UIC 57 USER RECORD DISPLAYS SCROLL OFF SCREEN 58 SYSGEN DISCREPANCY IN SCSNODE NAME LENGTH 59 SYSINIT QUOTA CACHING DISABLED ON THE SYSTEM DISK 61 UPGRADE CVTUAF DOES NOT COPY USER DATA AREA VMSINSTAL FAILS DURING VERSION 4.0 UPGRADE ON TU81 12.10.1 63 12.10.2 64 12.15.1 65 15.15.1 67 15.25.1 69 15.25.2 T0 VMSINSTAL VMIBCKERR.TMP INADVERTENTLY PLACED IN SAVE SET JOBCTL SNDSMB WITH FILESIZ OPTION FAILS PRINT SYMBIONT ISSUES BLANK PAGES WITH /SETUP SUGGESTION FOR DEFAULT FORM FOR EACH QUEUE PRINT SYMBIONT HOW TO PRINT HEADERS IN 80-COLUMN FORMAT UNEXPECTED SYMBIONT PROCESS TERMINATION K4l 73 DECnet e NETWORK JOBS USE DEFAULT DCLTABLES SPURIOUS NODE UNREACHABLE ERRORS STARTNET.COM INCORRECTLY PARSES NODE ADDRESS L STARTNET.COM FAILS TO CHECK FOR ALTPRI PRIVILEGE XDDRIVER DEVICE FULL ERROR WHEN INITIALIZING DMP-11 32.25.1 YQDRIVER YQDRIVER CORRUPTS NONPAGED POOL 32.45.1 81 TTDRIVER VT200 NOT DEFINED IN $DCDEF DMA NOT SET ON DMF-32 LINES 33.20.1 83 33.20.2 84 34.20.1 85 LPDRIVER SYSTEM-F-EXQUOTA ERROR ON PRINTOUT VAX/VMS Systems Dispatch, July 1985 TABLE OF CONTENTS (cont.) Component/ Product Seq. No. RMS READ FROM SYS$OUTPUT FAILS 40.40.1 COPY/OVERLAY FAILS IF DESTINATION WRITE-PROTECTED 40.40.2 CONFUSION ON $CREATE USING SEARCHLISTS $RENAME RETURNS INCORRECT ERROR MESSAGE 40.40.3 ACCESS CONTROL STRING PARSED INCORRECTLY 40.40.4 40.40.5 RTL VAX BASIC PROGRAMS RETURN AN INCORRECT ERL 45.1.1 93 55.5.1 95 55.10.1 55.10.2 97 98 55.20.1 99 55.30.1 55.30.2 101 102 55.65.1 55.65.2 103 104 56.5.1 105 INABILITY TO INSTALL EXECUTABLE IMAGES 56.10.1 107 LIBRARIAN PROBLEM DECOMPRESSING A LIBRARY 56.15.1 1 56.20.1 113 56.20.2 14 RANDOM BROADCAST CLASSES DISABLED 56.75.1 115 SET PASSWORD SET PASSWORD SIGNALS ERRORS TWICE 56.80.1 17 FOR ERRORS 50 AND 52 ANALYZE ANALYZE/IMAGE REPORTS INCORRECT LINK DATE AND TIME AUTHORIZE AUTHORIZE HAS TROUBLE PARSING /<ACCESS> QUALIFIERS REVOKE/IDENTIFIER DOES NOT REMOVE UICs BACKUP PROBLEM BOOTING STANDALONE BACKUP CONVERT CONVERT/RECLAIM MAY ACCESS VIOLATE CONVERT CAN INCORRECTLY REPORT DUP AND SEQ ERRORS DIRECTORY DIRECTORY OUTPUT MISSING TOTAL LINE DIRECTORY MAY DISPLAY NONEXISTENT FILES INITIALIZE INITIALIZE/INDEX:BLOCK=n NOT RECOGNIZED INSTALL LINKER LINKER OPEN FILE LIMIT PROBLEM LINKER REJECTS VALID FILE NAMES IN OPTIONS FILES SHOW DOCUMENTATION 119 SYS$TRNLNM EXAMPLE IS INCORRECT SNDOPR SYMBOLIC CODE INCORRECT UNDOCUMENTED ERROR MESSAGE FOR MOUNT 120 121 Ivp 123 WARNING MESSAGE CAUSES IVP TO FAIL STARLET ERROR IN XAB$ DEF INITIONS 85.50.1 125 VAX/VMS Systems Dispatch, July 1985 TABLE OF CONTENTS (cont.) Component./ Product Seq. No. Page OPCOM BATCH/REMOTE ENABLE OF OPERATOR TERMINALS ERRANT FORMATTING BEHAVIOR IN VAX/VMS PRINT SYMBIONT 95.5.1 95.5.2 127 129 95.5.3 138 95.5.4 139 SYS DELETION OF GLOBAL SECTIONS MICROFICHE INCORRECT ENTRIES IN VERSION 4.1 MICROFICHE ARTICLES OF GENERAL INTEREST CUMULATIVE INDEX (VERSION 3.n) 143 CUMULATIVE 161 INDEX (VERSION 4.n) COMPONENTS LIST 165 DIGITAL SOFTWARE LICENSING 175 DIGITAL EQUIPMENT COMPUTER USERS SOCIETY (DECUS) 177 HELPFUL HINTS FOR WRITING SPRs VAX/VMS Systems Dispatch 1 of 12 HINTS FOR WRITING SPRS 1.0 Introduction Software Performance Reports (SPRs) exist to benefit customers as well as DIGITAL. They provide informaton to customers and feedback to DIGITAL about software problems. The following descriptions provide guidelines for DIGITAL so that SPR problems can be solved. SPRs; submitting information to Some information is cammon to all other information is requested for only certain types of problems. 2.0 SPR Priority Levels The following explanations of SPR priorities should be used as a guideline for determining the priority of an SPR. determination should be based on the system Please note or facility actually been experienced at the site and perception of the impact of a potential problem. Priority 1. should that the priority behavior that has not be based on the Explanation MCST PRODUCTION WORK CANNOT BE RUN e.g., important production software is unusable, the system will not boot, necessary peripherals cannot be used as intended, no workaround exists. 2. SOME PRODUCTION WORK CANNOT BE RUN e.g., certain functions or jobs are not usable, level of performance is not as expected or same documented feature does not work as expected but there is a workaround. 3. ALL PRODUCTION WORK CAN BE RUN WITH SOME IMPACT ON USER e.g., significant manual intervention is required, performance has degraded but work can still be done. 4. ALL PRODUCTION WORK CAN BE RUN WITH NO SIGNIFICANT IMPACT ON USER e.g., problem can be patched easily, simple bypass procedure exists. 5. NO SYSTEM MODIFICATIONS NEEDED TO RETURN TO NORMAL PRODUCTION e.g., suggestion, consultation, documentation error or inquiry. 3.0 General Guidelines This section covers the information that should be provided with all SPRs. Depending upon the problem, this information will vary in quantity and content. Remember that the more pertinent information that is included, the easier it is for DIGITAL to resolve the problem. VAX/VMS Systems Dispatch 2 of 12 3.1 Scenario A camplete scenario should be supplied, usually in the form of a batch log console listing or SET HOST/LOG output file that shows exactly how the problem is produced. Supplying only the output produced by the problem is not enough. The entire scenario of what was done by the user is needed. The problem may be caused by an interaction between various system events, software packages, devices, SYSGEN parameters, DCL symbols or logical names. Same or all of the displays generated by the following commands may be required for different problems: $ SHOW LOGICAL/ALL/FULL $ SHOW SYMBOL/ALL/GLOBAL $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SHOW/ALL SYSGEN> SHOW/SPECIAL SYSGEN> EXIT 3.2 Limit Problem Scope As much as possible, eliminate all extraneous elements from the scenario. example, if the For execution of a very large program causes a problem, shorten the program to include only the code that causes the problem or write a small program first, that demonstrates the problem. logic errors may be discovered; second, This action has two benefits: the maintainer looking into the problem does not have to camprehend unnecessary material. 3.3 Machine-readable Files If possible, supply any software needed to reproduce the problem. This may include source programs, image files, sample data, command procedures, logical names etc. require format. If source programs are submitted, also include any libraries or files referenced. These files must be provided in machine-readable Console medium or ANSI magtape are the best media to include with the SPR. If the problem involves a system crash, include the system dump. The data should be written to an ODS-2 format disk or an example, the following caommands will magtape: $ INIT MIAO: DUMPS $ MOUNT/FOREIGN MTAO: $ BACKUP/IGNORE=NOBACKUP SYS$SYSTEM:SYSDUMP.IMP — $ MIAO:DUMPS/SAVE S DISMOUNT MIAO: ANSI magtape. For copy the system dump file to an ANSI VAX/VMS Systems Dispatch 3 of 12 NOTE Since the system dump file is frequently marked NOBACKUP (telling the BACKUP utility to copy the file attributes but not its contents), the file be must copied with: dump BACKUP/IGNORE=NOBACKUP This will insure that the file contents are copied, as well as the file attributes. The commands used to write the media should also be provided with the SPR. On a MicroVAX, where there is no console block storage device, use one of the floppy diskette drives to create machine-readable medium to be included with the SPR. The following commands can be used to copy files: $ INIT S$FLOPPYl: SPRDATA $ MOUNT S$FLOPPYl: SPRDATA $ CREATE/DIRECTORY $FLOPPY1: [DUMP] $ BACKUP MYDATA.DAT,MYIMAGE.EXE $ DISMOUNT $FLOPPY1: $FLOPPY]: [DUMP]SPRDATA/SAVE On a full VAX, where there is a console block storage commands can be used to copy machine-readable data: device, the scratch volume following $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT (At this time, remove the console medium and place a in the console block storage device.) $ INIT CSAl: SPRDATA $ MOUNT CSAl: SPRDATA $ CREATE/DIRECTORY CSAl: [DUMP] $ BACKUP MYDATA.DAT,MYIMAGE.EXE CSAl: [DUMP]SPRDATA/SAVE $ DISMOUNT CSAl: It is important to use BACKUP to write the media submitted with an SPR. Transferring files in a save set produced by BACKUP is much more reliable than copying files to the media. When machine-readable data is not provided in BACKUP save-set format, include the exact commands that were used to write the data and the commands used for reading it. Other formats are discouraged, since they may cause problems. VAX/VMS Systems Dispatch 4 of 12 All machine-readable media submitted with SPRs will be returned to the customer. 3.4 System Environment Every camputer site runs a different type of appear under classes of certain users conditions. different base For workload. example, priorities. Some problems only some sites give different These sites may encounter problems that other sites do not. This information can be extremely important in resolving the problem, especially for system hangs or system crashes. Describe any special software packages that are being used. Also, mention any foreign hardware devices or user-written drivers. Software version numbers should be included. For example, if there is a problem with accessing local symbols during a DEBUG session, the version numbers of DEBUG and all relevant compilers/assemblers should be specified. If any patches other than those from maintenance updates are being used, they should be mentioned in the SPR. 3.5 User Analysis (Optional) an analysis of the problem may be included. Any useful miscellaneous information should be included, such as, "Without xyz happening, the problem could not be reproduced" or "On version Vx.y, this problem does not occur." 4.0 Problem-specific Information to Include Resolution of different classes of problems generally requires different kinds of additional information. NOTE For those items that are identified with a single asterisk (*), the raw data file (SYSSERRLOG: ERRLOG.SYS) , not the formatted output from the ANALYZE/ERROR utility, should be included. Formatted output frequently does not include all the information needed to resolve the problem. For those double items asterisk that are (**), (SYS$SYSTEM: SYSDUMP.IMP), identified the not raw the with data a file formatted output from the SDA utility, should be included. Formatted output usually does not include all the information needed to resolve the problem. - Optionally, VAX/VMS Systems Dispatch 5 of 12 Problem Information to Include System Bugcheck/Crash A machine-readable copy of the system dump file must be included.** (Output from the SDA utility should not be sent since it usually does not include enough information to resolve the problem) . A copy of the error log at the time of the error should also be included because many system problems are triggered by hardware errors.* Machine-check: On a machine check, include a machinereadable copy of the error log, not output from the error log generator.* A machine-readable copy of the system dump file should also be included. ** System Hang: When a system appears "hung" (no response on any terminals), the system should be manually crashed and the system dump file included with the SPR. When the system is shut down in this way, the console listing is very important and should be included with the SPR. On VAX-11/730, VAX-11/780, VAX-11/782, VAX-11/785, and VAX 8600 primary console terminals, enter: (do nothing on the attached processor's console) ~p HALT @CRASH VAX/VMS Systems Dispatch 6 of 12 On VAX-11/750 console terminal, enter: Y/G F FFFFFFFF P 1F0000 On MicroVAX I: Push the HALT button on the front panel of the CPU box twice, so that the button is latched out (the red light in the center of the button is out). Then, on the console terminal, enter: E P E/I 0 E + mm E + ¥ + D/G F FFFFFFFF D P 1F0000 C (Then wait a minute or so) Note: If a CRT is being used, copy the displayed values from the examine cammands to paper and submit them with the SPR. The preceding command sequences cause the VAX or MicroVAX system to bugcheck in a manner that is recognized by VMS developers as a forced crash. Also include a description of the currently running workload. VAX/VMS Systems Dispatch 7 of 12 VAXclusters: If all machines in a VAXcluster are "hung" for a reason other than an explainable lack of quorum, a coordinated set of dumps plus console listings from all machines may be required for diagnosis. A coordinated set of dumps is a dump fraom every machine in the cluster taken in a way that ensures that the lock and other data structures are consistent between all dumps. To take a coordinated dump, first halt every VAX in the cluster. The last machine must be halted no more than 99 seconds after the first machine is halted. After all machines have been halted, crash each machine as directed under SYSTEM HANG, and provide all of the dumps and all of the console logs with your SPR. Executive: If it appears that there is a problem with the executive code, include the active values of the system parameters. These can be obtained by invoking SYSGEN and entering both the SHOW/ALL and SHOW/SPECIAL commands. A machine-readable copy of the source program showing the problem plus libraries, require files, and build files should also be included, if possible. Also include a copy of the machinereadable error log at the time of the problem. * Devices: For any suspected device or device driver error, include a copy of the error log at the time of the problem. * Corrupted RMS Files: When an RMS file becomes corrupted by software, an SPR should always be submitted. Items to include with the SPR are: VAX/VMS Systems Dispatch 8 of 12 1) A copy of the corrupted file. 2) Any programs (preferably with sources) and data that are necessary to reproduce the corruption. Note the distinction between programs that merely demonstrate that the file is corrupt, as opposed to a program that causes the corruption to occur. Please try to trim down the program to isolate the specific operations that led to the corruption. 3) A description of how the file is being processed when the corruption occurs. For example, how many users are accessing the file, what kind of operations are being performed on the file (SUPDATEs, $PUTs, $DELETEs, etc.). Sometimes accessing a corrupted file can cause nonfatal bugchecks. If it appears that a process is continually disappearing from the system, check the error log for nonfatal bugchecks. If this is the case, include a crash dump with the SPR. To obtain a crash dump (assuming the system manager has given permission), perform the procedure below. Since this procedure will crash the system, it is suggested that it be performed during off-peak hours. Be sure to give adequate warning if there are any users on the system. $ RUN SYS$SSYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SYSGEN> SET BUGCHECKFATAL 1 WRITE ACTIVE SYSGEN> EXIT $ RUN PROGRAM_THAT BUGCHECKS Intermittent: For a problem that is intermittent or that is not reproducible, include a copy of the machine-readable error log at the time of the problem. * 10 VAX/VMS Systems Dispatch 9 of 12 Command Language Interpreters: When submitting an SPR on a command language interpreter, it is important to show all symbols and logical names defined on the system by using the following commands: SHOW SYMBOL/ALL/GLOBAL SHOW SYMBOL/ALL/LOCAL SHOW LOGICAL/ALL/FULL Also, indicate whether private or modified command tables are being used. Job Controller: If the job controller process encounters a fatal error condition, it aborts execution and restarts itself (as a new process). Upon’ restart, the system job queue file is not reopened autamatically; a START/QUEUE/MANAGER command and appropriate START/QUEUE commands must be manually issued to restart batch and print processing for that node. For this type of controller problem, include a copy of the console log error message and a machine-readable copy of the job controller process dump written by the system to SYS$SYSTEM:JOBCTL.DMP. In addition, if the START/QUEUE/MANAGER command fails because of a corrupted system job queue file, also include a machinereadable copy of the queue file. The default queue file name is SYS$SYSTEM: JBCSYSQUE . DAT. Print Symbiont: Print symbiont process dump: If the print symbiont exits, a message from the job controller is printed on the console, together with an error message from the print symbiont. Also, a symbiont process dump is written 11 VAX/VMS Systems Dispatch 10 of 12 to SYS$SYSTEM:PRTSMB.DMP. Include a copy of these console log messages and a machine-readable copy of the symbiont process dump. Also include copies of the displays: SHOW QUEUE/FULL/ALL SHOW PRINTER (for all printer execution queues) SHOW QUEUE/FORM/FULL SHOW TERMINAL (all terminal execution queues) If a file was involved, include a DIRECTORY/FULL of the file and, if possible, a machine-readable copy of the file. If at all possible, attempt to explain the conditions which directly preceded commands detailed behavior the symbiont exit, such as used or attempted, and/or a description of the symbiont prior to exiting. Unexpected format or output generated with print symbiont: If the print symbiont problem exists in the formatting or output of data, include a machine-readable copy of the file and the library modules in use when printing. Include a DIRECTORY/FULL display of the file and a copy of the displays using the following commands: SHOW QUEUE/FULL/ALL SHOW QUEUE/FORM/FULL SHOW PRINTER and/or SHOW TERMINAL (whichever is applicable) Along with a description of the explicit PRINT command, include qualifiers and a copy of the FILE TRAILER page. Please provide all information required to repro— duce the behavior consistently. User-written and user-modified symbiont problems: Describe the problem as campletely as possible, including the intent of the user symbiont. Supply all details surrounding the problem and include a well-commented listing of the user-supplied symbiont or 12 VAX/VMS Systems Dispatch 11 of 12 routine. If the problem is associated with the specification of the queue, form, characteristics, parameters, or other input to the DCL command line, include a log file or a description of the PRINT command which demonstrates the problem. LIBRARIAN: If there is a problem with the LIBRARIAN, include the following material: 1. A machine-readable copy of the library itself 2. Machine-readable copies of all input files to the library 3. Information (DIRECTORY/FULL) on the library file 4. Information (LIBRARY/LIST/FULL) on the library contents If the problem can be duplicated at will, include the scenario and any command files used. LINKER: If there is a problem with the LINKER, include machine-readable copies of the object files, shareable images, and libraries used in the link, along with a full map (LINK/MAP/FULL). Debugger: Include sources, objects, and images for the program being debugged. If the program is large, it would be very helpful to reduce the size of the program to demonstrate the same problem. Also include a log of the debugging session and include the DEBUG.LOG file that the debugger produces. DECnet: For a DECnet problem, supply configurations of the systems involved in the problem. This information should include the version numbers of the operating systems and DECnet, the hardware on both systems, and the patch level of the DECnet software on the non-WMS system, if applicable. Depending on the nature of the problem, it might also be applicable to supply hard-copy display of executor, line or circuit parameters and/or counters. ax] VAX/VMS Systems Dispatch Terminals: 12 of 12 If there is a problem with the terminal driver, provide the following information: 1. A list of terminal characteristics (SHOW TERMINAL) 2. The type of terminal 3. The type of modem (if any) 4. Any special front-end equipment 5. Any unusual terminal configuration If the problem involves remote file access, it is often useful for the maintainer to know if the same or similar operation can be performed from a different account, or with the source and destination nodes reversed. Compiler/Assembler: If there is a problem with the assembler or a compiler, include the source program that caused the problem. (It is very important to include all require files and libraries that are referenced by the source program) . It is especially important to limit the scope of the problem when submitting SPRs on compilers. Include the version number of the compiler and the version number of the operating system. 14 KNOWN PROBLEMS AND RESPONSES (Version 3.n) 15 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: time limit 1985 1V VAX/VMS V3.7 VAX/VMS COMPONENT: CPU July offi12 Seq. 1.2.42 with a SYS is not deductible PROBLEM STATEMENT A subprocess in a multiprocess job is terminated CPU time limit exceeded message after using 1/n of the job's CPU quota (where n is the number of processes in the job). For example, a job with a CPU quota of 180 seconds creates two subprocesses. No single process 1/3 of the CPU time limit (or 60 in the job can use more than seconds) before timing out. The a CPU quota is supposed to be deductible quota but it is not being deducted on a job-wide basis. This causes a problem on systems whose software uses subprocesses extensively. RESPONSE A deductible allowance second is process quota is actually is one where given created. to That a portion of one another process is, word the process'’ when the "deductible" refers to the fact that a portion of the creator's quota is taken away, or deducted, when a subprocess is created. VMS also supports the notion of pooled or shared quotas. A main process in a process tree has a certain allocation and all processes in the same job tree use the same set of Buffered I/0 limit is an example of a pooled quota. 17, quotas. VAX/VMS Systems Dispatch, The only example (CPU time is of a also the July 1985 deductible quota only example of a the system one that cannot be borrowed from after it is no longer needed.) When a process creates 2 of a subprocess and limit, that number of clock ticks creator and given to the subprocess. and no CPU time arbitrarily gives new process. and does will get in VMS and specifies time. resource, given back a time CPU limit is specified for the offspring, VMS half of the creator's CPU time limit to the Thus, will CPU is taken away from the If a process is created if a process creates two not specify a CPU time limit, the half of the creator's CPU time offspring is consumable 2 get half of what is left, or There are two possible alternatives for this with VMS treating CPU time limit in its current the CPU time limit allocation to each of of the parent explicitly the offspring processes flexible allocation for each subprocess. than parent is offspring it 1/n of CPU creates, the fourth. application, fashion. 1If increased, then a larger can be accommodated. If specifies that one time limits consider parent's CPU time a for more limit P process the the subprocesses first offspring and the second 18 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: High AST July 1985 1 VAX/VMS V3.6 VAX/VMS Seq. ofH ]! 1.2.43 SYS latency PROBLEM STATEMENT Occasionally a high priority over 100 milliseconds. process experiences AST latency RESPONSE We expect to fix this problem in a 19 future update of VAX/VMS. of VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: violation 1985 20f. VAX/VMS V3.6 VAX/VMS COMPONENT: Access July Seq. 1 4.4.4 LOGINOUT during subsequent batch jobsteps PROBLEM STATEMENT Certain images subsequent cause an jobsteps of access violation if a multiple step batch job. executed during RESPONSE During the of second the CLI LOGOUT context rundown that block the the is deallocated context Using of jobstep, block, first valid. that an jobstep, LOGINOUT.EXE just before the LOGIN an assumption that Unfortunately, LOGINOUT's original memory. access and makes When violation an image attempts to the use results. DCL command: $ SUBMIT A,B can cause this type We expect to correct after Version of problem to occur. this problem 4.1. 21 in a future update of VAX/VMS VAX/VMS Systems OPERATING Dispatch, SYSTEM: PRODUCT: COMPONENT: Index file July 1985 ILpRe} VAX/VMS V3.5 Seq. 247 7.1.11 VAX/VMS F11AACP allocation failure PROBLEM STATEMENT The system crashed with the because of HDRNOTMAP bugcheck from the file system. RESPONSE The crash occurred The file system, in a VAX/VMS very fragmented Version 3, floppy would disk. only make one allocation attempt when extending the index file. If the allocation attempt succeeded, but did not allocate enough space to allow the index file to contain the desired file-ID, the file system would bugcheck the system with the HDRNOTMAP bugcheck. This problem workaround, qualifier on is corrected in VAX/VMS Version preallocate the index file the DCL command INITIALIZE. 23 by 4.0. using As a temporary the /HEADERS VAX/VMS Systems Dispatch, OPERATING SYSTEM: 1985 1) VAX/VMS V3.6 PRODUCT: Seq. 2y 7.5.41 VAX/VMS COMPONENT: SEARCH July RMS loses place on RMS$_PRN errors PROBLEM STATEMENT When a user who only has execute access directory attempts to search the results are produced. For example, to TEST.DIR, which contains file the execute, the following occurs: Entering the command: produces a which the both $ DIRECTORY of allow SUBDIR.DIR, to the top level of a directory tree, unexpected if a user has execute access A.B and user the access subdirectory to read and [TEST...]A.B protection violation error and two occurrences of A.B;l. RESPONSE The logic within RMS, which manages the wildcard directory searches, contained an error which would allow RMS to search a directory twice if it received an error attempting to access a subdirectory. We expect to correct this behavior 25 in a future update of VAX/VMS. VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Invalid July 1985 1l of V3.6 1 Seq. 7.5.42 file record RMS $RMS-W-RTB error on stream file PROBLEM STATEMENT An invalid error: "$RMS-W-RTB, is produced if record a program which exactly fits across a boundary. block too its large for user's attempts buffer and to read buffer" a the record in the stream terminator is split RESPONSE This behavior locate the is end caused of by terminator is encountered a has an error record that it split a across a in stream block record logic which format boundary, RMS terminator until attempts to files. If does realize it not the has attempted to store the first byte of the terminator in the user's buffer. If the user's buffer is precisely the size of the data portion of the record, the error noted above is flagged erroneously. We expect Version to correct this problem 4.1. 26 in an update of VAX/VMS after VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Point-to-point July VAX/VMS VAX/VMS 1985 1% V3.7 Seq. o £ 8.18.2 XWDRIVER BSC modifier to $QIO PROBLEM STATEMENT If a $QIO write logical or physical with the point-to-point BSC modifier is issued to the XWDRIVER and the user buffer is improperly formatted, RO is returned with the wrong information. RO should contain the status code SS$_ABORT, but instead contains the user buffer address. RESPONSE We expect Version to fix this problem in 4.1. 27 a future update of VAX/VMS after Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Long module names July 1985 gty VAX/VMS V3.4 VAX/VMS 4l Seq. 11.4.10 LIBRARIAN confuse LIBRARIAN/LIST PROBLEM STATEMENT Module names longer that 15 characters destroy the output from the LIBRARIAN/OBJECT/LIST/FULL command. format of the RESPONSE We expect to correct this problem 29 in a future update of VAX/VMS. VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: July 1985 1 of VAX/VMS V3.5 Seq. 1 11.4.11 VAX/VMS LIBRARIAN LBR$GET_HELP returns wrong flag to output routine to update the HLP$M_OTHERINFO flag if following PROBLEM STATEMENT The LBR$GET_HELP routine between output routine fails invocations the conditions met: 1. LBR$GET_HELP 2. The subkey 3. The is is called with two keys. ambiguous. first matched helptext module contains help RESPONSE This problem is corrected in VAX/VMS 30 Version 4.1. subtopics. are VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: process 1985 1 VAX/VMS V3.5 VAX/VMS COMPONENT: Start-up July SET Seq. of i 11.15.8 TERMINAL hangs doing SET TERMINAL PROBLEM STATEMENT SET TERMINAL/WIDTH=n user and types the CTRL/S target on executed the terminal from terminal has the a command while DEC_CRT the fixed in VAX/VMS Version 4.0. 31 command attribute RESPONSE This problem is procedure set. is hangs if a executing VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: VMSINSTAL ignores July 1985 VAX/VMS V3.5 2 of Seq. gl 11.36.8 VAX/VMS VMSINSTAL device allocated error PROBLEM STATEMENT VMSINSTAL attempts to install software even when the device containing the distribution medium is allocated to another user. RESPONSE We expect to fix this problem in a future update of VAX/VMS. 33 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: CDU does July 1985 1o VAX/VMS V3.3 VAX/VMS Seq. £31! 11.42.1 CDU not allow defaults on lists PROBLEM STATEMENT The Command Definition Utility does not allow default values to be requires major specified for LIST type qualifiers. RESPONSE Allowing default values on LIST type qualifiers modifications to the Command Definition Utility. We will consider this suggestion for a future update of VAX/VMS. 35 VAX/VMS Systems Dispatch, OPERATING SYSTEM: Alefoy Seq. 3731 20.2.6 VAX/VMS COMPONENT: process 1985 VAX/VMS V3.3 PRODUCT: Remote July DECnet not deleted PROBLEM STATEMENT Under various disconnected in the remote happens, circumstances, an abnormal way when a remote (for example, not terminal process might the process is not become correctly terminal is using LOGOUT), compute-bound. When this deleted. RESPONSE This type problems. However, expect of behavior VAX/VMS one of can Version be caused 4.0 corrects these problems to resolve it is still by any some being of of known problems. investigated in a future update of VAX/VMS. 37 several these and we VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Problems July 1985 with 1l ofl V3,7 Seq. 20.2.7 DECnet DLM over permanent virtual circuits PROBLEM STATEMENT Two VAX systems are connected by means of VAX PSI, and a DECnet circuit is established between them using datalink mapping (DLM). The PSI circuit is a permanent virtual circuit (PVC). If anything goes wrong with the PVC 1link, shutting down the processors. either the "on-starting" or the only recovery method is Otherwise, the PVC remains "on-synchronizing” by in state. RESPONSE number of interactions propagated There through to the DECnet-VAX and We are expect a to the circuit change this code states behavior 38 between X.25 implementing within in a events PVC which support are within DECnet. future update of VAX/VMS. VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: login 1985 L VAX/VMS V3.6 VAX/VMS COMPONENT: Remote July Seq. iof vl 20.2.8 DECnet facility problem PROBLEM STATEMENT When not logging return off a normally remote terminal, to original used to regain control. process is deleted. the In this sometimes node case, and control CTRL/Y the remote problem is does must be terminal RESPONSE To the best of our knowledge, this fixed in VAX/VMS Version 4.0. There are, however, similar problems that exist in remote terminal logout. Future updates will include more fixes as we solve these individual problems. 39 VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: DECnet COMPONENT: RSTS July filespec 1985 Wof4i2 V3.4 Seq. 20.11.4 RMS incompatibility PROBLEM STATEMENT A VMS user trying to access files on a PDP-11/70 Version 8.0 cannot properly get directory files from an account on the PDP-11/70 if account is not octal. running RSTS information or copy the PPN of the RSTS Examples: 1. 2. $ COPY RSTS::"DB3:[1,99]XXX.YYY" $ DIR RSTS::"DB3:[1,99]" directory 3. and not all of * * returns the file fails. the first file in the names. § DIR RSTS::"DB3:[1,99]*.*" returns all the file but does not display the complete file names. names NOTE When using octal PPNs file specification, and the leaving off the quotes above operations work around the correctly. RESPONSE The effects described are caused by the in a quoted file specification. The various effects are described below. 1. The implications inherent explanations of the problem with wildcard COPY operations. Since the from the resulting source file destination file name, necessary 41 it is name is obtained to be able to VAX/VMS Systems interpret Dispatch, the PPNs, VAX/VMS obey the source is July 1985 2 of file name. 1In presented with file-name rules. a As the file a case name result, of nonoctal that the 2 does file not name must be specified in quotes and, by definition, any interpretation of the resulting file name is disallowed. This, in turn, means that any attempt at assigning destination file names is also disallowed and, hence, it is impossible to construct the destination file names for a wildcarded destination. 2. The problem with DIRECTORY operations not explicitly to multiple wildcarded. In order for DIRECTORY or RMS look for files, it is necessary to provide a "wildcarded" file specification. Without any wildcard information, RMS assumes that only one file exists that fits the requested specification. The DIRECTORY utility provides wildcard file name searches by specifying a default file name of *,*;* to RMS, which is merged into the file specification that the user included in the DIRECTORY command. This, however, does not work for quoted file specifications, such as "[1,99]", since these are defined to be fully specified and, therefore, none of the default file names from 3. The This the DIRECTORY problem with is corrected file name utility DIRECTORY in are included. truncating VAX/VMS Version quoted 4.0. The file full names. quoted is now displayed from a DIRECTORY command. Chapter 9 of the VAX/VMS Version 4.0 Guide to Networking VAX/VMS discusses the information presented here. 42 on VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: July 1985 1 VAX/VMS V3.3 Seq. of1l 20.14.2 DECnet RTPAD RTPAD and CTRL/O PROBLEM STATEMENT The RTPAD protocol is unable to return a As a result, all data is transferred discarded at the server end. CTRL/O through to the the host node. network and RESPONSE The old RTPAD protocol has no CTRL/O Version 4.0 is using a new remote that has such a message. 43 message. terminal However, protocol, called VAX/VMS CTERM, VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: DECnet COMPONENT: RTPAD single July 1985 lof1l V3.5 Seq. 20.14.3 RTPAD streams terminal $QIOs PROBLEM STATEMENT RTPAD has have remote a single than local stream terminals for with terminals with its reads reads $QIOs. This outstanding makes programs behave that differently outstanding. This a restriction behavior for a within future RTPAD. update of 44 We will VAX/VMS. consider changing this - RESPONSE KNOWN PROBLEMS AND RESPONSES (Version 4.n) 45 VAX/VMS Systems Dispatch, July 1985 OPERATING SYSTEM: VAX/VMS V4.0 PRODUCT: £ /21! Seq. 5.20.1 return valid VAX/VMS SYS COMPONENT: F$GETDVI Vo information invalid if disk not mounted PROBLEM STATEMENT The FS$GETDVI information lexical for function does not always DSA disks. RESPONSE For DSA disks, the correct disk geometry information is unknown until the disk is actually mounted. DSA disks can have different geometry characteristics, even when two packs can be mounted Since be the in the correct known until it that report disk information is not 1. 3. characteristics of a disk cannot is mounted, all VMS services and features geometry might report invalid geometry DSA disk. This includes, lexical function but to: following CYLINDERS, 2. geometry for any unmounted limited The same drive. F$GETDVI DEVDEPEND, The following and DVI$_TRACKS. DVI$_CYLINDERS, MAXBLOCK, $GETDVI SECTOR, system DVIS$_DEVDEPEND, item codes -- codes -- and TRACKS. service item DVI$_MAXBLOCK, DVIS_SECTOR, Some of the data returned by the IO$_SENSECHAR function. This condition is not documented because there is a precedent for returning invalid information when a disk is not mounted. The FREEBLOCKS, MAXFILES, and SERIALNUM are all additional examples of F$GETDVI item codes that do not return valid information unless the disk is mounted. 47 VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Excessive July 1985 1 V4.0 of 1 Seq. 5.20.2 even though SYS modified page list writing PROBLEM STATEMENT The modified page list is it has not reached its the free-page list. continuously high limit and is caused by a process has being there flushed, are adeguate pages on RESPONSE We believe working page this set table problem sizes. pages If might need to be some a users very removed having small from the frequently, even though they still contain references the modified list. 1In order to remove page table memory, VMS must first flush users' We recommend that the to alleviate this problem. the modified default 48 list working to set inadequate working working set, set to pages on pages from disk. size be increased VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: GETJPI July 1985 1Vof#2 V4.0 Seq. 5.20.3 SYS PROC_INDEX value PROBLEM STATEMENT SYSSGETJPI returns an incorrect value for the process index. RESPONSE The value equal to that $GETJPI returns for the PROC_INDEX item code is not the index into the PCB vector. When the PID format was changed in assumptions VAX/VMS should process 1ID. The unique across a Version be made only statement as a PROC_INDEX it the made was stressed that internal composition was a that process no of ID a was cluster. Since many applications were PID 4.0, about unique item using the identifier code to for satisfy a low word of process, this the Version 3.n we need. invented However, the in a continuing effort to allow maximum flexibility in future releases, a conscious effort was made to have no connection between this $GETJPI The item and internal VMS structures. documentation Reference Manual The process SYSGEN on page SYS-199 of the VAX/VMS System Services states: index parameter number is a number MAXPROCESSCNT, between which and the identifies 1 the process. Although process index numbers are reassigned to different processes over time, at any one instant, each process in the system has a unique process index number. 49 VAX/VMS Systems Dispatch, July 1985 2 of 2 ...The process index is intended to serve users who formerly used the low-order word of the PID as an index number. The last statement means that the $GETJPI item will serve as a unique, small-integer identifier. It does not mean that the process index $GETJPI item has the same value as that displayed by SDA. 50 VAX/VMS Systems Dispatch, OPERATING SYSTEM: July 1985 LSO VAX/VMS V4.0 PRODUCT: Seq. £ Al 5.20.4 VAX/VMS COMPONENT: SYS SHUTDOWN with REBOOT_CHECK can fail PROBLEM STATEMENT If a logical name SYS is defined, the system shutdown command procedure SYS$SYSTEM:SHUTDOWN.COM fails in its REBOOT_CHECK function that an and issues an incorrect error important system file cannot be message indicating located. RESPONSE This problem the is REBOOT_CHECK a result of function. a naive file-lookup We expect to correct algorithm in this problem in a future update of VAX/VMS. The list of logical names one might define to cause this problem is very long. It includes all the files the REBOOT_CHECK function is attempting to locate. Some examples are SYSBOOT, VMB, SYSINIT, F11BXQP, SYS, RMS, DCL, and TTDRIVER. Until a corrected SHUTDOWN procedure is available, this problem can be avoided by not performing the REBOOT_CHECK function. 51 VAX/VMS Systems Dispatch, OPERATING SYSTEM: 1985 1 VAX/VMS V4.0 PRODUCT: Seq. of 2 5.20.5 VAX/VMS COMPONENT: TODR definition July SYS removed in VAX/VMS Version 4.0 PROBLEM STATEMENT In VAX/VMS Version no longer defined appears to reference the be 4.0, in no the the processor $PRDEF macro replacement time-of-day register in symbol LIB.MLB. symbol PR$_TODR Moreover, to allow a some future VAX is there driver to register. RESPONSE In July 1983, it have was would not other processor these disappearing Also, documenting documentation a discovered time-of-day registers). register (in Everything was registers the was change sent with that as addition processors to converted processor-specific was initiated. 1In the first test field fact, several to handle entities. the software relevant package for VAX/VMS Version 4.0. However, the critical documentation inadvertently omitted from the documentation set. Had the 4.0 documentation, description "The no of it following longer definitions this change would have Internal common have to been appeared read as VAX/VMS Registers all processors. removed VAX (IPRs) from $PRDEF: - Interval Clock Next ICR - Interval Clock Interval TODR - Time Day the Interval Count Register Register Register ACCS - Accelerator Control Status Register ACCR - Accelerator Reserved PME - Performance Monitor 52 Version follows: Processor NICR of in Enable was are Their VAX/VMS Systems Dispatch, July 1985 20 of 2 "New CPU-specific processor register definition macros have been added to LIB.MLB, to define the CPU-specific IPRs. The macro names have the format $PRxxxDEF, where xxX is the number associated with the processor, e.g. $PR780DEF will define PR780$_ACCS. "The only legitimate references to these registers in CPU-dependent code. These references must use new CPU-dependent IPR definitions. "Note, however, that "time-wait directly reference the "time-wait" macro that CPU-independent loops" must clocks; they MUST is CPU-independent. "time-wait" macro has been are the NEVER wuse a A new, added to LIB.MLB that should eliminate any need for "time-wait" loops. It is called TIMEDWAIT. hand-coded "There PR$_ICR or should PR$_TODR to no do longer be "time-wait" any references loops. to TIMEDWAIT allows for up to six special-purpose instructions to be placed its timing loop. However, the loop timing is based having one BITx embedded within and one conditional branch instruction the loop. Therefore, if a loop has no embedded instructions, accordingly. A good rule TIME argument in on for a adjust the TIME argument of thumb is to add 25% to the loop with no embedded instructions. "There are places that reference PR$_TODR for logging purposes. Two new loadable, CPU-dependent routines, EXESREAD_TODR and EXE$WRITE_TODR, have been added for code The above that must reference description will this be VAX/VMS documentation. 53 type of value." included in a future version of the VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: 1985 1 VAX/VMS V4.0 VAX/VMS COMPONENT: Screen management July Seq. of 1 5.20.6 SYS symbols defined incorrectly PROBLEM STATEMENT The following incorrectly screen management symbols have been defined in STARLET.MLB: Incorrect name Correct name SMGK_TOP SMGS$K_TOP SMGK_RIGHT SMGK_LEFT SMGK_BOTTOM SMGSK_RIGHT SMG$K_LEFT SMG$K_BOTTOM RESPONSE We expect to correct VAX/VMS Version 4.1. these definitions A workaround is to extract the erroneous it, and reinsert it into STARLET.MLB. 54 in an update definition, after correct . VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: Temporary mailbox July 1985 d V4.0 Seq. eyl 5.20.7 SYS logical names PROBLEM STATEMENT After upgrading from VAX/VMS Version 3.7 many users were surprised to learn that longer appear in the group logical name to VAX/VMS Version temporary mailbox table. 4.0, names no Is it possible to set up a VAX/VMS Version 4 system so that temporary mailboxes will act in a manner that is compatible with VAX/VMS Version 3? 1Is it possible to define LNMSTEMPORARY MAILBOX in the group or system name table so available on a group or system basis? that the behavior change is RESPONSE Logical names that are names of TABLES must be placed into one of two logical name directories. One of these directories is process-specific and is located by the name LNM$PROCESS_DIRECTORY. The other directory is system-wide and is identified LNM$SYSTEM_DIRECTORY. Thus, logical names are either process private or system wide. The simplest solution table $ name into the is to place that the redirected system directory with the are by the table name names temporary mailbox command: DEFINE/TABLE=LNM$SYSTEM_DIRECTORY LNM$STEMPORARY_MAILBOX LNM$GROUP Note that this command causes the entire system to revert to VAX/VMS Version 3 behavior with one exception. Processes that create group logical names via the Create Mailbox system service must now have GRPNAM privilege. the VAX/VMS Version 4 name back behavior, to LNMS$JOB. 55 If certain processes wish define the to keep temporary mailbox table VAX/VMS Systems Dispatch, July OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Problems with 1985 1N V4.0 Seq. oVl 10.5.1 ACCOUNTING ACCOUNTING selection by UIC PROBLEM STATEMENT When the /UIC=[x,y] qualifier is used on the ACCOUNTING all users with either group values of x or member values displayed in the report that is generated. For command, of y are instance, the command : $ACCOUNTING/FULL/UIC=[156,040] produces a report as though the command had been: $ACCOUNTING/FULL/UIC=([*,040],[156,*]) RESPONSE An UIC error in the selections based on We expect UIC to selection proceed as logic causes though the all accounting selection record criteria were a wildcarded UIC. to correct this behavior 57 in a future update of VAX/VMS. VAX/VMS Systems Dispatch, July 1985 OPERATING SYSTEM: PRODUCT: COMPONENT: 1 of 1 VAX/VMS V4.0 Seq. 10.5.2 VAX/VMS ACCOUNTING User record displays scroll off screen PROBLEM STATEMENT When a full display of user message records is specified, the first line of the user message scrolls out of sight before the ACCOUNTING utility waits for the user to request more of the user message. The ACCOUNTING utility attempts to output six lines of user data in a five-line scrolling window. As a result, the first line scrolls out of sight whenever the user data consists of more than five We lines. expect to after Version correct this behavior 4.1. 58 in a future update of VAX/VMS — RESPONSE VAX/VMS Systems OPERATING Dispatch, SYSTEM: PRODUCT: COMPONENT: Discrepancy in July 1985 1o VAX/VMS V4.0 VAX/VMS Seq. £2 31! 11.35.1 SYSGEN SCSNODE name length PROBLEM STATEMENT There is confusion over whether the SCSNODE SYSGEN parameter is really eight characters long, as accepted by SYSGEN, or only six Generation characters long, as documented in the System Utility Reference Manual. RESPONSE The behavior Reference SCSNODE described in the Manual is correct; parameter are used. In we expect that SYSGEN will be restriction imposed by DECnet. 59 System only a Generation six future changed to Utility characters update respect of of the VAX/VMS, the length VAX/VMS Systems Dispatch, July OPERATING SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: SYSINIT Quota caching disabled on 1985 Lo V4.0 the Seq. £SE] 11.40.1 system disk PROBLEM STATEMENT SHOW DEVICE/FULL size of 0. The However, every set to 0. The only command mount a system on the SYSGEN other system disk always parameter ACP_QUOCACHE time the system is booted, way to change the the quota shows has quota set quota size is (there is no SET VOLUME/CACHE command). system disk, since the system disk is initialization process, a been cache via cache to 60. size is the MOUNT But one cannot mounted by the SYSINIT. RESPONSE This problem is caused by the system initialization process, SYSINIT, which inadvertently set a flag that effectively disabled quota caching when mounting the system disk. This caused the SYSGEN parameter ACP_QUOCACHE to be ignored for the system disk. We expect to correct this problem in a future update of VAX/VMS. 61 VAX/VMS Systems Dispatch, OPERATING SYSTEM: CVTUAF VAX/VMS COMPONENT: UPGRADE not 1985 1o VAX/VMS V4.0 PRODUCT: does July copy user data Seq. £#) 12.10.1 area PROBLEM STATEMENT The CVTUAF utility, run during the installation of VAX/VMS Version 4.0, did not attempt to copy the user data area from the records in the old UAF. Does current documentation exist for the user data areas? RESPONSE CVTUAF did attempt attempt was not We expect to The user data to copy the user data areas; unfortunately, future update the successful. correct area this is problem in a currently not documented in of VAX/VMS. the VAX/VMS Version 4.0 manual set. We expect to add the documentation future expansions to the Guide to System Security. 63 in VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: UPGRADE VMSINSTAL fails July 1985 1l V4.0 during Version Seq. 4.0 of 1 12.10.2 upgrade on TU81 PROBLEM STATEMENT The VAX/VMS Version distribution medium is 3 to Version 4 upgrade fails located on a TU81 tape drive. if the RESPONSE The problem occurs because the upgrade and installation procedures are not configuring the TU8l's port device before attempting to configure the procedures fail A corrected available TU81l's to class locate device. the TU81 distribution kit, Because of this problem, the BB-EY98A-BE, is successfully. part number from the Software Distribution Center. This problem will be corrected with a VAX/VMS. 64 future, remastered update of VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: VMIBCKERR.TMP July 1985 550 VAX/VMS V4.0 VAX/VMS Seq. £l 12.15.1 VMSINSTAL inadvertently placed in save set PROBLEM STATEMENT VMIBCKERR.TMP is the GET option of inadvertently included in the save set when using VAX/VMS after VMSINSTAL. RESPONSE We expect to Version 4.1. fix this problem in 65 a future update of VAX/VMS Systems OPERATING Dispatch, SYSTEM: PRODUCT: COMPONENT: SNDSMB with FILESIZ July 1985 i VAX/VMS V4.0 Seq. lgioy3l | 15.15.1 VAX/VMS JOBCTL option fails PROBLEM STATEMENT A $SNDSMB system service call using the Job Controller to the SMOSK_FILSIZ loop indefinitely. this problem option causes RESPONSE We expect to correct after Version 4.1. 67 in a future update of VAX/VMS VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Symbiont issues July 1985 ¥ VAX/VMS V4.0 VAX/VMS Seq. o £ 15.25.1 PRINT blank pages with /SETUP PROBLEM STATEMENT Extra or blank reset pages sequence are is generated specified by the print symbiont when for the current print a setup job. RESPONSE In VAX/VMS Version 4.0, it 1is possible to create library SETUP/RESET modules which are output to the device during the processing of the current print job. SETUP/RESET modules may be output before current job is The VAX/VMS feeds an Version after all update of a specific completed. 4.0 file, print before symbiont SETUP or RESET modules, VAX/VMS after all Version files, or incorrectly regardless 4.1, only inserts of those after form content. modules the In which insert printable text will be followed by a form feed. No form feed will be inserted after a recognized escape sequence, device control sequence, or operating system command. Certain limitations are imposed for output devices which require control sequences in the ASCII range of printable characters. Certain limitations might the user to reposition printable text. also exist output 69 to the for those top of devices page which after allow inserting VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: 1l of VAX/VMS V4.0 VAX/VMS COMPONENT: Suggestion July 1985 Seq. 1 15.25.2 PRINT for default form for each queue PROBLEM STATEMENT The documentation the command in the DEFINE/FORM VAX/VMS Version conflicts with 4.0 the DCL Dictionary documentation for for the command PRINT. The documentation for DEFINE/FORM states "If you omit the /FORM qualifier from your PRINT command, your job will be printed using whatever form has been specified for the queue." The documentation for the PRINT command indicates that the default form submitted with a print job is /FORM=0, the default form definition. The VAX/VMS Version 4.0 implementation of the PRINT command is to enter a job in the queue with /FORM=0, even if the queue is initialized with a form type inconsistent with the default form definition. Is the current behavior of the PRINT command the intended behavior? The desired behavior is the behavior documented in the description for DEFINE/FORM. Will support be added to enable the system manager to define a default form definition for each queue? RESPONSE The documentation Version from your default The 4.0 should PRINT for the have read: command, DEFINE/FORM "If your definition omit will be the in /FORM printed VAX/VMS qualifier using the form definition." information regarding default DCL PRINT command Support job you for is default correctly form forms on the VAX/VMS Version 4.0 documented. definitions for each queue is currently unavailable. We will consider this inquiry as a suggestion possible implementation in a future update of VAX/VMS. 70 for VAX/VMS Systems OPERATING Dispatch, July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: How to print PRINT headers in 1985 1 V4.0 Seq. of 2 15.30.1 SYMBIONT 80-column format PROBLEM STATEMENT In the within VAX/VMS an Version 80-column 3.0 print format. symbiont, Under VAX/VMS the page Version header 4.0, the fits page header is printed in a 132-column format. The header is truncated when the command SET PRINTER /WIDTH=80 /TRUNCATE is used. Is there some way to produce a page header in 80-column format? RESPONSE In VAX/VMS Version pages is device. In determined VAX/VMS and default form, produce a form with If a no the size PAGE the pages form DEFAULT, page the 4.0, separation definition. To by Version header For 3.0, is is of of 80 page and WIDTH formatting is on header and sizing by the used with /WIDTH=132 to a width of the PRINT and 80 columns. example: $ DEFINE/FORM/WIDTH=80/LENGTH=66/STOCK=DEFAULT _Form name: FORM_B80X66 _Form number: 2 71 and attributes determined specified header properly a width the of of separation the output the page current form command, the /LENGTH=66. columns, define VAX/VMS Systems Dispatch, July 1985 2 of This form must be specified with the PRINT to print the file FOOBAR.TXT with page FORM_80x66, $ use one of the following command. headers 2 For example, and the form commands: PRINT/FORM=FORM_80X66/HEADER FOOBAR.TXT or $ PRINT/FORM=2/HEADER FOOBAR.TXT Consult the VAX/VMS Daily Operations, DCL-229, for more and Version 4.0 Guide Section 9.3.3.3 and detailed information to System Management and the DCL Dictionary, page regarding form definition usage. NOTE The /STOCK=DEFAULT qualifier in the form definition indicates the stock type. Stock types in the form definition submitted with the PRINT command must match the stock type of the form definition initialized on the queue. This stock definition allows print jobs with the same stock to be automatically mounted without the operator to change paper stock on the queue. 72 the device and requiring reinitialize VAX/VMS Systems Dispatch, OPERATING SYSTEM: July 1985 1 VAX/VMS V4.1 PRODUCT: Seq. 'ofai2 15.30.2 VAX/VMS COMPONENT: PRINT SYMBIONT Unexpected symbiont process termination PROBLEM STATEMENT The print symbiont terminated abnormally. Immediately thereafter, it appeared that the job controller aborted with an access violation. Upon reboot, the symptoms repeated. Rebooting with STARTUP_P1 set to "MIN", then using the DCL command START/QUEUE/MANAGER/NEW_VERSION and reinitializing all queues, restored queue operations. Although the job controller is started with the /DUMP option, no dump is produced. RESPONSE In VAX/VMS Version 4.0, the print symbiont and job controller communicate via special messages. These messages contain information regarding errors incurred in the creation of batch jobs or the execution of print jobs. For example, if the job controller receives an error when attempting to open a batch logfile, a special print job is sent to the print symbiont. This print job contains no file identification. The job contains, instead, the Similarly, if of a This print to job, message print the error message returned to the job controller. the symbiont receives a fatal error during execution a special contains symbiont. operator The message the job console fatal is controller with "unexpected symbiont process an sent error sends the associated termination". 73 to the message job controller. received fatal error message by the message indicating VAX/VMS Systems For example, to create a example, The batch Dispatch, the job batch July 1985 controller logfile. received The batch and the batch job was logfile creation failed "LOGIN-F-CLITBLFAIL, 2 error an job error name when was of 2 attempting ACVCTESTS, for issued from the SYSTEM account. because of the following error: activating command interpreter tables" This was sent to symbiont error should have properly copy job as name the symbiont "ACVCTESTS" a special print printed as the error message by name user job. "SYSTEM". The on hard However, because of a problem in the creation of file separation pages, symbiont attempted to use the null filename in the creation of filename banner and subsequently incurred an access violation. The access violation error. This error prior to symbiont is correctly was communicated process interpreted to termination. the operator's console in two steps. by the job controller indicates an termination. The second controller the error is message the The as a job fatal fatal symbiont controller error the the is just sent to The first OPCOM message sent unexpected symbiont process sent which caused violate. to OPCOM the from the job symbiont process symbiont incurred termination. The job an access controller Deletion violation of the queues controlled type of problem. did not access and the job offending controller print job and The reported the restarting problem. the output by this symbiont process should suffice for this Rebooting with a new queue file should not be necessary. We plan Version to correct this problem 4.1. 74 in an update of VAX/VMS after VAX/VMS Systems Dispatch, OPERATING SYSTEM: use 1¥of Seq. =i 25.5.1 VAX/VMS COMPONENT: jobs 1985 VAX/VMS V4.0 PRODUCT: Network July DECnet default DCLTABLES PROBLEM STATEMENT When a remote DECnet object is invoked using the DECnet default nonprivileged account, DCL is started with the system default DCLTABLES rather than with those specified in the tables field of the DECnet entry in SYSUAF. RESPONSE There is a change in VAX/VMS Version 4.0 which forces network jobs to be started with DCL as their default CLI. This allows network access such as since network such as One MCR by accounts for jobs which their normal are required are set up to use (interactive to run DCL and other CLIs batch) use, command procedures NETSERVER.COM. side effect of this change is the use of the default DCLTABLES instead of any alternate tables defined in the UAF entry. This is necessary because an account using a different CLI, such as MCR, would have a table defined in the UAF entry which would not work correctly with NETSERVER.COM. Therefore, this should be viewed as a restriction. As a workaround, $ in include the command: SET COMMAND /TABLE=yourtable the LOGIN.COM procedure for the account 5 in question. VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Spurious node July 1985 1 V4.0 Seq. of 1 25.5.2 DECnet unreachable errors PROBLEM STATEMENT When executing the node with the the following command lowest DECnet procedure in a cluster, on address: $loop: the S dir $ $ wait 00:00:01 goto loop following 0::z error is "$DIRECT-E-OPENIN, reported following error opening "-RMS-E-FND, ACP file or "-SYSTEM-F~UNREACHABLE, reachable” 10 to 0::2Z.*;* 20 as iterations: input" directory lookup failed" remote node is not currently RESPONSE This is caused requests at by the a problem target a which validates this problem 76 node in a from future a If node an connect existing link correct target code connection. which has the same link number as the connect request, is erroneously dismissed as a duplicate request. to the the of logical expect on in address request We exists end update with of a higher the VAX/VMS. VAX/VMS Systems OPERATING Dispatch, July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: STARTNET.COM 1985 1% V4.0 Seq. of il 25.5.3 DECnet incorrectly parses node address PROBLEM STATEMENT STARTNET.COM always designation containing node address. agree with located on The the the returns a error an error number that indicates SYSGEN parameter line in STARTNET when is that the the selecting same node as an the address area DECnet does not SCSSYSTEMID. The problem is that is performing character deconcatenation: $ EXEC_AREA = EXEC_AREA - EXEC_LOC - "." RESPONSE This problem the meantime, $ to the will a be corrected workaround IF EXEC_ADDR .EQS. is in to a future change the update line of VAX/VMS. In in STARTNET.COM: CLUSTER_NODEADDR THEN GOTO CLOSE_TEMP following: $ GOTO CLOSE_TEMP thus bypassing SYSGEN the parameter check. If SCSSYSTEMID, the the 77 node problem address is differs caught by from NETACP. the VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: STARTNET.COM fails July 1985 1l of 1 VAX/VMS V4.0 VAX/VMS Seq. 25.5.4 from within DECnet to check for ALTPRI privilege PROBLEM STATEMENT The privilege STARTNET.COM, ALTPRI but is required STARTNET.COM to fails run to LOADNET.COM check for this required privilege. RESPONSE We expect to correct this problem in a future update of VAX/VMS. 78 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Device full July 1985 1 VAX/VMS V4.0 Seq. of] 32.25.1 VAX/VMS XDDRIVER error when initializing DMP-11 PROBLEM STATEMENT When initializing tributary after the the DMP-11, the initialization of first one returns the error message: "$SYSTEM-W-DEVICEFULL, device full - allocation failure" "$NCP-I-NMLRSP, listener response - Operator failure" RESPONSE This problem is fixed in VAX/VMS Version 4.1. 79 every VAX/VMS Systems Dispatch, OPERATING SYSTEM: 1985 lofl VAX/VMS V4.0 PRODUCT: COMPONENT: YODRIVER July Seq. 32.45.1 VAX BTS YQDRIVER corrupts nonpaged pool PROBLEM STATEMENT Subsequent to the release of VAX BTS discovered that under certain conditions, key on the Bisync terminal caused VMS to corrupted Version 1.1, it was pressing the <SYS REQ> crash because of badly pool. RESPONSE Under certain conditions, the <SYS REQ> key sends a zero-length message to the VAX host. YODRIVER (the BTS port driver) incorrectly detects and handles these =zero-length messages; instead, pool. the Since the there should be fixed patch to driver <SYS in REQ> be a key little future YQODRIVER Organization on overwrites a is not impact release available demand an 81 64K used in on user systems. of BTS; in from basis. arbitrary your the the bytes Bisync The of environment, problem will interim, Software nonpaged there Services is a Support VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: VT200 not defined July 1985 3 V4.0 Seq. Bifloy221 & 33.20.1 TTDRIVER in $DCDEF PROBLEM STATEMENT $DCDEF does not contain definitions for new terminals. RESPONSE Complete no longer terminal in definitions $DCDEF. The are located only definitions in in $DCDEF for compatibility with versions of VAX/VMS 4.0. All new applications should use the S$STTDEF for the terminal device types. $TTDEF remain and only prior to Version definitions from The documentation will be further clarified in a future revision of the VAX/VMS I/O User's Reference Manual, Part I, which (as of VAX/VMS Version 4.0) indicates on page 8-18 that S$TTDEF contains characteristics. symbol definitions 83 for terminal VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: DMA not set on July 1985 1 VAX/VMS V4.0 of 1 Seq. 33.20.2 to DMF-32 VAX/VMS TTDRIVER DMF-32 lines PROBLEM STATEMENT Under VAX/VMS comes up with Version /NODMA 4.0, any terminal connected a set. RESPONSE The problem parameter up with is that the TTY_ DEFCHAR2. DMA DMA bit Setting set. 84 (40 hex) this bit was not set in causes the lines the SYSGEN to come VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: July 1985 1 of V4.0 Seq. 2 34.20.1 LPDRIVER SYSTEM-F-EXQUOTA error on printout PROBLEM STATEMENT In VAX/VMS Version 4.0, the "SYSTEM-F-EXQUOTA, is printed small as when six exceeded quota" attempting blocks). error message: to print a relatively The error occurs when small the printer with the SET PRINTER/NOFF command. This problem only a line printer and not with a terminal printer. file (as is up set occurs with RESPONSE The line printer driver attempts to expand the data to a system buffer which will, in turn, be output by the device. When the printer is set up with the SET PRINTER/NOFF command, the line printer driver interprets a single form feed character as multiple line feed characters. If the expanded data is greater than the system buffer, the line printer driver attempts to allocate more memory. If the amount of memory allocated exceeds the SYSGEN parameter MAXBUF, the symbiont prints the following error message: "SYSTEM-F-EXQUOTA, In VAX/VMS Version manager, and print symbiont exceeded guota" 4.0, related the print symbiont, job utilities are completely now buffers output to the printer. 85 controller, queue rewritten. The VAX/VMS Systems Dispatch, July 1985 2 of 2 The error: "SYSTEM-F-EXQUOTA, in this line exceeded As a instance, printer the indicates driver default exceeded quota" to receiving the the system buffer symbiont output used by the buffer has system maximum buffer size. temporary workaround, avoid that expand this increase error. (decimal) might be required. 86 A the SYSGEN parameter MAXBUF to MAXBUF size greater than 5000 VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Read July 1985 1V V4.0 Seq. o £ 40.40.1 RMS from SYSSOUTPUT fails PROBLEM STATEMENT With VAX/VMS Version 4.0, FORTRAN program READ such (6,*) as the the user cannot read from SYSSOUTPUT. A following: VALUE END fails with the error message: RFOR-F-ERRDURREA, unit user error during read 6 file SYS$OUTPUT:.; PC 00000412 ~RMS-F-FAC, record operation specified file access not permitted by (FAC) RESPONSE VAX/VMS reads Version and 4.0 writes, only allows in previous as writes to versions SYS$SOUTPUT of VAX/VMS) (instead because of it is enforcing that the stream is meant for output. Previous versions of VAX/VMS incorrectly allowed reads from SYSSOUTPUT (and writes to SYSSINPUT). However, since many existing the old behavior will after Version 4.1. be programs restored 87 in depend a on future this update capability, of VAX/VMS VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: COPY/OVERLAY fails July 1985 1 of 1 VAX/VMS V4.0 Seq. 40.40.2 VAX/VMS RMS if destination write-protected PROBLEM STATEMENT COPY/OVERLAY does not work remote node and the Instead of copying destination, COPY produces "$COPY-E-OPENOUT, "-RMS-E-FEX, if the destination specified the data the file is located on a version number already from the source file exists. to the following error message: error opening NODE::FILE.EXT;1 as output" file already exists, not superseded” RESPONSE If a file accessor, is protected an access against conflict write occurs. If access a file by the network is available for write access, the COPY/OVERLAY operation succeeds with no errors. If the destination is protected against the write access request, the operation fails, since the COPY utility uses the create-if option when the /OVERLAY qualifier is specified. For DECnet file operations, this option is simulated within RMS as an $OPEN or "on-error" S$CREATE sequence. This simulation is attempting the $CREATE under circumstances other than the definition of create-if allowed. For instance, if the destination file is write access, RMS incorrectly attempts to create a SCREATE operation then fails with the error: "-RMS-E-FEX, since file already exists, locked against new file. The not superseded" the version in question already exists. We expect to correct this behavior in a future update of VAX/VMS after Version 4.1 so that RMS returns the correct $SOPEN and does not attempt to create a new file. 8g error from the VAX/VMS Systems Dispatch, July OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Confusion on 1985 jlieyzy V4.0 Seqg. 3k 40.40.3 RMS $CREATE using searchlists PROBLEM STATEMENT An attempted located file creation the first using Attempting, fails when translation for example, of the a destination directory is not searchlist. to create: SYS$SYSROOT: [SYSMGR.MGRUTIL] FOO.BAR fails if SYS$SYSROOT SYSSCOMMON:, where is defined SYS$COMMON destination directory as is a searchlist of $1$DUA21:[S¥S7.], $1$DUA21:[SYS7.SYSCOMMON.] and the is SYS$COMMON: [SYSMGR.MGRUTIL]. RESPONSE The RMS $CREATE service does Instead, it only translation of any example, the not first translation ($1$DUA21: [SYS7.SYSMGR.MGRUTIL]) This behavior Manual on page attempt to -explore a searchlist fully. attempts to create new files using the first searchlist logical name that it encounters. In the is documented of the destination did not exist. in the Record Management Services Reference RMS-40. 89 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: $RENAME returns July 1985 1 of V4.0 Seq. 1 40.40.4 RMS incorrect error message PROBLEM STATEMENT For VAX/VMS Version 4.0, the RMS $RENAME following error when the file to be $RMS-E-ACC, file Prior to following ACP VAX/VMS error, access Version which service renamed does returns not the exist: failed 4.0, S$RENAME would return is much more meaningful the and appropriate: $RMS-E-FNF, file not found RESPONSE fixed in VAX/VMS Version 4.1. o~ This problem is 90 VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Access July control 1985 1oL V4.0 Seq. 40.40.5 RMS string parsed incorrectly PROBLEM STATEMENT In addition to the user name and password, if an is specified in the access specification, there are control string of cases when the incorrectly remote conveyed to occurs when attempting the local system. the to COPY a node. file a For account example, from a use the name DECnet node password is remote this node to RESPONSE Several wutilities, including COPY, RMS option open-by-file-id for accessing their input files. This function is simulated for DECnet file access and the logic within RMS which performs this does not properly detect a masked password in the access control string. Thus, the masked We password expect VAX/VMS to is not replaced correct after Version this by the problem 4.1. 91 real in a one. future update of VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: 1985 1 VAX/VMS V4.0 VAX/VMS COMPONENT: Run-Time SUBCOMPONENT: VAX BASIC July BASIC programs Seq. £} 45.1.1 Library Language return fo an Support incorrect ERL for errors 50 and 52 PROBLEM STATEMENT If all of the following might return an incorrect 1. 2. Error 50 (Data number) must It occur must conditions ERL: format occur, error) or a VAX Error 52 BASIC program (Illegal occur. in a subprogram, external function, or DEF . 3. 4. The compilation in which the error occurs must execute an ON ERROR GO BACK. It can either explicitly execute this statement or implicitly execute it One of the by not outer having an error handler. routines must execute a RESUME. When the error handler does a RESUME, an access violation occurs. Normal condition handling cannot handle the exception and an improperly handled condition results. RESPONSE This problem was introduced with VAX/VMS fixed in a future update of VAX/VMS. Version 4.0 and will be There are two interim workarounds: 1. Add error handling to the subprogram that generated the error. 2. Have the next, outermost routine that has a handler for the specific error execute an ON ERROR GO TO 0. 93 VAX/VMS Systems Dispatch, OPERATING SYSTEM: July 1985 1*ofr VAX/VMS V4.0 PRODUCT: VAX/VMS COMPONENT: ANALYZE ANALYZE/IMAGE reports incorrect link Seq. date and ! 55.5.1 time PROBLEM STATEMENT VAX/VMS Version 4.0 ANALYZE/IMAGE yields an for link date and time for images created Version 3.n. RESPONSE This problem is fixed in VAX/VMS Version 4.1. 95 incorrect value during VAX/VMS VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: AUTHORIZE has July 1985 1Mo VAX/VMS V4.0 VAX/VMS f ! Seq. 55.10.1 when either AUTHORIZE trouble parsing /<access> qualifiers PROBLEM STATEMENT AUTHORIZE 'PRIMARY' UAF> has or trouble parsing 'SECONDARY' is /<access> entered twice. modify JOE /network=(primary, $UAF-E-BADVALUE, qualifiers 1-4, primary, 6-8) error in value specification /PRIMARY/ RESPONSE We expect to after Version redesign this syntax 4.1. 97 for a future update of VAX/VMS VAX/VMS Systems Dispatch, OPERATING July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: 1985 1 V4.0 Seq. of 1 55.10.2 AUTHORIZE REVOKE/IDENTIFIER does not remove UICs PROBLEM STATEMENT The command REVOKE/IDENTIFIER of the AUTHORIZE utility does not seem to work properly. It does not appear to be possible dissociate an identifier from a UIC with that command. to RESPONSE There are personal two types identity identifiers are of identifiers: owned their by a users. user A UICs and or a group is something RIGHT RIGHTs. holds; it is something solid which, if he holds right to access specified resources. RIGHT identifiers database; UIC then must they identifiers, on first be can be the other created granted hand, or (or it, be to A UIC users; which is a these a user allows him the added) revoked can of to or added the rights from users. with their users, but cannot be granted or revoked. The reason is that it does not make any sense to grant a person to another person, but it does make sense to grant a RIGHT to a person. To dissociate a UIC REMOVE/IDENTIFIER command. identifier 98 from a user, use the O VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Problem booting July 1985 oy it V4.0 Seq. 55.20.1 BACKUP standalone BACKUP PROBLEM STATEMENT Under some user to before circumstances, insert it This will with a CI is the standalone application through using the BACKUP might (third) second floppy request or TU58 the volume volume. only occur when booting from console media on a VAX adaptor and disks accessible through the CI (either HSC disks or MSCP server). disks served from other VMS nodes through the RESPONSE We expect that this problem will be fixed in a future update of VAX/VMS after Version 4.1. Until then, do not insert the third floppy or TU58 volume immediately after it is requested. Instead, make sure that activity has ceased (i.e., the red light on the TU58 has been off or the floppy drive has stopped clicking) for at least ten seconds before switching volumes. Standalone BACKUP will print a message describing each remote disk which has been configured into the system and is accessible. Failure to wait a sufficient amount of time might result some remote disks not being available for the backup. 99 in VAX/VMS Systems OPERATING Dispatch, SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: CONVERT CONVERT/RECLAIM may July 1985 . V4.0 access Seq. ofiHl 55.30.1 violate PROBLEM STATEMENT When attempting an access to perform a CONVERT/RECLAIM on an RMS violation occurs. The file is large, yet ISAM very file, sparsely populated as a result of many record deletions. RESPONSE The index structure is processing of the file is corrupt. However, we believe that CONVERT/RECLAIM should be able to determine that the data is incorrect, and this can we expect to it enhance CONVERT/RECLAIM to be more robust in a future update of VAX/VMS. A file CONVERT corrupted command in such manner be recovered by issuing a as: $ CONVERT OLD.DAT NEW.DAT This will produce a fresh version of the file, although it will be considerably smaller than the original file because of the scarcity of records in OLD.DAT. In order to preallocate space for the new file to allow for the eventual insertion of more records, use an FDL file which describes the eventual size of the file. EDIT/FDL provides an easy method to specify these parameters. 101 VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS CONVERT COMPONENT: CONVERT July can incorrectly 1985 1 V4.0 report Seq. DUP and SEQ of 1 55.30.2 errors PROBLEM STATEMENT CONVERT of mistakenly order when complains creating a about Prolog 1 segmented or 2 ISAM keys being out file. RESPONSE CONVERT compares segment showed previous key. concatenated by using We expect to current Since for Prolog segment-by-segment, the 3 key all key 3 files, Prolog to even be segments this if an greater are problem earlier than the extracted and can be avoided files. correct this problem VAX/VMS . 102 in a future update of VAX/VMS Systems Dispatch, July OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: DIRECTORY output 1985 Lo V4.0 Seqg. fAtl 55.65.1 DIRECTORY missing total line L PROBLEM STATEMENT In VAX/VMS total line. Version lines for 4.0, the DIRECTORY various does not directories display specified the on individual the command RESPONSE We expect to correct this problem 103 in a future update of VAX/VMS. VAX/VMS Systems OPERATING Dispatch, July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: DIRECTORY may 1985 1 V4.0 Seq. of 1 55.65.2 DIRECTORY display nonexistent files PROBLEM STATEMENT Issuing a a name node might simple cause and DIRECTORY command no wildcard nonexistent using characters files to be a file specification with (implicit displayed in or explicit) the DIRECTORY output. RESPONSE this problem in a future update of VAX/VMS. 104 N to correct ~ We expect VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: July 1985 oAl VAX/VMS V4.0 VAX/VMS Seq. 56.5.1 INITIALIZE INITIALIZE/INDEX:BLOCK=n not recognized PROBLEM STATEMENT The DCL command INITIALIZE fails to recognize the BLOCK keyword the /INDEX qualifier. RESPONSE We expect to fix this problem in 105 a future update of VAX/VMS. of VAX/VMS Systems Dispatch, July OPERATING SYSTEM: PRODUCT: VAX/VMS VAX/VMS COMPONENT: INSTALL Inability to The INSTALL way that appear install to be of Seq. an for of VAX/VMS certain INSTALL image =3 56.10.1 images changed compatibility compromised. installation feature was 1¥of V4.0 executable utility upward 1985 that was was Version 4.0 executable modified linked to with in such images disallow the a could the /TRACEBACK if: - the image - the image qualifier If you have those images subsequent is being installed with privilege(s) or is being installed with the /EXECUTE_ONLY (new for VAX/VMS Version 4.0) images that with attempt fall into this category, you the /NOTRACEBACK qualifier to install known the should relink specified. image A should be impossible, the successful. For the occasional instance where following command procedure /TRACEBACK attribute from the procedure's comments, the relinking may be image. As procedure is used to documented modifies eliminate the in the command the header of the image to convert it from a /TRACEBACK image into one that looks like it was linked /NOTRACEBACK. Once this procedure has modified the image in this way, there should be no problem INSTALLing the image. It is highly recommended possible. The following image header releases. offsets Therefore, only, guaranteed to remain unchanged. that the images are relinked command procedure relies on that it may change be viewed must work; correctly only between as soon as hard-coded major VAX/VMS temporary solution as a as long as these offsets NOTE The linker problem. has If certain there behavior is any which reference relates to the to this symbol SYSSIMGSTA from anywhere in the image, the linker ignores the /NOTRACEBACK command qualifier and links the image /TRACEBACK procedure may be anyway. used to For such undo the 107 images, linker's this command mistake. VAX/VMS Systems Dispatch, July 1985 2 of —_—————— DDV DN DDDNDDDNDDNDNnNDD Seq. This procedure calls PATCH/ABSOLUTE to modify the 3 56.10.1 transfer address array for an image. It deletes the first transfer address in the array by moving the following 3 entries in the array up one position, while placing a zero in the last position vacated. This procedure only operates on images containing the SYSSIMGSTA in the first entry in the transfer address address array. This procedure is useful for converting an image linked with /TRACEBACK into one that no longer has /TRACEBACK. Because this procedure uses certain image header offsets as hard-coded values, it will remain correct only for Version 4.0 of VAX/VMS and for subsequent releases as long as the image header offsets This Pl remain procedure = Name of valid. requires the image the to PATCH /ABSOLUTE /NOOUT /NOJOU Determine SO0 if the image is specification of be one parameter: modified 'P1' linked /TRACEBACK with the flavor of SYSSIMGSTA. EXAMINE /WORD 2 DEFINE BASE = \ REPLACE /LONG BASE 80000168 EXIT 80000168 EXIT EXIT $ IF $STATUS THEN GOTO PATCH_IMAGE $ PATCH /ABSOLUTE /NOOUT /NOJOU ‘P1l’ 1 ! Determine if the ! Pl of SYSSIMGSTA. flavor image is linked /TRACEBACK with ! EXAMINE /WORD 2 DEFINE BASE = \ REPLACE /LONG BASE 7FFEDF 68 EXIT 7FFEDF68 EXIT EXIT $ IF $STATUS THEN GOTO PATCH_IMAGE $ EXIT 108 the VAX/VMS Systems Dispatch, July 1985 3 of -——nNBnnonn Seq. 1 At this point, we have an image that was linked /TRACEBACK. Now, modify the transfer address array so that the image appears to the system as if it was linked /NOTRACEBACK. 1 PATCH /ABSOLUTE /OUT='Pl' Petrieve to offset /JOoUu='Pl' transfer address 'Pl’ array EXAMINE /WORD 2 DEFINE BASE = \ ! ! ! Move the longword ! ! Since the fourth array element contains a zero, will contain a zero as well once we're done. ! 56.10.1 PATCH_IMAGE: ! ! ! (which second, third in the array, and fourth array elements thus clobbering the first up one entry is SYSSIMGSTA for images linked with /TRACEBACK). () EXAMINE /LONG BASE + DEFINE CONTENTS = \ DEPOSIT /LONG BASE + 4 0 = CONTENTS ! EXAMINE /LONG BASE + DEFINE CONTENTS = \ 8 DEPOS1T /LONG 4 BASE + = CONTENTS ! EXAMINE /LONG BASE + DEFINE CONTENTS = \ 0C DEPOSIT /LONG BASE + 8 = CONTENTS ! UPDATE EXIT 109 the third 3 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: July 1985 1¥ef VAX/VMS V4.0 Seq. ) 56.15.1 VAX/VMS LIBRARIAN Problem decompressing a library PROBLEM STATEMENT The following decompress a error message is generated when attempting to library: "-LIBRAR-E-INDEXERR, index error in 'library file-spec'" RESPONSE The librarian maintains a copy of library address space of the process so that it same block of the library from the disk blocks in the virtual never needs to read the more than once. When a new library is being created, it is first built within the virtual address space and then written to the disk tile after the library is complete. be contained this problem The problem here is that the library is too large in the process' virtual address space. Solutions are being investigated for a future update to to of VAX/VMS. As a page workaround, increase file The system quota. configuration or either virtual by the the page virtual count process may page be authorized count or limited by the the quota. It may be necessary to raise either or both of these values. The process’ PGFLQUOTA may be changed in the User Authorization File with the AUTHORIZE Utility to be effective upon subsequent login. The value of VIRTUALPAGECNT may be changed with the SYSGEN Utility; it will be necessary to reboot the system to use the new value. Usage of virtual memory can be observed with CTRL/T while running the librarian. SHOW PROCESS/ACCOUNT and SHOW PROCESS/QUOTA also give useful information about the virtual memory usage and page file quota. 111 VAX/VMS Systems OPERATING Dispatch, July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Linker open file 1985 TWo V4.0 Seq. sl 56.20.1 LINKER limit problem PROBLEM STATEMENT The linker can incur an access number of object libraries. violation when processing a large RESPONSE The linker was modified for VAX/VMS Version 4.0 to leave open as many of its input files as possible (subject to the open file limit, of course) between passes as a performance aid. Prior to VAX/VMS Version 4.0, the linker opened and closed its input files up to three Because of times the as part limit of normal imposed by processing. the librarian on the number of simultaneously open library files, there is occasionally a problem determining which library file to close when it is necessary to do so. We expect to fix this problem in a future update of VAX/VMS. Until that time, a workaround is to specify an open file limit (FILLM parameter in SYSUAF.DAT) between 16 and 22. 113 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Linker rejects July 1985 lof1l VAX/VMS V4.0 VAX/VMS Seq. 56.20.2 when parsing LINKER valid file names in options some valid file files PROBLEM STATEMENT The linker files rejects specifications that are specified within options files. RESPONSE The linker does its own file parsing when specifications given within options files. file syntax accepted by the linker and by RMS processing file Unfortunately, the are not equivalent. In particular, the linker does not accept file names files that contain an underscore in the file type. in We expect VAX/VMS. to correct this problem 114 in a future update of options VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: Random BROADCAST July 1985 VAX/VMS V4.0 1i7ofi1! Seq. 56.75.1 VAX/VMS SHOW classes disabled PROBLEM STATEMENT Upon logging in, certain BROADCAST classes might be disabled. RESPONSE This problem is fixed in VAX/VMS Version 4.1. 115 VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: July 1985 1ol VAX/VMS V4.0 VAX/VMS COMPONENT: SET SET PASSWORD. signals Seq. 56.80.1 PASSWORD errors twice PROBLEM STATEMENT In VAX/VMS messages Version 4.0, the SET PASSWORD utility signals error twice. RESPONSE This problem is caused by an error handling conflict in that image. We expect to correct this problem 1157 in a future update of VAX/VMS. VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: SYSSTRNLNM example July 1985 1l V4.0 Seq. of 1 65.5.1 DOCUMENTATION is incorrect PROBLEM STATEMENT The FORTRAN code for the translate logical name in the VAX/VMS System Services Reference Manual services is example incorrect. RESPONSE We will correct documentation this example in set. 119 a future revision of the VAX/VMS VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: SNDOPR symbolic July 1985 1 VAX/VMS V4.0 Seq. of 1 65.5.2 VAX/VMS DOCUMENTATION code incorrect PROBLEM STATEMENT The $SNDOPR service, which is described in the VAX/VMS System Services Reference Manual, lists an incorrect symbolic code, OPCSM_NM_CENTRAL. RESPONSE The correct the next symbolic code, revision of this OPC$M_NM_CENTRL, manual. 120 will be documented in VAX/VMS Systems OPERATING Dispatch, July SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Undocumented 1985 1O V4.0 Seq. £¢r2 65.5.3 DOCUMENTATION error message for MOUNT PROBLEM STATEMENT The following System error Messages and message Recovery $MOUNT-I-REDCACHE, is not documented Procedures volume in Reference mounted with the VAX/VMS Manual: reduced cache size RESPONSE This message was erroneously next revision of information should REDCACHE, volume Facility: the have omitted, but will system messages been included. mounted with reduced be included manual. cache The in size MOUNT Explanation: This informational /PROCESSOR=UNIQUE qualifier is message used on occurs the when MOUNT the command and insufficient paged pool is available to allocate a file system buffer cache using the sizes specified by the ACP_MAPCACHE, ACP_DINDXCACHE cache with User a minimal Action: /PROCESSOR=UNIQUE was to avoid ACP_DIRCACHE, SYSGEN the The ACP_HDRCACHE parameters. number of usual qualifier problem of Instead, buffers is reason before file and unique allocated. to VAX/VMS system a use the Version activity on 4.0 one volume degrading file system performance on other volumes. This degradation was caused by the single threaded nature of the file system ACP. 1:2) the following VAX/VMS Systems Dispatch, July 1985 In VAX/VMS Version 4.0, XQP provides a higher 2 of 2 the procedure-based level of file system concurrency than was The ACPs. multiple with even possible previously /PROCESSOR qualifier was retained to allow discrete I/O buffer caches to be associated with specific volumes, instead of all volumes sharing the same I/O buffer cache, which is the default behavior. Therefore, the recommended action is to remove the However, if discrete I/O /PROCESSOR=UNIQUE qualifier. buffer caches are needed, increase the size of the SYSGEN parameter PAGEDYN to account for the number of I1/0 buffers required. Also, increase the value of the SYSGEN parameter SYSMWCNT, paging. 122 to avoid increased system VAX/VMS Systems Dispatch, July 1985 OPERATING SYSTEM: VAX/VMS PRODUCT: VAX COMPONENT: IVP Warning message V4.0 COBOL causes 1 of 1 IVP Seq. 85.25.1 V3.1 to fail PROBLEM STATEMENT When the Procedure user chooses to (IVP), chooses run the Installation Verification not to save the IVP file in [SYSTEST], and chooses to installation, for example, * Do you want to run the purge IVP after the * Do you want to leave COBOLIVP.COM * Do you want the to purge following message files appears files installation in the the end of during [YES]? [SYSTEST] replaced by this at replaced Y directory installation the [YES]? N [YES]? Y the procedure: Successful test of VAX COBOL V3.1-38 $PURGE-W-SEARCHFAIL, error searching for VMI$SROOT: [SYSTEST]COBOLIVP.COM; -RMS-E-FNF, file not found $VMSINSTAL-E-IVPFAIL, The IVP for COBOL V3.1 has failed. RESPONSE If the IVP produced a "Successful test of VAX COBOL V3.1-38" message, the installation was successful, regardless of the inconsequential VMSINSTAL failure message at termination. This misleading message will COBOL following Version 3.1. be 123 fixed in a release of VAX VAX/VMS Systems Dispatch, OPERATING SYSTEM: 1985 1o VAX/VMS V4.0 PRODUCT: VAX COMPONENT: Error July Seq. FaRl! 85.50.1 PASCAL V2.6 STARLET in XAB$ definitions PROBLEM STATEMENT VAX PASCAL programs VAX PASCAL STARLET that no reference longer XABs execute as they are defined in the properly. RESPONSE The STARLET.PAS that shipped with VAX PASCAL V2.6 contains XABS fields that are not properly positioned in the XABSTYPE record. The problem can be worked around by cutting the XABSTYPE record definition from the older version of STARLET.PAS (it was shipped with VAX PASCAL V2.3), editing it into the new version, and then recompiling with the following commands: $ SET DEFAULT SYSSLIBRARY $ PASCAL/NOOBJ/ENV=STARLET.PEN STARLET This problem will be fixed in a 125 future version of VAX PASCAL. VAX/VMS Systems Dispatch, OPERATING SYSTEM: PRODUCT: COMPONENT: VAX/VMS VAX/VMS July 1985 1 V4.0 Seq. of 2 95.5.1 OPCOM Batch/remote enable of operator terminals PROBLEM STATEMENT VAX/VMS provides the operator error using this requires log that the ability the to set up REPLY/ENABLE operator be a terminal as an command. However, logged on to the terminal. It is highly desirable to extend the functionality of this command to set up terminals remotely by allowing the addition of a terminal device name. This, in turn, allows terminals to be set up for operations in the system start-up files. RESPONSE It is possible to set up user terminals as operator terminals in the SYSTARTUP.COM file. Please consider including the following commands in this command procedure. Also, note that this method can be used to disable operator messages on OPAO. To successfully execute command procedure, $! the ENABLE.COM $! $ ASSIGN/USER _TTAO: $ the DCL command following must REPLY/ENABLE be done: ;ENABLE USERS TERMINAL SYS$COMMAND REPLY/ENABLE $ EXIT 127 from a VAX/VMS Systems Dispatch, This be a method command $! can used procedure. to For DISABLE.COM St $ ASSIGN/USER _OPAO: $ REPLY/DISABLE $ EXIT and July 1985 execute example, 2 other REPLY of commands from REPLY/DISABLE: ;DISABLE BROADCAST ON OPAO: SYS$COMMAND REPLY/LOG: $! OPRLOG.COM $! $ ASSIGN/USER _TTAO: $ REPLY/LOG $ EXIT ;CLOSE CURRENT OPERATOR'S SYS$COMMAND 128 2 LOG VAX/VMS Systems Dispatch, July 1985 140 Seqg. ERRANT FORMATTING BEHAVIOR IN VAX/VMS PRINT £19) 95.5.2 SYMBIONT The goals of this document are to describe the desired the print symbiont for formatting files to paper, behavior of to explain errant and 4.0 formatting print hardware, in a and future Neither behavior symbionts, to to present maintenance the VAX/VMS in the VAX/VMS demonstrate the the expected Version masking VAX/VMS 3.n effect of formatting Version certain behavior update. Version 3.n nor the VAX/VMS Version 4.0 print symbiont properly formats the first data line of a page to the first printable line of the paper. Both of these versions are inconsistent in formatting data to the paper, but in different ways. Desired The desired described 1) behavior formatting Behavior data to the below: The first the data first regardless input 2) for Formatting of of the of headings a page should line carriage of appear the control on paper, type of an file. Placement pages the line printable printed of paper placement copy of and data should headings be and on subsequent consistent with data on the first page. 3) 4) When a header is requested, appear consistently of paper the on on every the the first header should the first appear on the line page. When a standard VAX/VMS print symbiont requested, should printable data line after third printable paper. 129 header the line is header of the page is VAX/VMS Systems Dispatch, July 1985 2 of 9 Seq. 95.5.2 Current Formatting Behavior In VAX/VMS Version 3.n, for files with carriage control of FORTRAN (FTN), PRINT (PRN), or implied (CR), the first data line of the page appears consistently on the second printable line of the paper. Furthermore, when a header is requested, the header is printed on the second printable line of the paper on the first page and on the first printable line of the paper on subsequent pages. Data lines following the header are similarly in error as a result of the header positioning. Files with carriage control type of NONE in Version 3.n are formatted correctly so that the first data line of every page is output to the first printable line of the paper. However, when /HEADER is specified in a file of carriage control type of NONE, headers are printed on the second printable line of the paper. In VAX/VMS Version 4.0, the print symbiont’'s main format routine attempts to format the data to ensure that the first data line of every page starts on the first printable line of the paper. Nevertheless, the first data line of a file with FTN or PRN carriage control is printed consistently on the second line of the first page and the first 1line of subsequent pages. Furthermore, when a header is requested in a file with FTN and PRN type carriage control, the first data line from the file is printed on the fourth printable line on the first page and on the third printable line on subsequent pages. Files with CR and NONE type carriage control are formatted correctly in VAX/VMS Version 4.0 so that the first data line of every page is output to the first printable line of the paper. Similarly, when /HEADER is specified in a file with CR and NONE carriage control, the first data line output from the file is printed correctly on the third printable line of the paper. The following behavior, tables respectively: describe 130 Version 3.n and Version 4.0 VAX/VMS Systems Dispatch, July 1985 3 of 9 Seq. Version 95.5.2 3. ===zzzzss=zs=zz=zszszs=saa PRINTABLE LINE FIRST PAGE CARRIAGE FTN PRN ====== CONTROL TYPE CR NONE 1 = o~ - data 2 data data data data 3 4 data data data data data data data data SUBSEQUENT 3 = % ) data PAGES 2 3 4 data data data data data data data data data data data data T/FEED/HEADER ====z=== =========== PRINTABLE LINE =========s======== CARRIAGE CONTROL TYPE CR FTN PRN & & =~ = 2 header header header header 3 4 = data S data = data data data SUBSEQUENT 3} header header header data PAGES 2 & £ = data 3 data data data data 4 data data data data FIRST PAGE 131 NONE = VAX/VMS Systems Dispatch, July 4 of 1985 Seqg. Version 4.0 95.5.2 PRINT/FEED PRINTABLE LINE FTN 1 2 3 4 data data data data data data data data data data data data data data SUBSEQUENT 1 data data data data PAGES 2 3 data data data data data data data data 4 data data data data FIRST PAGE Versi 4.0 CARRIAGE CONTROL TYPE PRN CR NONE PRINT/FEED/HEADER CARRIAGE PRINTABLE LINE PAGE CONTROL TYPE CR NONE FTN PRN header header header header data data data data data data header header header header data data data data data data data data PAGES C SUBSEQUENT W P FIRST 9 132 VAX/VMS Systems Dispatch. July 1985 5,,0£49 Seq. 95.5.2 Formatting Behavior Altered by Hardware Each line printer interprets horizontal and vertical format effectors into the proper physical action for that type of printer. Some of the older high-speed line printers mask one or more format effectors that immediately follow a form feed. This action can alter the placement of the first line of data on the page; for example, when a line feed that follows a form feed is ignored, the first printable data line will appear one line above its intended placement. Therefore, the output of such a printer Version 4.0 disagrees with with either VAX/VMS the previous Version 3.n or tables. The following table was generated on a high-speed line printer that exhibited this masking behavior. The VAX/VMS Version 3.n print symbiont resulting effect. 133 was used to demonstrate the VAX/VMS Systems Dispatch, July 1985 6 of Seqg. Masked 3.n behavior 95.5.2 PRINT/FEED ==a== =s=s=ssssmsz===ssss=ssSssazzss=ss PRINTABLE LINE FTN 1 2 3 = data data = data data . data data data data data 4 data data data data SUBSEQUENT 1 data data data data PAGES 2 data data data data 3 data data data data 4 data data data data FIRST PAGE CARRIAGE CONTROL TYPE PRN CR NONE PRINT/FEED/HEADER PRINTABLE LINE FIRST PAGE SUBSEQUENT PAGES CARRIAGE CONTROL TYPE FTN PRN CR NONE 1 header header header header 2 3 data data data data data 4 data data data data 1 2 3 4 header N data data header data data header data data data data data data 134 9 VAX/VMS Systems Dispatch, July 1985 Seq. Expected maintenance Future In a to of format data to the paper the first and subsequent update Formatting Behavior after VAX/VMS Version 4.0, we expect correctly. The first data line pages will print on the first printable line of the paper. This desired behavior will be achieved by the application of certain rules during the processing of the file. a) Line Overflow: If /WRAP or /TRUNCATE is enabled and the print symbiont detects an attempt to output data past the right margin, a carriage return-line feed pair is inserted in the data stream. b) Page Overflow: If JFEED 1is enabled and a vertical format effector attempts to position output into the bottom margin, that vertical format effector is replaced with a effectors 1include vertical tab. The following table form feed. 1line describes feed, the 135 Vertical form expected format feed, behavior: and VAX/VMS Systems Dispatch, July 8 1985 Seq. Expected n behavio 4.0 PRINT/FEED CARRIAGE CONTROL TYPE PRINTABLE PAGE LINE FTN PRN CR NONE 1 2 data data data data data data data data data data data data 3 data data data data data data data data data data data data data data data data SUBSEQUENT PAGES B wN e 4 ted behavior after Version data data data data 4.0 PRINT/FEED/HEADER s=sz===z=== PRINTABLE LINE PAGE SUBSEQUENT PAGES B WN FIRST FTN CARRIAGE CONTROL TYPE PRN CR NONE header header header header data data data data data data data data header header header header data data data data data data data 136 data 9 95.5.2 ==== =============== FIRST of VAX/VMS Systems Dispatch, July 1985 9 of Seqg. The intent of this article is behavior in the VAX/VMS print The this VAX/VMS well-formatted 95.5.2 to describe errant formatting symbiont, to demonstrate the error masking effect of hardware, for solving 9 and to present our strategy problem. print symbiont printable files. will A continue to well-formatted support file does not rely on the page overflow and line wrap logic of the print symbiont. Such a file includes all the necessary carriage control information to ensure proper positioning of the text at all page boundaries. 137 VAX/VMS Systems Dispatch, OPERATING SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Deletion of July 1985 1 of 1 (all versions) Seg. 95.5.3 SYS global sections PROBLEM STATEMENT When a global deleted, error the section file message is is created, cannot be returned mapped deleted to a file, immediately. indicating that the deleted, there are file and then 1Instead, is locked an by another user. RESPONSE When a global structures section that must is be released. section for delete and moves it After all references to it are $DGBLSC a number marks of the data global out of the normal search path. removed, the section actually evaporates and the file is available to be deleted. The following system services should be called (in the order listed below) to 2. references: SUPDSEC - file on the page table entry). $DELTVA - to write disk to back (this unmap all does all modified pages reset modified the references to the to the section flag global in the section (i.e., page table entries that map to the section). 3. $DGBLSC global 4. to release the data structures that define the section. $DASSGN - to release parameter to $CRMPSC not specifically the channel (this that was passed as is also done by requested by the user). 138 an input image rundown if N’ 1. all — release VAX/VMS Systems OPERATING Dispatch, SYSTEM: VAX/VMS PRODUCT: VAX/VMS COMPONENT: Incorrect The July entries VAX/VMS incorrect 1985 dRerey V4.1 Seq. a1 95.5.4 MICROFICHE in Version Version entries. 4.1 4.1 microfiche microfiche Those entries in index the contains Version 4.1 some index, starting with the MANAGE facility and extending to the end of the index, refer to incorrect page number and/or frame number. In all cases, the correct page number will be within one page The VAX/VMS place of of the Version the referencing Version 4.1 index, for correct. This error into future page the number 4.0 VAX/VMS new indicated index should Version listings on be 4.1 that the microfiche. retained index, were and used except shipped with microfiche. All new entries in the Version 1listings distributed with that version, will be corrected and microfiche updates. 139 will not be carried in when the 4.1 are over CUMULATIVE INDEX (Version 3.n) 141 VAX/VMS SYSTEMS DISPATCH CUMULATIVE INDEX FOR VAX/VMS V3.n JULY 1985 Following is a listing of all articles for VAX/VMS V3.n and layered products. The following components 1list was designed so that in future issues it could be expanded. there are allows for several numbers "reserved" for that purpose. Also, expanding the primary category te <include related 11.1 may be used for the COPY UTILITY, the components list will be reviewed to 11.2 may be used insure that for Consequently within each category the numbering scheme subsets. For example, the DIFFERENCES UTILITY, under etc. 11.0, UTILITI Periodically, it accommodates the current software needs. R = indicates a republished article Component/ Product Sequence Number. Operating System, Title of Article Mon/Yr VAX/VMS V3.0 VMS EXECUTIVE SYS 1.2.1 SHAREABLE IMAGE RESTRICTION V3.0 Nov 82 1.2.2 CRASH WITH USER-WRITTEN DRIVER v3.o Nov 82 1.2.3 VERSION 3.0 POWERFAIL RESTART ERROR 1.2.4 CPU TIME LIMIT ERRORS V3.0 V3.0 Jan 83 Jan 83 1.2.5 NETWORK ASSIGN FAILS V3.0 Mar 1.2.6 FLX TRANSFER OF UNFORMATTED BINARY FILES V3.0 May 83 1.2.7 SET MODE INAPPROPRIATE FOR DISK DEVICES V3.0 May 83 1.2.8 EXCESSIVE UBA PASSIVE RELEASES V3.0 May 83 1.2.9 1.2.10 NO ELEVATED PRIVILEGES FOR EXIT HANDLER $ASSIGN TO NET WITH LOGICALS V3.0 V3.0 Jul 83 Jul 83 1.2.1 LOCK CONVERSIONS TO SAME MODE v3.o Jul 83 1.2.12 PFN-MAP GLOBAL SECTIONS IGNORE PROTECTION V3.1 Jul 83 1.2.13 SS$_NOTALLPRIV NGT ALWAYS RETURNED V3.2 Jul 1.2.15 RX02 DOUBLE DENSITY PROBLEM V3.3 Jan 84 1.2.16 MORE DETAIL ON EXQUOTA V3.2 Jan 84 1.2.17 TPARSE SUBEXPRESSION AMBIGUITY TEST FAILS V3.2 Jan 84 1.2.18 1.2.19 VOLNUMBER DIFFERENT FROM SHOW DEVICE INITIAL VALUE OF THE LOCK STATUS BLOCK V3.2 V3.4 Jan 84 May 84 1.2.20 LIB$FIND_FILE FAILS AFTER V3.4 May 1.2.21 VMSIMAGES FILE IS DIFFERENT ON VAX-11/730 AND VAX-11/780 V3.4 May 84 1.2.22 PROBLEMS WITH BOOTBLDR V3.4 May 84 1.2.23 F$MODE RETURNS BATCH WHEN F$GETJPI RETURNS INTER V3.4 May 1.2.24 1.2.25 UNABLE TO BOOT WITH CACHE DISABLED POWERFAIL OF SECOND UBA ON 11/750 V3.5 V3.4 Sep 84 Sep 84 1.2.26 1.2.27 LOOP EXEC OR LOOP NODE ERROR BOOTBUILDER INIT/DENSITY PROBLEM V3.5 V3.6 Sep 84 Nov 84 1.2.28 BOOTBUILDER MEMORY GAP PROBLEM V3.6 Nov 84 1.2.29 WRITEBOOT NEEDED WHEN VERSION 1.2.30 ON MASSBUS 1.2.14 LOCAL MEMORY ADDRESS SET TOO HIGH 120 CALLS 83 Sep 83 84 84 V3.5 Jan 85 IMPROPERLY FORMATTED ERROR MESSAGES V3.5 Jan 85 1.2.31 EXCESSIVE SWAPPING TO GET BALANCE SET SLOT V3.5 Jan 85 1.2.32 SWAPPER TRIMS REAL-TIME PROCESSES V3.5 Jan 85 1.2.33 ACCESS VIOLATION WITH ANALYZE/DISK V3.6 Mar 1.2.34 $GETJPI FAILS ON PROCESSES IN MWAIT V3.1 Mar 85 1.2.35 READS WITH PROMPTS TO A MAILBOX DO NOT PROMPT V3.3 Mar 85 1.2.36 1.2.37 MOUNTED DEVICE NOT DEALLOCATED AT LOGOUT SECTBLFUL ERROR WHILE ACTIVATING IMAGE V3.5 V3.6 Mar 85 Mar 85 1.2.38 NO WORKING SET TRIMMING FOR LOW PRIORITY BATCH JOB V3.4 Mar 85 1.2.39 PROBLEMS WITH VAX-11/750 MICROCODE V3.5 May 85 1.2.40 $GETJPI FAILS WITH NULL PROCESS REQUEST V3.6 May 85 1.2.41 TU78 UNUSABLE AFTER WARM RESTART V3.7 May 85 143 3.5 IS INSTALLED V3.2 83 85 >roduct Sequence Number. Title of Article 1.2.42 CPU TIME LIMIT IS NOT DEDUCTIBLE 1.2.43 HIGH AST LATENCY Operating System Mon/Yr V3.7 Jul 85 V3.6 Jul 85 3ATCH, SPOOLING, JOB CONTROLLER BATCH 2.1.1 MAXJOBS NOT HONORED V3.0 Sep 83 2.1.2 HOW CAN A BATCH JOB DETERMINE ITS ENTRY NUMBER V3.4 Jul 84 QUEUE MANAGER 2.2.1 JOB ID NUMBER IS SOMETIMES NOT UNIQUE V3.2 Nov 83 JOB CONTROLLER 2.3.1 BATCH JOB INPUT FROM CARD READER FAILS V3.0 Jan 83 2.3.2 TRUNCATED ACCOUNT FIELD V3.0 Jan 83 2.4.1 2.4.2 PRINT/HEADER SKIPS LINE ON FIRST PAGE SPOOLED DEVICES LOSE FILES V3.0 V3.0 May 83 May 83 INPUT SYMBIONT 2.5.1 ALLOW MORE FLEXIBLE PLACEMENT OF EOF CARD V3.1 Jul 83 QUEUE 2.6.1 START/QUEUE ISSUED TO START A PRINT SYMBIONT V3.3 May 84 LOCK MANAGER 2.7.1 PROBLEM WITH INNER MODE LOCKING V3.6 Jan 85 3.1.1 3.1.2 RELOAD OF DRIVER WITH INCREASED UNITS SET TIME WRITES ACTIVE PARAMETERS V3.0 V3.0 Nov 82 Mar 83 3.1.4 CRASH WHEN CONNECTING SOFTWARE DEVICE V3.5 PRINT SYMBIONT 2.4.3 2.4.5 CONSOLE, BOOTING, SYSGEN DCL, Jan 84 V3.3 3.1.5 SYSGEN SHOULD SET CBT BIT FOR CR/NOCONT V3.4 Sep 84 3.2.1 SYSBOOT NOT COPIED CONTIGUOUSLY V3.4 May 85 V3.0 May 83 V3.0 V3.0 May 83 May 83 ACCOUNTING TIME SPECIFICATION PROBLEM 4.1.3 41,4 ACCOUNTING UICs >3 CHARACTERS CAUSE TERMINATION ACCOUNTING SORT REJECTS BLANK FIELDS 4.1.2 4.1.6 4.1.7 4.1.8 ACCOUNTING/SUMMARY/ID GIVES AN ERROR ACC/SUM/NOREPORT GIVES AN ERROR MESSAGE CTRL/C TO ACCOUNTING DOES NOT RESTORE VT100 ACCOUNTING SUMMARY HAS OUTPUT FORMAT ERRORS REPORT OF PAGES PRINTED IS INCORRECT V3.0 May 83 V3.0 May 83 ACCOUNTING UIC EXCLUSION DOES NOT WORK V3.0 V3.0 ACCOUNTING SUMMARY INCLUDES INVALID DATA V3.0 WILDCARDING DOES NOT WORK WITH ACCOUNTING ACCOUNTING/FULL DOES NOT WORK WITH PAGES >24 V3.1 ERRORS ACCESSING ACCOUNTING FILE V3.0 ACCOUNTING/SUMMARY KEYWORDS CANNOT BE ABBREVIATED V3.1 ACCOUNTING/OUTPUT SHOULD NOT DEFAULT TO SYS$OUTPUT V3.1 4.1.17 4.1.18 4.1.19 4.1.20 4.1.21 BAD NUMBER OF PAGES FOR ZERC PAGESIZE PRINTERS ELAPSED TIME FOR JOBS BASED ON QUEUE TIME REENABLING LOGIN FAILURES ACC SYMBOLS SIGNALS DUPSYM ACCOUNTING SUMMARY GENERATED INTEGER OVERFLOW 4.2.1 4.2.2 4.2.3 u.2.4 4.2.5 4.2.6 FALSE SYSINIT RECORDS IN ACCOUNTING FILE V3.1 AME WTLO$ DOES NOT ALLOW GROUP GLOBAL EFN V3.0 AME CANNOT HANDLE MULTIPLE MAC /CR IN GRP WRONG ERROR FOR > 9 CHARACTER FILENAME V3.1 V3.0 REPEATED MRKT$ CALLS OVERFLOW VIRT ADR SPACE SPWN$ DOES NOT WORK WITH MCR DEFAULT CLI AME DOES NOT CLOSE AN IMAGE BEFORE CHAINING May 83 V3.0 V3.0 V3.0 4.1.9 4.1.10 4.1.1 4.1.12 4.1.13 4.1.14 4.1.15 4.1.16 Sep 84 MESSAGES 4.1.1 4.1.5 AME May 83 Jul 83 ATTEMPTING TO INSTALL SECONDARY PAGING FILE OPERATOR FUNCTIONS, ACCOUNTING V3.1 V3.1 SYSGEN 3.1.3 SYSBOOT PRTSMB COMPUTES OVERPRINT INCORRECTLY PRINT/FLAG MISHANDLES PRINT/COPIES V3.0 V3.1 V3.2 V3.1 V3.1 V3.0 V3.0 V3.0 May 83 May 83 May May May May Jul Jul Jul 83 83 83 83 83 83 83 Sep 83 Sep 83 Sep 83 Jan 84 Sep 84 Sep 84 Jan 83 Mar 83 May 83 May 83 Jul 83 Sep 83 — Somponent/ Component/ Sequence Number Title of Article DcL 4.3.1 4.3.2 Product System Mon/Y) SPAWN CPU LIMIT V3.0 Nov 8: ON CONDITION THEN @FILESPEC V3.0 Nov 8: 4.3.3 F$VERIFY 4.3.4 CLI$GET_VALUE RETURNS 0 V3.0 V3.0 Jan 8: 4.3.5 EXPRESSION GREATER THAN 508 BYTES FAILS V3.0 Mar 8 4.3.6 CLI$_ABSENT NOT RETURNED IN CERTAIN CASE V3.0 Mar 8 4.3.7 AST QUOTA EQUAL ZERO CAUSES PROCESS TO HANG V3.0 May 8 4.3.8 ERROR EXIT NOT TRAPPED V3.0 May 8 4.3.9 4.3.10 4.3.11 FAIL TO ACTIVATE LOGINOUT GROUP LOGICAL NAMES ARE SKIPPED BY $DELLOG NEGATABLE INVALID AS KEYWORD V3.0 V3.0 V3.0 May 8 May 8 May 8: CDU DOES NOT CATCH AMBIGUOUS QUALIFIERS V3.1 P1-P8 IN LOGIN.COM V3.1 4.3.12 MCR MESSAGE OPCOM PRINT CLEDITOR (LOWER CASE) EVALUATES INCORRECTLY 4.3.13 EDIT/NOOUTPUT 4.3.15 Jan 8 May 8: V3.0 Jul 8: SPAWN INPUT FILE NOT FOUND V3.1 Jul 4.3.16 F$INTEGER HELP TEXT V3.1 Jul 8 4.3.17 DEFAULT FILE PROCESSING DOES NOT WORK V3.1 Jul 8 4.3.18 4.3.19 4.3.20 MULTIPLE LOCAL QUALIFIERS NOT ACCESSIBLE LIB$SPAWN FAILS WITH "TT" AS AN ARGUMENT F$FILE_ATTRIBUTES FAILS V3.1 V3.2 V3.2 Sep 8: Nov 8 Nov 8. 4.3.21 4.3.22 INCONSISTENT STATUS FROM SUBCOMMAND PROCEDURE OPTIONAL PARAMETER TO CLI$GET_VALUE V3.2 V3.2 Nov 8 Nov 8: 4.3.23 INVALID SHOW COMMAND DOES NOT REPORT ERRORS V3.2 Nov 8 4.3.24 INACCURATE "PRCNAM" ERROR REPORT V3.2 Nov 8: 4.3.25 NO PROMPT AFTER SET ON V3.3 Mar 8t 4.3.26 OPEN/WRITE/APPEND ERROR V3.3 Mar 8! 4.3.27 OUTPUT FILE NAME DERIVED FROM LOGICAL NAME V3.4 May 8L 4.3.28 INCONSISTENT USE OF UIC FORMAT V3.4 Jul 8! 4.3.29 F$CVTIME RETURNS INCORRECT TIME VALUE V3.4 Jul 8t 4.3.30 PROBLEM AFTER OPENING MANY FILES WITH OPEN V3.4 Jul 8 4.3.31 F$SEARCH DOES NOT RETURN A NULL STRING V3.4 Jul 4.3.14 LOGINOUT Operating Jul 8 8: 8t 4.4.1 LOGINS WITH NO SYSUAF FILE V3.0 Nov 8: 4.4.2 4.4.3 THE /DISK QUALIFIER REQURIES A COLON REMOTE TERMINALS WHEN JOB LIMIT IS ZERO V3.0 V3.1 Mar 83 Sep 8: 4.4y ACCESS VIOLATION DURING SUBSEQUENT BATCH JOBSTEPS V3.6 Jul 8¢ 4.5.1 EXTRA DELIMITERS CAUSES AN MCR ACCESS VIOLATION V3.0 May 8: 4.5.2 4.5.3 4.5.4 PROBLEMS WITH .DATA DIRECTIVE FIRST CHARACTER MISSING FROM COMMAN, PO .CLOSE USES CHANNEL NUMBER FROM .OPENA V3.1 V3.0 V3.0 Jul 83 Sep 8: Sep 8: 4.6.1 MESSAGE RETURNS IMPROPER STATUS V3.0 Jan 8 4.7.1 OPCOM LEAVES LOGFILE OPEN V3.0 Jan 4.7.2 EXTRA CHARACTER APPENDED TO OPERATOR REPLIES V3.0 May 8: 4.7.3 OPERATOR LOGFILE PROBLEMS V3.1 Sep 82 4.9.1 SUBMIT /FORMS=0 V3.0 Nov 82 4.9.2 SMINVOPT MESSAGE V3.0 Mar 83 4.9.3 START/QUEUE/TOP DOES NOT REINITIALIZE 4.9.4 PAGE NUMBER PRINT/FLAG_PAGE NOT DOCUMENTED CORRECTLY V3.3 V3.6 Jan 8l Nov 84 4.9.5 FIRST LINE OF FORTRAN FILE IMPROPERLY FORMATTED V3.5 Nov 84 4.10.1 COMMENTS IN CLD FILES V3.1 Jul 8: 145 83 Component/ Sequence >roduct Number Operating System Title of Article Mon/Yr DEBUGGER DEBUG LINE NUMBER MISMATCH IN FORTRAN DBG$INPUT AND DBG$OUTPUT INACCESSIBLE DEBUG INCORRECTLY SIGNALS BADSCOPE V3.0 V3.0 CTRL/Y, DEBUG DOES NOT RETURN TO PROMPT V3.0 V3.0 PROBLEM WITH SET TYPE QUADWORD V3.0 EXAMINE/ASCIT NOT CORRECT FOR FORTRAN V3.2 DEBUG DOES NOT PRINT BASIC STATEMENT NUMBERS > 99 V3.2 ERRORS REFERENCING PL/I RECORDS V3.2 IN PL/I, PASCAL AND COBOL Mar V3.0 INCORRECT ADDRESSES IN DST FOR SHAREABLE IMAGE SET BREAK ISSUES "STATEMENT NOT FOUND" CALL COMMAND FAILS Mar V3.0 V3.2 SHOW CALLS COMMAND FOREIGN DATA IN SET LANGUAGE CAUSES ERROR ERRORS WITH WATCHPOINTS IN COBOL DEPOSIT INTO HIGH LIMIT V3.1 VARYING STRINGS IN PASCAL V3.1 V3.2 V3.2 V3.1 DEBUG EVALUATES COMPLEX VARIABLES INCORRECTLY v3.2 DEBUG MISHANDLES TYPOGRAPHICAL ERROR V3.2 Nov ERROR V3.2 Nov Nov Jan IN EXAMINE COMMAND EXAMINE ERROR WHILE DEBUGGING PASCAL DEPOSIT FAILS TO STORE LARGE INTEGERS V3.2 5.1.24 5.1.25 EVALUATE GIVES V3.3 Jan 5.1.26 EVALUATE REAL*8 PROBLEM IN FORTRAN V3.3 Jan V3.2 Jan V3.3 Jan 5.1.23 5.1.27 INCORRECT ANSWER FOR G-FLOAT CANNOT SINGLE STEP PAST COBOL SORT STATEMENT DEBUG GIVES ERROR WHEN DEPOSIT IN PL/I V3.3 DEBUG GIVES INCORRECT ANSWER TO DYNAMIC V3.2 Jan Mar NO MESSAGE WAS GIVEN WHEN OPEN FAILED V3.4 v3.h LOGICAL PREDECESSOR OF FORTRAN CHARACTER ARRAY V3.4 May LINE-STEPPING PROBLEMS WITH FORTRAN V3.4 Jul TRACEBACK ERROR V3.4 Jul V3.5 Sep ARRAY EXAMINE PASCAL ARRAYS VALUE INCORRECT TRACEBACK DEBUGGING PASCAL EXAMINE RESULTS IN ERROR FOR PASCAL PROBLEM WITH EXAMINE @PC IN MACRO V3.5 PROBLEM LOGGING OUTPUT V3.2 Mar Sep Sep INCORRECT STATUS FROM TRACEBACK V3.0 May INCORRECT FORTRAN SOURCE LINE NUMBER SIGNALLED TRACEBACK GIVES PSECT INSTEAD OF ROUTINE V3.2 Nov V3.2 Jan ERROR MESSAGE V3.0 Mar EDTCAI S0s IN MODULE 4 TERMINAL REMAINS IN ALTERNATE KEYPAD V3.0 ERROR V3.0 IN DISPLAY FOR VT52 TERMINAL May May INSTRUCTION IS INCORRECTLY STATED V3.0 DOCUMENTATION v3.o May WRONG FILE SPEC PRINTED V3.0 Jul ODS-1 WILD CARD GROUP AND MEMBER NOT SUPPORTED ACCESS DATE EXPLICITLY SET V3.0 Mar V3.0 Mar DIRECTORY OF AN ODS-1 DISK HANGS PROCESS V3.0 May ODS-1 AND BYTE COUNT QUOTA V3.0 V3.2 Nov FILE SYSTEMS AND RMS FILES-11 ACP RENAME AND SET FILE DO NOT UPDATE REVISION DATE CIF FOR DANGLING DIRECTORY ENTRIES EXBYTLM DUE TO INDEX FILE WINDOW TURN V3.3 V3.4 Jul Sep Nov SET FILE/TRUNCATE GIVES FILE HEADER CHECKSUM ERROR V3.5 Jan HDRNOTMAP BUGCHECK V3.4 Mar INDEX FILE ALLOCATION FAILURE V3.5 Jul o EDITORS Component/ Product, Sequence Number. Title of Article Operating System Mon/Y1 INIT 7.2.1 /VERIFY HANDLED INCORRECTLY FOR FLOPPIES V3.0 Mar 8 MAGTAPE ACP 7.3.1 7.3.2 VOLUME PROTECTION AFFECTS MOUNT MULTIVOLUME FILES AND /OVERRIDE=SETID V3.0 May 7.3.3 7.3.4 TAPE DRIVE NOT DEALLOCATED ON LOGOUT #RMS-F-ENV ERROR CAN OCCUR ACCESSING V3.0 MAGTAPE FILES MOUNT V3.3 Mar 8! T.4.2 ACP WORKING SET TOO SMALL V3.0 Mar OPERATOR ASSIST MAY FAIL ON VOLUME SETS V3.0 T.4.4 Mar FILE STRUCTURE ERROR CONFUSES MOUNT V3.0 May T.4.5 NULL PARAMETER T.4.6 MOUNT DOES NOT PROPAGATE SEVERITY LEVEL V3.0 May T.4.7 SHOW DOES NOT ALWAYS DISPLAY CORRECT V3.2 Jan 8! T.4.8 MOUNT/FOREIGN CLEARS VOLUME VALID V3.2 Jan 8! T.5.1 CONVERT CORRUPTS ISAM FILE v3.0 Nov 8i 7.5.2 EDT FAILS WITH OVERDRAFT DISK QUOTA V3.0 : 7.5.3 WILD CARD ROOTED DIRECTORY ERROR V3.0 T.5.4 PADDING BLOCKS ON FOREIGN TAPE V3.0 7.5.5 INCORRECT $XABKEY STORE MACRO V3.0 7.5.6 PROBLEMS WITH PROLOGUE 3 COMPRESSED KEYS v3.o Te5.7 VAX-11 V3.0 7.5.8 CORRUPT FILE CONFUSES ANALYZE/RMS 7.5.10 SET RMS/BLOCK=1 MAY CAUSE CORRUPTION T.5.11 $XXX_STORE MACRO ERRORS USING AP, FP, T.5.12 RMS BUGCHECKS ON $CLOSE ON FOREIGN DEVICE V3.0 7.5.13 RMS CREATES FILE WITH INVALID KEY POSITION V3.0 T.5.14 WRITE_CHECK INCONSISTENCY V3.0 7.5.15 NIL SHARING AND MULTISTREAMING BUGCHECKS V3.0 7.5.16 7.5.17 RMS-F-BUG AND ANALYZE ERRORS LRL NOT SET IN FILE HEADER ON BATCH V3.0 V3.1 7.5.18 F$FILE_ATTRIBUTES FAILED V3.1 7.5.19 SHARED FILE DATABASE GETS FULL ON DELPRC V3.1 7.5.20 PARSE IN EIGHTH SUBDIRECTORY DELETES PROCESS T7.5.22 POSITION TO EOF INCORRECT FOR RELATIVE FILES 7.5.9 7.5.21 VALUE ABORTS MOUNT RMS SYSGEN PARAMETERS CAN HANG THE SYSTEM WILDCARD $PARSE CALL CAN CAUSE BUGCHECK v3.o Jul V3.0 V3.0 V3.0 SP V3.0 V3.1 DISK QUOTA ERROR DELETES PROCESS V3.0 RMS LOOPS WITH STREAM FORMAT COMMAND FILE v3.2 7.5.24 7.5.25 INCORRECT SIZE FOR BLOCK I/0 AT EOF HALT IN KERNEL MODE DUE TO AN INCORRECT V3.2 7.5.26 RMS CAN RETURN STALE DATA ON UDA50 V3.3 Mar 8L 7.5.27 $RENAME FAILS AFTER MANY FILES V3.4 Mar 84 7.5.28 $CREATE FAILS IF ENQLM IS EXCEEDED V3.4 May 8 7.5.29 SS$_EXDISKQUOTA NOT RETURNED TO USER V3.4 Jul 7.5.30 T7.5.31 WRITING UNBLOCKED RECORDS TO TAPE FILE PROTECTION CORRUPTED OVER NETWORK V3.4 Jul 8t 7.5.32 T7.5.33 RMS BUGCHECKS IF RECORD LOCK FAILS RECORD AND BUCKET SIZE TOO BIG V3.5 7.5.34 CORRUPTION AFTER ROOT BUCKET SPLIT V3.6 Nov 8t 7.5.35 RMSBUG WITH EXEC MODE FILE ACCESS V3.6 Jan 8% 7.5.23 RMS PATCH CONVERT Sep T.4.3 DENSITY RMS Jul V3.0 V3.2 V3.3 V3.5 V3.5 Jan 8t 84 Sep 84 Sep 8L Nov 8Y 7.5.36 REQUEST FOR LARGE DAP BUFFERS V3.6 Jan 8¢ 7.5.37 7.5.38 PROBLEMS WITH RMS PROLOG 3 ISAM FILES VERSION -0 NOT HANDLED CORRECTLY V3.7 V3.7 Jan 8% May 8¢ 7.5.39 7.5.40 GENERIC KEY MATCH PROBLEM LOSS OF FILE LIMIT QUOTA USING F$SEARCH V3.7 V3.7 May 8% May 8% 7.5.41 SEARCH LOSES PLACE ON RMS$_PRN ERRORS V3.6 Jul 85 7.5.42 INVALID %RMS-W-RTB ERROR ON STREAM FILE V3.6 Jul 85 7.6.1 CONVERT CALLS ARE NOT RE-ENTRANT V3.0 Mar 83 7.6.2 7.6.3 7.6.4 7.6.5 CONVERT FAILS TO CHECK OUT OF ORDER KEYS CONCURRENT CONVERTS IN SAME DIRECTORY MAY FAIL CONVERT FAILS TO CHECK OUT OF ORDER KEYS CONVERT TREATS SECONDARY NULLS AS DUPLICATES V3.0 May 83 V3.0 V3.0 V3.1 May 83 May 83 May 83 ‘omponent/ ‘roduct Sequence Title of Article 7.6.6 ACCESS VIOLATIONS IN CALLABLE CONVERT ROUTINES T.6.7 CONVERT FAILS WITH INTERNAL LOGIC ERROR V3.0 V3.0 7.6.8 CONVERT CREATES BAD PACKED DECIMAL KEYS V3.1 7.6.9 CONVERT CREATES CORRUPT ISAM FILE V3.1 7.6.10 7.6.11 7.6.12 CONVERT FAILS ON REPEATED CALLS V3.2 7.6.13 T.6.14 7.6.15 7.6.16 7.6.17 7.6.18 DL Operating Number System CONVERT ERROR LEAVES INPUT FILE OPEN V3.4 CALLABLE CONVERT IS NOT REENTRANT CONVERT DOES NOT IGNORE NULL KEYS INCORRECT CHECKING FOR NULL SECONDARY KEY VALUES V3.3 V3.3 V3.4 CONVERT ERRORS WITH TRUNCATE_ON_CLOSE V3.4 CONVERT ERROR MESSAGES ARE CONFUSING V3.5 PROBLEM WITH CALLABLE CONVERT ROUTINES V3.4 V3.4 CANNOT CONVERT NETWORK INDEXED FILES CORRECTLY 7.6.19 7.6.20 CONVERT WITH ALL NULL KEYS CONVERT/RECLAIM YIELDS ACCESS VIOLATIONS V3.6 T.7.1 FDL PROBLEMS WITH SPACE/TAB NULL_VALUE V3.0 7.7.2 7.7.3 OVERLY LARGE ISAM FILE ALLOCATIONS V3.0 T.T.4 INTERMITTENT FAILURE OF FDL$CREATE INCONSISTENCIES IN OPTIMIZE SCRIPT V3.2 AREA POSITION FILE_NAME BROKEN V3.3 V3.2 T.7.7 PRINT_ON_CLOSE DOES NOT PROMPT DUPLICATES_PER_SIDR HAS NO EFFECT 7.7.8 INTEGER OVERFLOW WITH NEGATIVE 7.7.9 7.7.10 FDL PRODUCED INVALID RECORD SIZE FDL CREATES INVALID PROLOG 2 FILES 7.7.5 T.7.6 V3.5 v3.o V3.2 V3.2 COMPRESSIONS V3.2 V3.5 [/0 DRIVERS Jan 83 /HARDCOPY/NOWRAP DOES NOT TRUNCATE V3.0 AUTOBAUD AND DFO03s AUTOBAUD AND PARITY V3.0 Jan 83 V3.0 Jan DELETION OF HUNG UP PROCESS V3.0 Jan 83 FIRST CHARACTER IN TYPEAHEAD LOST XOFF, THEN PHONE HANG UP, LEAVES ACTIVE PROCESS V3.0 Mar 83 V3.0 Mar 83 May 83 SET TERM/PERM/NOALT DOES NOT WORK V3.0 CURSOR POSITION CLEARED AT BEGINNING SEQUENCE SYS$CANCEL PROBLEM WITH THE TERMINAL DRIVER V3.0 Jul 83 V3.5 Mar PROCESS HANGS IN LEF WAIT STATE VERTICAL TABS EXPANDED TO LINE FEEDS 85 V3.5 Mar V3.6 Mar 85 DEFECTIVE MAGTAPE CAUSES ENDLESS LOOP V3.0 May 83 TMDRIVER RETURNS WRONG STATUS V3.5 84 LPDRIVER INCORRECT DEFAULT OF NGCR FOR PRINTERS V3.0 Mar XMDRIVER XMDRIVER CANCEL ROUTINE STOPS DMC DEVICE v3.o Jan 83 TMDRIVER 83 TSDRIVER - SS$_OPINCOMPL ON REVERSE TO BOT V3.0 May 83 BACKUP FAILS WITH /SS$_ENDOFFILE V3.6 Sep 84 COPY CAN FAIL FOR ODD-LENGTH RECORDS ON TU80 V3.7 May 85 TU78 TAPES WRITTEN AT THE WRONG DENSITY V3.0 Mar V3.0 May 8.12.3 REBOOT REQUIRED TO CLEAR FATAL CONTROLLER ERROR TIMEOUT ON REWIND OF A 3600 FOOT TAPE MBDRIVER 8.13.1 MBDRIVER DOES NOT TRANSMIT ZERO-LENGTH RECORDS V3.0 Nov 82 RTTDRIVER 8.14.1 SYSTEM CRASH IN ABORT I/0 v3.o May 83 TSDRIVER TFDRIVER YCDRIVER 8.12.1 8.12.2 V3.3 Mar 83 84 BROADCAST TO DMF32 TERMINAL MAY HANG PROCESS V3.0 May 83 DMF32 PARITY SPECIFICATION IS REVERSED V3.1 May 83 DEVICE TIMEOUT ERRORS ON DMF-32 32ND CHARACTER IS PRINTED IN FIRST COLUMN V3.2 Nov 83 V3.2 Nov 83 148 P TTDRIVER Component/ Product Sequence Operating Number Title of Article System Mon/Y MTDRIVER 8.16.1 EOT TERMINATES SKIP RECORD BUT NOT SKIP FILE V3.0 Sep & XGDRIVER 8.17.1 DMF32 SYNCHRONOUS PORTS DROPS DTR TOO EARLY V3.2 Sep & XWDRIVER 8.18.1 PROBLEM IN XWDRIVER V3.3 Jan 8.18.2 POINT-TO-POINT BSC MODIFIER TO $QIO V3.7 Jul 8 8.19.1 PROBLEM WITH LARGE TRANSFERS V3.4 Jul 8.19.2 I0$M_RESET MODIFIER INHIBITS ERROR LOGGING v3.o May 8 Sep 8 XADRIVER DUDRIVER XEDRIVER PADRIVER 8 8 8.20.1 MISSING UCB SETUP BY DUDRIVER V3.6 8.20.3 8.20.4 8.20.5 ERROR LOGGING CRASH DSA DISKS DO NOT RECOVER FROM POWER FAIL V3.5 Nov 8 V3.7 Mar PROCESSES HANG WAITING FOR HSC50 8 V3.5 8.20.6 Mar LOGICAL DISK READ LIMITED TO 127 BLOCKS 8 V3.6 May 8 8.21.1 XEDRIVER SENDS BYTE COUNT WITH DATA V3.6 Nov 8 8.21.2 XEDRIVER CRASHES SYSTEM ON POWERFAIL V3.7 May 8 8.22.1 "RECEIVED CONNECT WITHOUT PATH-BLOCK" ERRORS LARGE LRPSIZE CAUSES CI DRIVER CRASH V3.4 V3.5 Mar 8 Mar 8 BOOT PROBLEM AFTER DATE AND TIME ARE LOST V3.5 Mar 8 TUBO AND EOF PROBLEM V3.5 Mar 8 8.22.2 8.22.3 TSDRIVER 8.23.1 DOCUMENTATION 9.0.1 RTL REFERENCE MANUAL EXAMPLE HAS ERROR V3.0 Nov '8 9.0.1 9.0.2 9.0.3 9.0.4 STRING ROUTINE DOCUMENTATION ERRORS DOCUMENTATION ERROR FOR LIB$SET_SYMBOL V3.1 V3.1 Mar 8 Mar 8 ERROR IN CONDITION HANDLING EXAMPLE V3.1 Mar 8 UCB$W_BCNT CAN BE WRITTEN AT FORK IPL V3.4 Mar 8 GENERAL UTILITY PROCEDURES 9.1.1 LIB$SCANC DOES NOT SAVE R4 V3.1 Mar 8 9.1.2 9.1.3 9.1.4 PROBLEMS USING LIB$SPAWN FROM BATCH JOBS V3.1 V3.1 Mar 8 Mar 8 9.1.5 OTS$CVT_TX L AND INVALID CHARACTERS LIB$SPAWN AST ROUTINE V3.0 V3.1 Mar 8 Mar 8 V3.1 9.1.7 QUESTION ABOUT FLOATING POINT ACCURACY Sep 8 V3.0 Nov 8 LIB$PUT_BUFFER RETURNS SS$_EXQUOTA V3.1 Mar 8 CTRL/O HANDLED IMPROPERLY AFTER RCTRLO V3.1 V3.1 Mar 8 Mar 8 DEFAULT UNFORMATTED RECORD SIZE TOO BIG V3.1 Mar 8 LIST-DIRECTED WIDTH CHANGES WITH RECL= V3.1 Mar 8 9.1.6 LIB$SPAWN COMMAND LENGTH RESTRICTED 126 CHARACTER LIB$DO_COMMAND TERMINAL-INDEPENDENT SCREEN PROCEDURES 9.3.1 BASIC LANGUAGE SUI PPORT 9.21.1 9.21.2 PROBLEMS OPENING INDEXED FILES FORTRAN LANGUAGE SUPPORT 9.28.1 9.28.2 PASCAL V2 LANGUAGE SUPPORT RECORD_LENGTH > 65535 ACCEPTED V3.1 Mar 8 V3.1 V3.1 Mar 8 Mar 8 ERROR OPENING INPUT FROM COMMAND FILE V3.1 V3.1 V3.1 Mar 8 Mar 8 FAILURE OF FIRST OPEN CAUSES BUGCHECK V3.2 May 8 BACKUP COPIES OF SYSUAF.DAT V3.4 V3.5 V3.4 May 8 Jul 8 WRONG RECORD SIZE OF NON-DISK FILE USED FIND OF VARYING DOES NOT STORE LENGTH UPDATE USES WRONG SIZE CONTINUE FROM I/0 HANDLER GIVES ERROR SPURIOUS DEUNA ERRORS WHEN RUNNING UETP WRONG TEST CHOSEN FOR DUP-11 149 Mar 8 Jan 8 Sequence Hon/tr. Title of Article System ENDLESS RETRY LOOP V3.4 v3. Sep 84 11.22.1 11.22.2 DIFFERENCES UTILITY LOOPS WHEN /MERGED=0 DIFFERENCES UTILITY FLAGS MATCHING RECORDS b V3. V3.6 Jan 11.25.1 SEARCH HELP LIBRARIES V3.0 V3.0 Mar ERROR IN HELP BACKUP V3.0 V3.0 Mar ERRORS WHEN INVOKED BY COMMAND PROCEDURE May 11.25.7 HELP LOOPS ON WRITE ERROR V3.0 V3.0 V3.3 AUTHORIZE ACCESS VIOLATION V3.0 Jan 11.27.1 V3.0 Jan V3.0 Mar V3.0 V3.0 V3.0 V3.2 May May Number 11.20.24 11.20.25 11.25.2 11.25.3 11.25.4 11.25.5 11.25.6 11.27.2 11.27.3 11.27.4 RENAME DOES NOT UPDATE REVISION DATE HELP FOR SET TERM/DEVICE IS INCOMPLETE EQUIVALENT LOGICAL NAMES ERROR IN HELP FOR F$GETJPI AUTHORIZE CONSUMES EXCESSIVE VIRTUAL MEMORY ACCESS VIOLATION USING DEFAULT COMMAND UAF COPY SHOULD RESET MAIL Sep 84 Jan 85 Mar May Mar BYTLM DISPLAY FIELD TOO SMALL AUTHORIZE LIST COMMAND USAGE 11.27.7 11.27.8 HELP FOR MODIFY/ACCOUNT MISSING V3.3 Jan INVALID MINUTES TO SHUTDOWN May 11.28.1 V3.0 PHONE AND BROADCAST MAILBOXES LOGICAL NAMES FOR REMOTE NODES FAILS V3.0 Jan 11.30.1 11.30.2 V3.1 Sep SUBMIT/WSEXTENT=NONE V3.0 Mar 11.31.1 V3.0 Mar CLIt_ABSENT NOT RETURNED IN CERTAIN CASE V3.0 Mar V3.0 Jul v3.0 Jul V3.0 v3.u Jul V3.3 Jan 11.31.2 11.32.1 11.33.1 AUTHORIZE IGNORES LONG COMMAND STRINGS ACCESS VIOLATION SUBMIT/CHARACTERISTICS=255 MONITOR DOES NOT ACCEPT F$TIME 11.34.3 VMSUPDATE - CONSOLE VOLUME STATUS UPDATING ALTERNATE SYSTEM DISKS VMSKITBLD LACKS TUDRIVER.EXE 11.36.1 VMSINSTAL AND LOGICAL NAMES 11.34.1 11.34.2 11.36.2 11.36.3 11.36.4 11.36.5 11.36.6 11.36.7 11.36.8 11.37.1 11.37.2 11.38.1 11.38.2 11.38.3 . INCORRECT JOURNAL FILE PROTECTION V3.2 V3.3 UPDATE FAILS IF SYSUAF IS DEFINED VMSINSTAL DOES NOT FIND ALL USERS ERROR IF MULTIPLE PRODUCTS INSTALLED INSTALL OF BLISS-16 FAILS IF LOGGING VMSINSTAL IGNORES DEVICE ALLOCATED ERROR V3.4 SYSBOOT NOT CONTIGUOUS BACKLINK ERROR ON DISK WITH ANALYZE/DISK_ STRUCTURE INFINITE LOOP READING BACKUP JOURNAL FILE AUTOGEN IGNORES THE SWPFILCNT SYSGEN PARAMETER INCORRECT GROWLIM VALUE V3.5 iy 8. il 87 Nov 11.27.6 11.27.5 May Sep v 83 v 85 83 + 83 May Jan Mar May Sep b V3. Nov V3.4 Nov o V3.5 Jul 85 V3.3 May V3.6 Mar 85 V3.4 May 84 V3.1 £ 84 Jan 85 SHUTDOWN.COM AND VERSION NUMBER V3.4 Jan 85 May 11.39.2 DISK LEFT ALLOCATED TO NONEXISTENT PROCESS V3.4 V3.5 Sep 84 11.42.1 CDU DOES NOT ALLOW DEFAULTS ON LISTS V3.3 Jul 85 DOCUMENT ORGANIZATION CREATES PROBLEMS V3.0 Jan 83 11.39.1 ATION Operating ASYNCHRONOUS REWIND $QIO ISSUED TO A DRIVE NO DEFAULT FOR DIRECTORY/OUTPUT WRITE-BEHIND, READ-AHEAD DOCUMENTATION INCOMPLETE ERROR IN COMMAND LANGUAGE USER'S GUIDE CODE DOCUMENTATION ERROR FOR $ERASE STATUS AR BACKUP/NEW VERSION DOCUMENTATION UNCLE 152 84 V3.0 Jan 83 V3.0 V3.0 Mar V3.0 V3.0 83 83 May 83 May 83 Mar 93 83 Component/ Product Sequence Number Title of Article 12.1.7 INADEQUATE DOCUMENTATION ON F$PARSE Operating System Mon/Yr V3.4 Jul 84 V3.0 Mar 83 VAX-11 SORT/MERGE 13.1.1 CALLABLE TAG SORTS FAIL VAX-11 DECOR USER-LEVEL BUGS AND PROBLEMS 1h.1.1 14.1.2 RGB TO HLS CONVERSION NEW FRAME WITHIN A BATCH OF UPDATES V3.0 V3.0 Nov 83 Nov 83 14.1.3 DECOR CALLED FROM PASCAL PROGRAMS V3.0 Nov 83 14,14 MULTIPLE BATCHES AND DECOR$NEW_FRAME V3.0 Jan 84 14.1.5 VT125 HANDLER SUPPORT FOR 14.1.6 DECOR$DEF_COLOR_INDEX VT125 HANDLER AND STROKE_PRECISION TEXT V3.0 V3.0 Jan 84 Jan 84 w.2.1 PROBLEM STATEMENT V3.0 Nov 83 14.3.1 ARGUMENTS FOR HANDLER GET_ AND SET_ LOOKUP 14.3.2 ARGUMENTS TO HANDLER INIT ROUTINE ROUTINES V3.0 V3.0 Nov 83 14.3.3 DECOR$K_DEV_FULL_SUPPORT HANDLERS V3.0 Nov 83 14.3.5 DOCUMENTATION FOR DECOR$A_HIAT_ V3.0 Jan 84 14.3.6 14.3.7 WRITEABLE PSECTS IN HANDLERS HANDLER OUTPUT ESCAPE FUNCTIONS ARE V3.0 Jan 84 V3.0 Jan 84 V3.4 May 84 DECOR INSTALLATION DOCUMENTATION/ HANDLER WRITING 14.3.4 DEVICE TABLE MODULATION_TYPE ENTRY END_SEG CALLED INCORRECTLY V3.0 Nov 83 Jan 84 BASIC-PLUS-2 19.1.1 BASIC-PLUS-2 VERSION 2.2 TO SHIP IN MARCH DECnet-VAX NCP 20.2.1 LINE LOOPBACK PROBLEMS V3.0 Jul 83 20.2.2 ERROR CIRCUIT NOT FORMATTED V3.2 Nov 83 20.2.3 20.2.4 20.2.5 20.2.6 LOGIC ERROR IN NCP PROTOCOL KEYWORD SHOULD BE ETHERNET PROBLEM WITH NCP EXECUTOR MAXIMUM BUFFER REMOTE PROCESS NOT DELETED V3.4 V3.5 V3.6 V3.3 Jul Nov Mar Jul 20.2.7 20.2.8 PROBLEMS WITH DLM OVER PERMANENT VIRTUAL CIRCUITS REMOTE LOGIN FACILITY PROBLEM V3.7 V3.6 Jul 85 Jul 85 20.3.1 PERMANENT DATABASE NOT SHARED v3.0 Mar 83 20.3.2 SYSTEM HANGS DURING DOWN LINE LOADS V3.2 Nov 83 20.3.3 UNDOCUMENTED OPERATION FAILURE DETAIL V3.5 Mar 85 20.4.1 TOO MANY SINK NODES GIVES OVERFLOW V3.0 May 83 20.4.2 DECnet EVENT 4.0 INCORRECTLY FORMATTED V3.6 Jan 85 20.5.1 DECNET DOES NOT SUPPORT RESOURCE WAIT MODE V3.0 May 83 20.5.2 DECNET CRASHES WITH LARGE BUFFERS V3.0 Jul 83 20.5.3 20.5.4 DECNET CONNECT REJECT FAILURE INCORRECT MESSAGES SENT TO PHASE III END NODES V3.4 V3.5 Mar 84 Jul 84 CNDRIVER 20.6.1 DECNET CI CIRCUIT INITIALIZATION FAILURE V3.1 Jul 83 REMACP 20.7.1 ALLOCATED REMOTE TERMINALS v3.o Jul 83 NML EVL NETDRIVER 153 84 84 85 85 Component/ Sequence NETACP 20.8.1 NODE ADDRESS OUT OF RANGE ERROR V3.0 Sep 83 20.8.2 BAD MEMORY BUGCHECK ON NETWORK SHUTDOWN V3.2 Sep 83 20.8.3 20.8.4 20.8.5 20.8.6 SYSTEM-F-NOLINKS MESSAGE IS MISLEADING NCP ZERO KNOWN NODE COUNTERS FAIL NETACP CRASHES WITH INVALID KERNEL STACK NETACP BUGCHECKS ON SHUTDOWN V3.2 V3.4 V3.4 V3.4 Nov May May May 20.9.1 COMMAND FILES CONTAINING SET HOST FAIL V3.2 Sep 83 20.9.2 RTPAD ACCESS VIOLATION V3.1 Sep 83 LOGINOUT 20.10.1 DECNET DOES NOT ACCEPT NULL PASSWORDS V3.2 Nov 83 RMS 20.11.1 HANG DURING NETWORK CREATE AND NO DISKQUOTA V3.2 Nov 83 20.11.2 DECnet RECORD SIZE LIMIT OF 512 BYTES V3.2 Nov 83 20.11.3 20.11.4 STREAM FILES NOT SUPPORTED BY DECnet-VAX RSTS FILESPEC INCOMPATIBILITY V3.5 V3.4 Nov 84 Jul 85 20.11.5 TOPS-10 FILESPEC INCOMPATIBILITY V3.5 May 85 XMDRIVER 20.12.1 DMR-11 DOES NOT HANG UP PHONE LINE V3.2 Nov 83 MOM 20.13.1 DOWN-LINE LOAD CORRUPTED HOST ID V3.4 May 84 20.13.2 MISSING DATE/TIME ON DOWN-LINE LOAD V3.5 Mar 85 INCORRECT ERROR MESSAGE FROM SET HOST V3.4 Jul 84 RTPAD AND CTRL/O RTPAD SINGLE STREAMS TERMINAL $QIOS V3.3 V3.5 Jul 85 Jul 85 V3.2 Mar 83 Product SET HOST Number. RTPAD 20.14.3 Operating Title of Article System Mon/Yr 83 84 84 84 VAX-11 BASIC 21.1.1 ANNOUNCING VERSION 2.0 OF VAX-11 21.1.2 DEBUGGGING VAX-11 21.1.3 21.1.4 BASIC MEMORY REQUIREMENTS VAX BASIC V2.2 NOW AVAILABLE VAX-11 DOCUMENTATION 26.12.1 BASIC BASIC RECORDS V3.2 Jul 83 V3.2 V3.2 Jul 83 Jan 84 V3.0 Nov 82 V3.0 Mar 83 DSM DOCUMENT ORGANIZATION CREATES PROBLEMS VAX-11 FORTRAN 28.1.1 INSTALLATION OF V3.1 UPDATE VAX-11 PASCAL 30.1.1 30.1.2 INCORRECT CODE FOR [EXTERNAL] VARIABLES BAD CODE FOR CONSTANTS IN EXPRESSIONS V3.1 V3.1 Mar 83 Mar 83 30.1.4 TUNING THE VAX-11 PASCAL V2 COMPILER V3.3 Jan 84 30.1.3 USE OF THE /CHECK QUALIFIER V3.1 May 83 ADE GENERAL INFORMATION & 35.1.1 35.1.2 35.1.3 35.1.4 ANNOUNCING DIGITAL'S ADE V2.0 FOR NON-PROGRAMMERS MAINTENANCE UPDATE OF ADE V2.0 MAINTENANCE UPDATE OF ADE V2.1 MAINTENANCE UPDATE OF ADE VERSION 2.2 V3.0 V3.0 V3.1 V3.5 Jan Mar Nov Jan 83 §3 83 85 35.1.5 ANNOUNCING ADE V2.3 FOR MICROVMS vi.0 Nov 84 PDP-11 DATATRIEVE/VAX V2.5 36.1.1 36.1.2 36.1.3 ELEMENTARY, LIST FIELDS NOT PROPERLY HANDLED MODIFY OF DOMAIN WITH HIERARCHY MAY GIVE ERROR PROBLEM REFERENCING KEY FIELDS WITHIN A VIEW V3.0 V3.0 V3.0 Jan 83 May 83 May 83 36.1.4 ENTERING CTRL/C IN GUIDE MODE V3.0 May 83 Component/ Sequence Product Number Operating Title of Article System Mon/¥r VAX/VMS V3.2 VAX-11 DATATRIEVE ANNOUNCING VERISON 2.0 OF ANNOUNCING VERISON 3.0 OF VAX DATATRIEVE VAX-11 DATATRIEVE MULTIPLE FORMS FUNCTIONALITY NO LONGER SUPPORTED V3.2 Sep 83 V3.6 Nov 84 V3.6 Nov 84 V3.0 Jul 83 V3.2 Jan 84 V3.0 Jan 83 V3.0 Jul 83 VAX/VMS V3.x DOCUMENTATION 39.1.1 LIMITATIONS TO SHARING OF CDD RECORD DEFINITIONS VAX-11 42.1.1 CREATING SUBPROCESSES C IN VAX C RTEM-11 V1.0 GENERAL INFORMATION 4u.1 INTRODUCING RTEM-11 V1.0 VAX-11 DECale, V1.0 45.1.1 RESTRICTIONS/PROBLEMS VERSION IN VAX-11 DECALC 1.00 VAX-11 TDMS, V1.0 VAX-11 TDMS V1.0 V3.0 Jul 83 Mar 8y LOADING REQUIRED TERMINAL SERVICE DECTYPE/VMS V3.0 PRINTING 48.1.1 V3.0 Jan 84 V3.0 Jan 83 MESSAGE V3.0 Jan V3.0 Mar 83 Mar 83 PROBLEM PRINTING WITH DECTYPE Rttt CONFUSION IN THE USE OF CONCEALED DEVICES IRt oR-RR-R-R-R-2-] ARTICLES OF GENERAL INTEREST DEFENDING AGAINST PASSWORD GRABBERS Mar ERROR IN. USER WRITTEN SYSTEM SERVICE TEMPLATE HELPFUL HINTS IN DIAGNOSING USER PROGRAMMING May 83 UTILITY DN11 AND DR11-C UETP DEVICE TEST PROGRAMS LINKER PROBLEM WITH SHAREABLE IMAGE EXPRESSIONS DEVICE INTERRUPT PRIORITY LEVELS Mar 83 ERRORS RELATING TO DYNAMIC STRINGS AND MEMORY May ALLOCATION 83 50.1.9 DOCUMENTATION REQUIREMENTS FOR SPR PROBLEM 50.1.10 50.1.11 50.1.12 CORRECTION TO VERSION 3.5 VAX/VMS RELEASE NOTES 50.1.13 50.1.14 LOSS OF CARRIER ON REMOTE PRINTERS 50.1.15 50.1.16 SYSTEMS MAY CRASH DURING V4.0 INSTALLATION DELETION OF GLOBAL SECTIONS OPCOM T7.1.1 OPC$B_MS_TARGET FIELD SIZE INCORRECT V2,5 Nov 84 DISK QUOTA 77.1.2 QUOTA.SYS REVISION DATE NOT UPDATED v3.o Nov 84 May 83 REPORTS PAGE SIZE, PRINT DEVICES, Jan 84 8y AND AUTOMATIC FORM FEEDS ADDITIONAL INFORMATION ON PAGE SIZE, AND AUTOMATIC FORM FEEDS PRINT DEVICES ERRANT FORMATTING BEHAVIOR IN VAX/VMS PRINT SYMBIONT Sep 84 Sep 84 Jan 85 Jan 85 May 85 Component/ Sequence Product Number Title of Article Operating System Mon/Yr VERIFY T7.1.3 BACKLINK ALGORITHM v3.o Nov 84 TTDRIVER T7.1.4 QUESTIONS ABOUT BRDCSTMBX v3.o Nov 84 COPY 77.1.5 COPY CHANGES CBT ATTRIBUTES V3.1 Nov 84 77.1.6 COPY/OVERLAY WITH NULL INPUT DOES NOT WORK V3.0 Nov 84 XMDRIVER T7.1.7 DMR-11 DOES NOT HANG UP PHONE LINE V3.2 Nov 84 RMS T7.1.8 RENAME GIVES CONFUSING ERROR MESSAGE V3.2 Nov 84 ACCOUNTING 78.1.1 CTRL/C DOES NOT RESTORE VT100 V3.0 Nov 84 DIRECTORY 78.1.2 INDICATION OF SPOOLED OUTPUT BY DIRECTORY V3.0 Nov 84 OPCOM 78.1.3 USER NEEDS REPLY/ENABLE/PERMANENT V3.0 Nov 84 PATCH 78.1.4 FWD REFERENCES SYMBOLS SHOULD USE B", W*, OR L" V3.0 Nov 84 RMS 78.1.5 CORRUPT FILE CONFUSES ANALYZE/RMS V3.0 Nov 8y SHOW 78.1.6 SHOW PROCESS/CONTINUOUS UPDATE PROBLEMS V3.0 Nov 84 MTDRIVER 78.1.7 EOT TERMINATE SKIP RECORD V3.0 Nov 84 RMS 78.1.8 WRITE CHECK CONFUSION V3.0 Nov 84 OPCOM 78.1.9 OPERATOR LOG FILE PROBLEMS V3.1 Nov 84 BACKUP 78.1.10 SPURIOUS FIDERROR MESSAGE V3.2 Nov 84 DIRECTORY 78.1.11 RELATIVE VERIOSN NUMBERS ON /EXCLUDE V3.2 Nov 84 MOUNT 78.1.12 MOUNT MAGTAPE FAILS WITH EXCEEDED QUOTA V3.4 Nov 8y ¢ MOUNT 78.1.13 USER WANTS SET LRP=N COMMAND V3.4 Nov 84 AUTHORIZE 78.1.14 PROVIDE DIFFERENT HOURLY ACCESS FOR BATCH V3.5 Nov 84 SYSGEN 79.1.1 RELOAD OF DRIVER WITH INCREASED UNIT va.5 Nov 84 SHOW 79.1.2 ENHANCEMENT SUGGESTION FOR SHOW V3.0 Nov 84 RTL 79.1.3 TPARSE MACROS USE .LONG V3.0 Nov 84 SET 79.1.4 SHOW ENHANCEMENTS v3.o Nov 84 DISK QUOTA 79.1.5 ERROR MESSAGE TOO SEVERE V3.0 Nov SYs 79.1.6 PROBLEM IN FORMAT V3.0 Nov 84 TTDRIVER 79.1.7 SET TERM/PERM/NOALTYPEAHEAD DOES NOT WORK v3.o Nov 84 COPY 79.1.8 /NOTRUNCATE DOES NOT WORK V3.1 Nov 84 MOUNT 79.1.9 ALLOW GREATER OPERATOR COVERAGE V3.1 Nov 79.1.10 SET MESSAGE DEFAULTS V3.1 Nov 84 SET DEVICE AND QUEUE NAMES V3.1 Nov 84 BACKUP 79.1.12 /IGNORE=INTERLOCK VERSUS DEACCESS LOCK V3.1 Nov 84 LIBRARIAN 79.1.13 BINARY KEYS BROKEN V3.2 Nov 84 corPY SET 79.1.14 79.1.15 NON-SPANNED ATTRIBUTE LOST TO TAPE V3.0 Nov 84 V3.2 Nov 84 SET 79.1.11 SET ACCOUNT FAILURE 156 84 84 Component / Product Sequence Number Title of Article System Mon/Yr. BAD 79.1.16 BAD BLOCK FORMAT ON RPO6 V3.3 Nov 84 TSDRIVER 79.1.17 DTO7/TS11 IS NOT AVAILABLE AFTER SWITCH V3.4 Nov 84 Operating CUMULATIVE INDEX (Version 4.n) 159 VAX/VMS SYSTEMS DISPATCH CUMULATIVE INDEX FOR VAX/VMS Vi.n JULY 1985 Following is a listing of all articles for VAX/VMS VA4.n and layered products. The following components 1ist was designed there are several numbers allows for "reserved" so that in 1ist will be reviewed to future issues it could be expanded. that purpose. expanding the primary category to 55.35 1s used for the COPY utility, components for Consequently, Also, within each category the numbering scheme include related subsets. For example, under 55.0, Utilitie 55.60 is used for the DIFFERENCES utility, etc. insure that it accommodates the current Periodically, the software needs. R = indicates a republished article Component/ Product Sequence Number. Operating Title of Article System Mon/Yr VAX/VMS Vi.n SYs ACCOUNTING 5.20.1 F$GETDVI INFORMATION INVALID IF DISK NOT MOUNTED 5.20.2 V4.0 EXCESSIVE MODIFIED PAGE LIST WRITING Jul 85 5.20.3 GETJPI PROC_INDEX VALUE V4.0 V4.0 Jul 85 Jul 85 5.20.4 SHUTDOWN WITH REBOOT_CHECK CAN FAIL 5.20.5 TODR Vi, 0 Jul 85 V4.0 Jul 5.20.6 SCREEN MANAGEMENT SYMBOLS DEFINED INCORRECTLY V4,0 Jul 85 5.20.7 TEMPORARY MAILBOX LOGICAL NAMES V4,0 Jul 85 DEFINITION REMGVED IN VAX/VMS VERSION 4.0 85 10.5.1 PROBLEMS WITH ACCOUNTING SELECTION BY UIC V4.0 Jul 85 10.5.2 USER RECORD DISPLAYS SCROLL OFF SCREEN V4,0 Jul 85 INSTALL 11.19.5 INABILITY TO INSTALL EXECUTABLE IMAGES vi.o Jul 85 SYSGEN 11.35.1 DISCREPANCY IN SCSNODE NAME LENGTH V4.0 Jul 85 SYSINIT 11,40.1 QUOTA CACHING DISABLED ON THE SYSTEM DISK V4.0 Jul 85 UPGRADE 12.10.1 12.10.2 CVTUAF DOES NOT COPY USER DATA AREA VMSINSTAL FAILS DURING VERSION 4.0 UPGRADE ON TU81 vi.0 Jul V4.0 Jul 85 VMSINSTAL 12.15.1 VMIBCKERR.TMP INADVERTENTLY PLACED IN SAVE SET V4.0 Jul 85 JOBCTL 15.15.1 SNDSMB WITH FILESIZ OPTION FAILS V4.0 Jul 85 V4.0 vi. o Jul 85 Jul 85 PRINT 15.25.1 SYMBIONT 15.25.2 SUGGESTION FOR ISSUES BLANK PAGES WITH /SETUP DEFAULT FORM FOR EACH QUEUE 85 PRINT SYMBIONT 15.30.1 HOW TO PRINT HEADERS IN 80-COLUMN FORMAT V4.0 Jul 85 15.30.2 UNEXPECTED SYMBIONT PROCESS TERMINATION Vi1 Jul 85 Iv 23.1.1 WARNING MESSAGE CAUSES IVP TO FAIL V4.0 Jul 85 DECnet 25.5.1 NETWORK JOBS USE DEFAULT DCLTABLES vi.o Jul 85 25.5.2 SPURIOUS NODE UNREACHABLE ERRORS vi. 0 Jul 85 25.5.3 STARTNET.COM V4.0 Jul 85 25.5.4 STARTNET.COM FAILS TO CHECK FOR ALTPRI PRIVILEGE V4.0 Jul 85 XDDRIVER 32.25.1 DEVICE FULL ERROR WHEN INITIALIZING DMP-11 V4,0 Jul 85 YQDRIVER 32.45.1 YQDRIVER CORRUPTS NONPAGED POOL vi.0 Jul 85 INCORRECTLY PARSES NODE ADDRESS 161 Operating Component/ Sequence Product Number Title of Article System TTDRIVER 33.20.1 VT200 NOT DEFINED IN $DCDEF V4.0 33.20.2 DMA NOT SET ON DMF-32 LINES V4.0 34.20.1 SYSTEM-F-EXQUOTA ERROR ON PRINTOUT V4.0 READ FROM SYS$OUTPUT FAILS vi.0 LPDRIVER RMS COPY/OVERLAY FAILS IF DESTINATION WRITE-PROTECTED vi.0 CONFUSION ON $CREATE USING SEARCHLISTS vi.0 ACCESS CONTROL STRING PARSED INCORRECTLY vi.0 $RENAME RETURNS INCORRECT ERROR MESSAGE VAX BASIC PROGRAMS RETURN AN INCORRECT ERL FOR RTL ERRORS 50 AND 52 V4.0 vi.0 Jul 85 Jul 85 Jul 85 ANALYZE 55.5.1 ANALYZE/IMAGE REPORTS INCORRECT LINK DATE AND TIME V4.0 AUTHORIZE 55.10.1 55.10.2 REVOKE/IDENTIFIER DOES NOT REMOVE UICS V4.0 Jul 85 BACKUP 55.20.1 PROBLEM BOOTING STANDALONE BACKUP V4.0 Jul 85 CONVERT 55.30.1 55.30.2 CONVERT/RECLAIM MAY ACCESS VIOLATE V4.0 Jul CONVERT CAN INCORRECTLY REPORT DUP AND SEQ ERRORS vi.o Jul 85 DIRECTORY 55.65.1 55.65.2 DIRECTORY OUTPUT MISSING TOTAL LINE DIRECTORY MAY DISPLAY NONEXISTENT FILES V4.0 V4.0 Jul 85 Jul 85 INITIALIZE 56.5.1 INITIALIZE/INDEX:BLOCK=N NOT RECOGNIZED V4.0 Jul 85 INSTALL 56.10.1 INABILITY TO INSTALL EXECUTABLE IMAGES V4.0 Jul 85 LIBRARIAN 56.15.1 PROBLEM DECOMPRESSING A LIBRARY V4.0 Jul 85 LINKER 56.20.1 LINKER OPEN FILE LIMIT PROBLEM LINKER REJECTS VALID FILE NAMES IN OPTIONS FILES V4,0 Jul 85 56.20.2 V.0 Jul SHOW 56.75.1 RANDOM BROADCAST CLASSES DISABLED vi.0 Jul 85 SET PASSWORD 56.80.1 SET PASSWORD SIGNALS ERRORS TWICE V4.0 Jul 85 STARLET 61.1.1 ERROR IN XAB$ DEFINITIONS vi.0 Jul 85 SYS$TRNLNM EXAMPLE IS INCORRECT V4.0 V4,0 Jul 85 V4.0 Jul 85 V4.0 Jul 85 V4.0 V4.0 Jul 85 V4.0 Jul 85 ANALYZE ANALYZE/IMAGE REPORTS INCORRECT LINK DATE AND TIME V4.0 Jul 85 CONVERT CONVERT CAN INCORRECTLY REPORT DUP AND SEQ ERRORS V4.0 Jul 85 SYSGEN DISCREPANCY IN SCSNODE NAME LENGTH V4.0 Jul 85 RMS ACCESS CONTROL STRING PARSED INCORRECTLY V4.0 Jul 85 $RENAME RETURNS INCORRECT ERROR MESSAGE V4.0 Jul 85 BACKUP PROBLEM BOOTING STANDALONE BACKUP V4.0 Jul 85 UNDOCUMENTED ERROR MESSAGE FOR MOUNT vi.0 Jul DOCUMENTATION AUTHORIZE HAS TROUBLE PARSING /<ACCESS> QUALIFIERS vi.o SNDOPR SYMBOLIC CODE INCORRECT UNDOCUMENTED ERROR MESSAGE FOR MOUNT TEMPORARY MAILBOX LOGICAL NAMES SCREEN MANAGEMENT SYMBOLS DEFINED INCORRECTLY TODR DEFINITION REMOVED IN VAX/VMS VERSION 4.0 SYS SHUTDOWN WITH REBOOT_CHECK CAN FAIL DOCUMENTATION 75.1.1 85 85 Jul 85 Jul 85 85 Component/ Sequence Product Number Title of Article System Mon, Ivp 85.25.1 WARNING MESSAGE CAUSES IVP TO FAIL V4.0 Jul STARLET 85.50.1 ERROR IN XAB$ DEFINITIONS V4.0 Jul V4.0 Jul Operating ARTICLES OF GENERAL INTEREST OPCOM 95.5.1 95.5.2 BATCH/REMOTE ENABLE OF OPERATOR TERMINALS ERRANT FORMATTING BEHAVIOR IN VAX/VMS PRINT SYMBIONT Jul SYs 95.5.3 DELETION OF GLOBAL SECTIONS V4.0 Jul MICROFICHE 95.5.4 INCORRECT ENTRIES Vi1 Jul 163 IN VERSION 4.1 MICROFICHE COMPONENTS LIST 165 DISPATCH 5.0 10.0 11.0.0 12.0 INDEX Executive and 5.5 IMAGE ACTIVATOR 5.10 LOGICAL NAMES 5.15 MEMORY MANAGEMENT 5.20 SYs System Services System Management, Operations 10.0.0 System Management 10.5 ACCOUNTING 10.10 SDA 10.15 STARTUP Operations 11.5 ERROR LOGGING 11.10 EVENT LOGGING 11.15 LOGINOUT 11.20 OPCCRASH 11.25 OPCOM 11.30 SYSBOOT 11.35 SYSGEN 11.40 SYSINIT 11.45 VMB 11.50 WRITEBOOT Software Installation 12.5 INSTALL 12.10 UPGRADE 12.15 VMSINSTAL 167 & Security 13.0 Security 15.0 BATCH, PRINT, JOB CONTROLLER 15.5 BATCH 15.10 INPUT SYMBIONT 15.15 JOB CONTROLLER 15.20 LOCK MANAGER 15.25 PRINT 15.30 PRINT SYMBIONT 15.35 QUEUE MANAGER 20.0 DCL 25.0 DECnet 25.5 DECnet (generic) 25.10 DDCMP 25.15 DTS/DTR 25.20 EVL 25.25 FAL 25.30 HLD 25.35 MIRROR 25.40 MOM 25.45 NCP 25.50 NETACP 25.55 NML 25.60 REMACP 25.65 RTPAD (SET HOST) 168 30.0 Drivers 30.0 31.0 32.0 Disk Console & Tape Drivers 31.5 DBDRIVER 31.10 DDDRIVER 31.15 DLDRIVER 31.20 DMDRIVER 31.25 DODRIVER 31.30 DRDRIVER 31.35 DUDRIVER 31.40 DYDRIVER 31.45 MTDRIVER 31.50 TFDRIVER 31.55 TMDRIVER 31.60 TSDRIVER 31.65 TUDRIVER NET Drivers Drivers 32.5 CNDRIVER 32.10 NDDRIVER 32.15 NETDRIVER 32,20 NODRIVER 32.25 XDDRIVER 32.30 XEDRIVER 32.35 XGDRIVER 32.40 XMDRIVER 32.45 XQDRIVER 32.50 XWDRIVER 169 Sweden Digital Equipment AB P.O. Box 1250 S-17124 Solna 1 Sweden Denmark Digital Equipment Corp. AS Kristineberg 3 Finland Digital Equipment Corp. PL 16 SF-02201, Espoo 20 o5 DK-2100 Copenhagen 0 Denmark Oy Finland Norway Digital Equipment Corp. A/S Pottemakerveien 8 N-Oslo 5 Norway Austria, East Germany, West Germany, Poland, Hungary, Rumania, Czechoslovkia, Russia, Digital Equipment Corp. GmbH Rheinstrasse 28 D - 8000 Munich 40 West Germany Bulgaria Israel Decsys, Computers Ltd. 4, Yirmiyahu Str. IL-63505 Tel Aviv Israel Greece, Portugal, Spain, Switzerland, Yugoslavia, (Morocco, Algeria, Digital Equipment Corp. SA 9, Route des Jeunes Case Postale 191 CH-1211 Geneva 26 Tunisia, Cyprus, Turkey, Malta) Switzerland Mexico Digital Equipment de Mexico, S.A. de C.V. Ave. Lopez Mateos 427, 1st. Floor Guadalajara Jalisco Mexico China Digital Computer Hong Kong Ltd. 1303-1309 Dominian Ctr. 43-59 Queen's Road East Wanchai Hong Kong DIGITAL EQUIPMENT CORPORATION, Corporate Headquarters: Maynard, Massachusetts 01754, Telephone: (617)897-5111—-SALES AND SERVICE OFFICES: UNITED STATES —~ALABAMA, Huntsville « ARIZONA, Phoenix and Tucson ¢ CALIFORNIA, El Segundo, Los Angeles, Oakland, Ridgecrest, San Diego, San Francisco (Mountain View), Santa Ana, Santa Clara, Stanford, Sunnyvale and Woodland Hills « COLORADO. Englewood « CONNECTICUT, Fairfield and Meriden « DISTRICT OF COLUMBIA, Washington (Lanham, MD) « FLORIDA, Ft. Lauderdale and Orlando » GEORGIA, Atlanta « HAWAII, Honolulu + ILLINOIS, Chicago (Rolling Meadows) ¢ INDIANA, Indianapolis « IOWA, Bettendorf « KENTUCKY, Louisville « LOUISIANA, New Orleans (Metairie) « MARY- LAND, Odenton « MASSACHUSETTS, Marlborough, Waltham and Westfield « MICHIGAN, Detroit (Farmington Hills) e MINNESOTA, Minneapolis « MISSOURI, Kansas City (Independence) and St. Louis « NEW HAMPSHIRE, Manchester o NEW JERSEY, Cherry Hill, Fairfield, Metuchen and Princeton « NEW MEXICO, Albuquerque « NEW YORK, Albany, Buffalo (Cheektowaga), Long Island (Huntington Station), Manhattan, Rochester and Syracuse + NORTH CAROLINA, Durham/Chapel Hill « OHIO, Cleveland (Euclid), Columbus and Dayton « OKLAHOMA, Tulsa « OREGON, Eugene and Portland » PENNSYLVANIA, Allentown, Philadelphia (Bluebell) and Pittsburgh « SOUTH CAROLINA, Columbia « TENNESSEE, Knoxville and Nashville s TEXAS, Austin, Dallas and Houston « UTAH, Salt Lake City ¢ VIRGINIA, Richmond « WASHINGTON, Bellevue « WISCONSIN, Milwaukee (Brookfield) « INTERNATIONAL —ARGENTINA, Buenos Aires ¢ AUSTRALIA, Adelaide, Brisbane, Canberra, Melbourne, Perth and Sydney » AUSTRIA, Vienna ¢ BELGIUM, Brussels « BOLIVIA, La Paz » BRAZIL, Rio de Janeiro and Sao Paulo « CANADA, Calgary, Edmonton, Halifax, London, Montreal, Ottawa, Toronto, Vancouver and Winnipeg » CHILE, Santiago « DENMARK, Copenhagen * FINLAND, Helsinki « FRANCE, Lyon, Grenoble and Paris « GERMAN FEDERAL REPUBLIC, Cologne, Frankfurt, Hamburg, Hannover, Munich, Nuremburg, Stuttgart and West Berlin « HONG KONG « INDIA, Bombay ¢ INDONESIA, Djakarta s IRELAND, Dublin « ITALY, Milan, Rome and Turin ¢ IRAN, Tehran » JAPAN, Osaka and Tokyo ¢ MALAYSIA, Kuala Lumpur « MEXICO, Mexico City « NETHERLANDS, Utrecht « NEW ZEALAND, Auckland and Christchurch « NORWAY, Oslo « PUERTO RICO, Santurce ¢ SINGAPORE « SPAIN, Madrid « SWEDEN, Gothenburg and Stockholm » SWITZERLAND, Geneva and Zurich « UNITED KINGDOM, Birmingham, Bristol, Epsom, Edinburgh, Leeds, Leicester, London, Manchester and Reading «VENEZUELA, Caracas «
Home
Privacy and Data
Site structure and layout ©2025 Majenko Technologies
