Re: exit pgm and lpar

>
>You test the chgcmd api the same way we did.  Start the debugger, set the
>break points, prompt the command.  Granted we put a separate copy of the
>command in a different library to check.
>
>Rob Berendt
>


Rob,

I am on v4r4 so I cant test my assumptions.
Reading the documentation on chgc0100 exit point, you can only have one exit
point per cmd.
And the exit pgm is qualified by library, so the system will always call a
qualified pgm for the cmd. ( for security reasons, it better <g> )
So if you want to test chgs to your exit pgm, you have to disengage your
production exit point, chg the exit point to point to your new version, ....

My comments on exit pgms and my question on lpar have to do with thinking of
how you can keep applications separate from ( protected from ) each other on
the as400. Lpar can work for this purpose,  but I suspect it could lead to
duplication of objects, which can be a maintenance nightmare.

Consider an order entry system programmer wanting to use the chgc0100 exit
point to customize the sbmjob cmd. If such an exit pgm is registered, all
the sbmjob cmds run on the system will run thru the exit pgm of the order
entry system. Because of this implication, the exit pgm option will not be
used.

I appreciate ibm providing the feature. I just think that in the real world,
it will not be used very much. In fact, I am hard pressed to think of any
scenario were it will be used.

Steve Richter


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---