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 following five fields...."
In Chapter 13 of the CLIST manual (z/OS V1R7.0 TSO/E CLISTs), there is a section entitled "How to Read the CLIST Statement Syntax" and each following section describes a different statement - ATTN, CLOSFILE, CONTROL, etc. There is a section of the CLIST manual entitled "JCL Statements" which contains this information: "From a CLIST, you might want to submit a jobstream for execution. In the CLIST, you can include the required JCL statements (EXEC, DD, and so on). However, when you include the following JCL statements in a CLIST, you must use a particular CLIST function to prevent the CLIST from modifying the statements and causing subsequent JCL errors." The IBM terminology site (http://www-306.ibm.com/software/globalization/terminology/) defines statement as: An instruction in a program or procedure. However, they don't define tautology. :-) For concatenation, I have no problem running this job: //DPC088RX JOB (DPC088,JDG),'REXX RUN',CLASS=A,MSGCLASS=X, // MSGLEVEL=(1,1),NOTIFY=DPC088 TYPRUN=SCAN // EXEC PGM=IKJEFT1B //SYSEXEC DD DSN=DPC088.REXX.LIB,DISP=SHR //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DSN=DPC088.JCL.CNTL(REXX1),DISP=SHR // DD * %DISPDATE D /* // DD DSN=DPC088.JCL.CNTL(REXX2),DISP=SHR // DD * %DISPDATE U /* It produces this result: READY %DISPDATE J J 06076 READY %DISPDATE D D 76 READY %DISPDATE W W Friday READY %DISPDATE U U 03/17/06 READY END Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Shmuel Metz (Seymour J.) Sent: Friday, March 17, 2006 8:03 AM 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. ---------------------------------------------------------------------- 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
