Summary
The Tape Mount Manager module (tptmm) is responsible for drive manipulation such as opening the drive for access, rewinding and fast-forwarding, and providing a command template for writing and reading data from the tape in the Standard Independent Data Format (SIDF). The relevant environment variable (Windows) or script (UNIX) for the tape mount manager is sstptmm
Details
The Tape Mount Manager module (tptmm) is responsible for drive manipulation such as opening the drive for access, rewinding and fast-forwarding, and providing a command template for writing and reading data from the tape in the Standard Independent Data Format (SIDF). The relevant environment variable (Windows) or script (UNIX) for the tape mount manager is sstptmm.
| Message Number | Name | Explanation | Action |
|---|---|---|---|
| 1101 | MS_TMM_GENERAL_ERROR | Returned at tape mount time. This is a generic error message.. | |
| 1102 | MS_TMM_DRIVE_NOT_ALLOCATED | Returned at tape mount time. This message signals that the requested drive has not yetbeen allocated.. | |
| 1103 | MS_TMM_DRIVE_NOT_ALLOC_FOR_JOBID | Returned at tape mount time. The drive has been allocated by another job or a GUI session.. | |
| 1104 | MS_TMM_OPEN_UNSUCCESSFUL | Returned when attempting to open the tape drive for access, unsuccessfully. | (1) Make sure that you can see the tape drive from the operating system and that the most recent device drivers are installed. (2) Check the system logs on the operating system for any relevant errors. (3) Make sure that the tape drive supports and is set up to write in Variable Block Sizes instead of FixedBlock Sizes. Configuration here varies, e.g sometimes this is a specific driver that you need to use while other times this may be a jumper on the drive itself. Consult the drive manufacturers hardware manual for the tape drive. (4) Insert a tape into the drive. Test the drive with the DPX command line utility tapedump that resides in the tools (or bin) directory of DPX. Execute tapedump with no arguments and issue the following commands: tape DeviceName open rdonly quit If the open operation fails, DPX is unable to open the tape drive in Variable Block Size mode from the operating system itself. Contact the tape drive hardware manufacturer and consult DPX technical support.. |
| 1105 | MS_TMM_READ_ERROR | This message is generated when the tape mount manager detects a read error, possibly an unlabeled tape. | Pre-label all tapes before use. If all unlabeled tapes are to be overwritten by default, specify the -NLIFREADERR flag to the SSTPTMM module.. |
| 1106 | MS_TMM_LABEL_PARSE_ERROR | This message is returned when the tape mount manager encounters and error parsing the label.. | |
| 1107 | MS_TMM_LABEL_CREATE_ERROR | This message is returned when the tape mount manager encounters and error creating the label.. | |
| 1108 | MS_TMM_WRITE_ERROR | This message is returned when the tape mount manager encounters an error on write. | (1) Verify proper tape drive operation, using basic tape commands if possible. (2) Make sure that the tape drive fully supports extended file marks and is configured for writing invariable block size records. (3) Check the system logs for any errors.. |
| 1109 | MS_TMM_UNLOAD_ERROR | Returned when attempting unload after reading or writing, unsuccessfully. | (1) If this is a tape library, make sure that the device id and the device no. are correct, i.e. drive mapping.. |
| 1110 | MS_TMM_ClOSE_UNSUCCESSFUL | Returned when the tape mount manager encounters an error closing the drive.. | |
| 1111 | MS_TMM_FSF_ERROR | An error was received while performing a Forward Space File. | (1) This is an error during the fast-forward of the tape media. Typically, this is indicative of a hardware or media failure. Is the error media or drive specific? Check the system logs and use the command line utility tapedump that we provide to attempt to fast-forward to the relevant partition.. |
| 1112 | MS_TMM_FSR_ERROR | An error was received while performing a Forward Space Record.. | |
| 1113 | MS_TMM_BSF_ERROR | An error was received while performing a Back Space File.. | |
| 1114 | MS_TMM_BSR_ERROR | An error was received while performing a Back Space Record.. | |
| 1115 | MS_TMM_REW_ERROR | An error was received while performing a Rewind.. | |
| 1116 | MS_TMM_WRITE_FILEMARK_ERROR | An error was received while writing a filemark.. | |
| 1117 | MS_TMM_LOCK_ERROR | Opening the tape resulted in a lock error; the tape device is locked for access by another process. | This error could occur if some other software application has locked the drive for use. (1) If Windows, make sure that the Removable Storage Service is disabled for all nodes that can access the tape drive. (2) Make sure that no other application is opening the tape drive for access.(3) Ensure that you are using the manufacturers supplied device drivers for the device and not a thirdparty driver.. |
| 1118 | MS_TMM_NLTAPE_AND_VOLSER_EXIST | The tape in the drive had no label, and the requested tape volser exists in the database. . | |
| 1119 | MS_TMM_NL_TAPE_REJECT | The unlabeled tape in the drive is being rejected by the job.. | |
| 1120 | MS_TMM_WRONG_TAPE_MTD | A tape other than the one requested was mounted.. | |
| 1121 | MS_TMM_TIMED_OUT | This message signals a timeout of the Tape Mount Manager. | (1) The tape operation that we are trying to perform is timing out. It could be a connectivity of driver issue. This error is generally not descriptive enough to solve a problem. (2) If the tape drive is very slow to mount, try increasing the timeout and retry settings to the Tape Mount Manager (SSTPTMM). The (r)etry and (t)ime flags indicate how many mount retries and the mount attempt time, e.g.-r 5 -t 45 (3) Make sure that you are using the correct device drivers supplied by the drive manufacturer. For example, many tape drives will work with default device drivers on the Solaris operating system.However, these drivers support only Fixed Block Sizes and Variable Block Sizes are required for DPX. (4) Make sure that the tape is not write protected.. |
| 1122 | MS_TMM_DRIVE_NOT_IN_CORRECT_STATE | The tape mount manager detects a drive in an incorrect state for the required operation.. | |
| 1123 | MS_TMM_CLOSE_BUFFER_FAILED | A tape drive close buffer operation failed.. | |
| 1124 | MS_TMM_WRONG_DATA_MOVER_RESPOND | A Data Mover module other then the one assigned to the Tape Mount Manager is responding to messages.. | |
| 1125 | MS_TMM_WRONG_FN_RESPONSE | The Tape Mount Manager was expecting one message, but received another. . | |
| 1126 | MS_TMM_UNKNOWN_FN_CODE | The Data Mover from the associated Tape Mount Manager received a message of an unknown type.. | |
| 1127 | MS_TMM_CLOSE_ERROR | The Tape Mount Manager was unable to close the drive.. | |
| 1128 | MS_TMM_DRIVE_NOT_IN_QUEUE | The handle for the drive in question was not found in the tape drive queue.. | |
| 1129 | MS_TMM_VOLSER_NOT_AVAIL_ANY_MORE | The requested tape is not available at this time.. | |
| 1130 | MS_TMM_PARTITION_VERIFY_ERROR | There was an error verifying the tape partition. | (1) Check the system logs for any tape drive related errors. This could be a hardware problem;see if there are any commonalities such as an error with a specific tape (bad media) or a specific drive(bad drive).. |
| 1131 | MS_TMM_LABEL_PARTITION_NUMBER_IS_ZERO | The tape partition number is zero.. | |
| 1132 | MS_TMM_LABEL_PARTITION_TO_FSF_WRONG | Contact Catalogic Software Technical Support.. | |
| 1133 | MS_TMM_NL_TAPE | This message is issued when the job is requesting an unlabeled tape. | Verify the tape does not have a label with the Read Label function in device control, i.e. an NL label.. |
| 1134 | MS_TMM_VOLSER_EXISTS_IN_DATABASE | This message is issued when the job is requesting a tape with a volser that is in the database. . | |
| 1135 | MS_TMM_UNLOCK_ERROR | There was an error unlocking the requested tape drive.. | |
| 1136 | MS_TMM_FOUND_GUI_SOCK | This message indicates that the Tape Mount Manager knows the socket for the GUI.. | |
| 1137 | MS_TMM_ENOTREADY | The Data Mover generates this message when the associated Tape Mount Manager module is not ready.. | |
| 1138 | MS_TMM_ERROR_JUKE_MOUNT | Message sent to the database when there is an error mounting a Tape Library drive.. | |
| 1139 | MS_TMM_ERROR_JUKE_DISMOUNT | This message comes from the Tape Mount Manager when there is an error dismounting a Tape Library drive.. | |
| 1140 | MS_TMM_JUKE_NOT_IN_QUEUE | The handle for the Tape Library in question was not found in the tape drive queue.. | |
| 1141 | MS_TMM_DRIVE_NOT_ASSOCIATED_WITH_Tape | Library | A Tape Library operation was requested for a drive that is not associated in the database witha Tape Library.. |
| 1142 | MS_TMM_FOUND_EH_SOCK | This message indicates that the Tape Mount Manager knows the socket for the EventHandler.. | |
| 1143 | MS_TMM_FOUND_DMT_SOCK | This message indicates that the Tape Mount Manager knows the socket for the DataMover (Tape).. | |
| 1144 | MS_TMM_FOUND_DB_SOCK. | ||
| 1145 | MS_TMM_FOUND_JUKE_SOCK | This message indicates that the Tape Mount Manager knows the socket for the Tape Library.. | |
| 1150 | MS_TMM_INVALID_TAPE_ID | The tape identification string failed validation.. | |
| 1151 | MS_TMM_INVALID_TWINTAPE_ID | The twin tape identification string failed validation.. | |
| 1152 | MS_TMM_INVALID_DRIVEFILENAME | The tape drive filename failed validation.. | |
| 1153 | MS_TMM_INVALID_TWINDRIVEFILENAME | The twin tape drive filename failed validation.. | |
| 1154 | MS_TMM_INVALID_LOGICALDRIVEFILENAME | The tape drive logical filename failed validation.. | |
| 1155 | MS_TMM_INVALID_TWINLOGICALDRIVEFILENAME | The twin tape drive logical filename failed validation.. | |
| 1156 | MS_TMM_INVALID_JUKEFILENAME | The Tape Library filename failed validation.. | |
| 1157 | MS_TMM_INVALID_JUKEHOSTNAME | The Tape Library controller hostname failed validation.. | |
| 1158 | MS_TMM_INVALID_LOGICALJUKENAME | The logical Tape Library filename failed validation. . | |
| 1159 | MS_TMM_INVALID_OPERATORNODE | The operator node name failed validation.. | |
| 1160 | MS_TMM_INVALID_PHYPOOLID | The tape pool identification string failed validation.. | |
| 1161 | MS_TMM_INVALID_VOLSERNAME | The tape volser name failed validation.. | |
| 1162 | MS_TMM_INVALID_PARTITION_NUMBER | The tape partition number failed validation.. | |
| 1163 | MS_TMM_VOLSER_DOES_NOT_EXIST_IN_DB | The tape volser was not found in the database. | This specific volser was not found in the catalog, confirm with Administrator Menu->Reports->Media.. |
| 1164 | MS_TMM_READ_ERROR_VOL1 | The tape mount manager encountered an error while reading the tape volume. This maybe caused by attempting to read the label from unlabeled tape. | (1) If all unlabeled tapes are to be overwritten by default, specify the -NLIFREADERR argument to the SSTPTMM command. (2) Check the system logs for hardware errors. (3) It is possible this is bad media; check more than one tape for error reproducibility. (4) It is possible this is a bad tape drive; check more than one drive for error reproducibility. (5) Use the DPX tapedump utility to attempt to read data from the tape drive. Execute tapedump and enter: tape device name open rdonly rewind read quit. |
| 1165 | MS_TMM_READ_ERROR_HDR1 | The tape mount manager encountered an error while reading the first SIDF header on a data partition of the tape. | (1) Check the system logs for hardware errors. (2) Are the errors specific to a particular partition on the tape? This could be a defective drive; bad media;outdated, defective firmware or device drivers for the tape drive. Make sure that you have the latest firmware for the tape drive and the most recent device drivers supplied by the manufacturer.. |
| 1166 | MS_TMM_READ_ERROR_HDR2 | The tape mount manager encountered an error while reading the second SIDF header on a data partition of the tape. | (1) Check the system logs for hardware errors (2) Are the errors specific to a particular partition on the tape? This could be a defective drive; bad media;outdated, defective firmware or device drivers for the tape drive. Make sure that you have the latest firmware for the tape drive and the most recent device drivers supplied by the manufacturer.. |
| 1167 | MS_TMM_OPEN_RDWR_UNSUCCESSFUL | An attempt to open a drive with Read/Write access was unsuccessful.. | |
| 1168 | MS_TMM_UNKNOWN_JUKE_OPERATION | An unknown Tape Library operation was requested.. | |
| 1169 | MS_TMM_Tape | Library_PARM_NULL | This message denotes a non-Tape Library operation.. |
| 1170 | MS_TMM_VOLSER_WRITE_DATABASE_ERROR | There was a database error during a write volser operation.. | |
| 1171 | MS_TMM_TWIN_HAD_ERROR | The twin of the drive in question had an error. This does not imply that there is anything wrong with the original volume.. | |
| 1172 | MS_TMM_JUKE_ALLIGN_ERROR | There was an error during a Tape Library alignment or serialization operation.. | |
| 1173 | MS_TMM_VOLSER_IN_DRIVE_NOT_IN_DB | The tape in the drive has a volser unknown to the database. If this is in a Tape Library, the correct slot to return the tape to is therefore unknown.. | |
| 1174 | MS_TMM_READ_ERROR_NO_SLOT | Because of an error, the tape Tape Library slot associated with this volser is undefined.. | |
| 1175 | MS_TMM_NL_TAPE_NO_SLOT | Because of an unlabeled tape error, the tape Tape Library slot associated with this volser is undefined.. | |
| 1176 | MS_TMM_VOLSER_IN_DRIVE_NOT_ASSOCIATED_WITH_JUKE | The tape volser encountered does not belong to a Tape Library.. | |
| 1177 | MS_TMM_SCRATCH_POOL_IS_EMPTY | The scratch media pool is empty.. | |
| 1178 | MS_TMM_VOLSER_NOT_AVAILABLE | The tape volser is not available. | (1) This error is generated when a tape is associated with another backup job. Check the media status in device control. (2) If you have a virtual Tape Library, an Original Clusters job may be hanging onto the tapes that need to be used. Try recycling DPX on the nodes involved to clear cached information from currently running module and try again.. |
| 1179 | MS_TMM_ERROR_NO_EMPTY_SLOT | There is no empty slot for the requested operation.. | |
| 1180 | MS_TMM_PRI_DRIVE_NOT_ALLOC_FOR_JOBID | The primary drive is not allocated for the indicated job id.. | |
| 1181 | MS_TMM_SEC_DRIVE_NOT_ALLOC_FOR_JOBID | The secondary drive is not allocated for the indicated job id.. | |
| 1182 | MS_TMM_INVALID_AUTH_TYPE | The TMM module indicates that the authorization type is invalid.. | |
| 1183 | MS_TMM_INVALID_USERNAME | The TMM module indicates that the username is invalid.. | |
| 1184 | MS_TMM_INVALID_PASSWORD | The TMM module indicates that the password is invalid.. |