info-vax@ucbvax.ARPA (05/04/85)
From: Art Berggreen <ART@ACC>
Before I start digging into this problem, I thought I'd see if
anyone on the net has any ideas.
We have an RSX task image which runs fine under VMS 3.x. The
task does an ALUN to an RSX device name (e.g. XY0:) and does
vanilla READLBLK and WRITELBLK I/O. The native mode VMS driver
is named XYDRIVER and devices usually are XYA0:, XYB0:, ... .
Under 3.x the ALUN call would either use device spec defaults
and expand XY0: -> XYA0:, or if we provided a logical name
(either process or system wide) it would associate XY0: -> whatever.
Under 4.x the program appears to run ok, but the I/O request
doesn't seem to get to the driver's FDT routines (things just
hang waiting on I/O).
Does anyone know if the RSX emulator has changed in the way
it handles I/O request? Could the new logical name support
be affecting this (I have tried exec mode names)?
"Art Berggreen"<Art@ACC.ARPA>
------