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 statement, the SYSIN DD statement, the SYSTSIN DD statement etc.
>Are they not using their own terminology correctly?
I'd say not:
EDIT first.DSN -
second.dsn
Is two records. It's clearly on statement.
BTW, does the CLIST documentation also say statement when they mean
record? That could get even more confusing, since some CLIST
statements are not commands.
As for dconcatenation, I'd suggest testing a concatenation of DASD and
SYSIN data sets, e.g.,
//SYSTSIN DD DSN=SOME.INPUT,DISP=SHR
// DD *
more input
// DD DSN=YET.MORE.INPUT,DISP=SHR
If there is a problem, that is more likely to hit it than
concatenating like data sets.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
