|
DEVICE_DRIVER.MASTER indicates NV is owned by the PSI X.29 product
on OpenVMS VAX, and the Alpha device driver registry indicates the
same product owns the prefix on OpenVMS Alpha.
: Anyone got a guess as to what's happening here?
We need more information around the appliction activity, around the
failure codes, around the OpenVMS platform and version, and information
around the system event(s) that are occuring during the reported failures.
(LAT questions are likely best addressed in the NOTED::LAT conference.)
|
| > I am monitoring an application that deals with LAT (LTA) devices.
> Once in a while a different device type starting with the letters
> NVA pops up. Sometimes, after that happens I start seeing error
> codes that LTA devices are no longer available. At other times
> everything seems to be OK, that is LTA devices are still acquired
> as needed.
If you are dealing with LTA devices, how come you pick up NVA devices? What
characteristic(s) do you use to determine which devices to pick up?
What error code(s) are you seeing?
Are virtual terminals enabled?
> Anyone got a guess as to what's happening here?
My guess is you have an application bug :-)
Antonio
|
| re .1-
Thanks, that's actually all I needed to know; that the devices are
X.29 (X.25) devices.
re .2-
Yes, you're right, there is an application bug :->( With what I know
now I can deal with it better :->)
John
|