|
HP OpenVMS Systemsask the wizard |
|
The Question is:
I have this ISDRIVER running correctly under VMS 5.5-2. When we installed
VMS 6.2, I could not get this driver to come online. I re-macro'ed the file
and relinked per the documentation.
Do macro level drivers had to be editted to work correctly with VMS 6.2.
Thanks
-Kenneth
The box converts SCSI bus to GPIB bus signals.
.TITLE ISDRIVER - VAX/VMS GPIB-SCSI
.IDENT 'X-5'
; .LIST MEB
;***************************************************************************
;*
;* COPYRIGHT (c) 1989 BY
;* DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS.
;* ALL RIGHTS RESERVED.
;*
;* THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
;* ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
;* INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
;* COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
;* OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
;* TRANSFERRED.
;*
;* THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
;* AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
;* CORPORATION.
;*
;* DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
;* SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
;*
;*
;***************************************************************************
;++
; FACILITY:
; VAX/VMS Sample SCSI Class Driver
; ABSTRACT:
; This module contains a sample SCSI class driver. This template
; supports two modes of operation: either the SCSI command
; packets are formatted in the application program (passthru mode) or
; the SCSI command packets are formatted within the driver. In the
; latter case, command processing and error recovery are implemented
; within a third-party SCSI class driver derived from this driver.
; Passthru mode is the method of access used by the generic SCSI
; class driver (GKDRIVER). GKDRIVER provides access to a SCSI device
; from an application program. The QIO interface of the GKDRIVER
; is fixed. However, third-party SCSI class drivers can define a
; unique QIO interface. Third-party class drivers can have device
; specific error recovery, log device errors and implement
asynchronous
; event notification (AEN). Third-party class drivers have direct
access
; to the SCSI Port Interface (SPI) routines, while using the passthru
; function provides access to SCSI without writing a driver.
; The code to perform the IO$_DIAGNOSE function is included in this
; driver for informational purposes only. Typical third-party SCSI
; class drivers do not require this function. If the IO$_DIAGNOSE
; function is required, you should use the VMS-supported SCSI
; generic class driver (GKDRIVER).
; ISDRIVER supports three I/O functions:
; IO$_AVAILABLE - Inquiry and Test Unit Ready sequence,
; IO$_DIAGNOSE - Passthru function
; IO$_READLBLK - Return Inquiry data to user
The Answer is : Parts of the SCSI interface and GKDRIVER changed at OpenVMS V6.2 -- please see the associated documentation for details of these changes. (See the OpenVMS I/O User's Reference Manual, and the V6.2 new features and release notes documentation.) Device drivers can need various source code changes in order for them to operate over major OpenVMS upgrades. This particular driver appears to have been based on the example module SYS$EXAMPLES:SKDRIVER.MAR -- I would use that module as a starting point.
|