See the wait(2) man page for the reason why the return-code limited...
Basically, more than the return code is returned when a process
"ends" - and that consumes some flag bits.
- Dave Rivers -
>
> On Monday, 10/10/2005 at 06:45 ZE2, Carsten Otte <[EMAIL PROTECTED]> wrote:
> > Alan Altmark wrote:
> > > Eh? CP has *thousands* of return codes. I is just Plain Wrong to try
> to
> > > map them to the smaller name space of the Linux return code.
> > Good point. <me> adds mapping CP return value to Linux rc to his list of
> bad
> > ideas.
>
> If a program makes a rc = system("vmcp foo") call, will it get the full
> return code? Or can a program call vmcp in some other way?
>
> I am wondering if the problem with the 8-bittedness of the return code is
> a result of real truncation or if it's just an artifact of the shell's
> rendering of the return code. Maybe we should fix it? I think DJ is
> right: why have int main() if the program can't [usefully] return the full
> range of ints?
--
[EMAIL PROTECTED] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
