-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
Yeah. I just have not investigated how to deal with the side file.
It's on my list of things to look
at. :-)
Thanks,
Frank
If you don't need the contents of the side file you can allocate it to
to
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
To
IBM-MAIN@bama.ua.edu
cc
Subject
Re: CICS DFHLD0203 issues
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
Yeah. I just have not investigated how to deal with the side file.
It's on my
Chase, John jch...@ussco.com
Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
02/06/2010 01:33 PM
Please respond to
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
To
IBM-MAIN@bama.ua.edu
cc
Subject
Re: CICS DFHLD0203 issues
-Original Message
Mainframe Discussion List IBM-MAIN@bama.ua.edu
To
IBM-MAIN@bama.ua.edu
cc
Subject
Re: CICS DFHLD0203 issues
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Peter Nuttall
Hi John,
That's correct, but I believe for it to work correctly, if you specify
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Peter Nuttall
Fair enough, though I was sure I read somewhere that with 'Separate'
coded
the file created by the sysdebug DD was used during the Debugging
process
? ...
Indeed; that is its intent, and its contents
Peter Nuttall wrote:
Fair enough, though I was sure I read somewhere that with 'Separate' coded
the file created by the sysdebug DD was used during the Debugging process
? ...
Right. But the file created by the sysdebug DD statement at
compile time has its name stored in the load module;
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
[ snip ]
I am generally able to just do a PHASEIN and it recovers. But we need
to solve the underlying issue.
You've already mentioned avoiding compressing a DFHRPL library while
CICS is running.
IS there some other quick fix we can do
without requiring a recompile of all modules with NOTEST?
If you do recompile, use TEST(NOHOOK,SEPARATE) and you can have
all of the benefits of TEST(NOSEPARATE) (formatted dumps,
ability to debug with Debug Tool) without the large load
modules. The
Yeah. I just have not investigated how to deal with the side file. It's on my
list of things to look at. :-)
Thanks,
Frank
On 6/1/2010 at 1:16 PM, in message
vnetibm.20100601191635.9...@bldgate.vnet.ibm.com, Tom Ross
tmr...@stlvm20.vnet.ibm.com wrote:
IS there some other quick fix we can do
We're about 27 hours in to our first full day with z/OS in production and
having a few issues. Namely things like this:
IEW4009I FETCH FAILED FOR MODULE CVDCDCOP FROM DDNAME DFHRPL BECAUSE OF AN
I/O ERROR.
IEW4005I FETCH FOR MODULE CVDCDCOP FROM DDNAME DFHRPL FAILED
On Mon, 31 May 2010 07:16:27 -0600, Frank Swarbrick wrote:
I am generally able to just do a PHASEIN and it recovers. But we need to
solve the underlying issue.
Don't compress partition data sets within the DFHRPL concatenation while
CICS is running.
This appears to indeed have been the cause. Daily compress job at 5:15 am.
Shoot! Will get this loadlib removed from that. Thanks!!
Frank
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
On
12 matches
Mail list logo
