Peter,

You commented:

>I've been working with creating processes and GETPROCINFO which work
>with 32 bit PIN's.  I understand a PIN to be a bit like a process ID
>(pid) on UNIX.

Logically similar from an application point of view.

>But then I looked at PROCINFO.  That has a 16 bit PIN which is
>documented as not being compatible with GETPROCINFO PIN's.

16-bits is the carryover from the early days when MPE ran
on 16-bit h/w. 16-bit PINs fit nicely in a 32-bit integer :-)

The documentation comment is not correct with regard to there being
more than one kind of PIN. However, the comment might be trying to
point out that these two intrinsic refer to different PIN's when you
use the value of 0 (zero).

In GETPROCINFO you pass a PIN value of 0 (zero) to request
information about your parent (father) and in PROCINFO you pass
a value of 0 (zero) to request information about yourself (caller).

duane

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