That make sense: Here is what I find in a spawn test:
I printed out the process ids for each PID that was spawned from one of my processes: pid 83886667(0x0500024B) test#1 pid 590 (0x0000024E) test#2 pid 16777806(0x0100024E) test#3 pid 589 (0x0000024D) test#4 pid 83886673(0x05000251) test#5 Looks like it could be an index or as Paul Gilmartin suggested as "...an attempt to insure long-term uniqueness..." Thanks for the info guys! ----------------- Scott Wm. Jackson Informatica Corporation ----------------- -----Original Message----- From: MVS OpenEdition [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Wednesday, January 10, 2007 11:34 AM To: [EMAIL PROTECTED] Subject: Re: [MVS-OE] USS Process Identifier (PID) information... Someone once told me that the lower 16 bits are some kind of index into a process table, the upper 8 bits are a sequence number to make the PID unique, and the other 8 bits are a sysplex identifier. Note this little experiment: [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0010000eb ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0020000eb ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0030000eb ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0040000eb ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0050000eb ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> ps -o xpid,args XPID COMMAND 0000000ea bash 0000000ec ps -o xpid,args [EMAIL PROTECTED]:/u/F4185> The lower 16 bits didn't change for the first few ps process, but the serial number did. -----Original Message----- From: MVS OpenEdition [mailto:[EMAIL PROTECTED] Behalf Of Jackson, Scott Sent: Wednesday, January 10, 2007 7:10 AM To: [EMAIL PROTECTED] Subject: USS Process Identifier (PID) information... (posted to IBM-MAIN and MVS-OE) All, A coworker just asked a question about UNIX Systems Services Process Identifiers (PIDs) that I do not have ready answer. Does the PID contain "information" relevant to the process? After looking at several PIDs we noticed that looking at the hexadecimal representation of the PID it looked like it may contain some sort of "status" flags in the first halfword... Example of some PIDS that contain, various times, 0x0100, 0x0300, and 0x0500. In others there are 0x0200 .I couldn't find anything in the POSIX standards or IBM docs... (I'm running 1.7 of z/OS FWIW)... I also didn't see these patterns in z/Linux or other OS types... Any meaning to these or am I seeing things? Thanks! Example 1 1st PID 0000 0001 decimal 1 (BPXOINIT) 2nd PID 0100 0154 decimal 16777556 PPID=1 3rd PID 0100 0145 decimal 16777541 PPID=16777556 4th PID 0000 0161 decimal 353 PPID=16777541 Example 2 1st PID 0000 000A decimal 10 (INETD) 2nd PID 0300 0151 decimal 50331985 PPID=10 3rd PID 0300 0148 decimal 50331976 PPID=50331985 4th PID 0400 01A7 decimal 67109287 PPID=50331976 Example 3 1st PID 0000 0001 decimal 1 (BPXOINIT) 2nd PID 0500 017E decimal 83886462 PPID=1 3rd PID 0500 0167 decimal 83886439 PPID=83886462 4th PID 0300 01D6 decimal 50332118 PPID=83886439 ----------------- Scott Wm. Jackson Principle Software Engineer Informatica Corporation ----------------- It's here... PowerCenter For Z/OS It's here... PowerCenter For z/Linux ---------------------------------------------------------------------- For MVS-OE subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO MVS-OE ---------------------------------------------------------------------- For MVS-OE subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO MVS-OE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
