Posted by Jim Prestwood on February 20, 2002 at 16:49:30:
In Reply to: Remove iof version in IOF for CICS posted by Dave Trigger on February 20, 2002 at 14:46:29:
: I've installed IOF CICS,, and I want to put the IOF modules in the same Libraries as my IOF/TSO modules,, I've been looking through the install and options library,, and for the life of me can't find where it's set.
: Can you point me to the right area.
: Do you see any issues with me installing IOFCICS in the same libraries as IOFTSO?
If the question relates to the IOF/CICS distribution libraries created
by the install dialog (prefix.IOFC7G0.SOURCE, .OPTIONS, .INSTALL, etc.)
then the answer is that you should maintain separate libraries for the
two products.
If you are asking about the target linklist library, which is the
ultimate destination for load modules (IOFC7G0A, IOFC7G0M, IOFC7G0P,
and IOFC7G0U), there is no problem. Both the CICS and TSO versions
can share a common library since the TSO modules will all begin with
IOFT... and the ones for CICS will begin with IOFC... thus avoiding
any possible naming conflict. This library is specified in options
member C64LINK.
The location for those modules (IOFCIC and IOFCMT) which must reside
in a library which is part of your CICS DFHRPL DD concatenation is
specified in options member C66CRPL.
One final note. If you specify the same SVC/ESR number (options
member A10AUTH) that you used for IOF/TSO, then you do not need to
install another copy of the SVC/ESR for IOF/CICS. The SVC/ESR
distributed with the TSO and CICS versions are the same.