Exit from RTEM-II using JOAT /E. Invoke RTEM-II again and retry the operation. If the error persists, obtain a new copy of FIP.SAV and the device handler specified in the error message. Retry the operation. If the error recurs, submit an SPR to DIGITAL. Include a description of the hardware configuration, the version number of your host operating system, and the version numbers of RTEM-II and FIP.
?FIP-F-File not found dev:filename.typ
The input file specified was not found, or no input files with the expected name or type were found when a wildcard was defined.
Check for a typing error in the command line, verify that the file exists as entered in the command line, and try the operation again.
?FIP-F-Insufficient memory
Memory overflow occurred, caused by too many device and/or file specifications (usually in wildcard operations) •
Try copying the files one at a time without using wildcards.
?FIP-F-Invalid command
The command line is incorrect. An option that is not compatible with the command may have been used.
Check for a typing error. Verify that the format and syntax are correct and try the operation again.
?FIP-F-Invalid device dey:
An invalid or nonexistent device was specified.
Check for a typing error in the command line. Verify that the device indicated is loaded in the device drive.
?FIP-F-Invalid directory
The specified device does not contain a valid directory.
Make sure the device is a valid input or output device and contains a valid directory. Try to transfer the files again.
?FIP-F-Invalid option
An invalid option was used in the command line.
Check for a typing error in the command line. Use only those options listed as valid for FIP.
~FIP-F-Invalid use of wildcards dev:filename.typ
The output file specification contained embedded wildcards (* or %) as in A*B.MAC and A%B.MAC.
Correct any errors in the use of wildcards. RT-II rules apply in the use of wildcards.
?PIP-P-Ro LUM available
In a transfer to or from a Files-II device, no logical unit number (LUN) was available.
T.o free a LUN for the current operation, use JOAT to detach a device that was previously attached with JOAT.
?PIP~P-Output error dev:filnam.typ
1. An unrecoverable error occurred while FIP was transferring a file.
Check the procedures for recovery from hard error conditions described in the RT-ll System Message Manual.
2. There was not enough room on the device to transfer the specified file. In a multiple file operation, execution was successful on files preceding the one interrupted by the error.
In a transfer to RTEM-ll, squeeze the device. In a transfer to the host operating system, delete files to create more storage space.
?FIP-P-Output file full dev:filnam.typ
The output file was too small to receive the input file.
Make sure there is enough space on the output device to receive the file. Try to transfer the file again.
?FIP-P-Protected file already exists
FIP tried to create an RTEM-II output file with a name already associated with an existing protected file. No new file is created.
Use the monitor RENAME/NOPROTECT command or the PIP /Z option to change the protection status of the existing file, or use a different name to create the new file.
?PIP-P-System error
An attempt was made to use a device not on the system, or a serious error occurred.
Make sure the device you want to use is loaded. Check the directory of the relevant device to ensure that the necessary system programs are intact. Exit from RTEM-ll, invoke it again, and try the operation again.
?FIP-P-Too many output files
More than one output file was specified in the command line.
Limit the number of output files on the command line to one.
?FIP-P-Wrong version of RTEM-ll
FILE INTERCHANGE PROGRAM (FIP)
Exit from RTEM-II, invoke it again, and try the operation again. Do not attempt to run FIP under monitors not distributed in the RTEM-li kit.
?FIP-I-Output file not superseded dev:filename.typ
A file of the same name as specified resides on the output vol~e.
FIP /N was used to prevent copying files of the same name (and version for Files-II output).
This is an informational message.
?FIP-W-File created: protected file already exists dev:filnam.typ A protected RTEM-ll file exists along with a newly created unprotected
file of the same name.
List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, delete or rename it. If the protected file appears first, rename it or change the protection code with the PIP /Z option or the monitor RENAME/NOPROTECT command.
?FIP-W-Library file not copied dev:filnam.typ
An OBJ library is an input file in a FIP /8 transfer command. The file name is shown in the message. The transfer is not completed.
Do not use the /8 option to copy OBJ libraries. Use the /QUERY or PIP /Q option to selectively copy files, and type NO for each OBJ library.
?FIP-W-No .SYS action
The /Y option was not included in a command aimed at implicitly copying files of type .SYS. A wildcard transfer will most likely cause this message. The command is executed for all files but those of the .SYS file type.
Use /Y to implicitly copy files of type .SYS.
CHAPTER 6
MODIFYING THE VIRTUAL SYSTEM DEVICE
This chapter tells host system managers how to add and delete files in the shared area of the virtual system device.
You can modify the virtual system device to include RT-ll utility programs and any other files RTEM-ll users may want to share. You can select specific files to copy from your RT-ll distribution kit to the shared area or create a shared area from the entire volume.
The directory for the shared area of the virtual system device is expandable to accommodate additional system programs. This chapter shows how to make additional utilities, libraries, and data files available to all RTEM-ll users by copying new files to the shared area and extending it if necessary.
To reserve space for future expansion in the shared area of the virtual system device, the directory contains directory fillers.
Directory fillers are unique to RTEM-ll and are removed to convert a shared area to a private area. The basic difference between a shared and private area is the presence of directory fillers in the former.
For an overview of the virtual system device, see Section 2.2.
Section 6.1 summarizes the procedure for modifying the shared area of the virtual system device. Section 6.2 provides an example that illustrates this procedure.
6.1 MODIFICATION PROCEDURE
This section summarizes the steps required to create a shared area or to add, delete, or modify files that reside in an existing shared area of the virtual system device.
To create or modify a shared area, work from a privileged account but not from the account in which the shared file will reside. The default location for the shared file is LB:[l,l]RTllSH.DSK on an RSX-ll system or SYS$LIBRARY:RTllSH.DSK on a VAX/VMS system.
6.1.1 Establish Shared Area as a Temporary File
First, copy the shared area to a temporary file. You can modify this copy while the original shared area serves as part of the virtual system device.
$ COpy LB:[l,l]RTllSH.DSK output-filename.TMP