Ok, I'm back to working on this aspect of a problem. So, I tried something
interesting to try to figure this one out. The following JCL does NOT expand
the string (the JOB after this does):
//SXT7279T JOB (T,,MC),'TEST PARMDD ',CLASS=I,
// TIME=(,05),
//* TYPRUN=SCAN,
//
On Fri, 12 Dec 2014 18:36:21 +, Steve Thompson sthompso...@humana.com
wrote:
Ok, I'm back to working on this aspect of a problem. So, I tried something
interesting to try to figure this one out. The following JCL does NOT expand
the string (the JOB after this does):
//SXT7279T JOB
On 12/12/2014 02:35 PM, Tom Marchant wrote:
On Fri, 12 Dec 2014 18:36:21 +, Steve Thompson sthompso...@humana.com
wrote:
SNIPPAGE
The EXPORT has to be coded BEFORE the SET statements, as documented
in the first paragraph describing the EXPORT statement.
Symbols must be set to a value
On 12/12/2014 03:02 PM, Steve Thompson wrote:
On 12/12/2014 02:35 PM, Tom Marchant wrote:
On Fri, 12 Dec 2014 18:36:21 +, Steve Thompson
sthompso...@humana.com wrote:
SNIPPAGE
The EXPORT has to be coded BEFORE the SET statements, as
documented
in the first paragraph describing the EXPORT
It's wrong to quietly ignore an unsupported construct. Logging-DDname
in a SYSIN data set mentioned in PARMDD should result in a JCL syntax
error and failure of the job before execution.
Your opinions are always welcome. They are not always agreed with.
For this case, I probably agree that a
...ignored...! WTF!? Time for a Requirement? Either
the substitution result should be logged in logging-DDname
or it should appear in an informative message after
the EXEC statement.
You are always encouraged to submit requirements. Logging might well be
rejected. It is a chicken-and-egg
On Mon, 8 Dec 2014 07:59:53 -0500, Peter Relson wrote:
... At the time that PARMDD is (and
has to be) processed (under the initiator task), various i/o operations
are not supported (apparently including those needed to write to a the
intended log). Changing that could be very costly, thus
: December 7, 2014 12:16
Subject: Re: PARMDD -- any one use yet?
On Sun, 7 Dec 2014 11:20:40 -0500, Peter Relson wrote:
I might well be thinking of something else, but for whatever reason I
was thinking that something might show what substitution is done for
PARMDD
Found it in:
http://www-01.ibm.com
We would still need to explain why JOB A
works while JOB B, based on JOB A, isn't
working.
Perhaps you could consider starting this thread over again, this time
providing the complete information.
I might have missed it, but I do not think you showed what the symbol
values were, and you did
On 12/07/2014 02:23 AM, Peter Hunkeler wrote:
SNIPPAGE
SYMBOLS parameter
Parameter type
Keyword, optional
Purpose
Use the SYMBOLS parameter to request JES to perform symbol substitution within
in-stream data.
Syntax
SYMBOLS=({JCLONLY|EXECSYS|CNVTSYS} [,logging-DDname])
Valid values: Specify one
On 12/07/2014 02:24 AM, Peter Hunkeler wrote:
We would still need to explain why JOB A works while JOB B, based on JOB A,
isn't working.
How about posting the two JCLs?
--
Peter Hunkeler
--
For IBM-MAIN subscribe /
On Sun, 7 Dec 2014 11:20:40 -0500, Peter Relson wrote:
I might well be thinking of something else, but for whatever reason I was
thinking that something might show what substitution is done for PARMDD
Found it in:
In 5483d3f5.9040...@copper.net, on 12/06/2014
at 11:13 PM, Steve Thompson ste...@copper.net said:
I know of NOTHING using cores today.
Well, then you only know about machines designed in the last few
decades. But you can find some 1960's (1950's?) vintage machines in
museums.
How about
In 5483d485.5010...@copper.net, on 12/06/2014
at 11:16 PM, Steve Thompson ste...@copper.net said:
We would still need to explain why JOB A works while JOB B, based on
JOB A, isn't working.
Obviously, because they are different. It may take some experimenting
to determine which differences
In 5480ca98.3040...@copper.net, on 12/04/2014
at 03:56 PM, Steve Thompson ste...@copper.net said:
On 12/04/2014 03:04 PM, Paul Gilmartin wrote:
On 2014-12-04 12:35, Steve Thompson wrote:
SNIP
Like, what's the most efficient way to clear a register?
-- gil
SNIP
Well, mine is to pull the
In 5480d9dd.6000...@copper.net, on 12/04/2014
at 05:02 PM, Steve Thompson ste...@copper.net said:
The one that does not work does pass to IKJEFT1B ISPSTART
cmd(%NCMPL and that's it. The rest of the parm string is NOT
passed.
What happedns if you surround the parameter with apostrophes,
On 12/06/2014 06:20 PM, Shmuel Metz (Seymour J.) wrote:
In 5480ca98.3040...@copper.net, on 12/04/2014
at 03:56 PM, Steve Thompson ste...@copper.net said:
On 12/04/2014 03:04 PM, Paul Gilmartin wrote:
On 2014-12-04 12:35, Steve Thompson wrote:
SNIP
Like, what's the most efficient way to
On 12/06/2014 06:22 PM, Shmuel Metz (Seymour J.) wrote:
In 5480d9dd.6000...@copper.net, on 12/04/2014
at 05:02 PM, Steve Thompson ste...@copper.net said:
The one that does not work does pass to IKJEFT1B ISPSTART
cmd(%NCMPL and that's it. The rest of the parm string is NOT
passed.
What
A suggestion then: Specify a SYMBOLS logging DD, as I did in my example. It
*should* tell you what substitutions were actually made. I believe I've
read of such; I don't readily find it in the JCL Reference.
The JCL reference explains the SYMBOLS parameter as:
SYMBOLS parameter
Parameter
We would still need to explain why JOB A works while JOB B, based on JOB A,
isn't working.
How about posting the two JCLs?
--
Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Might one conclude that the substitution works just fine, but that the
application to which you are sending the data can't handle longer data?
It is the user's responsibility to provide to the application only what it
can handle. The system will not prevent it (except for authorized cases
On 12/05/2014 07:23 AM, Peter Relson wrote:
Might one conclude that the substitution works just fine, but that the
application to which you are sending the data can't handle longer data?
It is the user's responsibility to provide to the application only what it
can handle. The system will not
On Thu, 4 Dec 2014 17:08:30 -0500, Farley, Peter x23353 wrote:
A suggestion then: Specify a SYMBOLS logging DD, as I did in my example. It
*should* tell you what substitutions were actually made.
I believe I've read of such; I don't readily find it in the JCL Reference.
Paul Gilmartin had a
I've run into a situation where we have a parm that expands to more than 100
characters (sound like a familiar problem?).
So, I've tried to use the PARMDD EXEC Keyword. And sure enough it points over
to the specified DDName.
So I have it coded like this:
// EXPORT SYMLIST=*
:
You may have put the EXPORT statement at the wrong point in the JCL. Try
putting it right after the JOB statement.
On Thu, 4 Dec 2014 18:40:03 +, Steve Thompson sthompso...@humana.com
wrote:
I've run into a situation where we have a parm that expands to more than 100
characters (sound
Date: Thu, 4 Dec 2014 12:56:53 -0600
From: Peter X. DeFabritus pxdef...@gmail.com
You may have put the EXPORT statement at the wrong point in the JCL. Try
putting it right after the JOB statement.
SNIPPAGE
Sorry, it behaved the same whether it was just after the JOB card or just
before the
On 2014-12-04 12:35, Steve Thompson wrote:
So, if you need to your parm line (string), think about how you do the split.
Because the next line read is concatenated to the prior line ignoring the
right side spaces (at least that's what I have experienced). If you need a
space between
On 12/04/2014 03:04 PM, Paul Gilmartin wrote:
On 2014-12-04 12:35, Steve Thompson wrote:
SNIP
Like, what's the most efficient way to clear a register?
-- gil
SNIP
Well, mine is to pull the power plug. I don't have to write code,
I don't have to deal with MAKE, BINDER, or anything else.
-- any one use yet?
I've run into a situation where we have a parm that expands to more than 100
characters (sound like a familiar problem?).
So, I've tried to use the PARMDD EXEC Keyword. And sure enough it points over
to the specified DDName.
So I have it coded like this:
// EXPORT
, December 04, 2014 4:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PARMDD -- any one use yet?
The following definitely works, tested on V2.1 system today. HTH.
//YOURJOBX JOB (0,0). . . == Supply your own
//*
//* DOC
On 12/04/2014 04:15 PM, Farley, Peter x23353 wrote:
The following definitely works, tested on V2.1 system today. HTH.
SNIPPAGE
Yeah I'm having a Rod Serling afternoon.
I have two JOBs now where I am using this. One works, the other
does not.
The one that does not work does pass to
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Thompson
Sent: Thursday, December 04, 2014 5:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PARMDD -- any one use yet?
On 12/04/2014 04:15 PM, Farley, Peter x23353 wrote:
The following definitely works, tested on V2.1 system today. HTH.
SNIPPAGE
Yeah
32 matches
Mail list logo
