In [EMAIL PROTECTED], on 03/16/2006
at 08:52 AM, Greg Shirey [EMAIL PROTECTED] said:
Well, I'm confused. The manual (TSO/E User's Guide) does seem to be
pretty consistent in using the word statement to refer essentially
to a line (whether continued or not) of JCL - the EXEC statement, the
JOB
OK, when I search the bookshelf on-line for z/OS 1.7, I get 386 hits for
'statement.' In the JCL manual, it says (partially):
A JCL statement consists of one or more 80-byte records. Each record is in
the form of an 80-column punched-card image. Each JCL statement is logically
divided into the
[EMAIL PROTECTED] wrote:
P.S.:
You can also use the EX command in SYSTSIN to invoke your RACF command
file as a CLIST, instead of specifying it directly in the SYSTSIN DD
statement.
SYSTSIN DD *
EX 'DSN'
/*
Nice idea, but how do I get the same behavior as feeding the file into
program
IKJEFT1A does return after the first non-zero return code
even if the input comes from a data set executed via ex
command. Either the SYSTSIN DD * or the PARM= version
work for me.
Or did I missunderstand you question?
Peter Hunkeler
CREDIT SUISSE
//TMP EXEC PGM=IKJEFT01,
// PARM='EX ''VB.INPUT'' LIST CLIST'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
It seems I have supplanted the CLIST facility ;-)
Peter Hunkeler
CREDIT SUISSE
In [EMAIL PROTECTED],
on 03/14/2006
at 12:00 AM, Ted MacNEIL [EMAIL PROTECTED] said:
No, command == TSO command
Statement == line within file
You're overlooking continuation lines.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
No, command == TSO command
Statement == line within file
You're overlooking continuation lines.
Actually, I'm not.
The poster I replied to was confused about the statement:
Each command must start on a new statement.
That was what I was trying to clarify.
A continuation is not a new statement.
In [EMAIL PROTECTED], on 03/14/2006
at 11:41 AM, Paul Gilmartin [EMAIL PROTECTED] said:
IBM's lexical conventions, traceable to the limitations of the 029
keypunch and 407 card reader
Not even close.
No professor, having a limited number of
lectures to deliver, will choose to waste any of
In [EMAIL PROTECTED], on 03/14/2006
at 12:14 PM, Tom Schmidt [EMAIL PROTECTED] said:
Each command or subcommand must begin on a separate statement.
That sounds like a candidate for an RCF.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
In [EMAIL PROTECTED], on 03/14/2006
at 03:08 PM, Paul Gilmartin [EMAIL PROTECTED] said:
I know, but it could also be cabled to a 70* computer and used as a
printer and card reader, in which case it could read only 72 columns
of each card.
There was certainly a 716[1] printer for the 7090
In [EMAIL PROTECTED], on 03/14/2006
at 08:25 PM, Chris Mason [EMAIL PROTECTED] said:
The real reason I'm posting - and again relying on positively antique
OS education - is that I have always treated it as a golden rule of
data set concatenation that the attributes of the first data set in
the
In a recent note, Shmuel Metz (Seymour J.) said:
Date: Wed, 15 Mar 2006 07:48:58 -0500
In [EMAIL PROTECTED], on 03/14/2006
at 03:08 PM, Paul Gilmartin [log in to unmask] said:
I know, but it could also be cabled to a 70* computer and used as a
printer and card reader, in which
Norbert Friemel wrote:
Ulrich,
how about this:
1) create a simple two line rexx in data set A.B.EXEC:
/* rexx */
Or replace
//TMP EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DISP=OLD,DSN=VB.INPUT
with
//TMP EXEC PGM=IKJEFT01,
First a correction of my own typo. I was familiar with a
407 at the University of Colorado circa 1970, not mid-1950's.
(Not quite that old, yet.) And it was standalone on the job
prep floor, not connected to any computer.
In a recent note, Shmuel Metz (Seymour J.) said:
Date: Wed, 15
In [EMAIL PROTECTED], on 03/15/2006
at 07:05 AM, Paul Gilmartin [EMAIL PROTECTED] said:
I may well stand corrected on the device type. However I have a
distinct memory of colleagues at one 7090 installation submitting
jobs with the notation to the operator: 80 column data; do not read
job
In [EMAIL PROTECTED], on 03/15/2006
at 08:37 AM, Paul Gilmartin [EMAIL PROTECTED] said:
And I understand that nowadays at least BLKSIZE is taken from the
maximum among the catenands, not the first. But the calling program
must be notified synchronously of the crossing of the
In [EMAIL PROTECTED],
on 03/15/2006
at 12:00 AM, Ted MacNEIL [EMAIL PROTECTED] said:
Actually, I'm not.
Then you're confused.
The poster I replied to was confused about the statement: Each
command must start on a new statement.
Hardly surprising, because that sentence says nothing. The
I have a question that's so basic I'm almost ashamed to ask.
Quite often I need to execute RACF commands via the TMP in batch. The
commands are lengthy and don't always fit in 80 columns so I'm using
variable length records. With VB data sets, the TSO command parser
expects line numbers in
Ulrich,
Not knowing exactly which commands you are doing, or how many this may or
may not work for you.
You can always use a FB record. The commands can be split along multiple
lines so long as there is a hyphen (-) or plus (+) at the end of the line to
indicating it is being continued on the
On Tue, 14 Mar 2006 15:45:03 +0100 Ulrich Boche [EMAIL PROTECTED] wrote:
:I have a question that's so basic I'm almost ashamed to ask.
:Quite often I need to execute RACF commands via the TMP in batch. The
:commands are lengthy and don't always fit in 80 columns so I'm using
:variable length
Binyamin Dissen wrote:
You can use 80 character records.
Put a + at the end of the line which tells TSO that the command is continued
on the next line.
I know how to continue TSO input lines. However, in most cases,
splitting the line would be more inconvenient than shifting the variable
Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
Of Ulrich Boche
Sent: Tuesday, March 14, 2006 11:09 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Batch TMP RECFM(VB) Input
Binyamin Dissen wrote:
You can use 80 character records.
Put a + at the end of the line which tells TSO that the command
Ulrich,
Then the only other thought I have is that you are doing this under ISPF.
You need to change the profile of the Data Set you are using from one that
has numbs on to a different profile.
I do not have a system in front of me. But if you create a new VB file with
the profile you want,
If your commands are already in a separate VB file rather than inline, you
could precede the TMP step with a DFSORT step (if you have it) that reads
the file and creates a temporary VB file that has the sequence numbers.
OPTION COPY
OUTFIL OUTREC=(1,4,SEQNUM,8,ZD,5)
Bill Godfrey
On Tue, 14 Mar
In a recent note, Lizette Koehler said:
Date: Tue, 14 Mar 2006 10:31:20 -0700
Then the only other thought I have is that you are doing this under ISPF.
You need to change the profile of the Data Set you are using from one that
has numbs on to a different profile.
I do not have a
In a recent note, Imbriale, Donald (Exchange) said:
Date: Tue, 14 Mar 2006 11:39:53 -0500
I just created a VB PDS, added a job and submitted it and it ran without
incident. No line numbers anywhere, no need to shift anything to make
room for non-existent line numbers. All is well.
Ulrich,
The short answer to your question is: No.
As documented in the fine manual:
The SYSTSIN and SYSTSPRT DD statements can refer to a sequential data set
or a member of a partitioned data set.
It is recommended that the SYSTSIN DD be defined as a fixed block format
data set, with an LRECL
In a recent note, Tom Schmidt said:
Date: Tue, 14 Mar 2006 12:14:08 -0600
If SYSTSIN is a variable length data set (VB), the first 8 bytes of the
record will be treated as a sequence number and ignored. If SYSTSIN is a
variable length data set with ASA control characters (VBA),
: Batch TMP RECFM(VB) Input
In a recent note, Tom Schmidt said:
Date: Tue, 14 Mar 2006 12:14:08 -0600
If SYSTSIN is a variable length data set (VB), the first 8 bytes of the
record will be treated as a sequence number and ignored. If SYSTSIN is a
variable length data set
Sounds redundant. Aren't command and statement synonyms?
No, command == TSO command
Statement == line within file
-
-teD
I’m an enthusiastic proselytiser of the universal panacea I believe in!
--
For IBM-MAIN subscribe /
No professor, having a limited number of
lectures to deliver, will choose to waste any of them describing
the continuation conventions for JCL, or HLASM, or even TSO.
It's more productive to teach UNIX or Windows instead.
The above tends toward the ludicrous.
If you're not going to teach the
the attributes of the first data set will be
the ones set in the OS control blocks at the time the data set is opened and
the attributes of succeeding data sets are utterly ignored.
Not true, since ESA 3, for block-size.
(I cannot remember for sequential, but it reallocates the buffer for PDS,
Unless there were two of them, the 407 was a tabulating machine in the
1950's. Sounded like a washing machine in distress when operating
properly.
snip
IBM's lexical conventions, traceable to the limitations of the
029 keypunch and 407 card reader (I know, but..) are unduly
burdensome.
In a recent note, Kirk Talman said:
Date: Tue, 14 Mar 2006 16:29:20 -0500
Unless there were two of them, the 407 was a tabulating machine in the
I know, but it could also be cabled to a 70* computer and used as
a printer and card reader, in which case it could read only 72
columns
Ulrich,
how about this:
1) create a simple two line rexx in data set A.B.EXEC:
/* rexx */
execio * diskr cmdin (finis
2) run your batch tmp with DD=CMDIN pointing to the VB data set and
the following line in SYSTSIN:
EX 'A.B.EXEC' EX
The rexx will read all lines from the data
Ulrich,
how about this:
1) create a simple two line rexx in data set A.B.EXEC:
/* rexx */
Or replace
//TMP EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DISP=OLD,DSN=VB.INPUT
with
//TMP EXEC PGM=IKJEFT01,
Boche
Sendt: 14. marts 2006 17:09
Til: IBM-MAIN@BAMA.UA.EDU
Emne: Re: Batch TMP RECFM(VB) Input
Binyamin Dissen wrote:
You can use 80 character records.
Put a + at the end of the line which tells TSO that the command is
continued on the next line.
I know how to continue TSO input lines
37 matches
Mail list logo
