Thanks, Alexei, Blair, and Bryan.

The *NEW activation group did occur to me but I was sloppy in my testing
of the non-C versions.  The first run of those used the default
activation group then I recompiled them using *NEW activation groups.  I
signed off and signed on to get rid of any 'memory' in the default
activation group but I had compiled the *NEW versions into a different
library by mistake so I never actaully ran them.  Doh!  Since they
appeared to function I presumed the problem was with C calling C rather
than the activation group issue.

I just tried that with the *NEW versions of non-C and of course it fails
exactly like the C versions.

Blair,  I'm pleased to see your comments regarding granularity.  That
will make things more flexible.

Bryan,  I see CEE0200 has more useful information at 510 than at 440, to
wit the specific mention of activation group *NEW.

Alexei,  I do require the ALWMLTTHD(*YES) attribute for the job so I
can't change that.  Since the called program is also a CPP for a command
I don't really want it to run in *CALLER since that is likely to be the
default activation group.

I think I will revisit the spawn() technique which does work in a
multi-threaded job.

Thanks again for your help.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].