Silo Media Manager Installation and User’s Guide Abstract This guide describes how to install and use the Silo Media Manager software. It includes information about connection with an HP NonStop™ S-series system. This guide is written for anyone who installs or uses the Silo Media Manager software. Product Version N.A. Supported Release Version Updates (RVUs) This guide supports G06.03 and all subsequent G-series RVUs for the CTL700 tape library and G06.
Document History Part Number Product Version 541559-001 N.A.
Silo Media Manager Installation and User’s Guide Index Examples Figures What’s New in This Manual ix Manual Information ix New and Changed Information About This Manual xi Notation Conventions Tables ix xi 1.
. Configuring the SMM Client on the NonStop System Contents Configuring the SMM Server on the NonStop System 3-2 (continued) Verifying the Host Port Number 3-29 Stopping the Processes on the NonStop System 3-31 4. Configuring the SMM Client on the NonStop System Configuration Options 4-2 Configuring the TCP/IP Process Name PARAM Running the Client Processes 4-8 Stopping the Processes on the Client 4-10 4-6 5.
A. Silo Media Manager Quick Start Guide Contents SMM Utility Interface Program (INTFACE) CAPREPORT Function 7-9 DRIVEREPORT Function 7-10 REFRESH Function 7-10 7-1 (continued) A. Silo Media Manager Quick Start Guide INSTALL STEP 1 A-1 CD Version of SMM Software (Server) A-1 E-mail version of SMM Software (Server) A-2 INSTALL STEP 2 A-3 E-mail Version of SMM Software (Client) A-6 B. Server SMM and Client SMM Process Functions SERVER B-1 CLIENT B-2 C.
D. Interfacing to SMM Contents Troubleshooting Examples for SMM GUI Operations C-8 (continued) Example 5 C-10 Example 6 C-10 Example 7 C-11 Example 8 C-11 Troubleshooting Examples for INTFACE C-12 Example 1 C-12 Example 2 C-13 Troubleshooting Examples for Miscellaneous Problems C-13 Example 1 C-13 Example 2 C-14 Example 3 C-14 Sense Data Errors C-15 NOT READY SENSE KEY CODES C-15 HARDWARE ERROR SENSE KEY C-17 ILLEGAL REQUEST SENSE KEY C-19 UNIT ATTENTION SENSE KEY C-22 ABORTED COMMAND SENSE KEY C-24 D.
Examples Contents Examples Example A-1. Example A-2. Example A-3. Example A-4. Creating a Startup File for the Server A-3 Configured SMM SERVER - CONFIG A-5 Client STARTUP File A-6 Configured SMM CLIENT CONFIG Program A-6 Figures Figure 1-1. Figure 1-2. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 2-8. Figure 2-9. Figure 2-10. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 3-7. Figure 3-8. Figure 3-9. Figure 3-10.
Figures (continued) Contents Figures (continued) Figure 3-21. Figure 3-22. Figure 3-23. Figure 3-24. Figure 3-25. Figure 3-26. Figure 3-27. Figure 3-28. Figure 3-29. Figure 3-30. Figure 3-31. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Figure 4-10. Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4. Figure 5-5. Figure 5-6. Figure 5-7. Figure 5-8. Figure 5-9. Figure 5-10. Figure 5-11. Figure 5-12. Figure 5-13. Figure 5-14. Figure 6-1. Figure 6-2.
Figures (continued) Contents Figures (continued) Figure 6-3. Figure 6-4. Figure 6-5. Figure 6-6. Figure 6-7. Figure 6-8. Figure 6-9. Figure 6-10. Figure 6-11. Figure 6-12. Figure 6-13. Figure 6-14. Figure 5-15. Figure 5-16. Figure 5-17. Figure 5-18. Figure 5-19. Figure 6-20. Figure 5-21. Figure 5-22. Figure 5-23. Figure 5-24. Figure 5-25. Figure 5-26.
Tables (continued) Contents Tables (continued) Table D-12. Table D-13. Table D-14.
What’s New in This Manual Manual Information Silo Media Manager Installation and User’s Guide Abstract This guide describes how to install and use the Silo Media Manager software. It includes information about connection with an HP NonStop™ S-series system. This guide is written for anyone who installs or uses the Silo Media Manager software. Product Version N.A. Supported Release Version Updates (RVUs) This guide supports G06.03 and all subsequent G-series RVUs for the CTL700 tape library and G06.
What’s New in This Manual New and Changed Information Silo Media Manager Installation and User’s Guide —541559-001 x
About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
Change Bar Notation About This Manual Silo Media Manager Installation and User’s Guide —541559-001 xii
1 Overview and Hardware/Software Requirements for Silo Media Manager (SMM) This section contains these topics: Product Overview 1-1 SMM Connection Configuration Overview 1-2 Workstation Hardware and Software Requirements 1-5 System Software Requirements 1-5 Product Overview Silo Media Manager (SMM) allows tape libraries and tape drives to run unattended labeled backups, restores, and allows manual interaction with a graphical user interface (GUI).
Overview and Hardware/Software Requirements for Silo Media Manager (SMM) SMM Connection Configuration Overview The Silo Media Manager software requires NonStop labeled tape cartridges. In addition to being labeled magnetically, each tape cartridge must have a special external label that displays the volume ID in both a standard OCR format and a bar code.
Overview and Hardware/Software Requirements for Silo Media Manager (SMM) Control Path and Data Path Configuration Control Path and Data Path Configuration Figure 1-1.
Overview and Hardware/Software Requirements for Silo Media Manager (SMM) Control Path and Data Path Configuration Figure 1-2. Silo Media Manager Configuration with SL500 Tape Library The Silo Media Manager solution consists of a SCSI control path, plugged into either a PMFC or the ServerNet/DA S-SAC and directly to the library. The Control path is the path responsible for tape cartridge movement and library control. The Data path, on the other hand, is for tape drives.
Overview and Hardware/Software Requirements for Silo Media Manager (SMM) Workstation Hardware and Software Requirements Workstation Hardware and Software Requirements The workstation must have this hardware and software: • • • • • • Windows 2000, Windows XP Professional, or later Internet Explorer 5.
Overview and Hardware/Software Requirements for Silo Media Manager (SMM) System Software Requirements Silo Media Manager Installation and User’s Guide —541559-001 1 -6
2 Silo Media Manager Software Installation for the NonStop S-Series Server and Client This section contains these topics: Installation of the Server SMM 2-1 Installation of the Client SMM 2-7 Installation of the Server SMM Overview of the Installation Process Installation of Silo Media Manager (SMM) consists of: • • • Installing the SMM software Transferring files via FTP Configuring the SMM serve and the SMM GUI to establish communication between the selected NonStop S-series system and the tape libr
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Installing the Software Installing the Software 1. Place the Silo Media Manager CD in the CD-ROM drive on your PC workstation. The software will load automatically. During Installation, the SMM Icon shown in Figure 2-1 appears. 2. Double-click on the SMM Icon to begin your SMM session. Figure 2-1. Silo Media Manager Desktop Icon a.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP Transferring Files via FTP 1. On the Main tab, under Utilities, click FTP. Figure 2-3 shows the Main tab with FTP selected in the Utilities section. Figure 2-3.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The FTP dialog box appears. Figure 2-4. FTP Dialog Box 2. In the FTP dialog box, under HP NonStop Host Information: • • • In the Host box, type the IP address of the NonStop system that is attached to the tape library. In the User box, type your user group and name. You must be a super-group user to transfer files. In the Password box, type the password for the user ID shown in the User box.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The Open dialog box appears. Figure 2-5. Open Dialog Box - Server Files 5. Navigate to the drive for the CD-ROM when the Open window appears (See Figure 2-5). 6. Select all the files in the Server directory as illustrated in Figure 2-5. 7. Click Open.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The FTP dialog box reappears as shown in Figure 2-6. Figure 2-6. FTP Dialog Box - Files Selected 8. Under Files selected, 17 files selected appears. 9. Click FTP files to begin the file transfer.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Installation of the Client SMM Installation of the Client SMM Overview of the Client The client software is installed on a second NonStop system and is designed to communicate with another NonStop system, which is the host to the tape library device. The server controls the robot on the tape library. The client sends its requests to the server, and the server then sends the request to the tape library.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP Transferring Files via FTP 1. On the Main Tab, under Utilities, click FTP. Figure 2-7 shows the Main tab with FTP selected in the Utilities section. Figure 2-7.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The FTP dialog box appears. Figure 2-8. FTP Dialog Box 2. At the FTP dialog box, under HP NonStop Host Information: ° ° In the Host box, type the IP address of the NonStop client. ° In the Password box, type the password for the user ID shown in the User box. In the User box, type your user group and name. You must be a super-group user to transfer files. Note.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The Open dialog box appears. Figure 2-9. Open Dialog Box - Client Files 5. Navigate to the drive for the CD-ROM when the Open window appears (See Figure 2-9). 6. Select all the files in the Client directory as illustrated in Figure 2-9. 7. Click Open.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP The FTP dialog box reappears as shown in Figure 2-10. Figure 2-10. FTP Dialog Box - Client Files Selected 8. Under Files selected, 16 files selected appears. 9. Click FTP files to begin the file transfer.
Silo Media Manager Software Installation for the NonStop S-Series Server and Client Transferring Files via FTP Silo Media Manager Installation and User’s Guide —541559-001 2- 12
3 Configuring SMM on the NonStop System This section contains this topic: Configuring the SMM Server on the NonStop System 3-2 Silo Media Manager Installation and User’s Guide —541559-001 3 -1
Configuring SMM on the NonStop System Configuring the SMM Server on the NonStop System Configuring the SMM Server on the NonStop System 1. Type RUN CONFIG at the TACL prompt where SMM is installed. Figure 3-1. RUN CONFIG 2. Type a password and press enter. Note. The file TSIMMSP is created after the password is entered. If you ever forget your password, purge this file and create a new password. A new TSIMMSP file will then be created. A menu scrolls up with configuration options.
Configuring SMM on the NonStop System Configuring the SMM Server on the NonStop System Figure 3-2.
Configuring SMM on the NonStop System Configuration Options Configuration Options CONFIG_DEVICE Type CONFIG_DEVICE to add or edit the Open SCSI device name (name of tape library) and the host device name for the device. Figure 3-3.
Configuring SMM on the NonStop System Configuration Options SET_SECURITY Type SET_SECURITY to enable or disable security for the SMM GUI. Figure 3-4. SET_SECURITY The SET_SECURITY command in the configuration to set security either off or on for the GUI. The SET_SECURITY command is set to either Y/N, see above. YES means you want security enabled. A guardian logon will be required to access the GUI and the LMM password will be required to MOUNT/DISMOUNT/LABEL and use the commands on the SERVICES tab.
Configuring SMM on the NonStop System Configuration Options Figure 3-5. GUARDIAN LOGON Once the logon is validated, the connection will continue. When loading or unloading a tape from a tape drive, the SMM password must be given when prompted for or the load/unload will not occur. See the following example: Figure 3-6.
Configuring SMM on the NonStop System Configuration Options When labeling tapes from the MEDIA LABELING tab, the SMM password must be given when prompted for or the load/unload will not occur. See the following example: Figure 3-7.
Configuring SMM on the NonStop System CONFIG_DRIVE Type CONFIG_DRIVE to add or edit a tape drive within the device. Figure 3-8.
Configuring SMM on the NonStop System Configuration Options CONFIG_HOMETERM Type CONFIG_HOMETERM to add or edit the name for the Home Term where messages are to be displayed. Figure 3-9.
Configuring SMM on the NonStop System Configuration Options CONFIG_HOSTPORT# Type CONFIG_HOSTPORT# to add or edit the TCPIP port number for the host. The number can be up to 65535. Figure 3-10.
Configuring SMM on the NonStop System VEIW_CONFIG Type VIEW_CONFIG to view all of the configurations for the device. Figure 3-11.
Configuring SMM on the NonStop System Configuration Options CONFIG_ALTSYS# Type CONFIG_ALTSYS# to configure an alternate system number. This is for use in disaster recovery. The alternate system number provides the ability to use a temporary system for 15 days. Figure 3-12.
Configuring SMM on the NonStop System DRIVE_UP Type DRIVE_UP to bring a drive up in the configuration. Figure 3-13.
Configuring SMM on the NonStop System Configuration Options DRIVE_DOWN Type DRIVE_DOWN to make a drive unavailable in the configuration. Figure 3-14.
Configuring SMM on the NonStop System 3 Configuring SMM on the NonStop System DEL_DRIVE Type DEL_DRIVE to delete a selected drive from the configuration. Figure 3-15.
Configuring SMM on the NonStop System ALTER_PASSWORD Type ALTER_PASSWORD to edit the current password to a new one. Figure 3-16.
Configuring SMM on the NonStop System HELP Menu Type HELP to see all of the commands and their functions. Figure 3-17.
Configuring SMM on the NonStop System EXIT Menu Type EXIT to exit the utility program. Figure 3-18.
Configuring SMM on the NonStop System ADD9840C ADD9840C - Allows command line entry of 9840C tape labels without having to use the GUI. This program will create the LBL9840C file or add to an existing one. This command must be followed by the INTFACE REFRESH command to update the active SMM. Note. If a tape is going to be manually mounted, either with the GUI or with INTFACE MOUNT command, the label must be added to the LBL9840C file using the GUI or with the ADD9840C command.
Configuring SMM on the NonStop System Configuring the TCP/IP Process Name PARAM Configuring the TCP/IP Process Name PARAM At the TACL prompt type “PARAM TCPIP^PROCESS^NAME $ZB01A” as shown in Figure 3-20. Figure 3-20.
Configuring SMM on the NonStop System Configuring the TCP/IP Process Name PARAM At the TACL prompt set the TCPIP^PROCESS^NAME PARAM to $ZB10A as shown in Figure 3-21. Figure 3-21.
Configuring SMM on the NonStop System Testing Communication between the NonStop Server and the Tape Library Testing Communication between the NonStop Server and the Tape Library Note. There are two ways to test communication by running TPTSTR (See the following examples). Example 1 Note. TPTSTR is a test to see if the tape library is communicating with the server. 1. Logon as SUPER.SUPER at the TACL prompt where SMM is installed. 2. Volume over to the location where the Server files were transferred. 3.
Configuring SMM on the NonStop System Testing Communication between the NonStop Server and the Tape Library 4. Press enter and the following information will be shown as shown in Figure 3-23. Figure 3-23.
Configuring SMM on the NonStop System Testing Communication between the NonStop Server and the Tape Library Example 2 1. Logon as SUPER.SUPER at the TACL prompt where SMM is installed. 2. Volume over to the location where the Server files were transferred. 3. Type RUN TPTSTR at the TACL prompt (See Figure 3-24). Figure 3-24.
Configuring SMM on the NonStop System Testing Communication between the NonStop Server and the Tape Library 4. Press enter and type the SCSI name of the tape library (in this example the SCSI name is $STKL700) at the next TACL prompt (See Figure 3-25). Figure 3-25.
Configuring SMM on the NonStop System Testing Communication between the NonStop Server and the Tape Library 5. Press enter and the following information will be displayed (See Figure 3-26). Figure 3-26.
Configuring SMM on the NonStop System Running the Server Processes on the NonStop System 3 Configuring SMM on the NonStop System Running the Server Processes on the NonStop System Once SMM has been configured on the HP NonStop S-series system, the TCP/IP process name PARAM needs to be set and the process executed before connecting to the robot using the GUI. Note. Use the appropriate home terminal process for your system. Server files and client files need to be run by using SUPER.GROUP access. 1.
Configuring SMM on the NonStop System Running the Server Processes on the NonStop System Figure 3-28.
Verifying the Host Port Number Configuring SMM on the NonStop System Verifying the Host Port Number Verifying the Host Port and EMS Messaging Numbers are Listening Once the SMM server processes have started and the STATUS command has determined that the appropriate files are running. Verify that the host port and the host EMS messaging port numbers are listening for a GUI connection: 1. At the TACL prompt, type “SCF” 2. Type “STATUS PROCESS ” Figure 3-29.
Verifying the Host Port Number Configuring SMM on the NonStop System Verifying that the Host Port and EMS Messaging Numbers are Established Once the SMM GUI is connected, verify that both of the host port and host EMS messaging port numbers are both in an established state (See Figure 3-30): 1. At the TACL prompt, type “SCF” 2. Type “STATUS PROCESS,TCP/IP PROCESS NAME>” Figure 3-30. Verifying the Host Port and EMS Messaging Numbers Established Host Port and EMS Messaging Number Established 3.
Configuring SMM on the NonStop System Stopping the Processes on the NonStop System Stopping the Processes on the NonStop System To stop the processes on the server, close the SMM GUI and return to the TACL prompt. Volume over to the location where the server files are installed. Type “OBEY STOPALL” at the TACL prompt to stop the processes. A screen similar to Figure 3-31 appears. Figure 3-31.
Configuring SMM on the NonStop System Stopping the Processes on the NonStop System Silo Media Manager Installation and User’s Guide —541559-001 3- 32
4 Configuring the SMM Client on the NonStop System Log on as SUPER.SUPER. Then volume over to the location of the transferred client files. At the TACL prompt, type RUN CONFIG. Select and enter the password at the next prompt to go any further with configuration. A Help menu displays the configuration options. Figure 4-1 shows the Configuration Menu. Figure 4-1.
Configuring the SMM Client on the NonStop System Configuration Options HELP Menu Type HELP to see all of the commands and their functions. Figure 4-2.
Configuring the SMM Client on the NonStop System EXIT Menu Type EXIT to exit the utility program. Figure 4-3.
Configuring the SMM Client on the NonStop System VIEW_CONFIG Type VIEW_CONFIG to view all of the configurations for the device. Figure 4-4.
Configuring the SMM Client on the NonStop System Configuration Options CONFIG_CLNTPORT# Type CONFIG_CLNTPORT# to add or edit the TCPIP port number for the host. Figure 4-5.
Configuring the SMM Client on the NonStop System Configuring the TCP/IP Process Name PARAM Configuring the TCP/IP Process Name PARAM At the TACL prompt type “PARAM TCPIP^PROCESS^NAME $ZB01A” as shown in Figure 4-6. Figure 4-6.
Configuring the SMM Client on the NonStop System Configuring the TCP/IP Process Name PARAM At the TACL prompt set the TCPIP^PROCESS^NAME PARAM to $ZB10A as shown in Figure 4-7. Figure 4-7.
Configuring the SMM Client on the NonStop System Running the Client Processes Running the Client Processes Once the SMM client has been configured, the TCP/IP Process Name PARAM needs to be set and the process executed before you use the GUI to connect to the robot. To run the SMM client, exit the configuration menu by typing EXIT at the prompt. When the TACL prompt appears, type the following as shown in Figure 4-8. Figure 4-8.
Configuring the SMM Client on the NonStop System Running the Client Processes At the TACL prompt, type OBEY STATUS and press enter. Figure 4-9 shows the files and processes that are running. Figure 4-9.
Configuring the SMM Client on the NonStop System Stopping the Processes on the Client Stopping the Processes on the Client 1. To stop the processes on the client, return to a TACL prompt. 2. Volume over to the location where the client files have been installed. 3. Type OBEY STOPALL at the TACL prompt to stop the processes. A screen similar to Figure 4-10 appears. Figure 4-10.
5 Configuring the Server SMM and Client SMM GUI This section contains the following topics: Configuring the Server SMM GUI 5-2 Connecting to the Tape Library with the SMM Server GUI 5-6 Configuring the Client SMM GUI 5-9 Connecting to the Tape Library with the SMM Client GUI 5-11 Silo Media Manager Installation and User’s Guide —541559-001 5 -1
Configuring the Server SMM and Client SMM GUI Configuring the Server SMM GUI Configuring the Server SMM GUI 1. Return to the SMM GUI after the server files have started. See Figure 5-1. 2. On the Main tab, under Utilities, click Configure. See Figure 5-1. Figure 5-1.
Configuring the Server SMM and Client SMM GUI Configuring the Server SMM GUI The Configure Multiple Devices dialog box appears as shown in Figure 5-2. Figure 5-2. Configure Multiple Devices Dialog Box At the Configure Multiple Devices dialog box, enter the following information in the text fields: • • • • In the IP Address box, enter the IP address of the NonStop system where the device is located. In the Port box, enter the port number selected in the Configuration menu.
Configuring the Server SMM and Client SMM GUI Support STK Option Support STK Option Note. This option is only required if your tape library has 9840C tape drives. You must select the 9840 tapes that will be supported by this drive type. When the tapes are selected, you only have to update when new tapes have been imported. If you update, all of the tapes must be reselected. Figure 5-3. Support STK9840C Media Dialog Box 1.
Configuring the Server SMM and Client SMM GUI Support STK Option 2. View all of the 9840C media that are in the tape library. Figure 5-5. Support STK9840C Media Dialog Box 3. Select the desired media in the “Support STK8940C Media Dialog Box.” Figure 5-6. Support STK9840C Media Dialog Box Note.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Server GUI Connecting to the Tape Library with the SMM Server GUI 1. Under Utilities, click Select. See Figure 5-7. Figure 5-7.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Server GUI The Select Device dialog box appears. 2. Select the Node/Device. 3. Click OK. Figure 5-8 shows the Select Device dialog box. Figure 5-8. Select Device 4. Click OK.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Server GUI The Main tab shows that the device has been connected at 100%. See . Figure 5-9.
Configuring the Server SMM and Client SMM GUI Configuring the Client SMM GUI Configuring the Client SMM GUI 1. Return to the SMM GUI after the client files have started. See Figure 5-10. 2. Under Utilities, click Configure. Figure 5-10.
Configuring the Server SMM and Client SMM GUI Configuring the Client SMM GUI The Configure Multiple Devices dialog box appears as shown in Figure 5-11. Figure 5-11. Configure Multiple Devices Dialog Box At the Configure Multiple Device dialog box, enter the following information: • • • • In the IP Address box, enter the IP address of the Client node where the device is located. In the Port box, enter the port number selected in the Configuration menu.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Client GUI Connecting to the Tape Library with the SMM Client GUI 1. Under Utilities, click Select. See Figure 5-12. Figure 5-12.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Client GUI The Select Device dialog box appears. Figure 5-13. Select Device Dialog Box 2. Select the Node/Device. 3. Click OK. See Figure 5-13.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Client GUI The Main tab shows that the device has been connected at 100%. See Figure 5-14. Figure 5-14.
Configuring the Server SMM and Client SMM GUI Connecting to the Tape Library with the SMM Client GUI Silo Media Manager Installation and User’s Guide —541559-001 5- 14
6 SMM GUI Operations This section contains the following topics: SMM GUI Tabs 6-2 Silo Media Manager Installation and User’s Guide —541559-001 6 -1
SMM GUI Tabs SMM GUI Operations SMM GUI Tabs Main Tab The SMM Main tab lists Silo Information on the right and has four Utilities on the bottom left of the screen.Three of the Utilities are covered in Section 2: Configure, Select, and FTP. For information on the Ping Utility, see Main Tab - Ping Utility on page 6-3. Figure 6-1.
Ping SMM GUI Operations Ping Figure 6-2. Main Tab - Ping Utility At the Ping dialog box, enter the IP address of any computer on the system and click Ping. Reply lines appear in the dialog box indicating that the devices are communicating successfully. See Figure 6-2. NSK User ID and Password When you have selected your device, you will be required to enter your NSK user ID and password. Figure 6-3.
Media Library Tab SMM GUI Operations Media Library Tab The Media Library Tab, shown in Figure 6-4, lists all the tape cartridges that are in the tape library. These tape cartridges are listed on the left side of the property sheet, under Slot Inventory. The domain for each tape cartridge is listed also (domain being a CT9840-1/CT9840FC-1 tape cartridge or a DLT7000/SuperDLT tape cartridge). Each tape cartridge is externally labeled with a barcode. Figure 6-4.
Legend Tab SMM GUI Operations Legend Tab The Legend tab describes what each colored light represents (See Figure 6-4). Panel Tabs The Panel Tabs show the tape drive configuration. The tape library configuration has a list of all the drives that are inside of the tape library. There are ten drives on each panel tab; Panel 1 shows drives 1 - 10, and Panel 2 shows drives 11 - 20. Each drive is labeled with its name (See Figure 6-5). Figure 6-5.
Legend Tab SMM GUI Operations Cap(s) Tab To move a tape cartridge to a tape drive, click a tape label inside of the slot inventory and drag it to a drive. The SMM GUI will also show the status of each tape drive by indicating a colored light. Refer to the legend tab to see what each colored light represents (See Figure 6-4 on page 6-4). Figure 6-6. Media Library Tab - Cap(s) To export a tape cartridge to the Cartridge Access Port, click a tape cartridge and drag it to the right of the tab.
Print SMM GUI Operations Print Click Print on the Media Library Tab and a HTML page will appear. This page is useful for obtaining system information and troubleshooting. Services Tab The Services Tab allows you to perform services on your drives, including bringing tape drives in and out of service and renaming tape drives. Legend Tab The Legend tab describes what each colored light represents. See Figure 6-7. . Figure 6-7.
Services Tab SMM GUI Operations The Services tab includes: Media Count View the total number of each particular tape drive present in the library. Current Loaded State View the number of drives and slots that are currently in use. Silo Configuration View all information on the capacity of the library and the capacity of the CAP. Panel Tabs The Panel 1 and Panel 2 tabs allow you to view the status of particular drives. Figure 6-8.
Services Tab SMM GUI Operations View the current status of drives by looking at the legend keys to the left of the drive. To change the status/configuration of a drive or to rename a drive, click that tape drive to see the Drive configuration Menu shown in Figure 6-9 on page 6-9. At the Services tab, click a drive to view the Drive configuration dialog box for that particular drive. Figure 6-9 appears. Figure 6-9.
Services Tab SMM GUI Operations • In the Password box, enter the appropriate password to perform any service options. This password was configured during installation of SMM, during View_Config. Under Take Out Of Services, the following information is viewable only: Node The name of the NonStop system hosting the drive. Name The name of the drive as viewed by the host system. Address The address of the drive within the library. Label The barcode label of a tape that is mounted in the drive.
Services Tab SMM GUI Operations 1. Under Choose an option, click Dismount. 2. The Services tab, Figure 6-8, reappears. The tape is dismounted and the drive status light is now green, indicating that the drive is online and empty.
Media Labeling Tab SMM GUI Operations Media Labeling Tab The Media Labeling Tab allows you to label tape cartridges. See Figure 6-10. Figure 6-10. Media Labeling Tab Follow these steps to label a tape cartridge: 1. Select a tape drive to label. All media that is compatible with the selected drive will be displayed. Note. SMM will only display drives that are connected to the same system as this particular GUI session. You can open multiple GUI sessions connected to multiple systems, if necessary. 2.
Media Labeling Tab SMM GUI Operations 4. Under Media Inventory, select all the tape cartridges that are desired to be labeled. 5. Click Start Labeling. 6. Enter your host configured password. Figure 6-11.
Media Labeling Tab SMM GUI Operations Figure 6-12 will appear. Figure 6-12. Initializing Volume Label View the Status of the current operation Tapes are labeled in the order they were selected In this example, you can see that three tapes were selected to be labeled as BACKUP: 000011, 000021, and 000022. See Figure 6-10 on page 6-12. In Figure 6-12, notice on the right side of the dialog box that tape 000011 is being labeled because it was the first tape selected.
Scheduler Tab SMM GUI Operations Scheduler Tab The Scheduler main tab, shown in Figure 6-13, is the starting point for scheduling any type of backup. Figure 6-13.
Scheduler Tab SMM GUI Operations Silo Media Manager Installation and User’s Guide —541559-001 6- 16
SMM GUI Operations 6 SMM GUI Operations Existing Immediate Backup From the Scheduler main tab, shown in Figure 6-13 on page 6-15, follow these steps and use Figure 6-14 as an example. Figure 6-14. Existing Immediate Backup - File Select 1. Select Existing Backup. 2. Under HP NonStop Disks Volumes, navigate to the file that you want to backup. When you choose a subvolume, the files within that subvolume will be displayed under Select Existing Backup File To Run. 3. Select the backup file you want to run.
SMM GUI Operations 4. Select Immediate. Use Figure 6-14 as an example. 5. Click Start Backup to begin the backup. Existing Scheduled Backup From the Scheduler main tab, shown in Figure 6-13 on page 6-15, follow these steps and use Figure 5-15 as an example. Figure 5-15. Existing Scheduled Backup 1. Select Existing Backup 2. Under HP NonStop Disks Volumes, navigate to the file that you want to backup.
SMM GUI Operations 3. Select the backup file you want to run. 4. Select Scheduled. Use Figure 5-15 as an example. 5. In the Name Backup box, from the drop-down menu, select the name of the existing backup. 6. In the Cycle box, from the drop-down menu, select the frequency you would like for the backup to occur. 7. In the hour box, from the drop-down menu, select the time of day that you would like for the backup to occur. 8.
SMM GUI Operations Create an Immediate Backup From the Scheduler main tab, shown in Figure 6-13 on page 6-15, follow these steps and use Figure 5-16 as an example. Figure 5-16. Create Immediate Backup 1. Select Create Backup. 2. Under HP NonStop Disks Volumes, select the volume where you want to create the backup. 3. Select Immediate. 4. In the Name Backup box, select a name for your backup. Use Figure 5-16 as an example.
SMM GUI Operations 5. Click Set Defines and continue to Set Defines on page 6-21. Set Defines When you click Set Defines on the Scheduler tab, the Set Defines dialog box appears. Follow these steps to Set Defines and use Figure 5-17 as an example. Figure 5-17.
SMM GUI Operations At the Set Defines dialog box Step 1: • • • • • In the Add Define box, create a name for the define on the host system. In the Media Type box, from the drop-down menu, select a cartridge type. In the Volume box, from the drop-down menu, select as many volumes as necessary to complete the backup. In the Label Type box, from the drop-down menu, select the type of backup. In the Retention Days box, choose the number of days you would like for the backup to be retained. 1.
SMM GUI Operations Figure 5-18 appears, indicating that you are now on Step 2. Figure 5-18. Set Defines - Step 2 At the Set Backup Script dialog box Step 2: • • • • In the Process Name box, it is recommended to leave the default value, but you can alter the Process Name if necessary. In the Terminal Name box, it is recommended to leave the default value. In the Output Name box, it is recommended to leave the default value.
SMM GUI Operations Figure 5-19 appears, indicating that you are on Step 3. Figure 5-19. Set Defines - Step 3 At the Created Backup Script dialog box Step 3: • Review your backup script information and make sure that it is correct. You can also alter the script to perform any functions that are not able to be performed through the GUI, such as TAPE_CATALOG. 5. Click Finish. 6. When the Scheduler tab reappears, if you are Creating an Immediate backup, click Start Backup (See Figure 6-20).
SMM GUI Operations Figure 6-20.
SMM GUI Operations Create a Scheduled Backup From the Scheduler main tab, follow these steps and use Figure 5-21 as an example. Figure 5-21. Create Scheduled Backup 1. Select Create Backup. 2. Under HP NonStop Disks Volumes, select the volume where you want to create the backup. 3. Select Scheduled. 4. In the Name Backup box, select a name for your backup. Use Figure 5-21 as an example. 5. Click Set Defines and continue to Set Defines on page 6-21.
SMM GUI Operations 6. After you have Set Defines, the Scheduler main tab reappears. Continue following these steps, using Figure 5-22 as an example. Figure 5-22. Create Scheduled Backup - Final Steps 7. In the Name Backup box, be sure that you selected the correct backup name. 8. In the Cycle box, from the drop-down menu, select the frequency you would like for the backup to occur. 9. In the hour box, from the drop-down menu, select the time of day that you would like for the backup to occur. 10.
SMM GUI Operations 11. Click Start Backup. Use Figure 5-22 as an example. Edit a Backup From the Scheduler main tab, shown in Figure 6-13 on page 6-15, follow these steps and use Figure 5-23 as an example. Figure 5-23. Edit Backup 1. Select Edit Backup. Note. you can only edit a scheduled backup. 2. Select Scheduled. 3. In the Name Backup box, from the drop-down menu, select a scheduled backup to edit. Use Figure 5-23 as an example.
SMM GUI Operations At this point, you can edit the backup as you see fit. From the drop-down menus, you can change the Cycle, Hour, and/or the Start Date. You can also delete the backup entirely by clicking Delete Backup. 4. Make the appropriate changes and click Start Backup.
Queue Manager Tab SMM GUI Operations Queue Manager Tab The Queue Manager tab displays all the tape labels that have been active. You can delete a selected item or all items. Figure 5-24 is a picture of the Queue Manager tab. Figure 5-24. Queue Manager Tab To delete an item, select that item and click Delete Item. When Delete All is selected all the items are deleted.
EMS Log Tab SMM GUI Operations EMS Log Tab The EMS Log is an Event Messaging Service of the NonStop system. It shows the date and time that each event takes place. See Figure 5-25. Figure 5-25. EMS Log Tab You can save the EMS Log by giving it a file name and clicking save.
SMM Log Tab SMM GUI Operations SMM Log Tab The SMM Log tab displays the events occurring within SMM. It shows the date and time the event took place. You can save the SMM log as a text file to view later. See Figure 5-26. Figure 5-26.
7 Using the SMM Utility Interface Program (INTFACE) Section 4 covers the following topics: Overview 7-1 SMM Utility Interface Program (INTFACE) 7-1 Overview A NonStop EMS subsystem for such purposes is provided. In this regard, a subsystem process name has been assigned to licensed users and will in turn filter (EMS filter) for messages from that subsystem. Unrecognized subsystems will have their messages rejected.
Using the SMM Utility Interface Program (INTFACE) IMPORT Function IMPORT Function The IMPORT function of the utility program will allow the importing of all tape cartridges in the CAP of the tape library connected to the NonStop system. It reports an error if the import does not occur. Syntax: Run .INTFACE/NAME/ IMPORT Examples: Run $SYSTEM.SMM.INTFACE/NAME/ IMPORT 000001 $SYSTEM.SMM IMPORT is the function. 000001 is the tape number. $SYSTEM.
Using the SMM Utility Interface Program (INTFACE) EXPORT Function You can use this TACL routine. ?TACL routine == == This TACL routine is an example that can be used to EXPORT tapes from a tape == library to the CAP using the SMM UTILITY with the EXPORT function. Variables in == BOLD have to be changed for your environment. == == Usage for the SMM UTILITY EXPORT function: == The given parameters are needed. == Run .
Using the SMM Utility Interface Program (INTFACE) REPORT Function #output Bad Status - [^status] ] == endif #set ^status #unframe REPORT Function The REPORT function of the utility program allows you to create a report on disk of the tape library contents. It reports only tape cartridges in valid slots, not in the CAP or in a tape drive. Syntax: Run .INTFACE/NAME/ REPORT Examples: Run $SYSTEM.SMM.INTFACE /NAME/ REPORT $SYSTEM.OUTPUT.
Using the SMM Utility Interface Program (INTFACE) REPORT Function 3. The operator imports them into the tape library with the GUI. 4. Now the SMM utility REPORT function can be invoked in a TACL routine to create a tape library inventory file on disk. This can be done immediately or scheduled for a certain time of day using a batch scheduler such as Netbatch. 5. The TACL routine uses the inventory output file to check each tape cartridge against the DSM/TC database.
Using the SMM Utility Interface Program (INTFACE) REPORT Function #push silo^out == variable for naming REPORT output diskfile #push media_status == output variable for mediacom #push media_in == input variable to mediacom #push tape_list == variable to contain REPORT diskfile used in FILETOVAR #push tapevol == tape cartridge number extracted from tape_list variable in loop #push line == output variable from VFIND to find tape cartridge in DSM/TC #push smm^loc == NonStop server location of SMM ISV $.
Using the SMM Utility Interface Program (INTFACE) REPORT Function == Loop through tape library Inventory, comparing VOLSER to MEDIACOM info and set == tapevolume to SCRATCH if in RELEASED state [#loop |while| not [#emptyv/blank/ tape_list] |do| #extractv tape_list tapevol #set media_in INFO TAPEVOLUME [tapevol],POOL [^pool] sink [#wait media_in] == == Finding the status of the tape cartridge in mediacom from the mediacom output vfind /quiet, to line/ media_status "[tapevol]" == == If LINE variable is not
Using the SMM Utility Interface Program (INTFACE) MOUNT Function MOUNT Function The MOUNT function of the utility program allows the mounting of one tape cartridge to a tape drive in a tape library connected to the NonStop server. It reports an error if the mount did not occur. Syntax: Run .INTFACE/NAME/ MOUNT Example: Run $SYSTEM.SMM.INTFACE/NAME/ MOUNT 000001 $TAPE1 $SYSTEM.SMM Run $SYSTEM.SMM.INTFACE/NAME/ MOUNT 000001 NONE $SYSTEM.
Using the SMM Utility Interface Program (INTFACE) DISMOUNT Function DISMOUNT Function The DISMOUNT function of the utility program allows the dismounting of one tape cartridge from a tape drive in a tape library connected to the NonStop server. It reports an error if the dismount does not occur. Syntax: Run .INTFACE/NAME/ DISMOUNT Example: Run $SYSTEM.SMM.INTFACE/NAME/ DISMOUNT 000001 $SYSTEM.SMM DISMOUNT is the function. 000001 is the tape cartridge number.
Using the SMM Utility Interface Program (INTFACE) DRIVEREPORT Function DRIVEREPORT Function The DRIVEREPORT function of the utility program allows the reporting of tapes in the tape drives. Syntax: Run .INTFACE/NAME/ DRIVEREPORT Example: Run $SYSTEM.SMM.INTFACE/NAME/ DRIVEREPORT $SYSTEM.OUTPUT.DRVLIST $SYSTEM.SMM CAPREPORT is the function. $SYSTEM.OUTPUT.DRVLIST is the output file for the listing. $SYSTEM.
A Silo Media Manager Quick Start Guide INSTALL STEP 1 This section describes how to install the SMM software for your host system. The host is the system that is attached to the tape library. This section discusses how to install SMM from a CD as well as how to install SMM received via e-mail. CD Version of SMM Software (Server) 1. Double-click on the GUI icon on the CD to install the GUI on your PC. 2. Rename the current SMM subvolume on the NonStop out of the way. 3. Start the GUI on your PC. 4.
Silo Media Manager Quick Start Guide E-mail version of SMM Software (Server) E-mail version of SMM Software (Server) 1. Double-click on the GUI icon in the e-mail to install the GUI on your PC. 2. Unzip the server & client attachments in the e-mail to different temporary directories on your PC. 3. Start the GUI on your PC. 4. Choose the FTP function button. 5. Enter the IP number of the server system. 6. Enter the super.super password. 7. Enter the \system.$vol.
Silo Media Manager Quick Start Guide INSTALL STEP 2 INSTALL STEP 2 1. Choose all the files. 2. Click FTP. 3. When you get the new version FTP'ed to the host, go to the server/client system(s), volume to the $vol.subvol where you installed SMM. 4. If this is not the first install of SMM on your system, you may copy the startup/shutdown files from the renamed old SMM subvolume.
Silo Media Manager Quick Start Guide ° ° INSTALL STEP 2 Enter the name of the tape device Continue this way until all devices have been added, then answer N to any more drives to configure. 6.
INSTALL STEP 2 Silo Media Manager Quick Start Guide Example A-2.
E-mail Version of SMM Software (Client) Silo Media Manager Quick Start Guide E-mail Version of SMM Software (Client) If you have SMM CLIENT systems (NonStop systems with tape drives in the library, but that the library control path is not physically attached to), you can unzip the client zip file to another directory on your PC, and use the GUI to place those files on the client systems. They configure the same way. 1. On the SMM CLIENT systems, do the following: 2.
Silo Media Manager Quick Start Guide E-mail Version of SMM Software (Client) Included as part of the SERVER files on the CD or in the ZIP file, there is a VERSION.101 file that is also downloaded to the NonStop when you select all files. This is the file that will tell which version you have. It is new as of 5.08. Please call us if you have issues with the install. You can always speak with Larry Meyers.
Silo Media Manager Quick Start Guide E-mail Version of SMM Software (Client) Silo Media Manager Installation and User’s Guide —541559-001 A- 8
B Server SMM and Client SMM Process Functions SERVER TSISMMS0: This process is the initiator. It starts all other processes, socket connections for all client and GUI connections. All messages from the client process and GUI are sent here and then sent along to TSISMMS5. TSISMMS1: This process handles all control path (mount, dismount, import and exports). TSISMMS2: This process sends messages to TSISMMS2 from TSISMMS0. It acts as a buffer.
Server SMM and Client SMM Process Functions CLIENT CLIENT TSISMMC0: This process is the initiator. It starts all other processes, socket connections for all GUI connections. All messages from the client process and GUI are sent here and then sent along to TSISMMC5. TSISMMC1: This process connects to the system via TCP/IP. All messages are sent from this point. TSISMMC2: This process sends messages to TSISMMC1 from TSISMMC0. It acts as a buffer.
C Troubleshooting Troubleshooting Examples for SMM Example 1 PROBLEM: Why does only TSISMMS0 start and the other SMM processes don't? SOLUTION: This could be an SMM configuration issue concerning the HOME TERM. Issue a 'RUN CONFIG' from the subvolume that the SMM Server and/or Client is installed in. Once the password is entered, issue a 'VIEW_CONFIG' to see if the HOME TERM is configured. If not, configure the HOME TERM as instructed in Section 3 of this manual. The HOME TERM can be any valid terminal.
Example 4 Troubleshooting Example 4 PROBLEM: Why is the SMM process TSISMMS0 looping? SOLUTION: Normally, this will happen if SMM was started without the TCPIP^PROCESS^NAME param being defined before starting it. Make sure you have used the startup file, and if so, make sure the startup file has the following line: PARAM TCPIP^PROCESS^NAME . Example 5 PROBLEM: I have installed an updated version of SMM and now I cannot get the Server/Client processes running...
Example 7 Troubleshooting Example 7 PROBLEM: When I startup SMM, it tells me I am on a backup system and that it not true... SOLUTION: Two things can cause this: 1. During the initial CONFIG, somebody put a space for the CONFIG_ALTSYS#. Stop SMM, delete the TSIMMSDT file if it exists, issue a 'RUN CONFIG' in your SMM subvolume, enter CONFIG_ALTSYS# and just hit enter. 2. Security of the RLSEID file will now allow access so SMM can read it. Make sure you are running SMM as SUPER.SUPER.
Troubleshooting Examples for SMM GUI Troubleshooting Troubleshooting Examples for SMM GUI Example 1 PROBLEM: The SMM Server GUI will not connect to my silo... SOLUTION: Possible Reason #1: This could be an SMM configuration issue. Issue a 'RUN CONFIG' from the subvolume that the SMM Server is installed in. Once the password is entered, issue a 'VIEW_CONFIG' to see the port that is configured for SMM, the silo name, and the system controlling the silo.
Example 3 Troubleshooting Example 3 PROBLEM: The SMM GUI is hanging at 20%... SOLUTION: Possible Reason #1: Older versions of the SMM GUI have problems recognizing the TSIQ1 file. When the SMM GUI tries to connect to the silo, SMM reports the TSIQ1 file and this causes the SMM GUI to hang at 20%. This can be corrected by purging the TSIQ1 file from your SMM subvolume. Possible Reason #2: The SMM software was not cycled after an IPL of the silo.
Example 5 Troubleshooting Example 5 PROBLEM: I lose my tape drive configuration in the SMM GUI every time I replace a bad tape drive... SOLUTION: This has been a known issue and has been corrected in previous SMM updates. If you are experiencing the loss of your tape drive configuration while swapping out tape drives, please contact us and we will send you the SMM update to alleviate this problem.
Example 7 Troubleshooting Example 7 PROBLEM: I installed SMM version 5 and now the GUI is not showing all of the tape drives... SOLUTION: This may happen if you are using a 9710 or 9740 silo. The problem is that most likely the firmware of the silo is below 2.00.02. For SMM version 5 or above, the silo should have no less than 2.00.02 on it. Check the version of firmware on the silo via the control panel on the silo or by viewing the SMM GUI Main tab with a silo connected [should read at least 2XXX].
Troubleshooting Examples for SMM GUI Operations Troubleshooting Troubleshooting Examples for SMM GUI Operations Example 1 PROBLEM: Why is the SMM GUI labeling process hanging? SOLUTION: Normally, this is caused by tape drives that are not defined to SMM correctly. There has to be a match between the way the tape drives are in the silo and the way they are configured in SMM.
Example 3 Troubleshooting Example 3 PROBLEM: When I try using the SMM GUI to label a tape, no tape drive shows up in my dropdown list... SOLUTION: Possible Reason #1: Normally, this is a problem with the SMM GUI configuration. Check both the RUN CONFIG and SMM GUI configuration to make sure the system name configured matches the actual system name because the labeling process compares that: Example: \S7000 => $STKL700 => 192.168.1.99 => 4001 are labeling on \S7000 machine S7000 => $STKL700 => 192.168.1.
Example 5 Troubleshooting Example 5 PROBLEM: How do I handle tapes in my silo with a label name of 'UNKNWN'? SOLUTION: The only time this will happen is if the silo cannot read the tape's external label. If you IPL the silo with an UNKNWN piece of tape media present in one of the library slots, the silo will automatically export the UNKNWN tape media to the CAP for operator intervention.
Example 7 Troubleshooting Example 7 PROBLEM: Why are none of my tapes being mounted automatically in the silo when using SMM? SOLUTION: Normally, this is due to the $ZSVR mount message either not happening or not containing the correct information. "$ZSVR MOUNT XXXXXX" is a good message "$ZSVR MOUNT" is a bad message "$ZSVR XXXXXX $TAPE1" is a bad message The word MOUNT or DISMOUNT must be followed by a valid 6 digit tape number or SMM will not recognize it.
Troubleshooting Examples for INTFACE Troubleshooting Possible Reason #2: Another reason is that in a labeling process, OVERRIDE ON is not specified. It is possible that the $ZSVR dismount message may contain another label than the barcode that SMM sees. If so, SMM will not dismount the tape due to a mismatch in the labels. Click the OVERRIDE ON button in the Media Labeling tab on the SMM GUI when trying to label your tapevolumes.
Example 2 Troubleshooting Example 2 PROBLEM: When I run the INTFACE Utility program, I receive a run-time error... SOLUTION: The most common reason for this is that the INTFACE Utility program does not know where to find the PROCFILE file in the SMM ISV location or that SMM is not started. You have to make sure the SMM ISV location is included on the command line and that the SMM software is running. For example: The 2nd parameter [$SYSTEM.OUTPUT.TAPELIST] can be any valid fully qualified filename.
Example 2 Troubleshooting Example 2 PROBLEM: Which PORT is the SMM server configured to run on? SOLUTION: The server the NonStop S-series communicates with the silo and SMM software is through the use of TCP/IP port numbers. This has to be configured when the SMM software is installed. It can normally be anything between 4001 and 8000. It will show up when you run a VIEW_CONFIG in your SMM configuration menu.
Sense Data Errors Troubleshooting Sense Data Errors Sense Data messages SMM will display in EMS NOT READY SENSE KEY CODES Description Sense Key ASC ASCQ Not Ready, Cause Not Reportable 2h 04h 00h Not Ready, In Process of Becoming Ready 2h 04h 01h Not Ready, Manual Intervention Required 2h 04h 03h Not Ready, Maintenance Mode 2h 04h 81h Not Ready, Cartridge Access Port Open 2h 3Ah 02h Not Ready,Cleaning Cartridge Installed 2h 30h 03h If a command is sent when the library is not r
NOT READY SENSE KEY CODES Troubleshooting ² ² ² If the library front door is open, closing the door causes the library to reinitialize and go into a ready state. If the library is in an inoperable state, reinitialize the library using the operator panel. If the library is in maintenance mode, take the library out of this mode using the operator panel or CSE port.
HARDWARE ERROR SENSE KEY Troubleshooting HARDWARE ERROR SENSE KEY Description Sense Key ASC ASCQ Hardware Error, General 4h 40h 01h Hardware Error, Tape Drive 4h 40h 02h Hardware Error, Cartridge Access Port 4h 40h 03h Hardware Error, Imbedded Software 4h 44h 00h The library generates a Hardware Error sense key if a hardware or firmware error is detected during command execution. The following codes describe the conditions that generate hardware errors.
HARDWARE ERROR SENSE KEY Troubleshooting DEFAULT SMM Message: 4nn: Sense Data - Not Ready, Unknown Sense Explanation: The ASC or ASCQ code is an unknown code.
ILLEGAL REQUEST SENSE KEY Troubleshooting ILLEGAL REQUEST SENSE KEY Description Sense Key ASC ASCQ Parameter Length Error 5h 1Ah 00h Invalid Command 5h 20h 00h Invalid Element 5h 21h 01h Invalid Field in CDB 5h 24h 00h Logical Unit Not Supported 5h 25h 00h Invalid Field in Parameters 5h 26h 00h Invalid Release of Persistent Reservation 5h 26h 04h Incompatible Medium 5h 30h 00h Saving Parameters Not Supported 5h 39h 00h Medium Not Present, Drive Not Unloaded 5h 3Ah
ILLEGAL REQUEST SENSE KEY Troubleshooting INVALID FIELD IN CDB SMM Message: 5240: Sense Data - Illegal Request, Invalid Field in CDB Explanation: The CDB structure has an invalid field. LOGICAL UNIT NOT SUPPORTED SMM Message: 5250: Sense Data - Illegal Request, Logical Unit Not Supported Explanation: The logical unit is not supported. INVALID FIELD IN PARAMETERS SMM Message: 5260: Sense Data - Illegal Request, Invalid Field in Parameters Explanation: There is an invalid field in the parameters.
ILLEGAL REQUEST SENSE KEY Troubleshooting MEDIUM MAGAZINE REMOVED SMM Message: 53B12: Sense Data - Illegal Request, Medium Magazine Removed Explanation: The medium magazine has been removed. DESTINATION ELEMENT FULL SMM Message: 53B0D: Sense Data - Illegal Request, Destination Element Full Explanation: The destination element is full. Usually this error occurs when you are attempting to move a tape to a cell that currently has a tape in it.
UNIT ATTENTION SENSE KEY Troubleshooting UNIT ATTENTION SENSE KEY Description Sense Key ASC ASCQ Power-On Occurred 6h 29h 01h Not Ready-to-Ready Transition 6h 28h 00h CAP Element Accessed 6h 28h 01h Mode Parameters Changed 6h 2Ah 01h Reservations Preempted 6h 2Ah 03h Reservations Release 6h 2Ah 04h Registrations Preempted 6h 2Ah 05h Microcode Has Been Changed 6h 3Fh 01h SCSI Bus Reset 6h 29h 02h Bus Device Reset Message Occurred 6h 29h 03h The library generates
UNIT ATTENTION SENSE KEY Troubleshooting Explanation: The library generates this type of Unit Attention when the library transitions to a ready state from a not ready state. This transition can occur following any conditions that cause a not ready state. A Unit Attention is generated for all initiators. CAP ELEMENT ACCESSED SMM Message: 6281: Sense Data - Unit Attention, CAP Element Accessed Explanation: The library generates this type of Unit Attention when the operator opens and closes the CAP.
ABORTED COMMAND SENSE KEY Troubleshooting ABORTED COMMAND SENSE KEY Description Sense Key ASC ASCQ SCSI Parity Error 0Bh 47h 00h Initiator Detected Error 0Bh 48h 00h Command Overlap 0Bh 4Eh 00h The library generates an Aborted Command error code when a SCSI command is aborted because of a SCSI protocol error.
Troubleshooting ABORTED COMMAND SENSE KEY Silo Media Manager Installation and User’s Guide —541559-001 C -25
Troubleshooting ABORTED COMMAND SENSE KEY Silo Media Manager Installation and User’s Guide —541559-001 C -26
D Interfacing to SMM Command Outputs This section describes how to structure interprocess commands for use within the Guardian operating system. Any byte that is not specified with data (an empty byte) should be specified as a space (see Examples of Structure). Table D-1. Detail Command Byte Structure Argument No. of Bytes Command 2 Device Node 10 Device Name 10 Label 8 Drive Node 10 Drive Name 10 Res. 1 20 Res. 2 10 Res.
Dismount Media Command Interfacing to SMM Table D-2. Mount Media Command for Control Path No.
Dismount Media Command Interfacing to SMM Table D-3. Dismount Media Command for Control Path No.
Export Media Command Interfacing to SMM Export Media Command The Export Media Command is used to remove the specified media, by media label from the device via the Cartridge Access Port (CAP). The Export Media Command seeks the specified tape label to perform the export. For details see Table D-4. Table D-4. Export Media Command for Control Path Argument No.
Import Media Command Interfacing to SMM Import Media Command The Import Media Command is used to add media to the specified storage device. The Import Media Command seeks the specified tape label to perform the import. For details see Table D-5. Table D-5. Import Media Command for Control Path No.
Inventory Update Media Command Interfacing to SMM Inventory Update Media Command The Inventory Update Media Command is used to inquire about what labels were inserted or removed from the CAP and also to inquire about what labels reside inside the device. For details see Table D-6. Table D-6. Inventory Update Command for Control Path Argument No.
Command Inputs Interfacing to SMM Command Inputs This section describes the response information structure from the issued commands, which will be returned from SMM as interprocess messages. These responses will include error information, when appropriate, for the issued command. Table D-7. Detail Message Command Byte Structure Argument No.
Mount Media Message Interfacing to SMM Mount Media Message The Mount Media message notifies the requester that the Mount Media command successfully completed or that an error caused the command to fail. With a Mount command, it returns the drive position the tape label was moved to (0-9 bottom to top) and the slot position (address) the tape label was moved from. A -1 (a 255 will be in both bytes) means that no change occurred. For details, see Table D-8. Table D-8.
Dismount Media Message Interfacing to SMM Dismount Media Message The Dismount Media message notifies the requester that the Dismount Media command successfully completed or that an error caused the command to fail. With a Dismount Command, it returns the tape drive position the tape label was moved from (0-9 bottom to top) and the slot position (address) the tape label was moved to. A -1 (a 255 will be in both bytes) means that no change occurred. For details, see Table D-9. Table D-9.
Import Media Message Interfacing to SMM Table D-10. Export Media Message for Control Path Argument No.
Inventory Update Media Message: Interfacing to SMM Table D-11. Import Media Message for Control Path Argument No.
Inventory Update Media Message: Interfacing to SMM Table D-12. Inventory Update Media Message for Control Path Argument No.
Inventory Update Media Message: Interfacing to SMM Table D-12. Inventory Update Media Message for Control Path Drive Label Name 8 000300 (char) Drive Label Media Domain 1 1(dec) Drive Label Media Type 1 D (dec) Drive Transport Domain 1 1 (dec) Drive Transport Type 1 1 (dec) Drive Transport Serial No. 32 331000048141 (char) Table D-13.
Inventory Update Media Message: Interfacing to SMM Table D-14.
Examples of Structure Interfacing to SMM Examples of Structure Sending Inventory Update Note. The command number changes from the character 'a' when sending to a character '7' when receiving.
Examples of Structure Interfacing to SMM m_pcBuffer[39] = ' ' m_pcBuffer[40] = ' ' m_pcBuffer[41] = ' ' m_pcBuffer[42] = ' ' m_pcBuffer[43] = ' ' m_pcBuffer[44] = ' ' m_pcBuffer[45] = ' ' m_pcBuffer[46] = ' ' m_pcBuffer[47] = ' ' m_pcBuffer[48] = ' ' m_pcBuffer[49] = ' ' m_pcBuffer[50] = ' ' m_pcBuffer[51] = ' ' m_pcBuffer[52] = ' ' m_pcBuffer[53] = ' ' m_pcBuffer[54] = ' ' m_pcBuffer[55] = ' ' m_pcBuffer[56] = ' ' m_pcBuffer[57] = ' ' m_pcBuffer[58] = ' ' m_pcBuffer[59] = ' ' m_pcBuffer[60] = ' ' m_pcBuf
Examples of Structure Interfacing to SMM m_pcBuffer[86] = ' ' m_pcBuffer[87] = ' ' m_pcBuffer[88] = ' ' m_pcBuffer[89] = ' ' m_pcBuffer[90] = ' ' m_pcBuffer[91] = ' ' m_pcBuffer[92] = ' ' m_pcBuffer[93] = ' ' m_pcBuffer[94] = ' ' m_pcBuffer[95] = ' ' m_pcBuffer[96] = ' ' m_pcBuffer[97] = ' ' m_pcBuffer[98] = ' ' m_pcBuffer[99] = ' ' m_pcBuffer[100] = ' ' m_pcBuffer[101] =' ' m_pcBuffer[102] = ' ' m_pcBuffer[103] =' ' m_pcBuffer[104] =' ' m_pcBuffer[105] =' ' m_pcBuffer[106] =' ' m_pcBuffer[107] =' ' m_pcB
Examples of Structure Interfacing to SMM pcReplyBuffer[2] = '7' pcReplyBuffer[3] = 0 pcReplyBuffer[4] = '\' pcReplyBuffer[5] = 'T' pcReplyBuffer[6] = 'S' pcReplyBuffer[7] = 'I' pcReplyBuffer[8] = 'S' pcReplyBuffer[9] = '7' pcReplyBuffer[10] = ‘2’ pcReplyBuffer[11] = 0 pcReplyBuffer[12] =0 pcReplyBuffer[13] =0 pcReplyBuffer[14] = '$' pcReplyBuffer[15] = 'S' pcReplyBuffer[16] = 'T' pcReplyBuffer[17] = 'K' pcReplyBuffer[18] = '9' pcReplyBuffer[19] = '7' pcReplyBuffer[20] = '1' pcReplyBuffer[21] = '0' pcReply
Examples of Structure Interfacing to SMM pcReplyBuffer[49] = 0 pcReplyBuffer[50] = 0 pcReplyBuffer[51] = 0 pcReplyBuffer[52] = 0 pcReplyBuffer[53] = 0 pcReplyBuffer[54] = 0 pcReplyBuffer[55] = 0 pcReplyBuffer[56] = 0 pcReplyBuffer[57] = 0 pcReplyBuffer[58] = 0 pcReplyBuffer[59] = 0 pcReplyBuffer[60] = 0 pcReplyBuffer[61] = 0 pcReplyBuffer[62] = 0 pcReplyBuffer[63] = 0 pcReplyBuffer[64] = 0 pcReplyBuffer[65] = 0 pcReplyBuffer[66] = 0 pcReplyBuffer[67] = 0 pcReplyBuffer[68] = 0 pcReplyBuffer[69] = 0 pcReply
Examples of Structure Interfacing to SMM pcReplyBuffer[96] = 0 pcReplyBuffer[97] = 0 pcReplyBuffer[98] = 0 pcReplyBuffer[99] = 0 pcReplyBuffer[100] = 0 pcReplyBuffer[101] =0 pcReplyBuffer[102] =0 pcReplyBuffer[103] =0 pcReplyBuffer[104] =0 pcReplyBuffer[105] = 0 pcReplyBuffer[106] = 0 pcReplyBuffer[107] = 0 pcReplyBuffer[108] = 0 pcReplyBuffer[109] = 0 pcReplyBuffer[110] = 0 pcReplyBuffer[111] = 0 pcReplyBuffer[112] = 0 pcReplyBuffer[113] = 0 pcReplyBuffer[114] = 0 pcReplyBuffer[115] = 0 pcReplyBuffer[116
Examples of Structure Interfacing to SMM pcReplyBuffer[144] = 0 pcReplyBuffer[145] = 0 pcReplyBuffer[146] = '0' pcReplyBuffer[147] = '0' pcReplyBuffer[148] = '6' pcReplyBuffer[149] = '8' pcReplyBuffer[127] = 0 pcReplyBuffer[150] = '5' pcReplyBuffer[151] = '1' pcReplyBuffer[152] = ' ' pcReplyBuffer[153] = ' ' pcReplyBuffer[154] = 0 pcReplyBuffer[155] = h0x01 pcReplyBuffer[….
Examples of Structure Interfacing to SMM SendBuffer1[23] SendBuffer1[24] SendBuffer1[25] SendBuffer1[26] SendBuffer1[27] SendBuffer1[28] SendBuffer1[29] SendBuffer1[30] SendBuffer1[31] SendBuffer1[32] SendBuffer1[33] SendBuffer1[34] SendBuffer1[35] SendBuffer1[36] SendBuffer1[37] SendBuffer1[38] SendBuffer1[39] = '0'; = '0'; = '2'; = '0'; = '8'; = ' '; = ' '; = ' '; /* DRIVE NODE*/ = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; SendBuffer1[40] SendBuffer1[41] SendBuffer1[42] SendBuffer1[
Examples of Structure Interfacing to SMM SendBuffer1[70] SendBuffer1[71] SendBuffer1[72] SendBuffer1[73] SendBuffer1[74] SendBuffer1[75] SendBuffer1[76] SendBuffer1[77] SendBuffer1[78] SendBuffer1[79] SendBuffer1[80] SendBuffer1[81] SendBuffer1[82] SendBuffer1[83] SendBuffer1[84] SendBuffer1[85] SendBuffer1[86] SendBuffer1[87] SendBuffer1[88] SendBuffer1[89] = ' '; /* RESERVED 2 */ = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; /* RESERVED 3 */ = ' '; = ' '; = ' '; = ' '; = ' '; =
Examples of Structure Interfacing to SMM SendBuffer1[117] = ' '; SendBuffer1[118] = ' '; SendBuffer1[119] = ' '; SendBuffer1[120] = ' '; SendBuffer1[121] = ' '; SendBuffer1[122] = ' '; SendBuffer1[123] = ' '; SendBuffer1[124] = ' '; SendBuffer1[125] = ' '; SendBuffer1[126] = 0; /* ERROR/STATUS CODE */ SendBuffer1[127] = 0; Command = 2 Node Name = \TSIS72 Label = 000208 Drive Name = $STKL700 Status Code = 0 Received 136 bytes of 136 bytes pcReplyBuffer[0] = 0 pcReplyBuffer[1] = 136 pcReplyBuffer[2] = '2' p
Examples of Structure Interfacing to SMM pcReplyBuffer[29] = '8' pcReplyBuffer[30] = 0 pcReplyBuffer[31] = 0 pcReplyBuffer[32] = 0 pcReplyBuffer[33] = 0 pcReplyBuffer[34] = 0 pcReplyBuffer[35] = 0 pcReplyBuffer[36] = 0 pcReplyBuffer[37] = 0 pcReplyBuffer[38] = 0 pcReplyBuffer[39] = 0 pcReplyBuffer[40] = 0 pcReplyBuffer[41] = 0 pcReplyBuffer[42] = 0 pcReplyBuffer[43] = 0 pcReplyBuffer[44] = 0 pcReplyBuffer[45] = 0 pcReplyBuffer[46] = 0 pcReplyBuffer[47] = 0 pcReplyBuffer[48] = 0 pcReplyBuffer[49] = 0 pcRep
Examples of Structure Interfacing to SMM pcReplyBuffer[76] = 0 pcReplyBuffer[77] = 0 pcReplyBuffer[78] = 0 pcReplyBuffer[79] = 0 pcReplyBuffer[80] = 0 pcReplyBuffer[81] = 0 pcReplyBuffer[82] = 0 pcReplyBuffer[83] = 0 pcReplyBuffer[84] = 0 pcReplyBuffer[85] = 0 pcReplyBuffer[86] = 0 pcReplyBuffer[87] = 0 pcReplyBuffer[88] = 'V' pcReplyBuffer[89] = 0 pcReplyBuffer[90] = 0 pcReplyBuffer[91] = 0 pcReplyBuffer[92] = 0 pcReplyBuffer[93] = 0 pcReplyBuffer[94] = 0 pcReplyBuffer[95] = 0 pcReplyBuffer[96] = 0 pcRep
Examples of Structure Interfacing to SMM pcReplyBuffer[123] = 0 pcReplyBuffer[124] = 0 pcReplyBuffer[125] = 0 pcReplyBuffer[126] = 0 pcReplyBuffer[127] = 0 pcReplyBuffer[128] = 0 pcReplyBuffer[129] = 0 pcReplyBuffer[130] = 0 pcReplyBuffer[131] = 0 pcReplyBuffer[132] = 255 pcReplyBuffer[133] = 255 pcReplyBuffer[134] = 0 pcReplyBuffer[135] = 11 Received Export Tape information Exported Tape: 000208 From Slot: 11 To Cap 0 Sending Import Information Sent 128 bytes of 128 bytes SendBuffer2[0] = '3';/* COMMAND
Examples of Structure Interfacing to SMM SendBuffer2[25] SendBuffer2[26] SendBuffer2[27] SendBuffer2[28] SendBuffer2[29] SendBuffer2[30] SendBuffer2[31] SendBuffer2[32] SendBuffer2[33] SendBuffer2[34] SendBuffer2[35] SendBuffer2[36] SendBuffer2[37] SendBuffer2[38] SendBuffer2[39] SendBuffer2[40] SendBuffer2[41] SendBuffer2[42] SendBuffer2[43] SendBuffer2[44] SendBuffer2[45] SendBuffer2[46] SendBuffer2[47] SendBuffer2[48] SendBuffer2[49] SendBuffer2[50] SendBuffer2[51] SendBuffer2[52] SendBuffer2[53] SendB
Examples of Structure Interfacing to SMM SendBuffer2[72] = ' '; SendBuffer2[73] = ' '; SendBuffer2[74] = ' '; SendBuffer2[75] = ' '; SendBuffer2[76] = ' '; SendBuffer2[77] = ' '; SendBuffer2[78] = ' '; SendBuffer2[79] = ' '; SendBuffer2[80] = ' '; /* RESERVED 3 */ SendBuffer2[81] = ' '; SendBuffer2[82] = ' '; SendBuffer2[83] = ' '; SendBuffer2[84] = ' '; SendBuffer2[85] = ' '; SendBuffer2[86] = ' '; /* RESERVED 4 */ SendBuffer2[87] = ' '; SendBuffer2[88] = ' '; SendBuffer2[89] = ' '; SendBuffer2[90] = ' '
Examples of Structure Interfacing to SMM SendBuffer2[119] = ' '; SendBuffer2[120] = ' '; SendBuffer2[121] = ' '; SendBuffer2[122] = ' '; SendBuffer2[123] = ' '; SendBuffer2[124] = ' '; SendBuffer2[125] = ' '; SendBuffer2[126] = ' '; /* ERROR/STATUS CODE */ SendBuffer2[127] = ' '; Command = 3 Node Name = \TSIS72 Label = 00020 Drive Name = $STKL700 Status Code = 0 Received 136 bytes of 136 bytes pcReplyBuffer[0] = 0 pcReplyBuffer[1] = 136 pcReplyBuffer[2] = '3' pcReplyBuffer[3] = 0 pcReplyBuffer[4] = '\' pc
Examples of Structure Interfacing to SMM pcReplyBuffer[30] = 0 pcReplyBuffer[31] = 0 pcReplyBuffer[32] = 0 pcReplyBuffer[33] = 0 pcReplyBuffer[34] = 0 pcReplyBuffer[35] = 0 pcReplyBuffer[36] = 0 pcReplyBuffer[37] = 0 pcReplyBuffer[38] = 0 pcReplyBuffer[39] = 0 pcReplyBuffer[40] = 0 pcReplyBuffer[41] = 0 pcReplyBuffer[42] = 0 pcReplyBuffer[43] = 0 pcReplyBuffer[44] = 0 pcReplyBuffer[45] = 0 pcReplyBuffer[46] = 0 pcReplyBuffer[47] = 0 pcReplyBuffer[48] = 0 pcReplyBuffer[49] = 0 pcReplyBuffer[50] = 0 pcReply
Examples of Structure Interfacing to SMM pcReplyBuffer[77] = 0 pcReplyBuffer[78] = 0 pcReplyBuffer[79] = 0 pcReplyBuffer[80] = 0 pcReplyBuffer[81] = 0 pcReplyBuffer[82] = 0 pcReplyBuffer[83] = 0 pcReplyBuffer[84] = 0 pcReplyBuffer[85] = 0 pcReplyBuffer[86] = 0 pcReplyBuffer[87] = 0 pcReplyBuffer[88] = 'W' pcReplyBuffer[89] = 0 pcReplyBuffer[90] = 0 pcReplyBuffer[91] = 0 pcReplyBuffer[92] = 0 pcReplyBuffer[93] = 0 pcReplyBuffer[94] = 0 pcReplyBuffer[95] = 0 pcReplyBuffer[96] = 0 pcReplyBuffer[97] = 0 pcRep
Examples of Structure Interfacing to SMM pcReplyBuffer[124] = 0 pcReplyBuffer[125] = 0 pcReplyBuffer[126] = 0 pcReplyBuffer[127] = 0 pcReplyBuffer[128] = 0 pcReplyBuffer[129] = 0 pcReplyBuffer[130] = 0 pcReplyBuffer[131] = 0 pcReplyBuffer[132] = 255 pcReplyBuffer[133] = 255 pcReplyBuffer[134] = 0 pcReplyBuffer[135] = 11 Received Import Tape information Imported Tape: 000208 From Cap: 1010 To Slot 11 Sending Move Medium Information Command = 0 Node Name = $STKL700 Label = 000208 Drive Name = $TAPE1 Status
Examples of Structure Interfacing to SMM SendBuffer3[20] SendBuffer3[21] SendBuffer3[22] SendBuffer3[23] SendBuffer3[24] SendBuffer3[25] SendBuffer3[26] SendBuffer3[27] SendBuffer3[28] SendBuffer3[29] SendBuffer3[30] = ' '; = ' '; = '0'; /* LABEL */ = '0'; = '0'; = '2'; = '0'; = '8'; = ' '; = ' '; = '\\'; /* DRIVE NODE*/ SendBuffer3[31] SendBuffer3[32] SendBuffer3[33] SendBuffer3[34] SendBuffer3[35] SendBuffer3[36] SendBuffer3[37] SendBuffer3[38] SendBuffer3[39] SendBuffer3[40] SendBuffer3[41] SendBuffe
Examples of Structure Interfacing to SMM SendBuffer3[67] SendBuffer3[68] SendBuffer3[69] SendBuffer3[70] SendBuffer3[71] SendBuffer3[72] SendBuffer3[73] SendBuffer3[74] SendBuffer3[75] SendBuffer3[76] SendBuffer3[77] SendBuffer3[78] SendBuffer3[79] SendBuffer3[80] = ' '; = ' '; = ' '; = ' '; /* RESERVED 2 */ = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; = ' '; /* RESERVED 3 */ SendBuffer3[81] = ' '; SendBuffer3[82] = ' '; SendBuffer3[83] = ' '; SendBuffer3[84] = ' '; SendBuffer3[85] = '
Examples of Structure Interfacing to SMM SendBuffer3[114] = ' '; SendBuffer3[115] = ' '; SendBuffer3[116] = ' '; SendBuffer3[117] = ' '; SendBuffer3[118] = ' '; SendBuffer3[119] = ' '; SendBuffer3[120] = ' '; SendBuffer3[121] = ' '; SendBuffer3[122] = ' '; SendBuffer3[123] = ' '; SendBuffer3[124] = ' '; SendBuffer3[125] = ' '; SendBuffer3[126] = ' '; SendBuffer3[127] = ' '; Command = 0 Node Name = \TSIS72 Label = 000208 Drive Name = $STKL700 Status Code = 0 Received 136 bytes of 136 bytes pcReplyBuffer[0]
Examples of Structure Interfacing to SMM pcReplyBuffer[26] = '0' pcReplyBuffer[27] = '2' pcReplyBuffer[28] = '0' pcReplyBuffer[29] = '8' pcReplyBuffer[30] = 0 pcReplyBuffer[31] = 0 pcReplyBuffer[32] = '\' pcReplyBuffer[33] = 'T' pcReplyBuffer[34] = 'S' pcReplyBuffer[35] = 'I' pcReplyBuffer[36] = 'S’ pcReplyBuffer[37] = '7' pcReplyBuffer[38] = ‘2’ pcReplyBuffer[39] = 0 pcReplyBuffer[40] = 0 pcReplyBuffer[41] = 0 pcReplyBuffer[42] = '$' pcReplyBuffer[43] = 'T' pcReplyBuffer[44] = 'A' pcReplyBuffer[45] = 'P'
Examples of Structure Interfacing to SMM pcReplyBuffer[73] = 0 pcReplyBuffer[74] = 0 pcReplyBuffer[75] = 0 pcReplyBuffer[76] = 0 pcReplyBuffer[77] = 0 pcReplyBuffer[78] = 0 pcReplyBuffer[79] = 0 pcReplyBuffer[80] = 0 pcReplyBuffer[81] = 0 pcReplyBuffer[82] = 0 pcReplyBuffer[83] = 0 pcReplyBuffer[84] = 0 pcReplyBuffer[85] = 0 pcReplyBuffer[86] = 0 pcReplyBuffer[87] = 0 pcReplyBuffer[88] = 'X' pcReplyBuffer[89] = 0 pcReplyBuffer[90] = 0 pcReplyBuffer[91] = 0 pcReplyBuffer[92] = 0 pcReplyBuffer[93] = 0 pcRep
Examples of Structure Interfacing to SMM pcReplyBuffer[120] = 0 pcReplyBuffer[121] = 0 pcReplyBuffer[122] = 0 pcReplyBuffer[123] = 0 pcReplyBuffer[124] = 0 pcReplyBuffer[125] = 0 pcReplyBuffer[126] = 0 pcReplyBuffer[127] = 0 pcReplyBuffer[128] = 0 pcReplyBuffer[129] = 0 pcReplyBuffer[130] = 255 pcReplyBuffer[131] = 255 pcReplyBuffer[132] = 0 pcReplyBuffer[133] = 0 pcReplyBuffer[134] = 0 pcReplyBuffer[135] = 11 Received MountTape information Mounted Tape: 000208 From Slot: 11 To Drive 0 Sending DISMOUNT Mo
Examples of Structure Interfacing to SMM SendBuffer4[22] SendBuffer4[23] SendBuffer4[24] SendBuffer4[25] SendBuffer4[26] SendBuffer4[27] SendBuffer4[28] SendBuffer4[29] SendBuffer4[30] SendBuffer4[31] SendBuffer4[32] SendBuffer4[33] SendBuffer4[34] SendBuffer4[35] SendBuffer4[36] SendBuffer4[37] SendBuffer4[38] SendBuffer4[39] SendBuffer4[40] SendBuffer4[41] SendBuffer4[42] SendBuffer4[43] SendBuffer4[44] SendBuffer4[45] SendBuffer4[46] SendBuffer4[47] SendBuffer4[48] SendBuffer4[49] SendBuffer4[50] SendB
Examples of Structure Interfacing to SMM SendBuffer4[69] = ' '; SendBuffer4[70] = ' '; /* RESERVED 2 */ SendBuffer4[71] = ' '; SendBuffer4[72] = ' '; SendBuffer4[73] = ' '; SendBuffer4[74] = ' '; SendBuffer4[75] = ' '; SendBuffer4[76] = ' '; SendBuffer4[77] = ' '; SendBuffer4[78] = ' '; SendBuffer4[79] = ' '; SendBuffer4[80] = ' '; /* RESERVED 3 */ SendBuffer4[81] = ' '; SendBuffer4[82] = ' '; SendBuffer4[83] = ' '; SendBuffer4[84] = ' '; SendBuffer4[85] = ' '; SendBuffer4[86] = ' '; /* RESERVED 4 */ Send
Examples of Structure Interfacing to SMM SendBuffer4[116] = ' '; SendBuffer4[117] = ' '; SendBuffer4[118] = ' '; SendBuffer4[119] = ' '; SendBuffer4[120] = ' '; SendBuffer4[121] = ' '; SendBuffer4[122] = ' '; SendBuffer4[123] = ' '; SendBuffer4[124] = ' '; SendBuffer4[125] = ' '; SendBuffer4[126] = ' '; /* ERROR/STATUS CODE */ SendBuffer4[127] = ' '; Command = 1 Node Name = \TSIS72 Label = 000208 Drive Name = $STKL700 Status Code = 0 Received 136 bytes of 136 bytes pcReplyBuffer[0] = 0 pcReplyBuffer[1] =
Examples of Structure Interfacing to SMM pcReplyBuffer[28] = '0' pcReplyBuffer[29] = '8' pcReplyBuffer[30] = 0 pcReplyBuffer[31] = 0 pcReplyBuffer[32] = '\' pcReplyBuffer[33] = 'T' pcReplyBuffer[34] = 'S' pcReplyBuffer[35] = 'I' pcReplyBuffer[36] = 'S' pcReplyBuffer[37] = '7' pcReplyBuffer[38] = ‘2’ pcReplyBuffer[39] = 0 pcReplyBuffer[40] = 0 pcReplyBuffer[41] = 0 pcReplyBuffer[42] = '$' pcReplyBuffer[43] = 'T' pcReplyBuffer[44] = 'A' pcReplyBuffer[45] = 'P' pcReplyBuffer[46] = 'E' pcReplyBuffer[47] = '1'
Examples of Structure Interfacing to SMM pcReplyBuffer[75] = 0 pcReplyBuffer[76] = 0 pcReplyBuffer[77] = 0 pcReplyBuffer[78] = 0 pcReplyBuffer[79] = 0 pcReplyBuffer[80] = 0 pcReplyBuffer[81] = 0 pcReplyBuffer[82] = 0 pcReplyBuffer[83] = 0 pcReplyBuffer[84] = 0 pcReplyBuffer[85] = 0 pcReplyBuffer[86] = 0 pcReplyBuffer[87] = 0 pcReplyBuffer[88] = 'Y' pcReplyBuffer[89] = 0 pcReplyBuffer[90] = 0 pcReplyBuffer[91] = 0 pcReplyBuffer[92] = 0 pcReplyBuffer[93] = 0 pcReplyBuffer[94] = 0 pcReplyBuffer[95] = 0 pcRep
Examples of Structure Interfacing to SMM pcReplyBuffer[122] = 0 pcReplyBuffer[123] = 0 pcReplyBuffer[124] = 0 pcReplyBuffer[125] = 0 pcReplyBuffer[126] = 0 pcReplyBuffer[127] = 0 pcReplyBuffer[128] = 0 pcReplyBuffer[129] = 0 pcReplyBuffer[130] = 255 pcReplyBuffer[131] = 255 pcReplyBuffer[132] = 0 pcReplyBuffer[133] = 0 pcReplyBuffer[134] = 0 pcReplyBuffer[135] = 11 Receive Dismount Tape information Dismounted Tape: 000208 From Drive: 1030 To Slot 11 Example /* You will have to run THRDPTY file as process
Examples of Structure Interfacing to SMM TSISRVFileNum, cc, ccx, err, wCountRead long WriteTag char = 0; = 3; anBuffer[31000], SendBuffer1[130], SendBuffer2[130], SendBuffer3[130], SendBuffer4[130]; memset(anBuffer, 0, 31000); wCountRead = 0; nResult = FILE_OPEN_("$RECEIVE", (short)8, &nFileNumber, , /* ACCESS MODE */ , /* EXCLUSION MODE */ 0, /* NOWAIT DEPTH */ 1); /* OPEN OPTIONS */ err = FILE_OPEN_((char _far *)"$TPTY", (short)strlen("$TPTY"), (short _far *)&TSISRVFileNum); /* EXPORT */ SendBuffe
Examples of Structure Interfacing to SMM SendBuffer1[8] = ' '; SendBuffer1[9] = ' '; SendBuffer1[10] = ' '; SendBuffer1[11] = ' '; SendBuffer1[12] = '$';/* SCSI DEVICE NAME */ SendBuffer1[13] = 'S'; SendBuffer1[14] = 'T'; SendBuffer1[15] = 'K'; SendBuffer1[16] = '9'; SendBuffer1[17] = '7'; SendBuffer1[18] = '1'; SendBuffer1[19] = '0'; SendBuffer1[20] = ' '; SendBuffer1[21] = ' '; SendBuffer1[22] = '0'; /* LABEL */ SendBuffer1[23] = '0'; SendBuffer1[24] = '0'; SendBuffer1[25] = '9'; SendBuffer1[26] = '8';
Examples of Structure Interfacing to SMM SendBuffer1[55] = ' '; SendBuffer1[56] = ' '; SendBuffer1[57] = ' '; SendBuffer1[58] = ' '; SendBuffer1[59] = ' '; SendBuffer1[60] = ' '; SendBuffer1[61] = ' '; SendBuffer1[62] = ' '; SendBuffer1[63] = ' '; SendBuffer1[64] = ' '; SendBuffer1[65] = ' '; SendBuffer1[66] = ' '; SendBuffer1[67] = ' '; SendBuffer1[68] = ' '; SendBuffer1[69] = ' '; SendBuffer1[70] = ' '; /* CURRENT PASSWORD */ SendBuffer1[71] = ' '; SendBuffer1[72] = ' '; SendBuffer1[73] = ' '; SendBuffe
Examples of Structure Interfacing to SMM SendBuffer1[102] = ' '; SendBuffer1[103] = ' '; SendBuffer1[104] = ' '; SendBuffer1[105] = ' '; SendBuffer1[106] = ' '; /* ALTERNATE FIELD 3 (10 BYTES) */ SendBuffer1[107] = ' '; SendBuffer1[108] = ' '; SendBuffer1[109] = ' '; SendBuffer1[110] = ' '; SendBuffer1[111] = ' '; SendBuffer1[112] = ' '; SendBuffer1[113] = ' '; SendBuffer1[114] = ' '; SendBuffer1[115] = ' '; SendBuffer1[116] = ' '; /* ALTERNATE FIELD 4 (10 BYTES) */ SendBuffer1[117] = ' '; SendBuffer1[118
Examples of Structure Interfacing to SMM 0, 31000); wCountRead = 0; /* IMPORT */ SendBuffer2[0] = 0x33;/* COMMAND */ SendBuffer2[1] = 0x51;/* THIRD PARTY REQUEST */ SendBuffer2[2] = '\\'; /* DEVICE NODE NAME */ SendBuffer2[3] = 'S'; SendBuffer2[4] = '7'; SendBuffer2[5] = '0'; SendBuffer2[6] = '0'; SendBuffer2[7] = '0'; SendBuffer2[8] = ' '; SendBuffer2[9] = ' '; SendBuffer2[10] = ' '; SendBuffer2[11] = ' '; SendBuffer2[12] = '$';/* SCSI DEVICE NAME */ SendBuffer2[13] = 'S'; SendBuffer2[14] = 'T'; SendBuff
Examples of Structure Interfacing to SMM SendBuffer2[41] SendBuffer2[42] SendBuffer2[43] SendBuffer2[44] SendBuffer2[45] SendBuffer2[46] SendBuffer2[47] SendBuffer2[48] SendBuffer2[49] SendBuffer2[50] SendBuffer2[51] SendBuffer2[52] SendBuffer2[53] SendBuffer2[54] SendBuffer2[55] SendBuffer2[56] SendBuffer2[57] SendBuffer2[58] SendBuffer2[59] SendBuffer2[60] SendBuffer2[61] SendBuffer2[62] SendBuffer2[63] SendBuffer2[64] SendBuffer2[65] SendBuffer2[66] SendBuffer2[67] SendBuffer2[68] SendBuffer2[69] SendB
Examples of Structure Interfacing to SMM SendBuffer2[88] = ' '; SendBuffer2[89] = ' '; SendBuffer2[90] = ' '; SendBuffer2[91] = ' '; SendBuffer2[92] = ' '; SendBuffer2[93] = ' '; SendBuffer2[94] = ' '; SendBuffer2[95] = ' '; SendBuffer2[96] = ' '; /* ALTERNATE FIELD 2 (10 BYTES SendBuffer2[97] = ' '; SendBuffer2[98] = ' '; SendBuffer2[99] = ' '; SendBuffer2[100] = ' '; SendBuffer2[101] = ' '; SendBuffer2[102] = ' '; SendBuffer2[103] = ' '; SendBuffer2[104] = ' '; SendBuffer2[105] = ' '; SendBuffer2[106] =
Examples of Structure Interfacing to SMM NumToSend, (short _far *)&CountActuallyWritten, WriteTag); cc = READUPDATEX((short)nFileNumber, (char _far *)anBuffer, (short)sizeof(anBuffer), (short _far *)&wCountRead); nResult = REPLYX((char _far *)anBuffer, (short)wCountRead); memset(anBuffer, 0, 31000); wCountRead = 0; /* MOUNT */ SendBuffer3[0] = 0x30;/* COMMAND */ SendBuffer3[1] = 0x51;/* THIRD PARTY REQUEST */ SendBuffer3[2] = '\\'; /* DEVICE NODE NAME */ SendBuffer3[3] = 'S'; SendBuffer3[4] = '7'; SendBuf
Examples of Structure Interfacing to SMM SendBuffer3[25] SendBuffer3[26] SendBuffer3[27] SendBuffer3[28] SendBuffer3[29] SendBuffer3[30] SendBuffer3[31] SendBuffer3[32] SendBuffer3[33] SendBuffer3[34] SendBuffer3[35] SendBuffer3[36] SendBuffer3[37] SendBuffer3[38] SendBuffer3[39] SendBuffer3[40] SendBuffer3[41] SendBuffer3[42] SendBuffer3[43] SendBuffer3[44] SendBuffer3[45] SendBuffer3[46] SendBuffer3[47] SendBuffer3[48] SendBuffer3[49] SendBuffer3[50] SendBuffer3[51] SendBuffer3[52] SendBuffer3[53] SendB
Examples of Structure Interfacing to SMM SendBuffer3[72] = ' '; SendBuffer3[73] = ' '; SendBuffer3[74] = ' '; SendBuffer3[75] = ' '; SendBuffer3[76] = ' '; SendBuffer3[77] = ' '; SendBuffer3[78] = ' '; SendBuffer3[79] = ' '; SendBuffer3[80] = ' '; /* HOST PORT */ SendBuffer3[81] = ' '; SendBuffer3[82] = ' '; SendBuffer3[83] = ' '; SendBuffer3[84] = ' '; SendBuffer3[85] = ' '; SendBuffer3[86] = ' '; /* ALTERNATE FIELD 1 (10 BYTES) */ SendBuffer3[87] = ' '; SendBuffer3[88] = ' '; SendBuffer3[89] = ' '; Send
Examples of Structure Interfacing to SMM SendBuffer3[119] = ' '; SendBuffer3[120] = ' '; SendBuffer3[121] = ' '; SendBuffer3[122] = ' '; SendBuffer3[123] = ' '; SendBuffer3[124] = ' '; SendBuffer3[125] = ' '; SendBuffer3[126] = ' '; /* ERROR/STATUS CODE */ SendBuffer3[127] = ' '; NumToSend = 128; DELAY(1000); ccx = WRITEX(TSISRVFileNum, (char _far *)&SendBuffer3, NumToSend, (short _far *)&CountActuallyWritten, WriteTag); cc = READUPDATEX((short)nFileNumber, (char _far *)anBuffer, (short)sizeof(anBuffer),
Examples of Structure Interfacing to SMM SendBuffer4[8] = '2'; SendBuffer4[9] = ' '; SendBuffer4[10] = ' '; SendBuffer4[11] = ' '; SendBuffer4[12] = '$';/* SCSI DEVICE NAME */ SendBuffer4[13] = 'S'; SendBuffer4[14] = 'T'; SendBuffer4[15] = 'K'; SendBuffer4[16] = '9'; SendBuffer4[17] = '7'; SendBuffer4[18] = '1'; SendBuffer4[19] = '0'; SendBuffer4[20] = ' '; SendBuffer4[21] = ' '; SendBuffer4[22] = '0'; /* LABEL */ SendBuffer4[23] = '0'; SendBuffer4[24] = '0'; SendBuffer4[25] = '9'; SendBuffer4[26] = '8';
Examples of Structure Interfacing to SMM SendBuffer4[55] = ' '; SendBuffer4[56] = ' '; SendBuffer4[57] = ' '; SendBuffer4[58] = ' '; SendBuffer4[59] = ' '; SendBuffer4[60] = ' '; SendBuffer4[61] = ' '; SendBuffer4[62] = ' '; SendBuffer4[63] = ' '; SendBuffer4[64] = ' '; SendBuffer4[65] = ' '; SendBuffer4[66] = ' '; SendBuffer4[67] = ' '; SendBuffer4[68] = ' '; SendBuffer4[69] = ' '; SendBuffer4[70] = ' '; /* CURRENT PASSWORD */ SendBuffer4[71] = ' '; SendBuffer4[72] = ' '; SendBuffer4[73] = ' '; SendBuffe
Examples of Structure Interfacing to SMM SendBuffer4[102] = ' '; SendBuffer4[103] = ' '; SendBuffer4[104] = ' '; SendBuffer4[105] = ' '; SendBuffer4[106] = ' '; /* ALTERNATE FIELD 3 (10 BYTES) */ SendBuffer4[107] = ' '; SendBuffer4[108] = ' '; SendBuffer4[109] = ' '; SendBuffer4[110] = ' '; SendBuffer4[111] = ' '; SendBuffer4[112] = ' '; SendBuffer4[113] = ' '; SendBuffer4[114] = ' '; SendBuffer4[115] = ' '; SendBuffer4[116] = ' '; /* ALTERNATE FIELD 4 (10 BYTES) */ SendBuffer4[117] = ' '; SendBuffer4[118
Examples of Structure Interfacing to SMM err = FILE_CLOSE_(TSISRVFileNum, 0); err = FILE_CLOSE_(nFileNumber, 0); PROCESS_STOP_(); } /* end main() */ Silo Media Manager Installation and User’s Guide —541559-001 D -60
Index B SMM server (continued) OBEY GO 3-27 OBEY STATUS 3-28 OBEY STOPALL 3-31 RUN CONFIG 3-2 RUN TPTSTR 3-23 TCP/IP process name PARAM 3-20 verifying EMS messaging numbers 3-29, 3-30 host port 3-29, 3-30 VIEW CONFIG 3-11 Backups 1-1 Barcode 6-4 C Client files 2-9 Configuration client SMM GUI 5-9 configuring multiple devices 5-10 connecting to tape library 5-11 sever SMM GUI 5-2 configuring multiple devices 5-3 connecting to tape library 5-6 SMM client 3-16 CONFIG CLNPORT# 4-5 configuration menu 4-1 EXIT
N Index INTFACE 7-1 CAPREPORT function 7-9 command inputs D-7 dismount media message D-9 export media message D-9 import media message D-10 inventory update media message D-11 mount media message D-8 command outputs D-1 dismount media command D-2 export media command D-4 import media command D-5 inventory update media command D-6 mount media command D-1 DISMOUNT function 7-9 DRIVEREPORT function 7-10 EXPORT function 7-2 IMPORT function 7-2 MOUNT function 7-8 REPORT function 7-4 IP address 6-3 P N Tabs
U Index scheduler 6-15 create immediate backup 6-20 block size 6-23 output name 6-23 process name 6-23 set defines 6-21 terminal name 6-23 create scheduled backup 6-26 cycle 6-27 name backup 6-27 start date 6-27 edit a backup 6-28 existing immediate backup 6-17 existing scheduled backup 6-18 services 6-7 current loaded state 6-8 drive configuration menu 6-9 legend 6-7 media count 6-8 panel 6-8 silo configuration 6-8 SMM log 6-32 TACL prompt 3-2 Tape cartridges 6-4 Tape drives 1-1 5259 2-1, 2-7 CT9840FC-1
W Index Silo Media Manager Installation and User’s Guide —541559-001 Index -4
