This appendix lists and describes the system messages, error or informative, that you may encounter while you are working with Tape Management Facility (TMF). These system messages are found in either the tape.msg file or your standard output file. For system messages indicating that a TMF error has occurred, contact your system administrator. For internal problems, contact your system support staff.
Each message description is followed by a label that signifies the message recipient. The following labels are used with TMF system messages:
| USER | Individual (end user) using TMF to manage tapes | |
| ADM | TMF administrator | |
| USER/ADM | Individual (end user) or TMF administrator |
TM000 - Tape resource(s) have been reserved for you
Tape resources have been reserved for you by means of the tmrsv(1) command. - USER
TM001 - Unable to open pipe_desc pipe pathname (errno = errno)
TMF was unable to open the pathname pipe; the error returned is errno. This message may indicate that TMF is not running. - ADM
TM002 - Unable to write to path_desc pathname (errno = errno)
A write(2) request to a file or pipe of type, path_desc, the pathname path name failed; the error returned is errno. - ADM
TM003 - Resource group_name is not available
The requested number of resources, belonging to the group_name resource group, are not available. - USER
TM004 - The group_name resource count, count, is invalid
The amount count of available resources of the group_name type, which is maintained by TMF, is invalid. This indicates an error in TMF. - ADM
TM005 - Exceeded the limit on the number of tape devices which can be specified, limit
The number of devices specified in the tmrls(1) command exceeds the maximum, limit, allowed. - USER
TM006 - An invalid request was sent to the Tape Management Facility
An invalid request was made to the Tape Management Facility. This indicates an error in TMF. - ADM
TM007 - The specified device does not support volume partitioning.
A partition number was specified on a command issued for a device which does not support volume partitions. Reissue the command without the partition number or issue the command to a device supporting partitions. - USER
TM008 - Should volume vsn on device device switch from label_type1 to label_type2 for user userid? reply y/n
The administrator must specify whether the tape named vsn on device may be switched from label_type1 to label_type2 for user userid. The administrator replies y for “yes” or n for “no”. - USER/ADM
TM009 - Unable to clear the abnormal status flag in the TMF driver (errno = errno)
A TMF stream process was unable to acknowledge an error detected by the TMF driver. - ADM
TM010 - Exceeded the limit of group_name resources which may be used
The use of the group_name resource was requested with the tmmnt(1) command, but the request was denied because the user is at the user's limit for resources of this type. The limit was established with the tmrsv(1) command, and you can obtain the current status with the tmrst(1) command. - USER
TM011 - Enter the VSN for the volume mounted on device device_name
You must specify the volume identifier of the volume on the device_name device . - ADM
TM012 - Unable to obtain memory for variable
TMF could not acquire memory for the variable variable. This indicates an error in the TMF. When this message is issued, TMF will exit. The administrator should collect the trace files for examination by software product support. - ADM
TM013 - Volume vsn on device device name has not expired. Reply y/n for user userid to write on tape
You must specify whether user userid may write on unexpired tape vsn. Reply y for “yes” or n for “no”. - ADM
TM014 - Unable to give you ownership of path pathname (errno = errno)
TMF issued a chown(2) command for the pathname path, and the errno error was received. - ADM
TM015 - Unable to obtain a reply to the request request (errno = errno)
A TMF command was unable to obtain a reply to the TMF request request; the errno error was received. This indicates an error in TMF. - USER
TM016 - The write to type pathname failed after writing only m bytes of the requested n bytes.
A write(2) request to a file or pipe described by type to the pathname path did not write all of the requested bytes. Only m bytes of the requested n bytes were written. - ADM
TM017 - The option specified, string, cannot exceed count characters.
The number of characters in string is larger than count and is the value of the option option. - USER
TM018 - Option option cannot be specified more than once
The option option is duplicated on your command line. - USER
TM019 - Volume remounts because an incorrect volume was mounted are not supported for volumes in an autoloader domain
An incorrect volume was mounted by an library. Recovery from this error is not attempted for volumes serviced by an library. - USER
TM020 - A file sequence number cannot be specified for scratch mount requests
A file sequence number cannot be specified with the -q option of the tmmnt(1) command if a volume was not also specified. - USER
TM021 - Exceeded the maximum number of volumes allowed, maxvsn
The number of volume identifiers in the volume identifier list is greater than maxvsn. Use fewer volume identifiers. - USER
TM022 - Options option1 and option2 are mutually exclusive
Options option1 and option2 are mutually exclusive. You may use only one of them. - USER
TM023 - A path name must be specified
Specify the path name by using the -p or -P option on the tmmnt(1) command line or as an argument to the tmcatalog(1) request. - USER
TM024 - Unable to create desc_path|filename (errno = errno)
TMF was unable to create either a file, directory, or process described by desc_path|filename. If the file was specified with a command option, check to see whether you have the correct permissions for creating the file. - USER/ADM
TM025 - Cannot reserve resources if resources are still held from a previous reservation request
You have issued a tmrsv(1) command, but you must release all previously reserved resources by using the tmrls(1) command. - USER
TM026 - Unable to communicate with TMF daemon
A command or child process was unable to communicate with the TMF daemon. This indicates an error in TMF. - USER/ADM
TM027 - The expiration date specified, date, must be of the format [c|@]yyddd
The expiration date specified is invalid. It must be of the format [c|@]yyddd. - USER
TM028 - The request to mount volume volume was canceled
The administrator canceled your mount request for volume vsn. - USER
TM029 - All tape resources have been released
TMF has released all tape reservations held by the user. - USER
TM030 - The file sequence number must be numeric or the character n or u
The file sequence number specified is invalid. It must be numeric or n to indicate that a new file should be created at the end of the tape, or u to indicate file positioning should be based on a file name. - USER
TM031 - Cannot write to volume volume, file path_name, because the volume was requested with write protection enabled
You requested the -r out option on the tmmnt(1) command and issued a write operation to the path_name file, but the volume mounted is write protected. - USER
TM032 - The file status specified must be new when requesting a file be created at the end of tape
You requested that a file be created at the end of tape by specifying the -q option with value n on the tmmnt(1) command, but you did not specify that the file is new with the -n option. - USER
TM033 - Unable to lock desc file pathname (errno = errno)
TMF was unable to lock the pathname file, used to communicate information between a TMF process and the TMF daemon. The error returned was errno. This indicates an error in TMF. - ADM
TM034 - Waiting for a device from group device_group_name
A device from the device_group_name group was requested with the tmmnt(1) command, but it was not available. TMF has queued the request and will assign a device from the device_group_name group as soon as one is available. - USER
TM036 - The volume offset cannot exceed the number of volumes.
The value specified on the offset option is larger than the number of volume identifiers in the volume identifier list. - USER
TM037 - The specified user does not have tape resources reserved
The user specified on a forced resource release request does not have any tape resources reserved. - USER
TM038 - Unable to send the request request to the TMF daemon
The TMF command is unable to send the request request to TMF. This may indicate that the TMF is not running. - USER
TM039 - Path pathname is already in use by TMF
Another tape file called pathname is being used by either you or another user. - USER
TM040 - Unable to unload volume volume (errno = errno)
A TMF command was unable to unload the volume volume. The errno error was returned on the unload request. - USER
TM041 - Unable to send an action message to the message daemon
TMF cannot communicate with the message daemon. - ADM
TM042 - Unable to find a stream owned by process pid
The TMF daemon received a request from a child process for the stream owned by the pid process. However, TMF was not able to find a stream owned by this process. This indicates an error with TMF. - ADM
TM043 - The option specified, value, is invalid
The value of value is invalid for the option option. - USER
TM044 - Unable to open tape the device device (errno = errno)
TMF is unable to open the tape device device. - USER
TM045 - Unable to terminate the process_type process name, pid pid (errno = errno)
TMF was unable to terminate one of its child processes. The errno error was received when attempting to terminate the name process, which has the process identifier, pid.
TM046 - Mount volume vsn (label_type) ring_option on device device_name for userid (session) NQSid reason or reply cancel / device name
The administrator must mount the tape with the vsn volume identifier, a label of label_type, write ring in or out, on the device_name device, for userid user with session of NQSid. An optional reason may be given. The administrator may mount the tape on the specified drive, reply with a different device name, or reply cancel. If the administrator replies cancel, the tape mount is canceled and the user cannot continue with the tape processing. - USER/ADM
TM047 - Remount volume vsn (label_type) ring_option on device device_name for userid (session) NQSid reason or reply cancel / device name
The administrator must remount the tape with the vsn volume identifier, a label of label_type, write ring in or out, on the device_name device , for userid user with session of NQSid. An optional reason may be given. The administrator may remount the tape on the specified drive, reply with a different device name, or reply cancel. If the administrator replies cancel, the tape remount is canceled and the user cannot continue with the tape processing. - USER/ADM
TM048 - Tape stream pathname assigned or reassigned to device_name
The pathname file is assigned or reassigned to device_name. - USER/ADM
TM049 - pathname : vsn(label_type) : state : blocks = number
number blocks were read or written to the pathname file with vsn and label_type when at the state state. - USER
TM050 - Tape device device_name has been released
The device_name tape name has been released. - USER
TM051 - Cannot request file positioning based on a file name with non-labeled tapes
File positioning based on a file name uses the file name found in the tape label to position the tape. It cannot, therefore, be requested with nonlabeled tapes. - USER
TM052 - The TMF block count, number1, does not match the label block count, number2, for file pathname
The block count for a file, calculated by TMF, number1, does not match the block count recorded in the tape label for this file, pathname. This indicates an error in TMF. - USER
TM053 - An unexpected signal, signal signo, was received by process process
The process process received an unexpected signal (signal number signo). This indicates an error in TMF. - ADM
TM054 - Device device name has not been configured in the Tape Management Facility
An invalid device name was specified on a TMF command. - USER
TM055 - An invalid device group name, group, was specified
An invalid device group name was specified on a TMF command. - USER
TM056 - Tape resource group has not been reserved
Either the device group name on the tmmnt(1) command does not match the device group name you used on the tmrsv(1) command, or you have not issued a tmrsv(1) command. - USER
TM057 - The path name specified for release, pathname, is not associated with a tape resource
pathname, which was used in the tmrls(1) command, was not mounted with a tmmnt(1) command. - USER
TM058 - Command command was interrupted by signal signo
The command (tmrsv(1) or tmmnt(1)) command has been interrupted by the signo signal. - USER
TM059 - Permission to write to volume vsn was denied
Permission to write to the vsn volume was denied by the front end. - USER
TM060 - Waiting for device device_name
The device_name device , which was requested with the tmmnt(1) command, was not available. TMF has queued the request and will assign the device as soon as it becomes available. - USER
TM061 - Permission to update directory dir is denied
You cannot update the dir directory because you do not have write permission in the directory. - USER
TM062 - File pathname on volume, vsn, is protected
The pathname file found on the vsn volume is volume protected. See the system administrator. - USER
TM063 - File pathname on volume vsn is not of the requested label type label_type
The pathname file found on the vsn volume has an incorrect label type. Check your tape. - USER
TM064 - File filename could not be found on volume vsn
The vsn volume identifier does not contain the specified file, filename. Check your tape. - USER
TM065 - File filename on volume vsn has not expired
The vsn volume identifier does not contain the specified file, filename, in an expired state. - USER
TM066 - A volume must be mounted on the specified device
The device specified with the TMF tmlabel(8) command must have a volume mounted. - ADM
TM067 - A tape volume must be specified for file filename
There is no VSN list for the filename file. - USER
TM068 - Cannot request user label processing when creating a new file or appending to an existing file
User label processing is only valid when accessing old files. - USER.
TM069 - An invalid request, request, was received from the TMF driver
An invalid request was received from the driver. This indicates an error in TMF. - ADM
TM070 - Unable to complete the request request issued to device device (errno = errno)
The errno error was encountered when performing the request request on the device device. - USER
TM071 - Unable to complete the request request issued to device device for file pathname (errno = errno)
The errno error was encountered when performing the request request on the device device for the pathname file. - USER
TM075 - Cannot allow user label processing on a volume which is not write protected
User label processing is valid only on write protected volumes. - USER
TM076 - An invalid label structure was detected on file filename on volume vsn
The vsn volume containing the filename file has an invalid label structure. - USER
TM077 - A user and session identifier must be specified
A user and session identifier must be specified on the tmfrls(1) command. - USER
TM078 - The Tape Management Facility is not available
The TMF daemon is stopped. Either a tmstop(8) command has been issued, or an error has occurred. - USER/ADM
TM079 - An invalid reply was received from the loader daemon
The reply to a loader request is invalid. TMF processing for this user will be terminated. - USER
TM080 - The message request failed because this message type is not supported by the front-end
A message request sent to a front end was not accepted because the front end does not support messages of this type. - USER
TM081 - The file sequence number specified, number, for file filename, exceeds the number of files on the specified volume set
The file indicated by the number file sequence number is not on the tape. - USER
TM082 - The default tape resource, resource, has not been reserved
A request was made with the tmmnt(1) command to mount a volume on a device belonging to the default resource group. The request failed because the default tape resource, resource, had not been reserved with the tmrsv(1) command. - USER
TM083 - An invalid request, code, was received from a TMF child process
The code request code is invalid. This indicates an error in TMF. - ADM
TM084 - Tape Management Facility internal error
TMF returned an error indicating an internal TMF error. - USER/ADM
TM085 - The specified volume does not exist in the volume identifier list for this stream
The volume identifier specified in a TMF request could not be found in the volume identifier list specified on the tmmnt(1) command for this stream. - USER
TM086 - Error error was encountered by the Tape Management Facility
TMF returned the error error. - USER
TM087 - An invalid range, value1-value2, was specified
The range specified is incorrect. value1 exceeds value2. - ADM
TM088 - The path name specified, pathname, already exists
You specified pathname on the tmmnt(1) command by using the -p option, and pathname exists. The -p option of the tmmnt(1) command does not delete the pathname file if it exists. You can either delete the pathname file or use the -P option. - USER
TM089 - Directory pathname was specified for the desc when a file name was expected
You specified pathname on the TMF command rather than the expected file name; pathname is a directory. - USER
TM090 - Because the environment variable, variable, is not set, the current working directory will be used instead for the file_type
It was requested that the variable environment variable be used by TMF command, but it is not set up correctly. - USER
TM091 - The path name of the desc cannot exceed number characters.
The path name specified is larger than the maximum of number characters accepted by TMF. See the system administrator. - USER
TM092 - Unable to get the current working directory (errno = errno)
TMF cannot get your current working directory. The errno is errno. - USER
TM093 - The desc specified must be either 'on' or 'off'
The state specified for desc must be either on or off. - ADM
TM094 - Waiting for another request to complete
The tmmnt(1) command was postponed to finish another request. - USER
TM095 - The limit on the number of tape users has been reached.
The maximum number of tape users was exceeded. - USER
TM096 - The label type specified on multifile volume mount requests must match the type specified on previous mount requests for the volume
The label type specified on a multifile volume mount request is incorrect. It must be identical to the type specified on the previous multifile volume mount requests. - USER
TM097 - The following tape users are deadlocked
The following users are deadlocked during device allocation. - ADM
TM098 - Waiting for device device to avoid a possible deadlock
Assigning the device device could lead to a possible system deadlock; therefore, allocation is delayed. - USER
TM099 - The tape stream open request specifies a file unknown to the TMF daemon
The tape stream path name was not known to TMF when it processed the request code sent by the user. - USER
TM100 - The write of the request_type request to file type pathname failed after writing only number1 bytes of the requested number2 bytes
The pathname file is used to communicate a request of the request_type type to a front end. TMF was unable to write the request to this temporary file. number1 bytes were written instead of the expected number2 bytes. - USER
TM101 - A device release is pending
When TMF was processing a release request, the device could not be released immediately. It will be released as soon as possible. - USER
TM102 - Waiting for a resource release to complete
TMF received your reserve request and is waiting for the release of devices from a previous release request. TMF delays the processing of your reserve request until all pending releases are completed. - USER
TM103 - Cannot mount a bypass label tape with the ring out
TMF is installed with the option that ring out must be used when the blp label type is used. - USER
TM104 - Operator replied : reply_string
The operator replied reply_string to an operator message about your tape. - USER
TM105 - Cannot send the request_type request because front-end fes is not logged on
The request_type request, sent to the fes front end could not be processed because the fes front end is not logged on. - USER
TM106 - The request_type request failed because the request was created incorrectly
An error was returned by the front end for the request_type request because TMF created the request incorrectly. - USER
TM107 - Unable to create a Tape Management Facility daemon (errno = errno)
TMF could not be brought up successfully because a new session for TMF could not be created. - ADM
TM108 - The request_type request failed because of an unknown condition error
The request_type request, which was sent to a front end, failed because of the error error. - USER
TM110 - Unable to register for signal signo (errno = errno)
Registration for the signo signal could not be completed; the error returned is errno. - ADM
TM111 - Permission to write filemarks denied
You attempted to read or write a filemark without using the -T option of the tmmnt(1) command. - USER
TM112 - Option option1 requires option option2
You must specify option2 along with option1 on the TMF command. - USER
TM113 - A label label was not found for file pathname, on volume vsn
Your pathname tape file either does not have a valid label label or is missing this label for vsn. - USER
TM114 - Device device is already in use
The device specified on the TMF command is already in use. - USER
TM115 - User end-of-volume processing has been action for tape file pathname
This informational message is sent to your tape.msg file. action can be set to selected on or deselected off for pathname during a TR_EOV request. - USER
TM116 - Unable to set the block size for label I/O (errno = errno)
TMF is unable to label a tape volume because it cannot set the block size to the label size; the error received is errno. - USER
TM117 - Permission to (re)catalog file filename was denied from the front end
The servicing front end did not allow you to catalog or recatalog the filename file. - USER
TM118 - Permission to delete file filename from the front-end catalog was denied by the front-end.
The servicing front end did not allow you to delete the filename file from the front-end catalog. - USER
TM119 - A request to position to a specific volume must specify a volume name
TMF user request, TR_PVSN, did not include a volume name. - USER
TM120 - The storage server was unable to complete the request_type request
The storage server encountered an error while attempting to complete the request_type request. - USER
TM121 - The record format specified must be one of the characters F, D, U, or V
The record format specified with the -F option of the tmmnt(1) command is invalid. It must be one of the characters, F, D, U, or V. - USER
TM122 - Stream pathname is busy
The stream specified for release with the -R option of the tmmnt(1) command cannot be released because the stream file is open. - USER
TM123 - Cannot request an unload of an assigned device, device
You requested an unload of the device device with the tmunld(8) command. Your request failed because the device is assigned to a user. - USER
TM124 - The request_type request failed because the station logged off
The request, request_type, sent to a front end failed because the station logged off while processing the request. - USER
TM125 - Cannot issue an request_type request to a downed device, device
You requested an unload of the device device with the tmunld(8) command. The request failed because the device is not configured up. - USER
TM126 - Cannot modify feature mode, feature in use
You attempted to use the tmset(1) command to modify a device feature. The request failed because the device is assigned. - USER
TM128 - The request_type failed because station message processing is not enabled
The request_type request sent to a front end, failed because station message processing is not enabled. - USER
TM129 - An invalid TMF request, request was issued for file pathname
You issued an invalid request, request, to TMF with the TMFC_DMNREQ ioctl system call for the pathname file. Check the /usr/include/tmf/sys/tmfctl.h include file for a list of valid requests. - USER
TM130 - File pathname is new and cannot, therefore, be read
You issued a read(2) request to a file, pathname, which was accessed as new on the tmmnt(1) command. - USER
TM131 - Unable to send request request_type: error reason
TMF received an error when it tried to send a station message to a servicing front end. reason was received as the reason for the error. - USER
TM132 - Permission to access file file_id denied by front-end feid
The servicing front end, feid, denied access to the file_id file. - USER
TM133 - The request_type request cannot be issued to a front-end which is not secure
The servicing front end is not secure. - USER
TM134 - File file_id cannot be cataloged because it already exists in the catalog
The servicing front end returned an error because file id was specified as a new file, and it already exists in the catalog. - USER
TM135 - File file_id does not exist in the catalog
The servicing front end returned an error because file_id was specified as an existing file and it does not exist in the catalog. - USER
TM136 - The data attribute specified must be one of the characters B, S, or R
The data attribute portion of the record format field specified with the -F option of the tmmnt(1) command is invalid. It must be one of the following characters: B, S, or R - USER
TM137 - Unable to update file file_id in the front-end catalog
The servicing front end returned an error because the catalog update failed. - USER
TM138 - Access to volume volume was denied
The servicing front end denied access to the volume volume. - USER
TM139 - The requested volume, volume, is not in the volume catalog
The servicing front end returned an error because the volume volume does not exist in the volume catalog. - USER
TM140 - Unable to update volume volume in the volume catalog
The servicing front end returned an error because the volume catalog update failed. - USER
TM141 - Unable to create the front-end message requesting a request_type
An error occurred during an attempt to build a station message. Contact your system support staff - USER/ADM
TM142 - An invalid station message type, request_type, was specified
This is an invalid station message type. Contact your system support staff. - USER/ADM
TM143 - The size of the station message specified, size, differs from the size of the data written to the station message file
The text of this station message is not of the size expected. Contact your system support staff. - USER/ADM
TM144 - Unable to read the station message reply header (errno = errno)
An error occurred while a station message reply was read from a front-end. Contact your system support staff. - ADM
TM145 - Unable to read from desc pipe pathname (errno = errno)
TMF was unable to read data from the pathname pipe; the error returned is errno. - ADM
TM146 - The size of the type read, bytes read bytes, differs from the expected size of bytes bytes
A read(2) operation returned a count different from that expected. - USER
TM147 - The identifier specified for the front-end request, id, is invalid
Front-end identifierid is invalid. - USER
TM148 - Unable to send a request to the front-end
An error occurred during an attempt to send a station message. - USER
TM149 - The request was rejected by the front-end
The servicing front end rejected your request. - USER
TM150 - The station message reply does not include the required table table
Required table, table, is missing from a station message reply. Contact your system support staff. - USER/ADM
TM151 - A catalog request cannot be issued when front-end servicing is disabled
Front-end servicing is turned off. - USER
TM152 - The last device within a range of devices was not specified
The format of the device range is invalid. An upper range is required. - ADM
TM153 - The no unload option can only be specified when configuring a device up
You specified the no-unload option on a request to configure a device down. - ADM
TM154 - A device configuration request must specify the device name(s) and state
An invalid device configuration request was issued. The device configuration request requires a device name and state. - ADM
TM155 - The front-end did not reply to the request_type request
Timed out while waiting for a reply from the servicing front end. - USER
TM156 - Front-end, feid, configured for the request_type request, is not enabled for station messages
The specified servicing front end does not accept type 3 station messages. - USER
TM157 - The specified path, pathname, must be closed when issuing a catalog request
The tmcatalog(1) command can be used only when the file is closed. - USER
TM158 - Unable to send message for user job_id, NQSid to front-end target_id(reason). Reply cancel or retry
The message message to server or front-end identifier cannot be sent for user because reason. - ADM
TM159 - Option -option cannot be specified when front-end servicing is disabled.
Front-end servicing must be enabled before requesting a front-end operation with the -option option. - USER
TM160 - User volume vsn closed
The vsn volume identifier was closed. - USER
TM161 - Unable to open desc file filename (errno = errno)
The filename file, could not be opened; the error returned is errno. Check to see if this file exists or whether you have the correct permissions for opening the filename file. - USER/ADM
TM162 - Extra parameters were specified at the end of command, string
Extra characters (string) were specified in the TMF command. - USER
TM163 - program_name (pid process_id): server server_name: error_text. Reply retry or cancel
program_name encountered a problem communicating with the server_name server on behalf of one or more requests. The problem is described in error_text. A reply of cancel aborts all requests that have encountered this problem. A reply of retry requeues all requests that encountered this problem and allocates more time for these requests to wait for the communication with the server_name server. - ADM
TM164 - Unable to read type file filename (errno = errno)
An error occurred when attempting to read the filename file; the error returned is errno. Check to see if this file exists or whether you have the correct permissions for reading the filename file. - USER/ADM
TM165 - Either a loader status or a device list must be specified with option -m
An invalid loader configuration request was issued via the tmconfig(8) command. When you specify the -m option, you must also specify a loader status or a device list or range. - ADM
TM166 - An invalid loader daemon request was created
TMF did not correctly create a loader daemon request. - USER
TM167 - The ring status specified, status, must be either 'in' or 'out'
An invalid ring status, status, was specified with the -r option of the tmmnt(1) command. The status must be in or out. - USER
TM168 - The function code specified on a loader daemon request, code, is not supported
TMF created a loader daemon request incorrectly. The loader function specified, code, is not supported. - USER
TM169 - Unable to change the owner and group of file_type pathname (errno = errno)
TMF was unable to change the owner or group of the pathname file; the error returned is errno. - ADM
TM170 - File pathname must be closed because of an unrecoverable error (errno = errno)
The user received an error on a tape request. No further requests will be accepted except for a close request. Close and reopen the tape file. - USER
TM171 - User reads and writes of file marks cannot be performed on single tape mark format tape
Single filemark format tapes are not allowed with the -T option. - USER
TM176 - Because multiple files are not supported for single tape mark format tapes, a file sequence number greater than one cannot be specified
Single filemark format tapes are not allowed with the -q option of the tmmnt(1) command. - USER
TM177 - Unable to create a temporary file needed to communicate the request request to the TMF daemon (errno = errno)
A TMF request was terminated because TMF was unable to create a file required to communicate the request to the TMF daemon; the error returned is errno. - USER/ADM
TM178 - Unable to provide the request request information to the TMF daemon indirectly
A TMF request was terminated because TMF was unable to communicate the request to the TMF daemon; the error returned is errno. - USER/ADM
TM179 - An operator request cannot be issued for a device controlled by an unattended media loader
With the tape loader in unattended mode, administrator requests are not valid; thus the request was aborted. - ADM
TM180 - Cannot write after a read
write(2) requests cannot directly follow read(2) requests. - USER
TM181 - The specified path_type path, pathname, does not exist
pathname specified with the TMF command does not exist. - USER
TM182 - Permission to read file filename was denied (errno = errno)
The filename file does not have read access enabled. - USER
TM183 - Cannot request concatenation when creating a new file or appending to an existing file
The -c option of the tmmnt(1) command was used to request that multiple tape files be read as though they were one tape file. This feature cannot be specified with either the -n or -a option. Correct the option specified and reissue the tmmnt(1) command. - USER
TM184 - Cannot issue a positioning request, other than a rewind request, to a concatenated file
The position request was terminated because the tape file is a concatenated file. The only valid positioning request for concatenated files is the rewind request. - USER
TM185 - Session sidterminated but left stream file pathname open
TMF allowed a stream file to remain open after the session owning the stream has terminated. - ADM
TM186 - Cannot read after a write
read(2) requests cannot directly follow write(2) requests. - USER
TM187 - Cannot position past the beginning of file file
A request to position backward by blocks was terminated because the beginning of the file was detected. - USER
TM188 - Cannot position past the end of file file
A request to position forward by blocks was terminated because the end of the file was detected. - USER
TM190 - **WARNING** device device_name (autoloader: library_name, server: server_name) is in state: state.
During the initialization of the server_name server for the library_name library, the device_name tape drive was reported by the server to be in the state state. Either check the state of the tape drive with the server and alter its state so that it can be used on the system or do not attempt to configured it up. - ADM
TM191 - Cannot issue a catalog request to a file, pathname, which has not been accessed
The tmcatalog(1) command can be used only after the file has been opened and closed. - USER
TM192 - A servicing front-end has not been defined
The tmcatalog(1) command cannot be used if a servicing front end is not being used. - USER
TM193 - Permission to operator file file denied by the front-end
The servicing front end has not given permission to perform the specified operation. - USER
TM194 - The operator requested that the request be retried
The message is being sent again to the front-end operator. - USER
TM195 - Unable to configure media loader loader to auto mode
The loader media loader could not be modified to auto mode. - ADM
TM196 - Unable to configure media loader loader to manual mode
The loader media loader could not be modified to manual mode. - ADM
TM197 - Unable to configure media loader loader to attended mode
The loader media loader could not be modified to attended mode. - USER
TM200 - The device status specified, status, must be either 'up' or 'down'
The status specified on a device configuration request must be either up or down. - ADM
TM201 - A hardware component must be specified
Either a device name, loader name, or group name must be specified on a configuration request. - ADM
TM202 - The default file sequence number can be used for only one of the multi-file mount requests for a volume.
Because unique files must be specified on multifile volume access requests, the default file sequence number can only be used by one of the mount requests. - USER
TM203 - The request to disable user end-of-volume processing was ignored because it is not enabled
A request to deselect user end-of-volume processing was ignored because user end-of-volume processing is not currently selected. - USER
TM204 - The request to configure component name was ignored because another request is pending
A tmconfig(8) command cannot be completed because a previous configuration command is still pending. - ADM
TM205 - The default file sequence number can be used for only one of the multi-file mount requests for a volume
Multiple tmmnt(1) commands were entered without specifying the file sequence numbers. The default is 1, which indicates the first file on the tape. Reenter the commands using file sequence numbers for the -q option. - USER/ADM
TM206 - An invalid message type, type, was specified in the FES request
A TMF child process issued a request to the TMF daemon to update file information for the file file, which could not be found. This indicates an error with TMF. - ADM
TM209 - Permission to write to file pathname denied
You have attempted to write to a file that does not have write permission. The write(2) request has been aborted. - USER
TM210 - Media loader name has not been configured in the Tape Management Facility
An invalid media loader name was specified. - USER
TM211 - A device list must be specified when requesting a device group reassignment with option -option
An invalid device group reassignment request was issued. This request requires a device, device list, or device range. - USER
TM212 - The communication path, code, to loader, name, is invalid
An invalid communication path was specified when a loader was defined in the configuration or parameter file. - ADM
TM213 - Media loader, name, is unable to change the ring status for volume vsn
A tape volume in the loader does not have the correct ring status for the vsn volume. The loader is unable to correct the ring status. The tape request has been aborted. - USER
TM214 - A stream ordinal must be specified
The TMF command required a stream ordinal. - USER
TM215 - Unable to obtain status information for loader name
You requested status information for loader name. TMF was unable to obtain this information. - USER/ADM
TM216 - Unable to send msgtype for user sid, NQSid to front-end feid (reason). Reply cancel, retry, or ignore
The TMF daemon was unable to send a message to the front end. The administrator should reply with cancel to abort the original request, retry to reissue the original request, or ignore to ignore the error condition. Multiple messages are generated when a tape is being mounted. If the administrator specifies ignore, it is assumed that the tape mount request will be satisfied as a result of one of the other messages issued. - ADM
TM217 - Scratch volume request denied.
A request was made to mount a scratch tape to a loader that does not support the type of scratch tape specified in the request. The mount request has been terminated. - USER
TM218 - Error in file config_file , line line_number, offset offset with option option.
A unique file name must be specified for the option option. The pathname file has already been specified for another file definition. - USER
TM219 - Cannot modify the status of loader loader because there are devices allocated to this loader which are assigned
A request to change the configuration of a loader cannot be completed if devices allocated to the loader have been assigned. The request has been terminated. - USER
TM220 - The media loader for device, device, cannot be modified when the device is configured up
The media loader for a device cannot be changed if the loader is not configured down. The tmconfig(8) request has been terminated. Configure the loader down, and reissue the loader change request. - USER
TM221 - Device device cannot be configured up when the loader for the device is down
You attempted to change or configure up the media loader for a device, and the loader is not configured down. The tmconfig(8) request has been terminated. - USER
TM222 - Unable to notify the TMF driver of the maximum block size, size (errno = errno)
TMF was unable to notify the TMF driver of the I/O type and maximum block size for a user when processing a user's open request; the error returned is errno. The user's open request was terminated. - ADM
TM223 - The devices belonging to device group, group are not all of the same device type
The configuration file is invalid. All devices belonging to the group group must be the same device type. - ADM
TM224 - Volume remounts because of an incorrect label type are not supported for volumes in an autoloader domain
A volume mounted by an library does not have the correct label type. Retrying the mount in an attempt to get a volume with the correct label type mounted is not supported for volumes controlled by an library. - USER
TM225 - The loader state specified, state, is invalid for loader loader.
A request was made to configure a loader to a state that is invalid. The request has been terminated. - USER
TM226 - The type volume name specified, vsn, must consist of all alphanumeric characters
An invalid volume was specified on the tmmnt(1) command. The volume specification must be alphanumeric. - USER
TM227 - The storage server was unable to mount the requested volume
A mount request issued to a storage server could not be completed. - USER
TM228 - Waiting for volume vsn
A request was made to mount the vsn volume. However, this volume is currently in use. TMF will place the mount(1m) request in a waiting state, and reissue the request when the volume is free. - USER
TM229 - Permission to mount the requested volume(s) was denied by the user exit.
Your mount(1m) request was terminated because of your site's verification specifications. Check to see that you have permission to mount this volume. - USER
TM230 - action < reason >? Reply y(yes), n(no), or q(requeue).
The message requests that you import or export a volume. Reply y if you wish to import or export, n to abort the job that requested the volume, or q to queue the mount(1m) request. - ADM
TM231 - Reply y/n when import is complete.
You replied y to an import or export request. When you complete the import or export, reply y to this message. - ADM
TM232 - Should volume vsn be ejected from loader loader to change the ring status? Reply y(yes) or n(no)
The administrator must respond either y if the system is to eject the specified vsn and change the state of the tape ring before returning the tape to the loader domain or n if the administrator does not want these actions to occur. - ADM
TM233 - Volume vsn is not scratchable. Reply `retry' or `cancel'
The mounted volume cannot be made into a scratch tape. Reply retry to mount another scratch tape or cancel to cancel the tape mount request. - ADM
TM234 - Embedded filemarks are not allowed on volume vsn
Embedded filemarks are not allowed on the vsn volume. - USER
TM235 - Unable to get the pending stream request from the TMF driver (errno = errno)
A user request is pending but the TMF daemon is unable to obtain the request from the TMF driver; the error returned is errno. - ADM
TM236 - Data compression is not supported for devices belonging to group, group
Data compression was requested with the -i option of the tmmnt(1) command with a device group that does not support data compression. - USER
TM237 - The density value specified is invalid for devices belonging to group, group
A density was specified with the -d option of the tmmnt(1) command with a device group that does not support this density. - USER
TM238 - Is volume vsn on device device a valid scratch volume for user userid, session sid? Reply y/n
Request that the administrator verify the scratch volume mounted. Reply y if the user is permitted to use the specified volume as a scratch volume or n to deny the request. - ADM
TM239 - Error in file config_file, line line_number, offset offset, with option option. File pathname cannot include any device type suffixes
The tape file specified for a device configuration contains a device type suffix. Eliminate the suffix from the definition. - ADM
TM240 - Cannot find host entry for sd=socket_descriptor
The entry for socket_descriptor is set, indicating that it is expecting a reply from another system. No entry has been queued within the tcpnet() function expecting such a reply. Check the network for proper functionality or contact your system support staff. - ADM
TM241 - Error from socket operation, sd=socket_descriptor, host=host, rc=rc, errno=errno: error_description
The error_description error has occurred while TMF was trying to do operation on socket_descriptor that is connected to host. Check the network or system host for proper functionality or contact your system support staff. - ADM
TM242 - Host name host not found
An attempt to obtain the network host entry for system host from the /etc/hosts file or from the /etc/host.bin file has failed. Contact your system support staff to correct the network files or to correct the tape configuration file. - ADM
TM243 - Unable to modify the file status flags for pipe pipename (errno = errno)
A file status setting required for TMF communication could not be set; the error returned is errno. - ADM
TM244 - The label write did not complete successfully
The tmlabel(8) command was unable to complete a label write. Only part of the label could be written. - ADM/USER
TM245 - Unable to create a pipe required to receive the request reply
The request request could not be completed because TMF could not create a pipe to receive the reply to the request. - USER
TM252 - Waiting for a device from group group to avoid a possible deadlock
The request could lead to a possible system deadlock; so the device allocation is delayed. - USER
TM253 - Device device is not available
You requested a specific device, but this device is not available. - USER/ADM
TM255 - Cannot use more tape resources than were reserved
A required option, option, has not been specified. Reissue the command specifying this option. - USER/ADM
TM257 - Supplementary logfile message from request:
This message issues a supplementary log file message from the front end. The message corresponds to the front-end request. - USER
TM258 - Unable to read the data from pipename pipe pathname (errno = errno)
A child process was unable to obtain data from its parent. An error occurred when reading from the pipename pipe; the error returned is errno.- ADM
TM259 - The TMF device assigned, device_name, is being used by a non-TMF process
The fact that a device configured as part of TMF has been opened by a process that was not supported by TMF has prevented TMF from accessing the device. - ADM
TM260 - Volume remounts to retry a failed label write is not supported for volumes in an autoloader domain
TMF has attempted a label a volume, but the label write request failed. Recovery is not possible for volumes managed by an library. - USER/ADM
TM261 - The expected size, size1, of data element element, differs from the actual size, size2
A TMF child process was unable to correctly read data from its parent. The size of the data expected for one element differs from what is expected. Check that the version of the parent is identical to that of the child. - ADM
TM262 - Unable to obtain the block information from device device for file pathname (errno = errno)
A user's request was terminated because TMF was unable to obtain the block size used for fixed-block I/O. - ADM
TM263 - Variable block I/O is not supported for devices belonging to group, group
You requested variable-block I/O via the tmmnt(1) command with a device group that does not support variable-block I/O. - USER
TM264 - Unable to acknowledge the stream request (errno = errno)
An error was returned on a system call request because a TMF process was unable to communicate correctly with the TMF driver. The process could not acknowledge that the request was received; the error returned was errno. - ADM
TM265 - Unable to obtain the device status for device device for file file (errno = errno)
Processing for a stream terminated because TMF was unable to obtain the status of a device following a device request; the error returned is errno. - ADM
TM266 - Unable to notify the TMF driver of the stream owner, owner (errno = errno)
A mount request terminated because the child created to process the mount request could not communicate the stream ownership information to the TMF driver. - ADM
TM267 - Unable to open device device for the stream stream, file pathname(errno = errno)
An error was returned while assigning the device device to the stream stream. TMF was unable to open the device for this stream; the error returned was errno. - ADM
TM268 - Unable to disable or enable writes past the EOT for file pathname (errno = errno)
By default, data cannot be output after the end-of-tape has been detected. A request has to be made to enable this capability. TMF encountered an error on a request to reset this capability to the default state or on a request to enable this capability; the error returned is errno. - ADM
TM269 - A device range and device list cannot both be specified
The format of a configuration request is invalid. - USER
TM271 - Unable to free device device from stream stream for file file (errno = errno)
TMF is unable to free file. - ADM
TM272 - Unable to provide the configuration to the TMF driver (errno = errno)
During TMF start-up processing, the TMF daemon was unable to notify the TMF driver of the configuration, and startup was terminated; the error returned is errno. - ADM
TM273 - Front-end servicing must be enabled
A front end was defined as the mount message destination for the device chosen for the volume mount, but front-end servicing has not been enabled. Enable front-end servicing with the tmset(8) command or modify the mount message destination. - USER
TM274 - Unable to clear stream stream_number (errno = errno)
TMF was unable to clear the stream_number stream; the error returned is errno. - USER/ADM
TM275 - Cannot export volume vsn from loader loader
The requested vsn volume was not found in the domain of the preferred loader loader. The volume could not be exported to the loader loader because either the loader is unattended or the administrator denied the request to export the volume. - USER
TM276 - The system indicated that a TMF request was pending for stream stream but no request was found (errno = errno)
Communication between the TMF daemon and a TMF child process failed. It was indicated that a TMF daemon request was pending, but no request was found. Processing for the stream stream is terminated. - ADM
TM277 - An invalid SSP request was received
A TMF child process received an invalid request from the TMF daemon. Processing for the stream is terminated. - ADM
TM279 - The parameter specified, param, must be in the range min_value to max_value
The user specified a value for parameter that is invalid. The value must in the range min_value to max_value. Correct the number specified and reissue the command. - ADM
TM280 - Terminating the user owning path pathname and using device device
When processing has terminated for a stream, the user's processing is then killed. - USER
TM281 - A volume identifier must be specified
The user did not specify any VSN with option -v on the TMF command. Correct the -v parameter and reissue the command. - USER
TM282 - An internal volume id must be specified
The user specified an external VSN without also specifying an internal VSN (-v =EXTID) on a TMF command. Correct the VSN specified and reissue the command. - USER
TM285 - Cannot specify a negative or non-numeric value value for the option
The user specified a nonnumeric value, parameter, for a partition number, partition_number. Specify a numeric value for all partition numbers and reissue the command. - USER
TM286 - A volume description cannot begin with the '=' delimiter
The user began the volume description with the = delimiter rather than with the internal volume identifier. Correct the volume description and reissue the command. - USER
TM288 - An external volume identifier must be specified after the first '=' delimiter
The syntax of the volume description is incorrect. A VSN must follow the = delimiter. Correct the volume description and reissue the request. - USER
TM292 - Unable to lock the SSP process pid, managing file pathname, in memory (errno = errno)
Process locking was requested with the -l option on the tmdaemon(8) command. TMF was unable to lock a Stream Service Program (SSP), created to manage the pathname stream in memory; the error returned is errno. - USER
TM294 - The reqt request has been interrupted
The reqt request has been interrupted. - USER
TM295 - The reqt request failed because the message size exceeds the segment size
An invalid front-end request was created. - USER
TM296 - Cannot export volume vsn from loader loader1 and import to loader loader2
The requested vsn volume was not found in the domain of the preferred loader2 loader. The volume could not be exported from the loader1 loader and exported to loader2 because either the loader is unattended or the administrator denied the request to move the volume. - USER
TM297 - Unable to change the permissions mode of file type file name(errno = errno)
TMF was unable to perform a chmod(8) on the named file. Contact your system support staff. - USER/ADM
TM298 - Cannot specify a negative value for the parameter
An invalid parameter, parameter, was specified. The parameter cannot be negative. The command is terminated. Correct the parameter and reissue the command. - USER/ADM
TM299 - Unable to complete the cmd command (errno = errno)
An unexpected error occurred when processing the cmd command. Contact your system support staff. - USER/ADM
TM400 - program data_structure1 V version_number1 is incompatible with system data_structure2 V version_number2, abort program.
The program name has been created with data_structure1 name version version_number1. This is incompatible with the data_structure2 name version version_number2 that was used to build the TMF daemon. Contact your system support staff to change either one of the components to create a matching set. - ADM
TM401 - The TMF child process expected n list elements from the TMF daemon but instead received m elements
When TMF starts a child process, it delivers a data structure to this process. The data structure contains the number of data structures that will follow and the size of each structure. This message indicates that there is a discrepancy between the number delivered and the number the child process has calculated. Contact your system support staff to resolve the discrepancy. - ADM
TM402 - Either a device name or `all' must be specified
The tmunld(8) command requires a device name or all. - USER
TM403 - Unable to enable or disable signals for process pid, stream stream (errno = errno)
The TMF driver communicates with the TMF daemon and its children using signals. When the TMF daemon or a child is ready to receive requests, it enables signals from the TMF driver. When it cannot accept signals, it disables the signals. This message is output if the TMF daemon or child cannot modify the signal state; the error returned is errno. - USER
TM404 - Unable to resume process pid, stream stream (errno = errno)
The TMF driver disables further processing of user system call requests when the TMF daemon or its child has a request pending for a user. Once the TMF daemon or its child has completed its processing, it will resume the user request with an ioctl(2) request to the TMF driver. This message is output if the request fails. - USER
TM405 - The volume mounted on device device differs from the requested volume
An incorrect volume was mounted on the device device. - USER
TM407 - The operator denied access to the scratch volume mounted on device device for file pathname
A scratch volume was mounted, and scratch volume verification has been configured. The administrator did not allow the mounted volume to be scratched, and the user's request was terminated. - ADM
TM408 - The operator canceled the scratch volume mount request
The mounted volume was not scratchable, and the scratch retry limit was reached. Permission to retry the scratch mount request was denied by the operator. - USER
TM410 - User exit function : function : returned : return_code
The user exit function function returned return_code. This is a site-defined message. - USER
TM411 - Cannot read the labels from volume vsn, file pathname (errno = errno)
TMF was unable to perform label processing. A label read failed with error errno. - ADM
TM413 - Permission to bypass label process denied
Root privilege is required to bypass label processing. - USER
TM414 - Exceeded the limit on the number of tape groups which can be reserved, count
You specified more tape groups on the tmrsv(1) command than what is allowed. - USER
TM415 - The option specified, value, must be greater than min
The user specified a value for the option option, which is less than the minimal value required for this option. Reissue the command specifying an option value which meets this requirement. - USER
TM416 - Because directory dir, specified with environment variable, variable, is not writeable, the current working directory will be used instead for the file
The user requested that the file be created in the directory specified with the variable environment variable. This directory is not writeable so that the current working directory is used instead. - USER
TM417 - Cannot import volume vsn to loader loader.
The requested vsn volume was not found in the domain of the preferred loader loader. The volume could not be imported to the loader loader because either the loader is unattended or the administrator denied the request to import the volume. - ADM
TM418 - A resource must be specified
A resource was not specified on the tmrls(1) command. Option -a, -d, or -p must be specified to indicate what resource or resources to release. - ADM
TM419 - A path or device name must be specified when requesting a resource privilege be kept
The -k option was specified on the tmrls(1) command without specifying a path name or a device name. - USER
TM420 - Exceeded the limit on the maximum number of active tape streams.
A mount request was terminated because TMF was at the limit of active tape streams. This limit was established by the max_streams value specified in the TMF configuration file or the default value specified in the tmfdefaults.h file. - ADM
TM421 - A media loader vendor address must be specified for device, device, controlled by media loader loader
Specify the library address of the tape drive with the device name specified by the vendor supplied software for that library. For a StorageTek library this address is in the format (acs,lsm,panel,drive), and for the EMASS library this address is a single number. Contact your system support staff to specify the correct library address for drive name. - ADM
TM422 - The specified file, pathname, does not exist
The pathname file does not exit. - ADM
TM423 - Error in line line_number, offset char_offset, with value value. Vendor address, value1, cannot exceed value2
A value is specified for value1 in the vendor address that is greater than the maximum boundary, value2, that can be specified for value1 in the vendor address. Contact your system support staff to change the value for value1 to a number that is less than value2. - ADM
TM424 - Error in line line_number, offset char_offset, with value value. The STK vendor address must be of the format, '(acs,lsm,panel,drive)'.
The StorageTek library vendor address has not been specified correctly: more values were encountered than the four making up the StorageTek library vendor address. Contact your system support staff to specify a correct StorageTek library address. - ADM
TM425 - Error in file config_file_name, line line_number, offset char_offset, with value value : text
Correct the error, text, and run again - ADM
TM426 - Error in file config_file_name, line line_number, offset char_offset, with parameter parameter. Exceeded the maximum number of items permitted, number
More than number of items were specified. Reduce the number of items and reissue the command - ADM
TM427 - Error in file config_file_name, line line_number, offset char_offset, with value value. The server name specified, char_string, is invalid
The server name specified by char-string is invalid. Specify a correct server name and reissue the command. - ADM
TM428 - Error in file config_file_name, line line_number, with statement preceding keyword_parameter. Parameter keyword_parameter is required in the preceding statement.
keyword_parameter is required in the preceding statement. Specify keyword_parameter and reissue the command. - ADM
TM429 - Error in file config_file_name, line line_number, offset char_offset, with value value. The value specified, char_string, cannot exceed number characters.
The name char_string is too long. The maximum length is number. Reduce length of name and reissue the command. - ADM
TM430 - Error in file config_file_name, line line_number, offset char_offset, with value value. value char_string has already been defined
The parameter char_string has already been defined. Remove this instance of the parameter and reissue the command. - ADM
TM433 - Error in file config_file_name, line line_number, offset char_offset, with value value. value value has not been defined
The item specified by the value value has not been defined. Add the definition of value. - ADM
TM435 - Unable to set the effective user ID of process_name to root (errno = errno)
TMF process, process_name, must execute as root. The process was terminated because the effective user identifier could not be set to root; the error returned is errno. - ADM
TM436 - The device group for device, device_name, cannot be modified when the device is configured up
The device cannot be reassigned a device group name unless it is in a down state. The tmconfig(8) request has been terminated. Configure the device down and reissue the command. - ADM
TM437 - Unable to obtain the status of the type, parameter (errno = errno)
TMF was unable to obtain the file status of pathname; the error returned is errno. - ADM
TM438 - The binary configuration file not created because of a previous error
The binary file file is not created because of a previous error. Correct the previous error and reissue the command. - ADM
TM439 - A servicing front-end identifier must be specified when mandatory front-end servicing is requested
Mandatory front-end servicing was requested in the TMF configuration file with the servicing_frontend_mandatory option. The servicing_frontend_id option must also be specified with this option. - ADM
TM440 - The servicing front-end identifier is ignored when mandatory front-end servicing is not requested.
The servicing_frontend_id option was specified in the TMF configuration file. This option is only required when the servicing_frontend_mandatory option is specified. Otherwise, it is ignored. - ADM
TM441 - The version of command tmconf is incompatible with the version of the TMF daemon
The TMF daemon was unable to successfully use the tmconf(8) command because the version of the tmconf(8) command is incompatible with the version of the TMF daemon. - ADM
TM442 - A loader name is valid only with options -d and -s
A loader name can only be specified on the tmmls(8) command with the -d or -s option. - ADM
TM443 - Exceeded the limit on the maximum number of loaders which can be specified, number
You specified more loader names on the tmmls(8) command than what is allowed. - ADM
TM447 - Unable to open file, pathname, needed to configure the TMF subsystem (errno = errno)
TMF start-up processing requires an open of the pathname file. TMF could not be started because this file could not be opened. The error returned is errno. - ADM
TM448 - The Tape Management Facility is already active
The TMF daemon could not be started because the TMF daemon is already active. Shutdown TMF and then reissue the tmdaemon(8) command. - ADM
TM449 - Unable to complete the request request issued to device device for stream pathname because of a hardware error
A nonrecoverable hardware error occurred while the device was processing the request request. - USER
TM450 - Unable to complete the req request issued to device device for stream pathname because the device is not ready
The device device could not be accessed either because the device is offline or there is no volume in the drive. - USER
TM451 - Unable to complete the req request issued to device device for stream pathname because the actual block size differs from the set size
A read(2) request issued to a fixed-length I/O device failed because the block size was not set to the correct length. - USER
TM452 - Unable to complete the req request issued to device device for stream pathname because the volume was not loaded correctly
A load error was detected when attempting to mount a tape volume. - USER
TM453 - Unable to complete the req request issued to device device for stream pathname because the volume is write protected
A write(2) request failed because write(2) requests are disabled for the mounted volume. - USER
TM454 - Unable to complete the pathname request issued to device device for stream pathname because the physical end of the media was detected
A write(2) request failed because the physical end of the tape media had been reached. - USER
TM455 - Unable to complete the req request issued to device device for stream pathname because the physical end of the media was detected
The request failed because the beginning of the tape media was detected. - USER
TM456 - Unable to complete the req request issued to device device for stream pathname because a filemark was detected
The request failed because a filemark was detected. - USER
TM457 - Unable to complete the req request issued to device device for stream pathname because the end of data was detected
The request failed because the end of the recorded data was detected. - USER
TM458 - Unable to complete the req request issued to device device for stream pathname because the end of tape warning was detected
The request failed because the early warning marking, indicating that the tape is positioned close to the physical end-of-tape, has been detected. - USER
TM459 - Unable to complete the req request issued to device device for stream pathname because the device state has changed
Either the volume has been changed or the device was reset while processing the req request. - USER
TM460 - Unable to complete the req request issued to device device for stream pathname because a setmark was detected
The request failed because a setmark was detected. - USER
TM461 - Unable to complete the req request issued to device device for stream pathname because the device mode is incompatible with the media mode
The mode in which the media was recorded is incompatible with the current device mode. - USER
TM462 - Unable to complete the req request issued to device device for stream pathname because of an unrecovered data error
An error was detected with the recorded data. - USER
TM463 - Unable to complete the req request issued to device device for stream pathname because the request was invalid
An invalid request was sent to the tape device. - USER
TM464 - Unable to complete the req request issued to device device for stream pathname because the block size exceeds the request size
A read(2) request failed because the buffer size is not large enough for the recorded data block. - USER
TM465 - Unable to complete the req request issued to device device for stream pathname because the volume was not loaded correctly
The requested tape volume was not properly loaded which caused the user's request to fail. Contact your system support staff. - USER/ADM
TM466 - Unable to complete the req request issued to device device for stream pathname because of a hardware error
The tape driver detected a fatal hardware error, which prevented the successful execution of the user's request. Contact your system support staff. - USER/ADM.
TM467 - Unable to complete the req request issued to device device for stream pathname because the device is not ready
The requested tape has been loaded but is currently not ready. Contact your system support staff. - USER/ADM
TM468 - Unable to complete the req request issued to device device for stream pathname because the actual block size differs from the set size
The block size of data on the requested tape is different from the size specified in the tmmnt(1) command. - USER
TM469 - Unable to position by files
TMF was unable to skip the specified number of files. Check your TMF message file for additional information about the positioning error. - USER
TM470 - Unable to write a filemark to volume volume
TMF was unable to write a filemark to the volume volume. Check your TMF message file for additional information about the write filemark error. - USER
TM471 - Option option cannot be specified in the tmmnt parameters
The tmmnt(1) option option was specified on the additional parameters option, -p or -P of the tmlist(1) command. It is not a valid option. Remove this option from the additional parameters option value and reissue the tmlist(1) command. - USER
TM472 -The specified loader, loader, has no associated devices
The administrator issued a tmconfig(8) request for a loader that does not have any associated devices. - ADM
TM473 - Device device is not supported
The device device, specified in the TMF configuration file, is a type that TMF does not support. TMF startup will be terminated. Remove the device device, which is not a valid entry, and restart TMF. - ADM
TM474 - No devices have been configured
No valid devices have been specified in the TMF configuration file. TMF startup will be terminated. Correct the configuration file and restart TMF. - ADM
TM475 - Should error recovery be attempted for the session on device device. Reply y/n?
An I/O error was encountered on the device device. You must specify whether error recovery should be attempted. Reply y for “yes” or n for “no.” - ADM
TM476 - Unable to allocate a new device for error recovery. Reply y/n to retry the assigned device.
An I/O error was encountered on the assigned device. TMF error recovery could not assign another device. Reply y to attempt error recovery using the assigned device. - ADM
TM477 - The load failure retry limit has been reached
TMF was unable to recover from a volume load error before reaching the retry limit. - USER
TM478 - Unable to load volume volume on device device
An autoloader volume mount of the volume volume on the device device completed successfully, but the device was not able to correctly load the volume. The mount request has been terminated. - USER
TM479 - Unable to complete the mount request (errno = errno)
A mount request failed with the errno error. See your TMF message file for additional information on the error. - USER
TM480 - The operator has forcibly released your tape resources
The operator has issued a tmfrls(8) command, and all your resources have been released. - USER
TM480 - Error in file file, line line, offset offset, with value value group device a library device may not belong to a device group with AVR enabled
A library device may not belong to a device group for which AVR has been specified. Correct the TMF configuration file and restart TMF. - ADM
TM500 - Select error (errno = error)
An error occurred while the tmavr process was waiting for a request from the TMF daemon. Run the tmcollect(8) command and give this information to your system support staff. - ADM
TM501 - Device operation operation type failed for device name file path (reason:errno = error)
An error operation type occurred while the tmavr process was attempting to collect label information on the name device. Run the tmcollect(8) command and give this information to your system support staff. - ADM
TM502 - An invalid AVR request (code) was sent to tmavr.
An unexpected commandcode was received by the tmavr process. Run the tmcollect(8) command and give this information to your system support staff. - ADM
TM503 - Unexpected errno (error), expected ESRCH on kill for process pid
A signal could not be delivered to a tmavr process pid. Run the tmcollect(8) command and give this information to your system support staff. - ADM
TM504 - Label read failed for device name (reason); should the tape be used? Reply y/n
A label could not be read on the name device for reason. The operator is asking you if the tape should be used. Answer y for “yes”or n for “no.” - USER/ADM
TM505 - Error in file file, line line, offset offset, with value value group device a library device may not belong to a device group with AVR enabled
A library device may not belong to a device group for which AVR has been specified. Correct the TMF configuration file and restart TMF. - ADM
TM911 - TMF failure, please run /usr/tmf/bin/tmcollect for: reason
An internal TMF error has been detected reason, and this message is logged to the /var/spool/tmf/daemon.stderr file. Run the tmcollect(8) command and give this information to your system support staff. - ADM
TM994 - Unable to open TMF lockfile lockfile (errno = errno)
During TMF initialization, the TMF daemon could not open the lockfile required for startup. - ADM
TM995 - The use of the Tape Management Facility (TMF) is regulated by\n license. The Cray License Manager is unable\n to grant permission to use TMF (error errno - reason)\n Contact Cray Research, Inc. to obtain a license and/or a key\n to use this software.
TM996 - Process process id has open tape device and can't be killed.
TMF is attempting to remove an active user and cannot kill the process that opened the tape file. - ADM
TM997 - Process process id exited , killing related pids with command.
TMF has detected the exit of the user process that owns the open tape file. It is attempting to kill any related processes. - ADM
TM998 - Tape subsystem terminating, request denied
A request was terminated because TMF is in the shutdown process. Reissue the request after TMF has been brought up. - USER
TM999 - Tape subsystem busy, TMF daemon termination pending
TMF is terminating and has found an active user; this delays the termination. - ADM