It looks like a POSIX PID is a reversed and truncated MPE/XL PID. Within the core OS, a PID is a 64-bit field comprised of a 32-bit PIN (Process Identification Number) and a 32-bit re-use counter (which keeps track of the number of times this PIN has been allocated to a new process). It appears POSIX is changing the 2 32-bit fields to 16-bit fields and then reversing the order. From the shell: shell/iX> ps PID TTY TIME COMMAND 589890 ldev354 0:00 JSMAIN.PUB.SYS 393304 ldev354 0:00 VTSERVER.NET.SYS info=ÿÿ w 2293878 ldev354 0:00 PS.HPBIN.SYS 458951 ldev354 0:01 CI.PUB.SYS 721121 ldev354 0:01 SH.HPBIN.SYS info=-L Now, from DEBUG(after exiting the shell so those processes are gone): $42 (JSMAIN.PUB.SYS) $c7 (CI.PUB.SYS) #S187 $58 (VTSERVER.NET.SYS) First look at the PID reported for my JSMAIN: $113 ($c7) nmdebug > =#589890 $90042 Now take a look at the PID stored in the PIB (Process Information Block) for my JSMAIN: $118 ($c7) nmdebug > fv pib(42) 'pib_type.pid' 4200000009 Look familiar? I have no idea why the choice was made to reverse the fields when defining the POSIX PID, but that appears to be what was done. -- --Pete Crosby ([log in to unmask]) > >Hello, >Does anyone know how to relate PIN (as shown in GLANCE) to PID >as shown in POSIX? > >I have *some* task/program/listner that is taking over the cpu, and >can identify it using glance, but don't know what to 'kill' to >get rid of it. > >[log in to unmask] >