Re:
>
>  When the accessor is a process in the POSiX directory I get nothing:
>
>  LIBIO   .DIAG    .SYS   MANAGER.SYS    Secured             PM Group

...not exactly "nothing" :)
...
>  SOCKET  .DIAG    .SYS   MANAGER.SYS    Secured             PM Group
>  STMXL   .DIAG    .SYS   MANAGER.SYS    Secured             PM Group
>            ..
>            ..
>            ..

Perhaps you meant "I get blanks and/or nulls for the file, group,
and account portions of the process' program file name"?

>    repeat
>      item_num_array[1] := 2015;
>      item_num_array[2] := 2002;
>      item_num_array[3] := 2034;
>      item_num_array[4] := 2035;
>      item_num_array[5] := 2095;
>      item_num_array[6] := 2131;
>      item_num_array[7] := 2033;

It's easier to maintin, and debug, if you arrange the item numbers
in ascending order.  (This applies to other intrinsics, too, like HPFOPEN.)

>      AIFPROCGET(overall_status,
>                 item_num_array,
>                 item_array,
>                 item_status_array,,
>                 pid_array_1[count_1]);
> ...
> ...
>    until condition...
>
> The AIFPROCGET errors out with a value of +6 in the overall_status.info
> field. I believe this is some kind of alignment problem between the

I'd try:

   1) display the individual item_status_array values ... perhaps that will
      tell you which parameter AIFPROCGET has a problem with.

   2) add code after your call to AIFPROCGET:

         if overall_status.all < 0 then
            begin
           ...display each value in item_num_array, and each value in
              item_array (i.e., so we can see the addresses!),
              and each value in item_status_array.
              (stopping when you get to item # 0, of course)

            display address of item_num_array, item_array, item_status_array,
            pid_array_1, and any other reference parms to AIFPROCGET.
               hint:  writeln ('item_status_array @ ',
                                 baddress (item_status_array):12);
            ...yeah, I normally never use Pascal I/O ... my code would be:

                 spout ('item_status_array @ ' +
                         hex32 (baddress (item_status_array));

   3) drop the use of item 2034 and use only 2131.
      Or:

           call for all items but 2034 and 2131

           call for 2034
           if err then call for 2131

Note that files accessed by "procreated" processes will also show up
as ".." for the process name.  These processes (e.g., PIN 3), will not have an
HFS name, so 2131 won't work any better for them.  An search of HP3000-L,
comp.sys.hp.mpe, and/or www.allegro.com will reveal how to determine the
"names" of such procesess.  (The "name" will be the name of the procedure
that was launched as a process ... for MPE, "procreate" means "procedure
create".)  (PIN 3 is generally "pm_cleanup")

--
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html

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