%dcl-e-open

[Richard J Maher]

Hi Steve,

[That error is very likely from a failed OPEN command and -- no matter what the target OPEN specification might be -- a DCL OPEN command isn't connected to IP nor to the BG port devices in any meaningful fashion in any available OpenVMS release. ]

What about an INETd server that does: -

$open/read/write socket sys$net

[I'd expect that the AUXS failure message is a bit of a canard, and due to the error not being fielded correctly by the connection; that the DCL error is being reflected and shown in the context of the IP processing or the IP tear-down.]

I reakon you're right.

Cheers Richard Maher

[Hein van den Heuvel]

Hmm,

I don't understand where the last series of reiplies come from. I thought it was established that the target disk was bad (partiry errors) and that the system effectivly write-locked the drive.
According to an earlier attachment, the devices status includes: "allocation inhibited because of error on bitmap,"

fwiw,
Hein.