Open SCSI Integrator’s Manual for NonStop Servers Abstract This manual assists developers in designing devices for connection to NonStop servers through their SCSI-2 interface. This manual describes the SCSI-2 protocol supported by the processor multifunction (PMF) customer-replaceable unit (CRU), the I/O multifunction (IOMF) CRU, and the S-PICs on the 6760 ServerNet Device Adapter (ServerNet/DA).
Document History Part Number Product Version Published 126530 N.A. August 1997 422988-001 N.A. August 1999 422988-002 N.A. April 2006 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
Open SCSI Integrator’s Manual for NonStop Servers Glossary Index Figures Tables What’s New in This Manual vii Manual Information vii New and Changed Information viii About This Manual xi Who Should Use This Manual What’s in This Manual Related Documents xi xi xii Your Comments Invited xiii Notation Conventions xiii 1. Overview The Open SCSI Interface 1-1 The External Open SCSI Bus Interface 1-2 2. Prerequisites Subject Knowledge 2-1 Regulatory Compliance 2-2 3.
3. Integrating Hardware (continued) Contents 3. Integrating Hardware (continued) Specifications 3-8 External SCSI Bus Cables 3-8 3-8 External SCSI Bus Cable Connectors SCSI Port Connector Pinouts Cable Lengths 3-8 3-10 4.
6. Managing Open SCSI Devices Contents 6.
7. The SCSI SAC (continued) Contents 7.
Figures Contents Figures Figure 1-1. Single-Path Open SCSI Bus Configuration 1-2 Figure 1-2. Dual-Path Open SCSI Bus Configuration Figure 3-1. Using ESD Protection When Servicing a CRU Figure 3-2. Single-Path SCSI Bus Configuration on PMF CRU or IOMF CRU Figure 3-3. Dual-Path SCSI Bus Configuration on PMF CRU or IOMF CRU Figure 3-4. Single-Path and Dual-Path Configurations On 6760 ServerNet/DA Figure 3-5. SCSI ID numbers and SACs on the 6760 ServerNet/DA 3-7 Figure 4-1.
Contents Open SCSI Integrator’s Manual for NonStop Servers—422988-002 vi
What’s New in This Manual Manual Information Open SCSI Integrator’s Manual for NonStop Servers Abstract This manual assists developers in designing devices for connection to NonStop servers through their SCSI-2 interface. This manual describes the SCSI-2 protocol supported by the processor multifunction (PMF) customer-replaceable unit (CRU), the I/O multifunction (IOMF) CRU, and the S-PICs on the 6760 ServerNet Device Adapter (ServerNet/DA).
New and Changed Information What’s New in This Manual New and Changed Information Note. In April 2006, this manual was updated to remove part numbers from Section 3, Integrating Hardware. To view part numbers, from the NonStop Technical Library (NTL) home page, select Support and Service > Service Information > Part Numbers. Table i lists the ways the Open SCSI Integrator’s Manual for Himalaya S-Series Servers has been updated from the previous version. Table i. Changes and Additions to the G06.
Running H/F 2 Running H/F 1 Table i. Changes and Additions to the G06.06 Version of This Manual (page 1 of 2) Section Title Changed or New 3 Integrating Hardware • • • • This section was originally titled “Device Hardware Integration.” Illustrations and text have been added about the following subjects: ° ° ° ESD protection Determining SCSI SAC ID numbers SCSI bus configurations Discussions of CRUs that control Open SCSI devices now include the 6760 ServerNet/DA.
What’s New in This Manual New and Changed Information Open SCSI Integrator’s Manual for NonStop Servers—422988-002 #
About This Manual This manual assists developers in designing devices for connection to NonStop S-series servers through their SCSI-2 interface. This manual describes the SCSI-2 protocol supported by the processor multifunction (PMF) customer-replaceable unit (CRU) and the I/O multifunction (IOMF) CRU, provides information on developing interface software, and describes the use of maintenance, diagnostic, and configuration software. This manual describes information for NonStop S-series servers on G06.
Related Documents About This Manual Section Title Abstract 5 Configuring Open SCSI Devices This section describes the software tasks required for configuring devices on the Open SCSI bus. 6 Managing Open SCSI Devices This section describes how to display current status information about, and control, Open SCSI devices. 7 The SCSI SAC This section describes the SCSI SACs on PMF CRUs, IOMF CRUs, and the S-PICs on 6760 ServerNet/DAs.
Notation Conventions About This Manual Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error ) ; !i !o !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
Notation for Management Programming Interfaces About This Manual [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Change Bar Notation About This Manual !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING. !r The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition.
About This Manual Open SCSI Integrator’s Manual for NonStop Servers—422988-002 xviii
1 Overview This section provides an overview of the Open SCSI subsystem, including a description of how the various components of this subsystem operate and interface with devices supplied by third-party integrators.
The External Open SCSI Bus Interface Overview The External Open SCSI Bus Interface The external Open SCSI bus can be connected in one of two configurations: single-path or dual-path. • • Figure 1-1 shows a typical single-path Open SCSI bus configuration with a single external device. This configuration requires that the external device be equipped with a terminator. Figure 1-2 shows a typical dual-path Open SCSI bus configuration with a single external device.
The External Open SCSI Bus Interface Overview Figure 1-2. Dual-Path Open SCSI Bus Configuration Processor 0 Processor 1 SCSI port SCSI port SCSI bus SCSI bus External device (no terminator required) CDT 102.CDD Note. The Open SCSI bus does not support SCSI-1 devices. The Open SCSI I/O process (IOP) software supports passthrough capability for an application. This means that an application can send commands to a device using SCSI command descriptor blocks (CDBs).
Overview The External Open SCSI Bus Interface Open SCSI Integrator’s Manual for NonStop Servers—422988-002 1 -4
2 Prerequisites This section describes the areas you should be familiar with before you integrate a device onto the Open SCSI interface: • • Subject Knowledge on page 2-1 (including related manuals, specifications, and reference documents) Regulatory Compliance on page 2-2 Subject Knowledge Listed here are subjects related to Open SCSI that developers and integrators should be generally knowledgeable about before starting their work. Table 2-1.
Regulatory Compliance Prerequisites Regulatory Compliance A complete listing of safety and regulatory compliance statements appears in the section Safety and Compliance in the back of this manual. Generally, regulatory compliance requirements for electronic equipment fall into two categories: product safety, and electromagnetic compatibility (EMC). These requirements vary according to the state, country, and area in which your system operates.
3 Integrating Hardware This section describes the hardware tasks required to attach devices to the Open SCSI bus, and lists specifications for necessary hardware.
Electrostatic Discharge (ESD) Precautions Integrating Hardware Figure 3-1 illustrates how to use an ESD kit when servicing a CRU. Figure 3-1. Using ESD Protection When Servicing a CRU System enclosure (appearance side) Grounding clip of ESD wriststrap attached to door latch stud ESD wriststrap with grounding clip Antistatic floor mats Antistatic table mat. Mat should be connected to a soft ground (1 megohm min. to 10 megohm max.) Clip 15-foot straight ground cord to screw on grounded outlet cover.
Configuring SCSI Connections Integrating Hardware Configuring SCSI Connections This section discusses SCSI configurations on the following NonStop S-series CRUs: • • • PMF CRU IOMF CRU 6760 ServerNet device adapter (ServerNet/DA) SCSI Configurations on the PMF CRU and IOMF CRU PMF CRUs and IOMF CRUs are configured the same for SCSI connections. Therefore, the text and illustrations refer to both PMF CRUs and IOMF CRUs.
SCSI Configurations on the PMF CRU and IOMF CRU Integrating Hardware Dual-Path Configuration Figure 3-3 shows the dual-path configuration. Each device on the bus is accessed through two SCSI SACs: one in each PMF CRU or IOMF CRU. This dual-path configuration is more fault-tolerant than the single-path because each device on the bus can be accessed using either SCSI SAC. Therefore, if one SCSI SAC fails, any device on the bus still can be accessed, using the other SCSI SAC.
SCSI Configurations on the 6760 ServerNet/DA Integrating Hardware SCSI Configurations on the 6760 ServerNet/DA The 6760 ServerNet/DA differs from the PMF CRU and the IOMF CRU in the following ways: • • • • The terminators on its SCSI ports are built into the SCSI SAC. Each port connects to a separate SCSI SAC. Terminators are built into its SCSI SACs, so the 6760 ServerNet/DA does not need a passthrough terminator.
SCSI Configurations on the 6760 ServerNet/DA Integrating Hardware Figure 3-4. Single-Path and Dual-Path Configurations On 6760 ServerNet/DA 6760 ServerNet/DA 6760 ServerNet/DA SINGLE -PATH CONFIGURATION SCSI terminator External device SCSI bus External device SCSI ports with built-in bus terminators External device SCSI bus External device DUAL-PATH CONFIGURATION SCSI bus SCSI bus External device SCSI port with built-in bus terminator CDT 027 .
Assigning SCSI ID Numbers Integrating Hardware Assigning SCSI ID Numbers Note. Do not configure two devices on the same SCSI bus with the same SCSI ID. If you do configure two devices on the same SCSI bus with the same SCSI ID, results are unpredictable. Whether your system operates on a single-path bus configuration or a dual-path bus configuration, an external device can be assigned a SCSI ID in the range of 0 through 5.
Specifications Integrating Hardware Specifications This subsection lists the specifications for external SCSI bus cables, external SCSI bus cable connectors, SCSI port connector pinouts, and SCSI cable lengths. External SCSI Bus Cables An external SCSI bus cable connects an external device on a SCSI bus to the SCSI port connector on a PMF CRU, IOMF CRU, or the S-PIC on a 6760 ServerNet/DA. These cables are available for purchase from HP in four lengths and are listed in Table 3-2 on page 3-10.
SCSI Port Connector Pinouts Integrating Hardware Table 3-1.
Cable Lengths Integrating Hardware Cable Lengths The maximum cumulative length of the SCSI cable is 82 feet (25 meters). The cumulative length of the SCSI cable is the sum of the lengths of each of the cables that connect the device to the SCSI bus, plus the sum of the length from the input connector to output connector within the device on the bus. SCSI cables can be purchased from HP in the lengths listed in Table 3-2.
4 The Open SCSI I/O Process (IOP) This section describes software topics associated with writing device drivers to interface with the Open SCSI I/O process (IOP), including Common Access Method (CAM) control blocks (CCBs). CAM operations, and IOP status values.
The Open SCSI I/O Process (IOP) Using the FILE_OPEN_ Procedure The remainder of this subsection discusses only those aspects of these Guardian procedure calls that apply to the Open SCSI interface. Note. For a complete description of the purpose, use, syntax, parameters, and limitations of the Guardian procedure calls, refer to the Guardian Procedure Calls Reference Manual.
The Open SCSI I/O Process (IOP) Using the WRITEREAD[X] Procedures nowait-depth This parameter is optional. If nowait-depth is present and nonzero, it specifies the number of nowait I/O operations that can be in progress for the file concurrently with other processing. The Open SCSI IOP supports nowait I/O and a limit of 15 nowait I/O operations. sync-depth This parameter is optional.
The Open SCSI I/O Process (IOP) Using the WRITEREAD[X] Procedures filenum When an application or driver successfully opens a SCSI device, a file-number value is returned. This value should be passed to the filenum parameter when calling WRITEREAD to send SCSI commands to the device. buffer This parameter specifies the buffer that contains control information as well as any data the application or driver sends to or receives from the device.
Structure of the WRITEREAD Buffer The Open SCSI I/O Process (IOP) Structure of the WRITEREAD Buffer The buffer passed to and returned from the WRITEREAD procedure contains a header block, a control field whose structure corresponds to that of a CAM control block (CCB), an optional sense-buffer field, and an optional data-buffer field. Figure 4-1 shows the basic layout of the buffer. Figure 4-1. WRITEREAD Buffer Structure Header Block CCB Sense Buffer (optional) Data Buffer (optional) CDT 006.
The WRITEREAD Buffer Header Block The Open SCSI I/O Process (IOP) Figure 4-2. WRITEREAD Buffer Structure for Read Operation Header Block CCB Sense Buffer (optional) Data Buffer (optional) Write Count Read Count CDT 007.CDD Figure 4-3 shows an example of the read count and write count for an operation that writes data to a device.
The WRITEREAD Buffer Header Block The Open SCSI I/O Process (IOP) Figure 4-4. WRITEREAD Buffer Header Block Structure Header Block hdr_begin ("PASS") hdr_size CCB version buffer_status Sense Buffer (optional) ccb_offset Data Buffer (optional) spare_1 spare_2 hdr_end ("THRU") CDT 009.
The Open SCSI I/O Process (IOP) The WRITEREAD Buffer Header Block ccb_offset This two-byte field contains the value of the byte offset of the CCB from the beginning of the WRITEREAD buffer. It can be the same value as the hdr_size field or some other size if the application programmer wants to put additional information or padding between the header block and the CCB. spare_1 This two-byte field is reserved for future use. spare_2 This two-byte field is reserved for future use.
The Open SCSI I/O Process (IOP) The CAM Control Block (CCB) The CAM Control Block (CCB) When you use the Open SCSI interface, the CCB control field in the WRITEREAD buffer must correspond exactly to the structure of a CCB for each CAM operation, even if not all the fields of the CCB are needed by a particular operation.
The CAM Control Block (CCB) The Open SCSI I/O Process (IOP) Table 4-1.
The CAM Control Block (CCB) The Open SCSI I/O Process (IOP) Table 4-2. Cam-Flag Bits (page 2 of 2) Flag Byte Supported by Open SCSI IOP? Bits Description 6 Initiate synchronous transfers 1 = Initiates 0 = No effect Yes Supported only with the Set I/O Characteristics operation. 5 Disable synchronous transfers 1 = Disables 0 = No effect Yes Supported only with the Set I/O Characteristics operation.
The Open SCSI I/O Process (IOP) • The CAM Control Block (CCB) For compatibility with future implementation, the application or peripheral driver should place into this field the address of the CCB in its own address space. Basic CCB Structure Table 4-3 shows the basic CCB structure, which is used for the following CAM operations (see also Table 4-1 on page 4-9). • • • • No Operation Release SIM Queue Reset SCSI Device Set I/O Characteristics Table 4-3.
The Open SCSI I/O Process (IOP) The CAM Control Block (CCB) CCB Structure for Abort SCSI Command The CCB structure shown in Table 4-4 is used for only one of the supported CAM operations, Abort SCSI Command (see also Table 4-1 on page 4-9). Table 4-4.
The Open SCSI I/O Process (IOP) The CAM Control Block (CCB) Table 4-5.
SIM Queue Operations The Open SCSI I/O Process (IOP) SIM Queue Operations The Open SCSI implementation of the SCSI Interface Module (SIM) queue and its operations is derived from the existing queuing mechanism within the I/O subsystem. The rules of operation that are specific to the Open SCSI interface are: • • • • • Freezing the SIM queue results in setting the I/O subsystem’s queue to a level that prevents normal I/O operation.
The Open SCSI I/O Process (IOP) File-System (FESTATUS) Error-Code Values Table 4-6. File-System Error Codes and Their Meanings (page 1 of 3) Error Code Corresponding FESTATUS Literal 0 FEOK No error detected by IOP in command execution. However, also check the CAM status values (Table 4-8 on page 4-20) and SCSI status values (Table 4-9 on page 4-21). 2 FEINVALOP Check for one of the following causes: • Diagnostic operations had an incorrect buffer length.
File-System (FESTATUS) Error-Code Values The Open SCSI I/O Process (IOP) Table 4-6. File-System Error Codes and Their Meanings (page 2 of 3) Error Code Corresponding FESTATUS Literal 28 FETOOMANY The IOP cannot process the I/O request at this time. When an application receives this error code in response to an operation, it should wait a small amount of time and retry the operation.
File-System (FESTATUS) Error-Code Values The Open SCSI I/O Process (IOP) Table 4-6. File-System Error Codes and Their Meanings (page 3 of 3) Error Code Corresponding FESTATUS Literal 190 FEDEVERR This is a generic, catch-all error code used when there is some problem communicating with the device and the IOP cannot return a more specific error status. 193 FENOMICROCODE The controller detected invalid microcode when it was started. The controller is not operational and should be reloaded.
Buffer-Status Values The Open SCSI I/O Process (IOP) Note. For a complete description of the Guardian file-system error messages, error codes and their meanings, and the cause, possible effect on the system, and recommended recovery action for each message, refer to the Guardian Procedure Errors and Messages Manual. Buffer-Status Values Buffer status is indicated by a two-byte field in the WRITEREAD buffer header block (see Figure 4-4 on page 4-7).
The Open SCSI I/O Process (IOP) CAM-StatusValues CAM-StatusValues The CAM-status field is supported in the CAM structure used in Open SCSI passthrough mode. Because of the nature of the WRITEREAD procedure call, which is used in the Open SCSI interface, polling the CAM-status field in the buffer does not detect completion of the request. An AWAITIO[X] procedure call must be used to detect completion of the request and transfer of the data back to the user buffer.
SCSI-Status Values The Open SCSI I/O Process (IOP) Table 4-8. CAM-Status Values and Their Meanings (page 2 of 2) CAM-Status Value (in hex) Meaning 1B A software error occurred. 40 The SIM queue is frozen. 80 Autosense data is available. SCSI-Status Values The SCSI status value from the CAM operation Execute SCSI I/O is put into the appropriate field in the CAM structure and return-d to the application.
The Open SCSI I/O Process (IOP) Open SCSI Integrator’s Manual for NonStop Servers—422988-002 4- 22 SCSI-Status Values
5 Configuring Open SCSI Devices This section describes the software and hardware tasks required for configuring devices on the Open SCSI bus. Viewing Configuration Information About Open SCSI Devices You use the Subsystem Control Facility (SCF) INFO SCSI command to display configuration information about Open SCSI devices. For complete details about the INFO SCSI command including command syntax, see the SCF Reference Manual for the Storage Subsystem.
Example of an INFO SCSI Summary Report Configuring Open SCSI Devices Summary Report Information The fields shown in the previous example of a summary report have the following meanings: * indicates an attribute whose value you can change with the SCF ALTER SCSI command. For more information, see Altering Open SCSI Attribute Values on page 5-7. Primary Location shows the physical location of the PMF CRU, IOMF CRU, or 6760 ServerNet/DA that controls the primary access path to the Open SCSI device.
Example of an INFO SCSI Detailed Report Configuring Open SCSI Devices Example of an INFO SCSI Detailed Report The command INFO SCSI $DEV5, DETAIL produces a detailed report such as the following. STORAGE - Detailed Info DEVICE $DEV5 I/O Process Configuration Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................ *Program............................... *RecSize............................... *StartState...........................
Example of an INFO SCSI Detailed Report Configuring Open SCSI Devices Detailed Report Information The fields shown in the previous example of a detailed report have the following meanings. I/O Process Configuration Information The following Open SCSI I/O process configuration information is listed in the detailed report produced by the INFO SCSI, DETAIL command: * indicates an attribute whose value you can change with the SCF ALTER SCSI command.
Configuring Open SCSI Devices Example of an INFO SCSI Detailed Report SCSI ID shows the SCSI ID of the Open SCSI device. This is the address used by the Open SCSI IOP to access the device. SCSI ID numbers are in the range 0 through 5. StructAreaSize shows the amount of memory (in 1-kilobyte units) to be allocated for data structures by the Open SCSI IOP. TraceBufLen shows the amount of memory (in 1-kilobyte units) to be allocated for internal trace data by the Open SCSI IOP.
Adding an Open SCSI Device Configuring Open SCSI Devices Adding an Open SCSI Device To add an Open SCSI device to the system configuration database, do the following: 1. If the device has already been installed, check that the device is installed properly. Verify the physical location (group, module, and slot) and the SCSI ID of the device. If the Open SCSI device has not been installed yet, first install the device following the instructions in the Himalaya S-Series Hardware Installation Guide. 2.
Configuring Open SCSI Devices Altering Open SCSI Attribute Values Altering Open SCSI Attribute Values Before you use the SCF ALTER SCSI command, review the ALTER SCSI considerations in the SCF Reference Manual for the Storage Subsystem. You use the ALTER SCSI command to change the configured attribute values for Open SCSI devices attached to your system. To display the results of the changes you have made, see Viewing Configuration Information About Open SCSI Devices on page 5-1.
Deleting an Open SCSI Device Configuring Open SCSI Devices • To change $DEV1 so that its Open SCSI IOP runs only at a low PIN and then check to make sure that the change took place, you issue commands such as: -> ALTER SCSI $DEV1, HIGHPIN OFF -> INFO SCSI $DEV1, DETAIL STORAGE - Detailed Info SCSI $DEV1 I/O Process Configuration Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................ *Program...............................
Configuring Open SCSI Devices Changing the Name of an Open SCSI Device 3. Use the SCF NAMES command to verify that the Open SCSI device has been removed from the system configuration database. For example: -> NAMES $ZZSTO, SUB SCSI STORAGE Names SUBSYS \ALM171.$ZZSTO SCSI $DEV1 Refer to the SCF Reference Manual for the Storage Subsystem for more detailed information.
Configuring Open SCSI Devices Changing the Name of an Open SCSI Device Open SCSI Integrator’s Manual for NonStop Servers—422988-002 5- 10
6 Managing Open SCSI Devices This section describes how to display status information and control Open SCSI devices Open SCSI Object States and Substates The state and substate of a SCSI object describe the status of the Open SCSI device or path to the device. Table 6-1 lists SCSI DEVICE object states and substates. Table 6-1. SCSI DEVICE Object States and Substates State Substate Description STARTED (none) The Open SCSI device is available. STOPPED (none) The Open SCSI device is not available.
Example of a STATUS SCSI Detailed Report Managing Open SCSI Devices Summary Report Information The fields shown in the previous example of a summary report have the following meanings: LDev shows the logical device number for the Open SCSI device. This number is arbitrarily assigned to a device when the device is configured and every time the system is loaded. Primary shows the current SCF state for the primary access path to the device (see Table 6-1 on page 6-1).
Example of a STATUS SCSI Detailed Report Managing Open SCSI Devices Detailed Report Information The following subsections describe the fields in the STATUS SCSI detailed report. SCSI Path Information The following Open SCSI device path information is provided in the detailed report produced by the STATUS SCSI, DETAIL command: LDev shows the logical device number for the Open SCSI device. This number is arbitrarily assigned to a device when the device is configured and every time the system is loaded.
Example of a STATUS SCSI Detailed Report Managing Open SCSI Devices SIM Queue Status shows the current status of the SCSI Interface Module (SIM) queue. The status can be FROZEN or UNFROZEN. When the SIM Queue Status is FROZEN, the application is responsible for the error recovery process. The rules of operation when the SIM queue is frozen are: • • • • • This condition prevents normal I/O operations. The IOP can initiate an I/O recovery operation while the SIM queue is frozen.
Viewing the Object Names of Open SCSI Devices Managing Open SCSI Devices Viewing the Object Names of Open SCSI Devices You use the SCF NAMES command to view the object names of any objects managed by the storage subsystem. The NAMES command does not change the state of any object. For complete details about the NAMES command including command syntax, see the SCF Reference Manual for the Storage Subsystem.
Managing Open SCSI Devices Starting an Open SCSI Device Report Information The fields shown in the previous examples of NAMES reports have the following meanings: SUBSYS shows the name of the storage subsystem manager process. DISK shows a list of the names of the DISK objects associated with the storage subsystem manager process. SCSI shows a list of the names of the Open SCSI objects associated with the storage subsystem manager process.
Managing Open SCSI Devices Example Example To stop the Open SCSI device $DEV0, enter: -> STOP $DEV0 Replacing an Open SCSI Device To replace an Open SCSI device, do the following: 1. Stop access to the Open SCSI device. For: -> STOP $DEV0 2. Physically remove the device from the SCSI chain. 3. Configure the SCSI ID on the replacement device according to the manufacturer’s instructions. 4. Install the replacement device in the SCSI chain. 5.
Managing Open SCSI Devices Replacing an Open SCSI Device Open SCSI Integrator’s Manual for NonStop Servers—422988-002 6 -8
7 The SCSI SAC The SCSI ServerNet addressable controller (SAC) is part of the PMF CRU, the IOMF CRU, and the SCSI Plug-In Card (PIC) on the 6760 ServerNet/DA. The SCSI SACs control the SCSI buses for the SCSI ports on these NonStop S-series CRUs. This section describes the SCSI SACs on PMF CRUs, IOMF CRUs, and S-PICs on the 6760 ServerNet/DAs.
SCSI SAC Bus-Phase Sequences The SCSI SAC SCSI SAC Bus-Phase Sequences The SCSI SAC supports all SCSI-2 bus phases. Table 7-1 shows how SCSI SAC busphase sequences correspond to the bus phases described in the SCSI-2 specification. Table 7-1.
Supported Bus-Phase Transitions The SCSI SAC Figure 7-1. Typical SCSI SAC Bus-Phase Sequence Bus-Free Phase Selection Phase Data Phase Status Phase Message-Out Phase Message-In Phase Command Phase Bus-Free Phase CDT 011.CDD Supported Bus-Phase Transitions Table 7-2 lists all allowable bus-phase transitions supported by the SCSI SAC. The leftmost column of this table lists the SCSI SAC bus phases that wait for a target busphase transition.
Supported Bus-Phase Transitions The SCSI SAC Table 7-2.
Bus-Free Phase The SCSI SAC Bus-Free Phase The bus-free phase is the quiescent condition that exists after a command completion, reset, timeout, or disconnect, while the SCSI bus waits for the next command. The SCSI bus exits the bus-free phase only in response to a selection sequence or reselection sequence. Selection Sequence The selection sequence is initiated by the SCSI SAC from the bus-free phase. This sequence consists of an arbitration phase and a selection phase.
Command Sequence The SCSI SAC Command Sequence The command sequence is initiated when the target enters the command phase. During the command phase, the command descriptor block (CDB) is sent to the target by the SCSI SAC. The target is permitted to retry the command phase as described under Target-Initiated Retry on page 7-11. Retrying the command phase by any other means is invalid. There are other command-phase transitions that are not permitted (see Table 7-2 on page 7-4).
Termination Sequence The SCSI SAC Termination Sequence The termination sequence is initiated by the SCSI SAC to terminate a SCSI operation. The SCSI SAC enters this sequence when it detects an error affecting the SCSI operation or when it must perform a soft reset. The SCSI SAC can enter this sequence from any other sequence except during the arbitration phase or bus-free phase. The SCSI SAC asserts the ATN signal, then waits for the target to make the transition to the message-out phase.
Command Complete (00) The SCSI SAC Command Complete (00) The target issues the Command Complete message in the message-in phase to indicate to the SCSI SAC that a SCSI operation has been completed and that valid status has been sent to the SCSI SAC. The SCSI SAC expects the target to present this message following a status phase. When the SCSI SAC accepts this message without a SCSI ATN signal, the target should make a transition to the bus-free phase.
Initiator Detected Error(05h) The SCSI SAC phase. The target must reconnect using a reselection sequence to continue the current SCSI operation. This message is valid only if the privilege to disconnect has been granted by the SCSI SAC. Otherwise, the SCSI SAC responds with a Message Reject message to prevent the target from disconnecting. If the target proceeds with the unauthorized disconnection, the SCSI SAC treats this as an unexpected disconnect.
Message Parity Error (09h) The SCSI SAC Message Parity Error (09h) In the message-out phase, the SCSI SAC issues the Message Parity Error message to inform the target that the SCSI SAC has received a message with bad parity. This provides a means for the target to return to the message-in phase to resend the message. The SCSI SAC expects the next phase to be a message-in phase or status phase.
Reconnection The SCSI SAC cycle. The SCSI SAC is set to the default agreement following a SCSI RST condition or a SCSI SAC power on/off cycle. Reconnection A target LUN with disconnection privilege is allowed to disconnect from the Open SCSI target-to-SCSI SAC interface after the completion of a Disconnect message sequence. The interrupted SCSI operation can be resumed by the target through the reselection sequence.
SCSI ATN (Attention) Signal The SCSI SAC • A valid Command Complete message received from the target When the target makes a transition to the bus-free phase at any other time, the SCSI SAC treats this as a target error condition. Unexpected disconnection causes the SCSI SAC to terminate the SCSI operation and report an error to the host. SCSI ATN (Attention) Signal The SCSI ATN (attention) signal is used by the SCSI SAC to request the target to enter the message-out phase.
Safety and Compliance Regulatory Compliance Statements The following warning and regulatory compliance statements apply to the products documented by this manual. Warning (FCC) This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Safety and Compliance Regulatory Compliance Statements Open SCSI Integrator’s Manual for NonStop Servers—422988-002 Statements -2
Regulatory Compliance Statements Safety and Compliance DECLARATION OF CONFORMITY Supplier Name: Supplier Address: COMPAQ COMPUTER CORP., NonStop DIVISION Compaq Computer Corporation, NonStop Division 10300 North Tantau Ave Cupertino, CA 95014, USA Represented in the EU By: Compaq Computer EMEA GmbH P.O.
Safety and Compliance Consumer Safety Statements Consumer Safety Statements Customer Installation and Servicing of Equipment The following statements pertain to safety issues regarding customer installation and servicing of equipment described in this manual. • • Keep door closed for normal operation. Batteries must be disposed of in compliance with local ordinances. Caution.
Safety and Compliance Consignes de sécurité à l'intention du client Consignes de sécurité à l'intention du client Installation et entretien du système par le client Les consignes de sécurité qui suivent concernent l'installation et l'entretien par le client du système décrit dans le présent manuel. • • Garder la porte fermée pendant le fonctionnement normal du système. Jeter les piles usagées conformément au règlement local en vigueur. Attention.
Safety and Compliance Verbraucher-Sicherheitsangaben Verbraucher-Sicherheitsangaben Geräteinstallation und -wartung durch den Kunden Die folgenden Angaben betreffen Sicherheitsfragen in Hinsicht auf die Geräteinstallation und -wartung durch den Kunden, wie sie in diesem Handbuch beschrieben werden. • • Tür für normalen Betrieb geschlossen lassen. Batterien müssen in Übereinstimmung mit örtlichen Vorschriften beseitigt werden. Vorsicht.
Safety and Compliance Declaraciones sobre la seguridad del consumidor Declaraciones sobre la seguridad del consumidor Instalación y servicio al equipo por el consumidor Las siguientes declaraciones tienen que ver con aspectos de seguridad relacionados con la instalación y servicio al equipo por el consumidor, y que se describen en este manual. • • Mantenga la puerta cerrada durante la operación normal del equipo. Las baterías (pilas) deben desecharse cumpliendo con los reglamentos locales. Precaución.
Safety and Compliance Forbrugersikkerhedsmeddelelser Forbrugersikkerhedsmeddelelser Installation og service af udstyr der udføres af kunden De følgende meddelelser vedrører sikkerheden angående installation og service af udstyr, der udføres af kunden, som beskrives i denne brugerhåndbog. • • Hold lugen lukket under normal drift. Batterierne skal kasseres i overensstemmelse med lokale vedtægter.
Safety and Compliance Veiligheidsinstructies voor de consument Veiligheidsinstructies voor de consument Installatie en onderhoud van apparatuur door de klant De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur. • • Houd bij normaal bedrijf de deur gesloten. Batterijen moeten overeenkomstig de plaatselijke voorschriften worden weggegooid. Opgelet.
Safety and Compliance Käyttöturvaa koskevia huomautuksia Käyttöturvaa koskevia huomautuksia Asiakkaan suorittama laiteasennus ja huolto Seuraavat huomautukset koskevat turvallisuusnäkökohtia, jotka asiakkaan täytyy ottaa huomioon tässä käsikirjassa kuvattuja laiteasennuksia ja huoltotoimenpiteitä suoritettaessa. • • Kansi täytyy pitää suljettuna normaalin käytön aikana. Paristot täytyy hävittää paikallisten säädösten mukaisesti. Varoitus.
Safety and Compliance Veiligheidsinstructies voor de consument Veiligheidsinstructies voor de consument Installatie en onderhoud van apparatuur door de klant De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur. • • Houd bij normaal bedrijf de deur gesloten. Batterijen moeten overeenkomstig de plaatselijke voorschriften worden weggegooid. Opgelet.
Safety and Compliance Misure precauzionali per i clienti Misure precauzionali per i clienti Installazione e manutenzione del sistema da parte del cliente Le seguenti misure precauzionali riguardano l’installazione e la manutenzione da parte del cliente del sistema descritto nel presente manuale. • • Mantenere la porta chiusa durante il funzionamento normale del sistema. Lo smaltimento delle batterie usate deve essere effettuato secondo la normativa locale. Avvertenza.
Safety and Compliance Informações de segurança para os consumidores Informações de segurança para os consumidores Instalação e manutenção do equipamento pelo cliente As seguintes informações se referem a questões de segurança relacionadas à instalação e manutenção, pelo cliente, do equipamento descrito neste manual. • • Para garantir o funcionamento normal, mantenha a porta fechada. As pilhas usadas devem ser descartadas de acordo com as leis locais. Cuidado.
Safety and Compliance Informações de segurança para os consumidores Informações de segurança para os consumidores Instalação e manutenção do equipamento pelo cliente As seguintes informações referem-se a questões de segurança relacionadas à instalação e manutenção, pelo cliente, do equipamento descrito neste manual. • • Para garantir o funcionamento normal, mantenha a porta fechada. As pilhas usadas devem ser descartadas de acordo com as leis locais. Cuidado.
Safety and Compliance Meddelanden beträffande konsumentsäkerhet Meddelanden beträffande konsumentsäkerhet Kundutförd installation och service De följande meddelandena beskriver säkerhetsföreskrifter för kundutförd installation och service av utrustning som beskrivs i denna manual: • • Dörren skall vara stängd under normal drift. Batterier måste kasseras i enlighet med lokala förordningar.
Safety and Compliance Kundutförd installation och service S7x000 Open SCSI Integrator’s Manual for NonStop Servers—422988-002 Statements- 16
Safety and Compliance Kundutförd installation och service S7x000 Open SCSI Integrator’s Manual for NonStop Servers—422988-002 Statements- 17
Safety and Compliance Kundutförd installation och service S7x000 Open SCSI Integrator’s Manual for NonStop Servers—422988-002 Statements- 18
Glossary ACL. See automatic cartridge loader (ACL). action. An operation that can be performed on a selected resource. adapter. See ServerNet adapter. adapter cable. (1) A cable that connects components that have incompatible electrical interfaces. (2) For the ServerNet wide area network (SWAN) concentrator, one of four types of cable that can connect any of the six 50-pin WAN ports to one of the supported electrical interfaces (RS-232, RS-449, X.21, or V.35). ADAPTER object type.
Glossary backplane backplane. A board that has connectors, on one or both sides of the board, into which circuit board assemblies plug. Backplanes are located behind card cages. backup processor. A processor in the HP NonStop operating system that communicates with the primary processor, allowing the processors to remain independent. A component failure in one processor has no effect on any other processor. Contrast with primary processor. base enclosure.
Glossary carrier carrier. (1) A sheet-metal structure that allows a single-high ServerNet adapter to be installed in a ServerNet adapter slot designed for a double-high ServerNet adapter. (2) An electrical signal that carries data. CCSA. See Common Communication ServerNet adapter (CCSA). CE. Customer engineer. See service provider. central processing unit (CPU). Historically, the main data processing unit of a computer. A a Himalaya system has multiple cooperating processors rather than a single CPU.
Glossary Communications Management Interface (CMI) and a software interface to the host. The CLIP stores and implements specific communications protocols. Communications Management Interface (CMI). A utility used in D-series and earlier releases to make online changes to the configuration of ATP6100, CP6100, and EnvoyACP/XF communications subdevices. In G-series releases, CMI functions are performed by the Subsystem Control Facility (SCF). communications subsystem.
Glossary correctable memory error (CME) correctable memory error (CME). An error caused by incorrect data at a particular memory location. The cause of the error is such that the error is automatically corrected by the system. Contrast with uncorrectable memory error (UCME). COUP. See Configuration Utility Program (COUP). CPU. See central processing unit (CPU). CRU. See customer-replaceable unit (CRU). current configuration file. See configuration file. customer engineer (CE). See service provider.
Glossary Distributed Systems Management (DSM) Distributed Systems Management (DSM). A set of tools used to manage NonStop systems and Expand networks. double-high ServerNet adapter. A ServerNet adapter that occupies an entire ServerNet adapter slot in a Himalaya S-series server. Contrast with single-high ServerNet adapter. double-high stack. A stack that includes a base, a frame, and two system enclosures. Contrast with single-high stack. downtime.
Glossary EMI EMI. See electromagnetic interference (EMI). EMS collector. An Event Management Service (EMS) process to which subsystems report events. enclosure. Similar to a cabinet in Himalaya K-series systems. An enclosure can contain components of a system or a peripheral. Base enclosures are placed on the floor and can have other enclosures stacked on top of them. Stackable enclosures can be placed on top of other enclosures. See also system enclosure and peripheral enclosure. enclosure interleaving.
Glossary fault tolerance fault tolerance. The ability of a NonStop system to continue processing despite the failure of any single software or hardware component within the system. FESA. See Fast Ethernet ServerNet adapter (FESA). field-replaceable unit (FRU). A unit that can be replaced in the field. FRUs that are not also customer-replaceable units (CRUs) can be replaced only by qualified personnel trained by HP and cannot be replaced by customers. See also customer-replaceable unit (CRU). file name.
Glossary GB GB. See gigabyte (GB). GCSC. See Global Customer Support Center (GCSC). gigabyte (GB). A unit of measurement equal to 1,073,741,824 bytes (1024 megabytes). See also kilobyte (KB) and megabyte (MB). Global Customer Support Center (GCSC). A support organization that provides telephone and remote diagnostic support for NonStop customers. There are GCSCs located all over the world. See also Online Support Center (OSC). graphical user interface (GUI).
Glossary indicator lights indicator lights. Two lights on a customer-replaceable unit (CRU) that indicate the status of the unit. The red or amber indicator light is lit when the unit is not working properly; during startup, this light can indicate that the unit is not yet functioning. The green indicator light is lit when the unit has proper power applied. See also light-emitting diode (LED). input/output process (IOP).
Glossary IOP an external ServerNet port, and three SCSI ServerNet addressable controllers (SACs) in a single unit. The IOMF CRU consists of three subassemblies: the multifunction I/O board (MFIOB), the ServerNet buffer board (SBB), and the power supply subassembly. IOP. See input/output process (IOP). IP. See Internet protocol (IP). IP address. An address that identifies a specific host to the Internet protocol (IP).
Glossary line interface unit (LIU) line interface unit (LIU). A dual-ported unit consisting of two parts: a communications line interface processor (CLIP) and a line interface module (LIM). An LIU can communicate with either the primary or the backup processor, providing fault tolerance. When it is a component of the communications subsystem, an LIU communicates with either processor through either of a pair of communications interface units (CIUs). LIU. See line interface unit (LIU). LMU.
Glossary main memory When the HP NonStop operating system is not running, communication must take place over a low-level link. You can also communicate with a NonStop S-series server over a low-level link when the operating system is running. See also service connection. main memory. Data storage, specifically the chips that store the programs and data currently in use by a processor.
Glossary MRouter MRouter. A field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC) that is part of the serial maintenance bus (SMB) architecture. The MRouter distributes the SMB throughout a group. MSP. See master service processor (MSP). multifunction I/O board (MFIOB).
Glossary offline offline. (1) Used to describe tasks that are performed outside of the control of an application or computer system. (2) Used to describe tasks that require system resources to be shut down. Contrast with online. offline change. Any change that requires system resources to be shut down. Offline changes are usually performed during a planned outage. Contrast with online change. offline configuration. Configuration performed offline by SYSGENR.
Glossary owner owner. (1) In the case of a disk file, the user or program that created the file, or a user or program to whom the creator has given the file with the File Utility Program (FUP) GIVE command. (2) In the case of a process, the user or program that created the process or, if the PROGID option was specified in the File Utility Program (FUP) SECURE command for the code file, the user or program that owns the code file.
Glossary plug-in card (PIC) plug-in card (PIC). A replaceable component used in some ServerNet adapters to provide a hardware option for the adapter. PMB. See processor and memory board (PMB). PMCU. See power monitor and control unit (PMCU). PMF CRU. See processor multifunction (PMF) CRU. Point-to-Point Protocol (PPP). A data communications protocol that provides a standard method of encapsulating Transmission Control Protocol over Internet Protocol (TCP/IP) information over point-to-point links.
Glossary primary path primary path. A path enabled as the preferred path. When a primary path is disabled, an alternate path becomes the primary path. Contrast with alternate path. primary processor. The processor that is designated as “owning” the ServerNet addressable controller (SAC) connected to separate processors running the NonStop operating system. The primary processor is the processor that has direct control over the SAC. Contrast with backup processor. process.
Glossary reconfiguration reconfiguration. The act of changing the hardware or software configuration of a running system. Examples include installing a new software release, adding hardware peripherals, and restructuring a database. Reconfiguring a system might or might not require a planned outage. remote access. For TSM, a form of remote support. Remote access, or dial-in, allows a service provider to dial in to your NonStop S-series server to diagnose hardware and software problems.
Glossary SE SE. System engineer. See service provider. SEB. See ServerNet expansion board (SEB). serial maintenance bus (SMB). A bus that connects service processors (SPs) within an enclosure to each other and to the customer-replaceable units (CRUs) in the group. serial maintenance bus (SMB) domain. The set of enclosures, modules, field-replaceable units (FRUs), and customer-replaceable units (CRUs) connected by a common serial maintenance bus (SMB). server.
Glossary ServerNet diagram contains up to four ServerNet addressable controllers (SACs), each of which can control either disk drives or tape drives. ServerNet diagram. A graphical layout of the logical connections between objects in the system. These objects can include processors, ServerNet routers, ServerNet adapters, disks on the SCSI bus, and so on. ServerNet dump. To copy the memory of a processor to disk using the ServerNet system area network (ServerNet SAN). ServerNet expansion board (SEB).
Glossary ServerNet port ServerNet port. A connector used for ServerNet links. Six ServerNet ports are located on a ServerNet expansion board (SEB). ServerNet router. An application-specific integrated circuit (ASIC) responsible for providing interconnection of ServerNet links in a ServerNet system area network (ServerNet SAN). A ServerNet router is never an end device. A ServerNet router in a Himalaya Sseries server has a total of six input and six output ServerNet ports. ServerNet SAN.
Glossary single-high ServerNet adapter appearance side. Cables are accessed from the service side. System enclosures are typically arranged so that the service side is the least visible side. See also appearance side. single-high ServerNet adapter. A ServerNet adapter that occupies only the upper half of a ServerNet adapter slot in a Himalaya S-series server. Contrast with double-high ServerNet adapter. single-high stack. A stack that includes a base, a frame, and one system enclosure.
Glossary state state. In Subsystem Control Facility (SCF) subsystems, one of the generally defined possible conditions of an object with respect to the management of that object. Examples of states are DEFINED, STARTED, and STOPPED. storage subsystem. A subsystem of the NonStop operating system that handles configuration and management of disk and tape devices in G-series RVUs. subnet. See subnetwork. subnetwork. A physical network within an Internet protocol (IP) network.
Glossary system processor (CLIP) and provides a variety of management functions such as coordinating data link control (DLC) and diagnostic task downloads. system. A node. All the processors, controllers, firmware, peripheral devices, software, and related components that are directly connected together to form an entity that is managed by one operating system image and operated as one computer. system area network (SAN).
Glossary system-managed process system-managed process. Another name for a generic process. See gigabyte (GB). system operator. See local operator and remote operator. system planner. The person who plans for the hardware and software installation of a new system or for changes to a system already installed. This person arranges for site preparation, schedules the installation, and completes the Installation Documentation Packet. system process.
Glossary TCP/IP subsystem TCP/IP subsystem. A NonStop subsystem that allows the use of TCP/IP to access a NonStop host from Macintosh, personal computer, and UNIX workstations. Applications running on a NonStop system or in an Expand network can transparently exchange data with TCP/IP devices. tape drive. A device that moves magnetic tape past magnetic read/write heads, which read data from or write data to the tape. tape dump. To copy the memory of a processor to tape. tape load. A system load.
Glossary Transmission Control Protocol (TCP) transaction processing (OLTP) environments. To furnish this service, the TMF subsystem manages database transactions, keeps track of database activity through audit trails, and provides database recovery methods. Formerly called Transaction Monitoring Facility (TMF). See also NonStop Transaction Manager/MP (NonStop TM/MP). Transmission Control Protocol (TCP).
Glossary TSM Service Application TSM Service Application. A component of the TSM client software. The TSM Service Application enables you to communicate with a NonStop S-series server when the NonStop operating system is running. When the operating system is not running, communication must take place using the TSM Low-Level Link Application. See also TSM Low-Level Link Application. TSM workstation. A PC-compatible workstation on which the TSM client software is running.
Glossary WAN subsystem manager process WAN subsystem manager process. A process named $ZZWAN provided as part of the wide area network (WAN) subsystem that starts and manages the WAN subsystem objects, the WAN product process, and device objects. Subsystem Control Facility (SCF) commands are directed to the WAN subsystem manager process for configuring and managing the WAN subsystem and the ServerNet wide area network (SWAN) concentrator. wide area network (WAN).
Index Numbers B 00 7-8 01h 7-8 02h 7-8 03h 7-8 04h 7-8 05h 7-9 06h 7-9 07h 7-9 08h 7-9 09h 7-10 0Dh 7-10 6760 adapter 3-5 80h 7-10 BackupCpu, viewing 5-4 Bus Device Reset 7-10 Bus Device Reset (0Dh) 7-10 Bus-free phase 7-5 Bus-cable connector specifications 3-8 Bus-phase transitions 7-3 C A Abort (06h) 7-9 Adapter 6760 3-5 Adapter name, viewing 5-5 ADD command (SCF) 5-6 Adding an Open SCSI device 5-6 Allowable SCSI bus configurations 3-3/3-5 ALTER command (SCF) 5-2, 5-7 Arbitration phase 7-2 Assigning
Index D Changing Open SCSI attributes 5-7 Command Complete message (00) 7-8 Command descriptor block (CDB) See CDB Command phase 7-2 Command sequence 7-6 Commands ADD (SCF) 5-6 ALTER (SCF) 5-2, 5-7 DELETE (SCF) 5-8/5-9 DETAIL (SCF) 5-3/5-5 INFO (SCF) 5-1/5-5 NAMES (SCF) 6-5/6-6 START (SCF) 6-6 STOP (SCF) 6-6/6-7 Connector specifications for bus cable 3-8 Devices (continued) object states and substates 6-1 replacing 6-7 software support 1-3 starting 6-6 stopping 6-6 viewing configuration information 5-1 c
Index F F FESTATUS literals 4-15/4-19 File-system error-code values 4-15/4-19 FILE_CLOSE_ 4-1 FILE_GETINFOBYNAME_ 4-1 FILE_GETINFOLISTBYNAME_ 4-1 FILE_GETINFOLIST_ 4-1 FILE_GETINFO_ 4-1 FILE_OPEN_ 4-2/4-3 G Guardian procedure calls AWAITIOX 4-1, 4-4, 4-20 CANCELREQ 4-1 DEVICE_GETINFOBYLDEV_ 4-1 DEVICE_GETINFOBYNAME_ 4-1 FILE_CLOSE_ 4-1 FILE_GETINFOBYNAME_ 4-1 FILE_GETINFOLISTBYNAME_ 4-1 FILE_GETINFOLIST_ 4-1 FILE_GETINFO_ 4-1 FILE_OPEN_ 4-2/4-3 WRITEREADX 4-3/4-4 Guardian procedure calls supported 4-1 H
Index N Messages (continued) Abort (06h) 7-9 Bus Device Reset (0Dh) 7-10 Command Complete (00) 7-8 Disconnect (04h) 7-8 Identify (08h) 7-10 Initiator Detected Error (05h) 7-9 Message Parity Error (09h) 7-10 No Operation (08h) 7-9 Reject (07h) 7-9 Restore Pointers (03h) 7-8 Save Data Pointer (02h) 7-8 SDTR (01h) 7-8 Synchronous Data Transfer Request (01h) 7-8 Messages supported 7-1, 7-7/7-10 N NAMES command (SCF) 6-5/6-6 No Operation (08h) 7-9 NumIO, viewing 5-4 O Object file name, viewing 5-4 Open SCSI
Index S S SAC see SCSI SAC SAC name, viewing Viewing SAC name 5-5 SAC SCSI ID, viewing 5-5 SAC subdevice number, viewing 5-5 Save Data Pointer (02h) 7-8 SCF 1-3, 2-1, 4-16, 4-17, 5-1, 6-1 SCF ADD 5-6 SCF ALTER 5-2, 5-7 SCF DELETE 5-8/5-9 SCF DETAIL 5-3/5-5 SCF INFO 5-1/5-5 SCF NAMES 6-5/6-6 SCF START 6-6 SCF STOP 6-6/6-7 SCSI bus configurations 1-2/1-3, 3-3/3-6 SCSI cables see Cable specifications SCSI ID viewing 5-1, 5-2, 5-5 SCSI IDs assigning 3-7 SCSI Interface Module (SIM) queue operations 4-15, 6-4 S
Index W configuration information 5-1 status 6-1 PrimaryCpu 5-4 record size 5-4, 6-4 SAC SCSI ID 5-5 SAC subdevice number 5-5 SCSI ID 5-1, 5-2, 5-5 status of devices 6-1 StructAreaSize 5-5 TraceBufLen 5-5 TraceLevel 5-5 W Write count 4-6 WRITEREAD buffer 4-5/4-14 See also CAM control block (CCB) header block 4-6 IOP 4-5/4-14 read operation 4-6 structure header block 4-6 read operation 4-6 write operation 4-6 write operation 4-6 WRITEREADX 4-3/4-4 Open SCSI Integrator’s Manual for NonStop Servers—422988-
Reader Comment Card Mail, E-Mail, or Fax Your Comments To ATTN: Product Manager—Software Publications LOC CAC-03 Compaq Computer Corporation Tandem Division Cupertino, CA 95014-2599 pubs.comments@compaq.
