On Wed, 16 May 2001 08:27:51 -0500, Jeff Keepers <[log in to unmask]> wrote:

>I am attempting to use the FINFO command under MPEX ver 6.0 to see if
>anyone is accessing a specific file.

I note you specifically state MPEX, not MPE/iX -- are you in fact using
VESOFT's product?

>I thought the FINFO option to use was 61 or
>''accessors".  When I attempt either one of these options, however, the
system
>returns the following error:
>
>     The option number specified is not valid for FINFO. (CIERR 9986)
>
>Am I running into a version problem?

It could be -- what does %VEVERSION return?  [this shows the same thing the
banner does, but you don't have to exit & reenter MPEX to get it :) ]

I believe MPEX has a table of FINFO parameters that it KNOWS about, so if
your version is older, it may not be in that table.  Generally, however,
VESOFT gets new releases of the OS as soon as possible in order to
compensate for new features implemented by HP such as this, so when new
releases of the OS come out, make sure you are on the most current version
of MPEX.

>The only other way I know how to do the above is to perform a
>%LISTF ,access to a temp file and then evaluate the temp
>file.  Any input would be most appreciated.

Since your purpose is to determine "if a file is being accessed", why not
use "OPENED" instead?  Check out the online help page for the word "opened"
within MPEX and you'll see four related items:

  1. OPENED, file attribute variable
  2. FMTOPENED, file attribute variable
  3. ISOPENED, spool file attribute variable
  4. OPENEDSYSFAIL, file attribute variable

Item 1 is what you want, and you can use it like this:

   %SETVAR X 0
   %while VEFINFO("target.file").OPENED
   %   PAUSE 30
   %   SETVAR X X+1
   %   if (X > 10)
   %      tellop Warning: 'target.file' has been opened too long! (5 mins)
   %   endif
   %endwhile

Item 2 is a shorthand way of testing for a file being opened AND displaying
a character if it is [used primarily in home-grown %LISTF format files]

Item 3 I (almost) always get confused with #1 -- this is the same thing,
but only applies to SPOOL files [the confusing part is that several other
boolean "attributes" are prefixed with "IS..." for normal files, and this
is one case where ISOPENED exists, but is simply the wrong attribute to be
using...]

Item 4 is less useful nowadays -- it applies to CM mode KSAM files and is
true if the system has marked the file as "opened during a system
failure".  The primary use of this attribute is to find KSAM files that
need a KSAMUTIL "keyinfo;recover" operation performed upon them...

Tom

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