HP3000-L Archives

September 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Thu, 6 Sep 2001 11:44:31 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
> Is there a way to test whether a DEVCTRL command was
> successful?

I talked to the author just now.  He says that he doesn't explicitly
set JCW or CIERROR to indicate success or failure.  However, if the
I/O system returns an error to him, he will format the error message
and write it to $STDLIST.  Thus, you might be able to redirect the
output of DEVCTRL and scan for errors.  I asked him if it would be easy
to add the ability to detect the current device status (e.g. compression
is ON, etc.) to DEVCTRL and he replied "no".

  FYI,
  Jeff Vance, CSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2