The parmlib statements in your LOADxx member are processed very early. The
same is probably true if it is specified in master JCL. The system
symbolics, like SYSR1, are not yet defined. The only indirect cataloging
you can use is to volser **. I found this out the hard way, once.
Bill
Looks like using the ACEE should work. Thanks for the idea!
As for that other stuff, I am just an applications person. THe Security guy is
the one who needs to worry about the whole conversion thing. In fact, it's not
just Top Secret to RACF. It's Top Secret on VSE to RACF on z/OS! But I'm
I'll take a look at that as well. Thanks.
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
On 1/29/2010 at 11:57 AM, in message
a3a2b85f1001291057p45c476a2u344b1e66dd488...@mail.gmail.com, Tony
Paul Gilmartin wrote:
Why re-invent the wheel?
I always thought that this came about because
CICS was a DOS app later ported to MVS.
This CICS smarts for managing virtual tasks and
not really OS waiting until there was absolutely
nothing else to do meant that CICS apps got
great throughput
Greg Price wrote:
| Paul Gilmartin wrote:
|| Why re-invent the wheel?
| I always thought that this came about because CICS
| was a DOS app later ported to MVS.
It was not. The three SE designers of CICS had reasonably but in the event
very prematurely assumed that OS/MVT woluld be
101 - 105 of 105 matches
Mail list logo