The COPY command transfers files from the OpenVMS volume to the FAT volume, or from the FAT volume to the OpenVMS volume. When executing a group of commands as part of a command procedure, the /ERROR quaifier makes it possible to detect the failure to copy a file by terminating EFI$CP execution with a valid status and with DCL symbols containing the source and target filenames. No file format or record conversions are performed. Wildcards are not permitted. EFI$CP supports binary files (generally fixed length 512-byte records) and stream files. It does block binary transfers for all file types and does not do record IO. It preserves the end- of-file markers when possible. In general, files types created by FTP from a UNIX or DOS/Windows system to VMS are the types suitable for EFI$CP. OpenVMS executables and binary firmware files work as expected. When transfering from FAT to RMS the default file format will be fixed length 512-byte records. Use the /ASCII command to set the attributes to STREAM_LF and the /TEXT command to set the attributes to STREAM. The switches are not useful when transfering from RMS to a FAT volume. There are basic checks for the the file organization made when copying files from OpenVMS onto the FAT volume, and files that are likely incompatible with typical FAT tools can trigger an INCOMPATFAT error such as the following: copy sys$login:login.com bar:\efi\ %EFI-W-INCOMPATFAT, record organization or file structure not supported by FAT Incompatible files will still be copied, however applications reading the files will have no means of knowing how to treat the contents. When copied back out to an RMS file they will not have the correct file or record attributes and may also be unusable. The most frequent error of this type is copying an OpenVMS text file with the standard variable length records. Use the OpenVMS CONVERT command to convert the files before using EFI$CP.