would be used to set the default plan. To override that I could specify a
different plan in a CEEROPT and compile this in to a user load library and
then include that load library in my JOBLIB concatenation. This works, but
could have the unitended consequence that any time I use that user load
batch jobs are to use. CEEPRMxx
would be used to set the default plan. To override that I could specify a
different plan in a CEEROPT and compile this in to a user load library and
then include that load library in my JOBLIB concatenation. This works, but
could have the unitended consequence
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
Is CEEROPT supposed to be able to affect a regular batch job, or is it
just for CICS and IMS? I
assembled a CEEROPT in to a private load library and then put it in my
JOBLIB concatenation
Well, I really would prefer both. CEEROPT can be used for, as you say, all
batch jobs. I would like as well something that could be done at the first
step in a job and have the remaining jobs pick it up. I'm pondering how that
can be done without making a requirement of IBM. I'm thinking
So here's what I've got working. Not the most obvious thing in the world, but
it seems to work. It forces me to use STEPLIB instead of JOBLIB for my LOADLIB
concatenation, which I don't prefer, but I can live with it.
'DVFJS.APPLIB.PARM(CEEROPT)':
CEEROPT CSECT
On Mon, 3 Jan 2011 10:12:04 -0700, Frank Swarbrick
frank.swarbr...@efirstbank.com wrote:
Well, I really would prefer both. CEEROPT can be used for, as you say, all
batch jobs.
I'm confused. If you want the options for all batch jobs, make the
settings permanent in CEEPRMxx.
I would
On Mon, 3 Jan 2011 12:31:49 -0700, Frank Swarbrick
frank.swarbr...@efirstbank.com wrote:
So here's what I've got working. Not the most obvious thing in the world,
but it seems to work. It forces me to use STEPLIB instead of JOBLIB for my
LOADLIB concatenation, which I don't prefer, but I can
It's somewhat of a general, not specific, desire. I want to use an ENVAR to
hold the name of the DB2 PLAN that my batch jobs are to use. CEEPRMxx would be
used to set the default plan. To override that I could specify a different
plan in a CEEROPT and compile this in to a user load library
On 12/31/2010 4:24 PM, Frank Swarbrick wrote:
!!!
I didn't see Lizette's message, but I believe this is exactly
what I want! I just tried it (SETCEE CEEROPT,ALL) and now my
batch job is picking up my CEEROPT. Tres cool!
Ah, I see. So I misunderstood what you wanted. I thought
you wanted
On Sat, 1 Jan 2011 09:56:17 -0700, Steve Comstock st...@trainersfriend.com
wrote:
On 12/31/2010 4:24 PM, Frank Swarbrick wrote:
!!!
I didn't see Lizette's message, but I believe this is exactly
what I want! I just tried it (SETCEE CEEROPT,ALL) and now my
batch job is picking up my CEEROPT
On 1/1/2011 1:33 PM, Mark Zelden wrote:
On Sat, 1 Jan 2011 09:56:17 -0700, Steve Comstockst...@trainersfriend.com
wrote:
On 12/31/2010 4:24 PM, Frank Swarbrick wrote:
!!!
I didn't see Lizette's message, but I believe this is exactly
what I want! I just tried it (SETCEE CEEROPT,ALL) and now
Is CEEROPT supposed to be able to affect a regular batch job, or is it just for
CICS and IMS? I assembled a CEEROPT in to a private load library and then put
it in my JOBLIB concatenation but it doesn't appear to have any effect. Works
fine for a CICS region. Is this working as designed
Frank Swarbrick wrote:
Is CEEROPT supposed to be able to affect a regular batch job, or is it just for
CICS and IMS?
CICS/IMS.
I assembled a CEEROPT in to a private load library and then put it in my JOBLIB
concatenation but it doesn't appear to have any effect. Works fine for a CICS
10:27 AM
To: IBM-MAIN@bama.ua.edu
Subject: CEEROPT
Is CEEROPT supposed to be able to affect a regular batch job, or is it just
for CICS and IMS? I assembled a CEEROPT in to a private load library and
then put it in my JOBLIB concatenation but it doesn't appear to have any
effect. Works fine
use a DD statement (I think) called CEE$OPT to pass
parms to programs for LE
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of
Frank Swarbrick
Sent: Friday, December 31, 2010 1:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: CEEROPT
On 12/31/2010 11:27 AM, Frank Swarbrick wrote:
Is CEEROPT supposed to be able to affect a regular batch job,
or is it just for CICS and IMS? I assembled a CEEROPT in to
a private load library and then put it in my JOBLIB concatenation
but it doesn't appear to have any effect. Works fine
Thanks for confirming that. I know all about CEEUOPT (which I hate, because it
makes it a link-time run-time option) and CEEOPTS DD (and PARM=). I just
can't see any reason why CEEROPT might not also be useful for batch.
Specifically, I was thinking I could make a CEEROPT member
:
On 12/31/2010 11:27 AM, Frank Swarbrick wrote:
Is CEEROPT supposed to be able to affect a regular batch job,
or is it just for CICS and IMS? I assembled a CEEROPT in to
a private load library and then put it in my JOBLIB concatenation
but it doesn't appear to have any effect. Works fine
Lizette was close. In z/OS 1.10 there was change made so that downleveled
LE runtime was not supported. Part of that change also included a change
to CEEROPT:
CEEROPT is expanded so that it can now be loaded outside of the CICS and
LRR environments.
This support is controlled by using keywords
On 12/31/2010 1:06 PM, Frank Swarbrick wrote:
Thanks for the validation, Steve! :-) That is exactly what I am
wanting. I'd like to be able do something so that an entire
batch job with multiple EXEC PGM=... steps would share the same
ENVAR runtime option. Is this not a reasonable thing to
On 12/31/2010 2:51 PM, Mark Zelden wrote:
Lizette was close. In z/OS 1.10 there was change made so that downleveled
LE runtime was not supported. Part of that change also included a change
to CEEROPT:
CEEROPT is expanded so that it can now be loaded outside of the CICS and
LRR environments
On Fri, 31 Dec 2010 15:01:00 -0700, Steve Comstock
st...@trainersfriend.com wrote:
On 12/31/2010 2:51 PM, Mark Zelden wrote:
Lizette was close. In z/OS 1.10 there was change made so that downleveled
LE runtime was not supported. Part of that change also included a change
to CEEROPT
!!!
I didn't see Lizette's message, but I believe this is exactly what I want! I
just tried it (SETCEE CEEROPT,ALL) and now my batch job is picking up my
CEEROPT. Tres cool!
And it's all there in pink and purple in the documentation. I just didn't know
what to look for!
Now I can end
23 matches
Mail list logo
