In these situations, as I understand it, the user program sets four items
that are used to execute the CICS application.
1) Transaction Code (must point to the mirror program)
2) Program id (DPL command subset)
3) User id (java gateway)
4) Password (java gateway)
Does anyone else feel uneasy with a user program specifying both the
transaction code and program id? The situation that worries me is the
specification of some globally authorized transaction code and say a
payroll update program.
I know this opens little that is not already available to a devious CICS
application programmer. But somehow I'm more comfortable with code
compiled here, and residing in my load library that some JAVA code running
in some SERVLET (or the like) somewhere "out there".
Thanks for your time.
>Does anyone else feel uneasy with a user program specifying both the
>transaction code and program id? The situation that worries me is the
>specification of some globally authorized transaction code and say a
>payroll update program.
What about turning the Security option XPCT or XPPT = YES (whichever)
in CICS/ESA so that the program id will be tested by RACF (or whatever
security), then the transaction id should not matter. I haven't had a
chance to try this, it is just a thought.
Mark Granger.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com