I am out of the office until 12/07/2009.
If you require immediate assistance, please contact my backup Fernando
Vega on 1-404-238-4580 or Jon Regitsky on 1-404-238-3134. Thank you.
Note: This is an automated response to your message IBM-MAIN Digest - 3
Dec 2009 to 4 Dec 2009 (#2009-338) sent
Paul Gilmartin wrote:
It's kinda like how people say steep learning curve
(understanding increases rapidly) when they mean
shallow learning curve (understanding increases slowly).
(Or maybe they have the ordinate and the abscissa conceptually
swapped: time on the Y-axis?)
I disagree !
The
A little plug for z/OS V1R11:
It contains a new setting in ALLOCxx to tell Allocation to not recall a
data set before deletion, when the program name is IEFBR14 and the
DISP=(OLD,DELETE) or DISP=(MOD,DELETE). Look for the
IEFBR14_DELMIGDS(NORECALL) setting in Initialization and Tuning
A little plug for z/OS V1R11:
It contains a new setting in ALLOCxx to tell Allocation to not recall a
data set before deletion, when the program name is IEFBR14 and the
DISP=(OLD,DELETE) or DISP=(MOD,DELETE). Look for the
IEFBR14_DELMIGDS(NORECALL) setting in Initialization and Tuning
On 12/04/2009 10:14 AM, bjbxd wrote:
Hello List,
We are looking for a tool to detect the loop for batch application,
any suggestion are appreciated.
My shop is runing z/OS, application is C/C++.
Bob.
Considering the speed of today's processors, all batch programs that run
for more than a
But if your only object in using IDCAMS is to avoid the JCL error if the
ds doesn't exist, the DD is completely unneeded. You seem to be
confusing the IEFBR14 deletion technique with the IDCAMS deletion
technique and trying to combine them.
Just use IDCAMS delete with the dsname instead of
Yes Ted, it`s a very big kluge with a very big hole.
I am waiting to see what they do to correct the issue.
For those that don`t know what the hole is...
If the job goes into allocation recovery or for whatever other reason the
DISP=(OLD,DELETE) migrated data set gets recalled prior to step
IF MAXCC = 8 THEN SET MAXCC = 0
just in case some totally unexpected error happens in IDCAMS.
You can sometimes get an RC=4 -- not necessarily for delete.
So I do:
IF MAXCC 9 THEN SET MAXCC = 0
-
Too busy driving to stop for gas!
--- On Fri, 12/4/09, Thompson, Steve steve_thomp...@stercomm.com wrote:
--SNIP
As IBM sales suffer, now's the time to buy a new mainframe
http://www.networkworld.com/news/2009/120409-ibm-mainframe.html
from above ...
But the economy and
Well, I disagree about the kluge part, (it solves the problem for which
the requirements were written), but disgarding that ...
How often does this very big hole occur? Does it make the function
unusable? (I'm really curious, not being argumentative). When the data
set is not deleted and
DanD wrote:
Yes Ted, it`s a very big kluge with a very big hole.
I am waiting to see what they do to correct the issue.
For those that don`t know what the hole is...
If the job goes into allocation recovery or for whatever other reason the
DISP=(OLD,DELETE) migrated data set gets recalled prior
11 matches
Mail list logo
