You're right. I had jumped back and taken only a quick glance at the
original post in the thread, and I was fooled by the wrapping. The //*
comment line was the only line in my email copy that had anything out to
the right, but that was not the line to which the OP was referring. The
On Fri, 26 Sep 2008 15:36:25 -0500, Mark Zelden wrote:
It isn't changed. I just re-ran my test. It wasn't valid.I was using
a modified version of DEALLOC (IEFBR14).
1) I think I had 3 STEPLIB libraries the first time and I put data in
col. 72
in all 3. So since there was no 4th
Looks like DD DISP=SHR,DSN=PROD1.TMON.CICS32.TCELOAD
should have been swallowed as a comment. No JCL error.
Date: Fri, 26 Sep 2008 11:31:38 -0500
From: [EMAIL PROTECTED]
Subject: STC JCL Question
To: IBM-MAIN@BAMA.UA.EDU
Greetings List - We just came across an issue that I would
Tom,
In your case, the book says
For all other JCL statements, you can continue the parameter field or the
comments field on the JCL statement. If you continue both the parameter
field and the comments field on the same card image, the system ignores
the indication to continue the comment.
by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
09/26/2008 10:31 AM
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
STC JCL Question
Greetings List - We just came across an issue that I would like to address
with
the group
From: [EMAIL PROTECTED]
Subject: Re: STC JCL Question
To: IBM-MAIN@BAMA.UA.EDU
The numbers in the original post are not in the comments field of a
regular JCL statement. The numbers are on a comment card that began with
//*.
The book says
Do not continue a comment statement using
You would think it would have failed for a JCL error but it did not.
But it brings to question what happens in this case? Did it invailidate that
line and not use it?
Inquiring minds want to know.
One blank after JCL statements, and all the text afterwards is a comment
(JCL101).
-
Too
Greetings List - We just came across an issue that I would like to address with
the group to determine why this happened.
In testing of going to release 3.2 of CICS we had an issue with only one of the
regions having a S0C4 abend in the TMON program at PLT startup. This did
not happen in any
See the section on continuing comments in the JCL reference.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/3.4.1.3?SHELF=IEA2BK81DT=20070427231644CASE=
I think your next statement would have been treated as a comment if 72 was
not blank.
--
Tom Marchant
If you have a valid DD statement (not a comment) and a non blank character in
col. 72 then I would have expected
a JCL error on the Continuation not being valid
IEFC621I EXPECTED CONTINUATION NOT RECEIVED
Lizette
Greetings List - We just came across an issue that I would like to address
On Fri, 26 Sep 2008 18:47:52 +, Ted MacNEIL [EMAIL PROTECTED]
wrote:
You would think it would have failed for a JCL error but it did not.
But it brings to question what happens in this case? Did it invailidate
that
line and not use it?
Inquiring minds want to know.
One blank after JCL
On Fri, 26 Sep 2008 18:47:52 +, Ted MacNEIL wrote:
One blank after JCL statements, and all the text afterwards is a comment
(JCL101).
But a nonblank in column 72 sometimes indicates a continuation.
The rules are too complicated for me to grasp.
-- gil
But a nonblank in column 72 sometimes indicates a continuation.
Always.
But, I missed that because of the way my BlackBerry formats text.
But, from what I saw, that should have caused a JCL error.
-
Too busy driving to stop for gas!
I forgot to mention and was hoping that my cut and paste would illustrate it,
but the numbers that were moved were from columns 68-75.
Did that leave anything in column 72?
I couldn't tell because of the way my BlackBerry formats messages.
-
Too busy driving to stop for gas!
On Fri, 26 Sep 2008 11:31:38 -0500, Patrick Lyon [EMAIL PROTECTED] wrote:
What we found was in the STEPLIB statement, on the line where we had the
SDFHLPA, the numbers that should be in columns 72-80 were pulled to the
left, probably an oversight when the dataset name was changed. The JCL is
On Fri, 26 Sep 2008 18:47:52 +, Ted MacNEIL [EMAIL PROTECTED] wrote:
You would think it would have failed for a JCL error but it did not.
But it brings to question what happens in this case? Did it invailidate
that line and not use it?
Inquiring minds want to know.
One blank after JCL
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
One blank after JCL statements, and all the text afterwards is a
comment
(JCL101).
(JCL102) Col 72 must be non-blank or it is treated as a
continuation.
ITYM must be blank.
-jc-
On Fri, 26 Sep 2008 19:19:53 +, Ted MacNEIL [EMAIL PROTECTED]
wrote:
I forgot to mention and was hoping that my cut and paste would illustrate
it, but the numbers that were moved were from columns 68-75.
Did that leave anything in column 72?
I couldn't tell because of the way my BlackBerry
On Fri, 26 Sep 2008 13:54:15 -0500, Patrick Lyon [EMAIL PROTECTED] wrote:
On Fri, 26 Sep 2008 18:47:52 +, Ted MacNEIL [EMAIL PROTECTED]
wrote:
You would think it would have failed for a JCL error but it did not.
But it brings to question what happens in this case? Did it invailidate
that
On Fri, 26 Sep 2008 13:56:34 -0500, Mark Zelden wrote:
If you had non-blank data in col. 72 it should have been a JCL error.
Not if the next record starts with // in column 1-2 followed by a space.
Then it should be treated as the continuation of a comment.
Here it is again:
On Fri, 26 Sep 2008 14:49:08 -0500, Chase, John [EMAIL PROTECTED] wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
One blank after JCL statements, and all the text afterwards is a
comment
(JCL101).
(JCL102) Col 72 must be non-blank or it
On Fri, 26 Sep 2008 13:56:34 -0500, Mark Zelden wrote:
You would think it would have failed for a JCL error but it did not.
If you had non-blank data in col. 72 it should have been a JCL error.
Open a PMR with IBM. I just tested this on z/OS 1.8 and got a JCL
error. On z/OS 1.9 I didn't. It
On Fri, 26 Sep 2008 14:36:31 -0500, Tom Marchant [EMAIL PROTECTED]
wrote:
On Fri, 26 Sep 2008 13:56:34 -0500, Mark Zelden wrote:
If you had non-blank data in col. 72 it should have been a JCL error.
Not if the next record starts with // in column 1-2 followed by a space.
Then it should be
On Fri, 26 Sep 2008 15:36:25 -0500, Mark Zelden wrote:
On Fri, 26 Sep 2008 14:36:31 -0500, Tom Marchant wrote:
Here it is again:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B670/3.4.1.3?SHELF=IEA2BK81DT=20070427231644CASE=
On Fri, 26 Sep 2008 15:06:20 -0500, Paul Gilmartin
24 matches
Mail list logo
