|o||The capacity in bytes of the tape in the device.|
|o||The size in bytes of the end-of-file (EOF) marks (often referred to simply as filemarks) that the tape device writes.|
If the fms.log file does not already exist in the current working directory, the fms command interpreter creates it. In this case, the directorys mode bits must grant the rwx (read, write, and execute) permissions to the issuer of the command. If there is an existing file, the command interpreter overwrites it, so the files mode bits need to grant only the w permission to the issuer of the fms command. The fms command interpreter also writes similar information to the standard output stream as it runs.
The file is in ASCII format. To display its contents, log onto the client machine and use a text editor or a file display command such as the UNIX cat command. By default, the mode bits on the fms.log file grant the required r permission only to the owner (which is the local superuser root by default).
The first few lines of the file provide a simple trace of the fms command interpreters actions, specifying (for example) how many blocks it wrote on the tape. The final two lines in the file specify tape capacity and filemark size in bytes, using the following format:
Tape capacity is <tape_size> bytes File marks are <filemark_size> bytes
The following example of the fms.log file specifies that the tape used during the execution of the fms command had a capacity of 2,136,604,672 bytes, and that the tape device writes filemarks of size 1,910,220 bytes.
fms test started wrote 130408 blocks Tape capacity is 2136604672 bytes File marks are 1910220 bytes
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.