VAX-11 RTEM RELEASE NOTES | This document describes the release information for VAX-11 RTEM V2.1, | V2.2 and V2.3. | Operating System: VAX/VMS Version 4.4 and subsequent versions | | Software: VAX-11 RTEM Version 2.3 1 VAX-11 RTEM RELEASE NOTES First Printing, June 1985 Updated, January 1986 | Updated, July 1986 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies. Copyright (c) Digital Equipment Corporation 1985, 1986. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: _____________ CTS-300 |d|i|g|i|t|a|l| RSTS DEC ------------- RSX DECmate MASSBUS RT-11 DECnet MicroPDP-11 RTEM-11 DECsystem-10 MicroVMS UNIBUS DECSYSTEM-20 PDP VAX DECUS P/OS VMS DECwriter Professional VT DIBOL Q-BUS Work Processor Rainbow 2 VAX-11 RTEM RELEASE NOTES CONTENTS PREFACE . . . . . . . . . . . . . . . . . . . . . . 5 CHAPTER 1 NEW FEATURES 1.1 RT-11 EMULATION SUPPORT . . . . . . . . . . . . . 1-1 1.2 RT-11 UTILITIES SUPPORT . . . . . . . . . . . . . 1-1 1.2.1 MACRO-11 Symbolic Debugger . . . . . . . . . . . 1-1 1.2.2 Native TRANSF.SAV Utility . . . . . . . . . . . 1-1 1.3 DEVICE SUPPORT . . . . . . . . . . . . . . . . . . 1-1 1.3.1 MU - TMSCP Tape Handler . . . . . . . . . . . . 1-2 1.3.2 DA - RC25 Disk Support . . . . . . . . . . . . . 1-2 1.3.3 DJ - RA60 Disk Support . . . . . . . . . . . . . 1-2 1.4 HOST COMMAND LINE EXECUTION . . . . . . . . . . . 1-2 1.5 CHANGES TO THE JOAT UTILITY /A, /D, /E, AND /M OPTIONS . . . . . . . . . . . . . . . . . . . . . 1-3 1.6 LS HANDLER SET OPTIONS . . . . . . . . . . . . . . 1-3 1.7 DCL COMMANDS . . . . . . . . . . . . . . . . . . . 1-4 1.7.1 Copy . . . . . . . . . . . . . . . . . . . . . . 1-4 1.7.2 Create . . . . . . . . . . . . . . . . . . . . . 1-5 1.7.3 Dismount . . . . . . . . . . . . . . . . . . . . 1-6 1.7.4 Mount . . . . . . . . . . . . . . . . . . . . . 1-6 1.7.5 Exit . . . . . . . . . . . . . . . . . . . . . . 1-7 1.7.6 Show Subset . . . . . . . . . . . . . . . . . . 1-7 1.7.7 Set . . . . . . . . . . . . . . . . . . . . . . 1-7 1.8 DOCUMENTATION . . . . . . . . . . . . . . . . . . 1-8 1.9 TERMINAL SERVICE . . . . . . . . . . . . . . . . . 1-8 1.10 INSTALLATION PROCEDURE . . . . . . . . . . . . . . 1-8 1.10.1 DCL Command and HELP . . . . . . . . . . . . . . 1-8 1.10.2 Subset of RT-11 Kit . . . . . . . . . . . . . . 1-8 1.10.3 RT-11 Customization Section Deleted . . . . . . 1-9 1.10.4 VAX-11 RTEM Customization Procedure . . . . . . 1-9 1.10.5 VAX-11 RTEM Distribution Kit . . . . . . . . . . 1-9 1.11 ADDITIONAL FIP UTILITY /A DEFAULT FILE TYPES . . . 1-9 CHAPTER 2 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS 2.1 RT-11 RESTRICTIONS . . . . . . . . . . . . . . . . 2-1 2.1.1 DCL Commands . . . . . . . . . . . . . . . . . . 2-1 2.1.2 LP Device Handler . . . . . . . . . . . . . . . 2-2 2.1.3 RL01/RL02 and RK06/RK07 Foreign RT-11 Volumes . 2-2 2.2 VAX-11 RTEM RESTRICTIONS . . . . . . . . . . . . . 2-2 2.2.1 VAX/VMS Long Directory and File Specifications . 2-2 2.2.2 VAX/VMS Search Lists . . . . . . . . . . . . . . 2-3 2.2.3 BATCH Operations . . . . . . . . . . . . . . . . 2-3 2.2.4 Mounting Foreign Devices . . . . . . . . . . . . 2-3 2.2.5 Line Printer Access . . . . . . . . . . . . . . 2-3 2.2.6 Gaining Access to Files Under Rooted Directories 2-3 2.2.7 DECnet Virtual Terminal . . . . . . . . . . . . 2-4 3 VAX-11 RTEM RELEASE NOTES 2.2.8 Using with SIPP . . . . . . . . . . . . 2-4 2.2.9 DX and DY Device Handler .SPFUN Requests . . . . 2-4 2.3 ADDITIONAL RESTRICTIONS . . . . . . . . . . . . . 2-5 2.3.1 Transferring VAX/VMS DCL Output Files . . . . . 2-5 2.3.2 Using RTEM for Batch Applications . . . . . . . 2-5 2.3.3 Invoking VAX-11 RTEM from DCL Command Procedures 2-6 2.4 CORRECTED SOFTWARE PROBLEMS . . . . . . . . . . . 2-6 2.4.1 LD Handler . . . . . . . . . . . . . . . . . . . 2-6 2.4.2 LP Handler . . . . . . . . . . . . . . . . . . . 2-7 2.4.3 VAX-11 RTEM DCL Processing . . . . . . . . . . 2-7 2.4.4 DU Handler . . . . . . . . . . . . . . . . . . . 2-7 2.4.5 JOAT Utility . . . . . . . . . . . . . . . . . . 2-7 2.4.6 RT-11 HELP/PRINTER * Command . . . . . . . . . . 2-7 CHAPTER 3 CUSTOMIZING RTEM 3.1 DEFAULT CUSTOMIZATIONS . . . . . . . . . . . . . . 3-1 3.1.1 Default Virtual Device Access Action . . . . . . 3-1 3.1.2 Default Virtual Device Size . . . . . . . . . . 3-2 3.1.3 Default Number of Extra Directory Bytes . . . . 3-2 3.1.4 Default RTEM Task Size . . . . . . . . . . . . . 3-2 3.1.5 Default File Specification of Shared Virtual Device File . . . . . . . . . . . . . . . . . . 3-2 3.2 RUNNING THE CUSTOMIZATION PROCEDURE . . . . . . . 3-3 CHAPTER 4 TECHNICAL INFORMATION 4.1 DISTRIBUTED MONITOR . . . . . . . . . . . . . . . 4-1 4.2 RTEMFB.SYS SYSGEN CONDITIONAL FILE . . . . . . . . 4-1 CHAPTER 5 NATIVE TRANSFER UTILITY (TRANSFER) 5.1 USING TRANSFER . . . . . . . . . . . . . . . . . . 5-2 5.1.1 TRANSFER Command Syntax . . . . . . . . . . . . 5-2 5.1.2 TRANSFER Mode Qualifiers . . . . . . . . . . . . 5-4 5.1.3 TRANSFER Control Qualifiers . . . . . . . . . . 5-5 5.2 TRANSFER MESSAGES . . . . . . . . . . . . . . . . 5-8 5.2.1 Message Format . . . . . . . . . . . . . . . . . 5-8 5.2.2 Messages Returned by TRANSFER . . . . . . . . . 5-9 4 VAX-11 RTEM RELEASE NOTES PREFACE PREFACE | This manual describes VAX-11 RTEM V2.3 and how it differs from VAX-11 | RTEM V2.2 and V2.1. Changes to VAX-11 RTEM for V2.3 are highlighted | by change bars. For VAX/VMS, the RTEM-11 product has been renamed VAX-11 RTEM. This | change reflects the RTEM requirement for the use of the PDP-11 | compatibility mode in order to run. Throughout this document, VAX-11 RTEM refers to the RTEM product that runs under VAX/VMS. RTEM, when used alone, refers to the RTEM product that runs under VAX as well as under PDP-11 systems. This document describes new features and corrected problems, and presents a comparison between this release of RTEM-11 and the previous releases: o Chapter 1 - NEW FEATURES This chapter describes the new devices, software components, and documentation. o Chapter 2 - CURRENT RESTRICTIONS AND CORRECTED PROBLEMS This chapter describes current software restrictions and problems, and lists software problems that have been corrected. o Chapter 3 - CUSTOMIZING RTEM This chapter describes alterations you can make to VAX-11 RTEM, and tells you how to run the customization procedure. o Chapter 4 - TECHNICAL INFORMATION This chapter provides some technical information about VAX-11 RTEM for advanced users. o Chapter 5 - NATIVE TRANSFER UTILITY (TRANSFER) This chapter tells you how to use the TRANSFER utility. TRANSFER copies files between a processor running RT-11 and another processor running VAX/VMS. 5 CHAPTER 1 NEW FEATURES NEW FEATURES | VAX-11 RTEM V2.3 incorporates new features necessary for the emulation | of RT-11 V5.4. | | | RT-11 EMULATION SUPPORT | 1.1 RT-11 EMULATION SUPPORT | | RTEM V2.3 emulates the RT-11 V5.4 foreground/background operating | environment just as RTEM V2.2 emulated the RT-11 V5.3 | foreground/background operating environment. The differences between _____ ______ | RT-11 V5.3 and RT-11 V5.4 are described in the V5.4 RT-11 System _______ _____ | Release Notes. | | | RT-11 UTILITIES SUPPORT | 1.2 RT-11 UTILITIES SUPPORT | MACRO-11 Symbolic Debugger | 1.2.1 MACRO-11 Symbolic Debugger | | VAX-11 RTEM V2.3 supports the new RT-11 V5.4 MACRO-11 symbolic ______ ________ ________ ______ _____ | debugger, DBG-11. Refer to the DBG-11 Symbolic Debugger User's Guide | for more information on DBG-11. Native TRANSF.SAV Utility 1.2.2 Native TRANSF.SAV Utility VAX-11 RTEM includes TRANSFER.EXE, a native version of the RT-11 TRANSF.SAV program. (TRANSFER.EXE is described in Chapter 5.) The VAX-11 RTEM distribution kit no longer includes TRANSF.SAV. DEVICE SUPPORT 1.3 DEVICE SUPPORT VAX-11 RTEM supports three new devices: MU, DA, and DJ. 1-1 NEW FEATURES NEW FEATURES MU - TMSCP Tape Handler 1.3.1 MU - TMSCP Tape Handler The MU handler supports magtape systems that implement the tape mass-storage communication protocol (TMSCP). See the RT-11 document set for more information on the MU handler. DA - RC25 Disk Support 1.3.2 DA - RC25 Disk Support Under VAX/VMS an RC25 disk drive is called DA. Under RT-11 the RC25 is called DU. VAX-11 RTEM maps any attachment of an RC25 DA device under VAX/VMS to an attachment of an RT-11 DU device. DJ - RA60 Disk Support 1.3.3 DJ - RA60 Disk Support Under VAX/VMS an RA60 disk drive is called DJ. Under RT-11 the RA60 is called DU. VAX-11 RTEM maps any attachment of an RA60 DJ device under VAX/VMS to an attachment of an RT-11 DU device. HOST COMMAND LINE EXECUTION 1.4 HOST COMMAND LINE EXECUTION | You can send any DCL or MCR command line under VAX-11 RTEM to VAX/VMS DCL for execution by specifying the /HOST qualifier. You can place the /HOST qualifier after the command or after its parameter. For example: .PHONE/HOST JOY .MAIL/HOST .DIRECTORY/HOST DISK$USERS:[DOCUMENTS] .DELETE/HOST DISK$USERS:[MILLER]TEMP.DSK;6 .REPLY/USER=MILLER "Hi Brad - Want to have dinner at 6?"/HOST RTEM passes the entire command line without the /HOST qualifier to the VAX/VMS system for execution. | | NOTE | | All previous restrictions on the use of the /HOST | qualifier have been removed beginning in VAX-11 RTEM | V2.3. You can execute any VAX/VMS command under | VAX-11 RTEM that you can execute at the VAX/VMS | command level. | 1-2 NEW FEATURES NEW FEATURES CHANGES TO THE JOAT UTILITY /A, /D, /E, AND /M OPTIONS | 1.5 CHANGES TO THE JOAT UTILITY /A, /D, /E, AND /M OPTIONS | The JOAT /A option mounts a native device using the native system MOUNT utility before it attaches that device under the RTEM environment. Therefore, you no longer need to execute the native MOUNT/FOREIGN command before you attach a foreign device under RTEM using JOAT. The JOAT /A option can also be expressed as the DCL command MOUNT/NATIVE/DEVICE. The JOAT /D option dismounts a native device using the native system DISMOUNT utility after it detaches that device from the RTEM environment. Therefore, you no longer need to execute the native DISMOUNT command after you detach a foreign device under RTEM using JOAT. The JOAT /D option can also be expressed as the DCL command DISMOUNT. The JOAT /E option dismounts all native devices previously mounted with /A. Then /E causes RTEM to exit to the native system. JOAT /E can also be expressed as the DCL command EXIT. | The JOAT /M option, previously available only on RSX versions of RTEM, | is now functional under VAX-11 RTEM. | | JOAT /M allows you to return to the host command language interpreter | without exiting RTEM. The /M option accepts no file or device | specifications. The system command line interpreter prompts you as if | you had exited RTEM. To return to VAX-11 RTEM, follow the directions | that JOAT displays when you enter the /M command. | | For example: | | .R JOAT | */M | ?JOAT-I-Returning to host system, type "$ LOGOUT" to continue. | $ SHOW TIME | 18-APR-1986 00:14:56.12 | $ LOGOUT | MILLER_1 logged out 18-APR-1986 00:16:13.11 | *^C | . LS HANDLER SET OPTIONS 1.6 LS HANDLER SET OPTIONS Two new SET options have been added to the RTEM LS handler. They duplicate the functions added to RT-11. o .SET LS 8BIT/NO8BIT o .SET LS ENDPAG=n 1-3 NEW FEATURES NEW FEATURES _____ ______ _______ _____ The preceding options are described in the RT-11 System Release Notes. DCL COMMANDS 1.7 DCL COMMANDS Seven DCL commands have been added to VAX-11 RTEM. You can use those commands in place of the cryptic commands of JOAT and FIP. The DCL COPY command has been extended to support file copies using FIP. The DCL CREATE, DISMOUNT, MOUNT, SET, and SHOW commands have been extended to support various JOAT functions. EXIT, a new DCL command, has been added to support the JOAT /E option. The RT-11 HELP command has been modified to reflect the addition of RTEM-specific DCL commands. Three of the following DCL commands (COPY, CREATE, and MOUNT) must be used with the /NATIVE option to work as RTEM commands. If you use those three commands without /NATIVE, the normal RT-11 commands execute. In the following DCL command descriptions, values in parentheses show the JOAT or FIP function that the DCL command qualifier replaces. Copy 1.7.1 Copy .COP[Y][/options] filespec[,filespec...][/options] filespec[/options] /NAT[IVE] (/F) The /NATIVE command option copies files to and from the RTEM environment. If you do not specify that option, the normal RT-11 COPY command executes. The /NATIVE qualifier is position dependent. If you place /NATIVE on the input file specification, files are copied from the native environment to the RTEM environment. If you place that qualifier on the output file specification, files are copied from the RTEM environment to the native environment. COPY command options you can use with /NATIVE are: /ASCII[:n.] (/A[:n.]) /NEWFILES (/G) /BINARY[:n.] (B[:n.]) /[NO]LOG (/W) /CONTIGUOUS (/C) /[NO]QUERY (/Q) /EXCLUDE (/P) /[NO]REPLACE (/N) /FORTRAN (/T) /SYSTEM (/Y) /IMAGE[:n.] (/I[:n.]) 1-4 NEW FEATURES NEW FEATURES Any other RT-11 COPY command options, if specified with /NATIVE, return the error: ?UCF-F-Invalid option for program Examples: .COPY UCF.MAC *.*/NATIVE !From RTEM to native system .COPY UCF.MAC/NATIVE *.* !From native system to RTEM Create 1.7.2 Create .CRE[ATE]/NATIVE Files-11-filespec (/C or /S) /NATIVE The /NATIVE option creates an RTEM virtual disk file. If you do not specify /NATIVE, the RT-11 CREATE command executes. You can place /NATIVE after the command or after its parameter. CREATE command options you can use with /NATIVE are: /ALLOCATE:n. (/C:n.) /ORDER[:xxx] (/O[:xxx]) /SHARED:dev[:] (filespec=dev:/S) /TEMPORARY (/Z) /[NO]QUERY (/Y) /UNIT:dev[:] (/V:dev:) Any other RT-11 CREATE command options, if specified with /NATIVE, return the error: ?UCF-F-Invalid option for program The default for CREATE/NATIVE creates a new empty virtual device file. The default size of that file is 494 decimal blocks. If you are the system manager, you can modify the default using the RTEM customization command procedure. RTEM attaches the new virtual device file to the next available VS device. If you create a virtual device file on a VS unit that is currently assigned to another virtual device, RTEM displays the following prompt. ?JOAT-I-Attach supersedes existing assignment ?JOAT-I-Are you sure ? If you specify /NOQUERY, RTEM suppresses that prompt. Examples: .CREATE/NATIVE WORK/ALLOCATE:1000. .CREATE/NATIVE RT11SH/SHARED=DL0: 1-5 NEW FEATURES NEW FEATURES Dismount 1.7.3 Dismount .DIS[MOUNT] rtdev[:] (/D) /[NO]QUERY (/Y) The default for DISMOUNT is /NOQUERY. If you specify the /QUERY option, RTEM prompts: ?JOAT-I-Detach Rtdev: - Are you sure ? Examples: .DISMOUNT VS3 .DISMOUNT DL0: Mount 1.7.4 Mount .MO[UNT]/NATIVE dev:[directory]filename.ext (/A or /V) /NATIVE The /NATIVE option mounts a native device or RTEM virtual disk file. If you do not specify /NATIVE, the RT-11 MOUNT command executes. You can place /NATIVE after the command or after its parameter. MOUNT command options you can use with /NATIVE are: /DEVICE (/A) /[NO]WRITE (/W[:NO]) /PRIVATE (/U) /FILE (/V) /[NO]WRITE (/W[:NO]) /EXTEND[:n.] (/T[:n.] /UNIT:DEV[:] (/V:VSn) (/A:DEV) /PRIVATE (/U) /[NO]QUERY (/Y) If you use MOUNT without an option, the file specification determines the default option. If the file specification ends with a colon (:), /DEVICE is the default. If the file specification does not end with a colon, /FILE is the default. If you specify /NOQUERY, RTEM suppresses the prompt ?JOAT-I-Attach supersedes existing assignment ?JOAT-I-Are you sure ? if you mount a virtual device file on a VS unit that is currently 1-6 NEW FEATURES NEW FEATURES assigned to another virtual device. Examples: .MOUNT DL0:/NATIVE Defaults to /DEVICE to mount DL0: .MOUNT WORK/NATIVE Defaults to /FILE .MOUNT DL0/NATIVE/DEVICE Forces /DEVICE mount (no colon) .MOUNT SYS$WORK:/NATIVE/FILE Mounts file associated with logical name SYS$WORK Exit 1.7.5 Exit .EXI[T] (/E) /[NO]QUERY (/Y) /STATUS:n. (/E:n.) The EXIT command, specific to RTEM, dismounts any devices previously mounted with the JOAT /A option. RTEM then exits to the native operating system. JOAT /A can also be expressed as the DCL command MOUNT/NATIVE/DEVICE. The default is /QUERY. If /NOQUERY is specified, RTEM suppresses the prompt: ?JOAT-I-Exit RTEM-11 - Are you sure ? Examples: .EXIT /NOQUERY .EXIT/STATUS:4 Show Subset 1.7.6 Show Subset .SHOW SUB[SET] (/L) SHOW SUBSET, available in RT-11, displays the logical disk subsets in effect. The RESORC utility has been modified to chain an exit to JOAT. JOAT then displays the current virtual and foreign device attachments. Set 1.7.7 Set .SET rtdev[:] [WRITE] [NOWRITE] [PRIVATE] [NO]WRITE (W[:NO]) 1-7 NEW FEATURES NEW FEATURES PRIVATE (U) The SET command, available in RT-11, changes device handler characteristics and certain system generation parameters. Examples: .SET VS3: NOWRITE .SET DL0 PRIVATE .SET VS1 WRITE DOCUMENTATION 1.8 DOCUMENTATION The RTEM-11 Release Notes have been put on line via the RTEM distribution kit. TERMINAL SERVICE 1.9 TERMINAL SERVICE characters are now intercepted by VAX/VMS. returns you to the DCL mode. INSTALLATION PROCEDURE 1.10 INSTALLATION PROCEDURE The VAX-11 RTEM installation procedure has been modified to reduce your installation time. DCL Command and HELP 1.10.1 DCL Command and HELP The installation procedure now adds the foreign RTEM VAX/VMS DCL command and an RTEM help frame to the system help processor. All emulator command syntax remains the same. Subset of RT-11 Kit 1.10.2 Subset of RT-11 Kit RTEM no longer requires an RT-11 binary distribution kit. A subset of the RT-11 binary distribution kit is included in the RTEM distribution kit. The only requirement is that under VAX/VMS you must have VAX-11 RSX V2.0 or subsequent versions installed before you install VAX-11 RTEM. 1-8 NEW FEATURES NEW FEATURES RT-11 Customization Section Deleted 1.10.3 RT-11 Customization Section Deleted The RT-11 customization section has been deleted. VAX-11 RTEM Customization Procedure 1.10.4 VAX-11 RTEM Customization Procedure The abort character question of the VAX-11 RTEM customization procedure has been deleted. VAX-11 RTEM lets you return to VAX/VMS by typing . VAX-11 RTEM Distribution Kit 1.10.5 VAX-11 RTEM Distribution Kit VAX-11 RTEM is now distributed on 1600 bits/in magnetic tape as well as on TU58 and RX01 media. ADDITIONAL FIP UTILITY /A DEFAULT FILE TYPES 1.11 ADDITIONAL FIP UTILITY /A DEFAULT FILE TYPES During the copy operation, FIP transfers the following file types in ASCII mode (/A) unless you override the default. These default file _______ ______ _____ types are in addition to those included in the RTEM-11 User's Guide. .C .H .MEM .CTL .S .ANS .TXT .CND 1-9 CHAPTER 2 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS This chapter lists current restrictions and corrected software problems, describes procedures to follow when you operate VAX-11 RTEM, and notes the differences between VAX-11 RTEM operation and RT-11 operation. RT-11 RESTRICTIONS 2.1 RT-11 RESTRICTIONS DCL Commands 2.1.1 DCL Commands | The VAX-11 RTEM DCL commands are implemented through the use of the _____ ______ | RT-11 User Commands First feature (UCF), described in the RT-11 System ______ _____ | User's Guide. You cannot write your own UCF processor for use under | RTEM because RTEM uses that facility for its DCL commands. | | The following RT-11 DCL commands do not function when VAX-11 RTEM UCF | command processing is enabled. UCF command processing is enabled by | default. | | B | CLOSE | D | E | GET | REENTER | SAVE | START | | If you use those commands while RTEM UCF command processing is | enabled, VAX-11 RTEM displays the error message: | | ?UCF-F-UCF command processing must be disabled | | If you must use those restricted commands, you can disable RTEM UCF | command processing by entering the command: 2-1 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS | .R UCF | ?UCF-I-UCF command processing is now DISABLED | | Then, to enable RTEM UCF command processing, enter: | | .R UCF | ?UCF-I-UCF command processing is now ENABLED | | While RTEM UCF command processing is disabled, the RTEM-specific DCL | commands (COPY/NATIVE, for example) are not available. LP Device Handler 2.1.2 LP Device Handler The following RT-11 command fails unless you load the RTEM LP device handler by using the RT-11 LOAD LP: command. .MACRO/OUTPUT/CROSS filespec The command fails because the RTEM LP device handler contains a volatile record management data base. If the LP handler has not been explicitly loaded before MACRO-11 chains to CREF, the handler is unloaded and loses its record management information. RL01/RL02 and RK06/RK07 Foreign RT-11 Volumes 2.1.3 RL01/RL02 and RK06/RK07 Foreign RT-11 Volumes Dismount any foreign RT-11 RL01/RL02 or RK06/RK07 disk volumes before you replace the disk cartridge currently in use. RT-11 supports bad-block replacement on those disks. RTEM device handlers may have the bad-block replacement information in memory, but they cannot tell when the disk packs have been removed. If you do not dismount the foreign volumes before you replace the disk, data on new disk cartridges may be corrupted. Use the RTEM DISMOUNT command to dismount the volume(s). After you insert the new disk cartridge, mount it with the MOUNT command. VAX-11 RTEM RESTRICTIONS 2.2 VAX-11 RTEM RESTRICTIONS VAX/VMS Long Directory and File Specifications 2.2.1 VAX/VMS Long Directory and File Specifications Long directory and file specifications are not supported by VAX-11 RTEM. Long directory specifications have more than nine characters. Long file specifications have file names longer than nine characters or file extensions longer than three characters. Any attempt to have access to directories or files with long specifications using VAX-11 2-2 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS RTEM fails. VAX/VMS Search Lists 2.2.2 VAX/VMS Search Lists The VAX/VMS logical name search list capability is not supported by VAX-11 RTEM. VAX-11 RTEM does not run if you set the process default device to a logical name that includes or references a search list. VAX-11 RTEM does not accept any file specification that includes or references a search list. BATCH Operations 2.2.3 BATCH Operations VAX/VMS BATCH does not support all the terminal handler functions needed by VAX-11 RTEM. Running the emulator as a BATCH job under VAX/VMS is not supported. Mounting Foreign Devices 2.2.4 Mounting Foreign Devices VMS displays an error message if you use the VAX-11 RTEM MOUNT/NATIVE/DEVICE (or JOAT /A) command to mount a device that was mounted with the VMS DCL MOUNT command. VAX-11 RTEM cannot sense if the device was previously mounted. You may ignore that error message. Line Printer Access 2.2.5 Line Printer Access Under VAX-11 RTEM the line printer used by the LP handler must be set up as a spooled device. By default, that line printer is LPA0. The default can be changed by the RTEM command line option /LP or by the system manager. The following are examples of commands that set up the line printer as a spooled device. $ SET DEVICE LPA0:/SPOOLED $ SET DEVICE LCA0:/SPOOLED $ SET DEVICE TTA3:/SPOOLED Gaining Access to Files Under Rooted Directories 2.2.6 Gaining Access to Files Under Rooted Directories For VAX-11 RTEM to use file specifications containing device names that translate to rooted directories, you must first define logical names to represent those rooted directories. 2-3 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS For each rooted directory in your system that you intend to access using VAX-11 RTEM, define a logical name $$n (where n = 0 to 377 octal) that corresponds to the rooted directory name. In the following example, the rooted directory logical name USER translates to __DRA0:[USERS.]. $ DEFINE/SYSTEM $$0 USER: or $ DEFINE/SYSTEM/EXEC/TRANSLATION=(TERMINAL,CONCEALED) $$0 __DRA0:[USERS.] Insert one of the preceding DEFINE commands at the end of the file SYS$MANAGER:VAX11RSX$DEVICE_NAMES.COM. Although $$0 is used in the preceding example, you may use any of the $$n logicals ($$0 to $$377 octal). For best performance, however, use the lowest numbered $$n logical name not currently in use on your system. Check the previously mentioned command file to determine the ______ ___ lowest numbered $$n logical name available. See the VAX-11 RSX _____________ ____ _________ ______ Compatibility Mode Reference Manual for more information on $$n logical names. DECnet Virtual Terminal 2.2.7 DECnet Virtual Terminal DECnet/VAX does not support all the terminal handler functions needed by RTEM-11. Running the emulator from a DECnet virtual terminal is not supported. In other words, do not invoke RTEM-11 from a remote terminal if you logged onto your system from that terminal using the SET HOST command. Using with SIPP 2.2.8 Using with SIPP VAX-11 RTEM aborts if you press while running the emulator. Under RT-11 CTRL/Y is used with SIPP (Save Image Patch Program) to install code modifications. When you run SIPP under RTEM, type a circumflex and Y (^Y) to install code modifications. Do not type the CTRL key and Y (CTRL/Y). DX and DY Device Handler .SPFUN Requests 2.2.9 DX and DY Device Handler .SPFUN Requests The use of some .SPFUN requests to the RX01 and RX02 device handlers is restricted under VAX/VMS. The VAX-11 RTEM DX and DY handlers convert such requests into VAX/VMS physical QIO functions. VAX/VMS 2-4 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS physical QIO functions require that the process running VAX-11 RTEM or the VAX-11 RTEM task image have the PHYS_IO privilege. The following .SPFUN requests are restricted: .SPFUN Code Function .SPFUN Code Function 377 Read physical sector 376 Write physical sector 375 Write physical sector with deleted data mark For security reasons, system managers should not install VAX-11 RTEM with any privilege in high-risk environments or environments in which VAX-11 RTEM users do not need the restricted .SPFUN requests. Only one DIGITAL-supported RT-11 program, FILEX, uses the .SPFUN requests. Therefore, the following RT-11 DCL commands do not work under VAX-11 RTEM without physical I/O privilege: DCL Command Filex Option Equivalent DCL Command Filex Option Equivalent COPY/INTERCHANGE /U DELETE/INTERCHANGE /U/D DIRECTORY/INTERCHANGE /U/L INITIALIZE/INTERCHANGE /U/Z If you install the VAX-11 RTEM task image with physical I/O, add the following VAX/VMS commands to your system start-up command file: $ ! $ ! Install VAX-11 RTEM W/PHYS_IO privilege. $ ! $ RUN SYS$SYSTEM:INSTALL SYS$SYSTEM:RTEM /PRIV=PHYS_IO $ ! ADDITIONAL RESTRICTIONS 2.3 ADDITIONAL RESTRICTIONS Transferring VAX/VMS DCL Output Files 2.3.1 Transferring VAX/VMS DCL Output Files Under VAX-11 RTEM use the COPY/FORTRAN (FIP /T) transfer option to transfer VAX/VMS DCL output files. Those files are written with FORTRAN carriage control. Using RTEM for Batch Applications 2.3.2 Using RTEM for Batch Applications Although RTEM is not supported in VAX/VMS BATCH mode, you can pass a command file to RTEM by means of the RT-11 IND utility in the following two steps: 2-5 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS 1. Create the following two command files under RTEM in a virtual device file. STARTM.COM: RUN SY:IND STARTM.CMD STARTM.CMD: .ENABLE SUBSTITUTION COPY RTCMDS.CMD/NATIVE *.* @RTCMDS.CMD EXIT/NOQUERY 2. Create a Files-11 file named RTCMDS.CMD and include your RT-11/RTEM IND/DCL commands. When you boot RTEM via the virtual device file containing the two command files, the commands in the Files-11 file are executed. Once the commands are executed, control returns to STARTM.CMD which runs the RTEM JOAT utility. JOAT exits RTEM and returns to the native system. You can create RTCMDS.CMD by using VAX/VMS DCL or some other application program. Invoking VAX-11 RTEM from DCL Command Procedures 2.3.3 Invoking VAX-11 RTEM from DCL Command Procedures To invoke RTEM from a VAX/VMS DCL command procedure, put the following VAX/VMS DCL ASSIGN command immediately before the VAX-11 RTEM command line. $ ASSIGN/USER_MODE SYS$COMMAND SYS$INPUT That command lets VAX-11 RTEM have access to the terminal at which the command procedure is running. If you omit that command, VAX-11 RTEM displays several error messages. Although VAX-11 RTEM runs, no input is accepted from the terminal. CORRECTED SOFTWARE PROBLEMS 2.4 CORRECTED SOFTWARE PROBLEMS LD Handler | 2.4.1 LD Handler | | VAX-11 RTEM V2.2, when you mounted a logical disk, sometimes caused | the logical disk handler (LD) to trap to 4. That problem has been | corrected. 2-6 CURRENT RESTRICTIONS AND CORRECTED PROBLEMS CURRENT RESTRICTIONS AND CORRECTED PROBLEMS LP Handler | 2.4.2 LP Handler | | In VAX-11 RTEM V2.2, when a VAX/VMS system manager set VAX-11 RTEM's | default printer to one other than LPA0, VAX-11 RTEM did not print | files. That problem has been corrected. | | | VAX-11 RTEM DCL Processing | 2.4.3 VAX-11 RTEM DCL Processing | | In VAX-11 RTEM V2.2, the numeric arguments on the RTEM DCL commands | defaulted to octal unless you specified a decimal point (.) after the | number. Now, the arguments default to decimal, to be compatible with | the RT-11 DCL commands. | | In VAX-11 RTEM V2.2, if you pressed a double the DCL commands | sometimes failed to operate until the emulator was re-booted. That | problem has been corrected. | | | DU Handler | 2.4.4 DU Handler | | In RTEM V2.2, using the DU handler sometimes caused the emulator to | crash after displaying the error message ?RTEM-U-System halt. That | problem has been corrected. JOAT Utility 2.4.5 JOAT Utility In RTEM V2.1 a problem in the JOAT utility prevented a local copy of the system shared virtual device file (LB:[1,1]RT11SH.DSK) from being attached READ/WRITE. That problem has been corrected. RT-11 HELP/PRINTER * Command 2.4.6 RT-11 HELP/PRINTER * Command If you entered the RT-11 command HELP/PRINTER *, RTEM aborted. That problem has been corrected in RTEM V2.2. 2-7 CHAPTER 3 CUSTOMIZING RTEM CUSTOMIZING RTEM Although RTEM needs no alteration for most applications, you can alter it in some ways. To make these changes, you must be the system manager. DEFAULT CUSTOMIZATIONS 3.1 DEFAULT CUSTOMIZATIONS This section describes the changes you can make to RTEM default operations. Section 3.2 describes the procedure for making these customizations. Default Virtual Device Access Action 3.1.1 Default Virtual Device Access Action When the RTEM bootstrap task or the JOAT utility attaches a virtual device file, read/write access is attempted unless you specified read-only access. By default, if read/write access fails, RTEM prompts you for confirmation of the attachment. If you respond affirmatively, the virtual device file is attached as permanently read-only. You can modify the default action in either of two ways: 1. If read/write access fails, RTEM issues a warning message and attempts to open the virtual device file with read-only access. 2. If read/write access fails, RTEM issues a fatal error message and does not grant access. 3-1 CUSTOMIZING RTEM CUSTOMIZING RTEM Default Virtual Device Size 3.1.2 Default Virtual Device Size When the RTEM bootstrap task or the JOAT utility creates a virtual device file, 494 (decimal) blocks are assigned. You can modify that default to any value in the range 10 to 60,000 (decimal) blocks. Default Number of Extra Directory Bytes 3.1.3 Default Number of Extra Directory Bytes When the RTEM bootstrap task or the JOAT utility creates a new virtual device file, the number of extra directory bytes is 0 by default. You can modify that default to any value in the range 0 to 100 (decimal) bytes. If you change the default, any previously created virtual device files having different defaults are incompatible with any virtual files you create under the newly modified version of RTEM. Consequently DIGITAL strongly recommends that the default never be modified. Default RTEM Task Size 3.1.4 Default RTEM Task Size The installed size of RTEM determines the size of the RT-11 user partition. The default size of the emulator is 32K words, giving a 28K word RT-11 virtual machine. You can modify that default to any value from 24K words, giving a 20K word RT-11 virtual machine, to the default maximum size of 32K words, giving a 28K word RT-11 virtual machine. Default File Specification of Shared Virtual Device File 3.1.5 Default File Specification of Shared Virtual Device File When RTEM is installed, the shared virtual device file location is LB:[1,1]RT11SH.DSK. You may want to move that file, after the initial installation of RTEM, to another account and/or disk. Such a move is useful, for example, if the system disk on which RTEM is installed is full. You can change the location where the RTEM bootstrap task looks for the file. However, the file specified must already exist and node names are not allowed in the file specification. 3-2 CUSTOMIZING RTEM CUSTOMIZING RTEM RUNNING THE CUSTOMIZATION PROCEDURE 3.2 RUNNING THE CUSTOMIZATION PROCEDURE The RTEM installation procedure creates a customization command file (SYS$SYSTEM:RTEM.COM on the VAX/VMS system). When executed, that command file asks for the default values for the customization options (explained in Section 3.1) and modifies the RTEM bootstrap task (SYS$SYSTEM:RTEM.EXE on the VAX/VMS system) to reflect any new defaults. You can run the command file as often as needed after you install RTEM. To run the customization procedure on a VAX/VMS system, log onto the system manager's account, preferably on a hard-copy terminal. That lets you record the changes you make. Then start the procedure with the command: $ @SYS$SYSTEM:RTEM 3-3 CHAPTER 4 TECHNICAL INFORMATION TECHNICAL INFORMATION This chapter provides some technical information about RTEM for advanced users. DIGITAL does not support any monitors or device handlers on RTEM other than those included in your RTEM distribution kit. System generations targeted for RTEM are not supported. DISTRIBUTED MONITOR 4.1 DISTRIBUTED MONITOR The RTEMFB monitor supplied with RTEM is generated from the sources used for an RT-11 FB monitor. The difference is that RTEM uses its own bootstrap module which correctly initializes the RT-11 environment under the native system. RTEMFB.SYS SYSGEN CONDITIONAL FILE 4.2 RTEMFB.SYS SYSGEN CONDITIONAL FILE The following RT-11 system-generation conditional file was used to create the RT-11 FB monitor shipped with RTEM, RTEMFB.SYS. .SBTTL RTEM.CND RT-11 V05 SYSTEM CONDITIONAL FILE ;SYSGEN EDIT LEVEL = V05.30 ;+ ; ; THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY ONLY BE USED ; OR COPIED IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE. ; ; COPYRIGHT (c) 1984, 1985 BY DIGITAL EQUIPMENT CORPORATION. ; ALL RIGHTS RESERVED. SPC$PS = 1 ;Save/set main-line PC and PS support SCCA$G = 1 ;Global SCCA support MTT$Y = 1 ;Multiterminal support MAT$S = 1 ;Asynchronous terminal status 4-1 TECHNICAL INFORMATION TECHNICAL INFORMATION TTYOUT = 40. ;Size of the output buffers TTYIN = 134. ;Size of the input buffers U$CL = 1 ;User command linkage U$TIL = 1 ;Utility commands L$ANG = 1 ;Language commands M$INI = 1 ;Minimal commands CLOCK = 60. ;Power line frequency RTE$M = 1 ;RTEM-11 support STAR$T = 1 ;Startup command file FPU$11 = 1 ;Floating point support BATC$H = 1 ;Batch support DL11$L = 1. ;Number of local DL11 interfaces DL11$M = 0. ;Number of remote DL11-E lines DL11$N = 1. ;Total number of DL11 lines DLC$0 = 177560 ;Status register of first DL11 (Consol) DLV$0 = 60 ;Vector of first DL11 (Consol) DZ11$N = 0. ;Number of DZ11 or DZ11V multiplexers 4-2 CHAPTER 5 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) The native transfer utility (TRANSFER) runs on your VAX/VMS system and copies files from an RT-11 stand-alone processor to the native processor and from the native processor to the standalone. TRANSFER can copy files from Files-11 volumes to RT-11 volumes. It can also perform transfers in the other direction; that is, from files on RT-11 volumes to files on Files-11 volumes. Files-11 is the disk volume format maintained by the VAX/VMS operating system. You can use command qualifiers to specify the format of the transferred output file. The supported formats are: o ASCII o Binary o FORTRAN o Image You can also use command qualifiers that cause TRANSFER to: o Supply additional information during the transfer operation o Display HELP information o Operate in PROMPT mode, an interactive mode with questions and defaults o Send the output file to the native system printer This chapter: o Explains how to use TRANSFER (Section 5.1) 5-1 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) o Lists TRANSFER error messages (Section 5.2) USING TRANSFER 5.1 USING TRANSFER TRANSFER can copy files between a PDP-11 processor running RT-11 and a VAX processor running VAX/VMS. No intermediary (such as RTEM) is required. To use TRANSFER, use VTCOM to establish a connection between the RT-11 _____ ______ stand-alone processor and the native system. (See the RT-11 System _________ ______ Utilities Manual for complete information on using VTCOM.) You can use the TRANSFER utility only after you have established that connection. TRANSFER is run only from the native processor. Run the TRANSFER utility by executing the TRANSFER command in response to the native system's prompt. You can abort a file transfer at any time and return to the native system's prompt by typing , the preferred method of aborting file transfers on VAX/VMS systems. You can also abort file transfers on VAX/VMS systems by typing and then executing the EXIT command in response to the monitor prompt. You can exit from TRANSFER and return to the native system's prompt by typing in response to a TRANSFER prompt. TRANSFER Command Syntax 5.1.1 TRANSFER Command Syntax The TRANSFER command has the following syntax: TRANSFER input-filespec{/ASCII [:n]} [ output-filespec{/ASCII [:n]}] {/BINARY [:n]} {/BINARY [:n]} {/FORTRAN [:n]} {/FORTRAN [:n]} {/IMAGE [:n]} {/IMAGE [:n]} /LOG /LOG /PROGRESS[:n] /PROGRESS[:n] {/REMOTE } {/REMOTE } {/TERMINAL } {/TERMINAL } /STATISTICS /SPOOL /STATISTICS or TRANSFER {/HELP } {/PROMPT } {/VERSION} 5-2 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) or TRANSFER From: input-filespec[/qualifier[/qualifier...]] To: output-filespec[/qualifier[/qualifier...]] where: input-filespec is the input file specification of the file you want to copy. No wildcards are allowed. No VAX/VMS virtual device can be specified. The file specification is operating system dependent. Consult your operating system documentation for the correct construction of the file specification. output-filespec is the file specification of the file to which you want the file transferred. No wildcards are allowed. You cannot specify any native system record oriented device such as a line printer, terminal, or magtape device. The file specification is operating system dependent. Consult your operating system documentation for the correct construction of the file specification. [ ] indicates optional parameters. { } indicates mutually exclusive qualifiers (pick one). Those qualifiers are mutually exclusive on the input-filespec or output-filespec, and must appear only once in the command. There are two types of TRANSFER qualifiers. o Mode qualifiers (/ASCII, /BINARY, /FORTRAN, and /IMAGE) determine the format of the transferred file. o Control qualifiers affect transfer file processing by providing information, by invoking the interactive mode, or by queuing the output file to a printer. TRANSFER recognizes certain file types. If you do not specify a mode qualifier, TRANSFER performs the transfer in the default mode for the file type you specify. The recognized file types and their defaults are displayed on your terminal by using the /HELP qualifier: $ TRANSFER/HELP IMAGE mode is TRANSFER's default transfer mode. If you do not specify 5-3 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) the /ASCII, /BINARY, /FORTRAN, or /IMAGE qualifier, and if the file you specify does not have a recognized file type, TRANSFER performs the transfer operation in IMAGE mode. TRANSFER Mode Qualifiers 5.1.2 TRANSFER Mode Qualifiers TRANSFER has four mode qualifiers that specify each type of supported file format. Format conversions can be in either direction between Files-11 volumes and RT-11 volumes. Only one transfer mode qualifier can be specified in a command. /ASCII[:n] /ASCII[:n] The /ASCII qualifier formats the output file as ASCII. On an RT-11 output volume, the file contains ASCII data records, each terminated by a carriage return/line feed, escape, form feed, or vertical tab. TRANSFER removes rubouts, nulls, and vertical tabs from input records and adds carriage-return/line-feed pairs to the end of records that do not end with escape, form feed, or line feed. When the native input file record attributes does not specify carriage control, TRANSFER assumes embedded carriage control. Embedded carriage control means that each record contains the embedded control characters necessary for proper formatting. In that case, carriage return/line feed pairs are not appended to records. In transfers from RT-11 to Files-11 volumes, TRANSFER removes carriage return/line-feed pairs from the end of records. If you specify a size value (:n), TRANSFER generates fixed-length records of that size and pads them with nulls if required. If you omit the size value (or specify a size of 0), TRANSFER generates variable-length records. /BINARY[:n] /BINARY[:n] The /BINARY qualifier formats the output file as binary. TRANSFER adds formatted binary headers and checksums to records that it copies to RT-11 files, and removes binary headers and checksums from records that it copies to Files-11 files. When you transfer files to Files-11 volumes, TRANSFER generates fixed-length records of the size (:n) you specify. If you omit the size value (or specify a size of 0), TRANSFER generates variable-length records. /FORTRAN[:n] /FORTRAN[:n] 5-4 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) The /FORTRAN qualifier transfers files that contain FORTRAN carriage control characters. Use the /FORTRAN qualifier when the first character of each record will be interpreted as the carriage control specifier. The /FORTRAN qualifier does not alter any record data. Use this qualifier only when the output volume is a Files-11 volume. TRANSFER generates fixed-length records of the size (:n) you specify. If you omit the size value (or specify a size of o), TRANSFER generates variable-length records. /IMAGE[:n] /IMAGE[:n] The /IMAGE qualifier transfers files without performing any record translations on them. With this qualifier, TRANSFER copies the files exactly as they are. When you transfer files to Files-11 volumes, TRANSFER generates fixed-length records of the size (:n) you specify. If you omit the size value (or specify a size of 0), TRANSFER generates fixed-length records of 512 bytes. TRANSFER Control Qualifiers 5.1.3 TRANSFER Control Qualifiers TRANSFER provides nine qualifiers to control transfer processing. /HELP /HELP The /HELP qualifier displays limited information about TRANSFER. It lists default TRANSFER formats for various file types. /LOG /LOG The /LOG qualifier creates a log of the names of all files transferred. The log displays on your terminal a success message, the complete input and output filespecs, and the number of blocks or records transferred. For example: $ TRANSFER FOO.TXT/LOG FOO.TXT %TRANSFER-S-COPIED, USER:[RTINDEX]FOO.TXT;2 copied to __TTB0::DK:FOO.TXT (6 blocks) /PROGRESS[:n] /PROGRESS[:n] The /PROGRESS qualifier displays the progress of the transfer at specific intervals while the operation is taking place. The intervals are displayed as records or blocks, depending on the format of the 5-5 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) file and the direction of the transfer. You can specify the interval (:n). The default PROGRESS report interval is 10 (decimal) records or blocks. The /PROGRESS qualifier displays: o an informational message o the time-of-day o the blocks or records transferred during the interval o the number of retries o the packet size An increase in the number of retries or decrease in the packet size generally indicates interference on the transmission line. If the packet size decreases to an unacceptable level, retry the transfer operation when your transmission line has less interference. An example of the /PROGRESS qualifier: $ TRANSFER FOO.TXT/PROGRESS:1 FOO.TXT %TRANSFER-I-PROGRESS, 14:33:25 blocks transferred=1 retries=0 packet_size=512 %TRANSFER-I-PROGRESS, 14:33:27 blocks transferred=2 retries=0 packet_size=512 /PROMPT /PROMPT The /PROMPT qualifier displays questions, indicates defaults, and accepts input. The questions and defaults change dynamically, based on the responses to earlier questions. PROMPT mode shows a list of available responses in parentheses. The default response appears in angle brackets. To choose the default response, press the RETURN key. Choose the default unless you are sure that another qualifier is correct. The following are sample PROMPT mode sessions. The following example copies the ASCII file V5NOTE.TXT from the RT-11 stand-alone system to the native system, keeping the same file name. Defaults are taken for the file format (ASCII) and native file record length (variable). $ TRANSFER/PROMPT Original file is on (HOST,REMOTE) : remote Name of original REMOTE file to copy: v5note.txt Name of file to create on HOST : Create HOST file with (ASCII,BINARY,FORTRAN,IMAGE) records : Create HOST file with fixed-length records (YES,NO) : %TRANSFER-S-COPIED,__TTA2::DK:V5NOTE.TXT copied to USER:[RT11]V5NOTE.TXT;19 5-6 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) (714 records) There were 0 retries, with 3362 characters saved through compression encoding. The following example copies the file VDT.OBJ from the native system to an RT-11 stand-alone system, keeping the same file name. Because VDT.OBJ is a binary file, the default BINARY qualifier is chosen by pressing RETURN. $ TRANSFER/PROMPT Original file is on (HOST,REMOTE) : Name of original HOST file to copy: vdt.obj Name of file to create on REMOTE : Create REMOTE file with (ASCII,BINARY,FORTRAN,IMAGE) records : %TRANSFER-S-COPIED, USER:[WINNING]VDT.OBJ;1 copied to __TTA2::DK:VDT.OBJ (8 blocks) There were 0 retries, with 276 characters saved through compression encoding. The following example copies the image file (executable program) VTCOM.SAV from the RT-11 system to the native system, keeping the same file name. All defaults are taken. $ TRANSFER/PROMPT Original file is on (HOST,REMOTE) : remote Name of original REMOTE file to copy: vtcom.sav Name of file to create on HOST : Create HOST file with (ASCII,BINARY,FORTRAN,IMAGE) records : Create HOST file with fixed-length records of size (0-512) <512>: %TRANSFER-S-COPIED,__TTC2:DK:VTCOM.SAV copied to USER:[RT11]VTCOM.SAV;2 (24 blocks) There were 0 retries, with 5274 characters saved through compression encoding. /REMOTE or /TERMINAL /REMOTE or /TERMINAL The /REMOTE and /TERMINAL qualifiers tell TRANSFER which file is on the RT-11 system. /REMOTE and /TERMINAL are interchangeable; they have the same meaning. Do not specify both qualifiers in the same command. To transfer a file from the native system to the stand-alone RT-11 system, use /REMOTE or /TERMINAL on the output-filespec. That operation is the default, so you can omit the qualifier from the command for that type of transfer. To transfer a file from the stand-alone RT-11 system to the native system, use /REMOTE or /TERMINAL on the input-filespec. The following example transfers the file FOO.TXT from the native system to the stand-alone RT-11 system: $ TRANSFER FOO.TXT FOO.TXT 5-7 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) The following example transfers the file FOO.TXT from the stand-alone RT-11 system to the native system: $ TRANSFER FOO.TXT/TERMINAL FOO.TXT /SPOOL /SPOOL The /SPOOL qualifier queues the TRANSFER output file to the default VAX/VMS system printer queue. Specify the /SPOOL qualifier on the native output-filespec. That qualifier is available only for VAX/VMS system transfers. /STATISTICS /STATISTICS The /STATISTICS qualifier displays on your terminal the number of retries and the number of characters saved through compression encoding. (Compression encoding is a transfer speed enhancement used by TRANSFER whether or not you specify the /STATISTICS qualifier.) For example: $ TRANSFER FOO.TXT/STATISTICS FOO.TXT There were 0 retries, with 400 characters saved through compression encoding. /VERSION /VERSION The /VERSION qualifier displays the TRANSFER utility's version number. TRANSFER MESSAGES 5.2 TRANSFER MESSAGES This section describes the messages that can be returned by the TRANSFER utility. Message Format 5.2.1 Message Format The messages displayed by the TRANSFER utility have the following format: %FACILITY-L-IDENT, TEXT [-FACILITY-L-IDENT, TEXT] where: FACILITY is the TRANSFER utility or operating system facility or component name. A percent sign 5-8 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) (%) prefixes the first message issued, and a hyphen (-) prefixes each subsequent message. L is the severity level indicator. It has one of the following values: Code Meaning Code Meaning S Success I Information W Warning E Error F Fatal or severe error Consult your native operating system documentation for the meaning of each severity level. IDENT is the abbreviation of the message text; the messages in the next section are alphabetized by this abbreviation. TEXT is the explanation of the message. [-FACILITY-L-IDENT, TEXT] is the next message. Messages Returned by TRANSFER 5.2.2 Messages Returned by TRANSFER The following is an alphabetical listing of the messages that can be returned by TRANSFER. Included is an explanation of each message and the recommended action to be taken. Consult your native operating system documentation for messages not listed here. AMBIGQUAL, ambiguous qualifier in command Explanation: The command qualifier abbreviation contains too few characters to make it unique. Another qualifier begins with the same characters. User action: Retype the command, using at least the first four characters of the qualifier name. CHKSUMERR, binary record checksum error Explanation: The checksum for a BINARY record was in error. 5-9 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) User action: Make sure the input file is not an object library. Object libraries must be copied in IMAGE mode rather than BINARY mode. Make sure the input file is a valid binary file. Retry the transfer. CLOSEIN, error closing 'input-file' as input Explanation: RMS encountered an error while closing the input file. This message is usually accompanied by an RMS message indicating the reason for the failure. User action: Take corrective action based on the RMS message. CLOSEOUT, error closing 'output-file' as output Explanation: RMS encountered an error while closing the indicated output file. This message is usually accompanied by an RMS message indicating the reason for the failure. User action: Take corrective action based on the RMS message. CONFQUAL, conflicting qualifier in command Explanation: You specified qualifiers that are mutually exclusive. For example, you can specify only one TRANSFER mode qualifier (/ASCII, /BINARY, /FORTRAN, or /IMAGE) in a command. Also, you can specify /REMOTE or /TERMINAL on only one side of a command. User action: Correct the qualifiers and retry the operation. FILSYNTAXERR, error in file specification Explanation: Your specification of a file for the RT-11 system was invalid. For example, the file name contained more than six characters. User action: Correct the file specification for the RT-11 system. 5-10 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) ILLBINFORMAT, illegal binary record format Explanation: You attempted to transfer a file from the RT-11 system to the native system using the /BINARY qualifier. The file was not a binary file or was a binary file with a bad format. User action: Make sure the mode qualifier agrees with the file format. Retry the operation. INVCMDSYNTAX, invalid command syntax Explanation: The TRANSFER utility command was invalid. User action: Correct the syntax and reenter the command. INVINPUTQUAL, invalid input qualifier /'qualifier' Explanation: The indicated input qualifier is invalid in the command. User action: Correct the qualifier and reenter the command. INVQUAL, invalid qualifier /'qualifier' Explanation: The indicated qualifier is invalid in the command. User action: Correct the qualifier and reenter the command. INVQUALVAL, invalid value for /'qualifier' qualifier Explanation: You specified an invalid value for the indicated qualifier. User action: Check the range of values for that qualifier. Correct the value for the qualifier and reenter the command. NOVTCOM, VTCOM not running on remote Explanation: VTCOM is not running on your RT-11 stand-alone system, or the native system response time is slow due to heavy usage. TRANSFER timed out before receiving a 5-11 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) response from VTCOM. User action: Make sure VTCOM is running on the RT-11 system. Decrease the load on the native system or lower the baud rate between the RT-11 system and the native system. Retry the operation. OPENIN, error opening 'input-file' as input Explanation: The indicated input file cannot be opened. This message is usually accompanied by an RMS message indicating the reason for the failure. User action: Take corrective action based on the RMS message. OPENOUT, error opening 'output-file' as output Explanation: The indicated output file cannot be opened. This message is usually accompanied by an RMS message indicating the reason for the failure. User action: Take corrective action based on the RMS message. QUOTNOOUTPUT, quoted string specification as input needs output specification Explanation: You did not specify the output (RT-11 only) file when the input (RMS) file was a quoted string specification. User action: Specify the output file when the input file is a quoted string specification. READERR, error reading 'input-file' Explanation: The indicated input file cannot be read. This message is usually accompanied by an RMS message indicating the reason for the failure. User action: Take corrective action based on the RMS message. 5-12 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) REMABORT, file transfer aborted by remote Explanation: The file transfer was aborted due to an I/O error on the RT-11 system, or the VTCOM RESET command was issued. User action: Check the procedures listed in Section 2 of _____ ______ _______ ______ the RT-11 System Message Manual for recovery from hard-error conditions. REMACCESS, error accessing remote Explanation: A hard error occurred on the native system during a file transfer. User action: Retry the operation after performing hard error recovery procedures on the native system. REMCLOSEIN, error closing 'input-file' as input on remote Explanation: TRANSFER encountered an error while closing the indicated input file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. REMCLOSEOUT, error closing 'output-file' as output on remote Explanation: TRANSFER encountered an error while closing the indicated output file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. REMOPENIN, error opening 'input-file' as input on remote Explanation: TRANSFER cannot open the indicated input file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. 5-13 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) User action: Take corrective action based on the other message. REMOPENOUT, error opening 'output-file' as output on remote Explanation: TRANSFER cannot open the indicated output file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. REMREADERR, error reading 'input-file' on remote Explanation: TRANSFER cannot read the indicated input file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. REMTIMEOUT, remote timed out during file transfer Explanation: TRANSFER timed-out during a file transfer. User action: Make sure VTCOM is running. Retry the operation. REMWRITEERR, error writing 'output-file' on remote Explanation: TRANSFER encountered an error while writing the indicated output file on the RT-11 system. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. SENSEMODE, couldn't read terminal characteristics Explanation: TRANSFER could not read the terminal hardware characteristics required for a file transfer operation. 5-14 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) User action: Retry the operation after performing hard-error recovery procedures on the native system. SETMODE, couldn't write terminal characteristics Explanation: TRANSFER could not set the terminal hardware characteristics required for a file transfer operation. User action: Retry the operation after performing hard-error recovery procedures on the native system. TERMINIT, error initializing terminal for i/o Explanation: TRANSFER could not initialize the terminal hardware on the native system for a file transfer operation. User action: Retry the operation after performing hard-error recovery procedures on the native system. TOOBIG, record too large for file's i/o buffer Explanation: You attempted to transfer a Files-11 record that was too large for TRANSFER's file buffer. User action: Make sure you are transferring a file in the correct mode, or transfer the file in IMAGE mode. TOOLONG, 'nn' byte record exceeds output file's maximum record length Explanation: You specified an output record length that was too small to hold the largest record from the RT-11 file. User action: Specify a record length large enough to hold the largest record from the RT-11 file, or transfer the file using variable-length records. USERABORT, file transfer aborted by user 5-15 NATIVE TRANSFER UTILITY (TRANSFER) NATIVE TRANSFER UTILITY (TRANSFER) Explanation: You aborted the file transfer by typing , or an I/O error occurred in the native system. User action: If an I/O error occurred, perform hard-error recovery procedures on the native system. Retry the operation. WRITEERR, error writing 'output-file' Explanation: RMS encountered an error while writing the indicated output file. This message is usually accompanied by another message indicating the reason for the failure. User action: Take corrective action based on the other message. 5-16