Use the * (asterisk) parameter to begin an in-stream data set. The data records immediately follow the DD * statement; the records may be in any code such as EBCDIC. The data records end when one of the following is found:
/* in the input stream
// to indicate another JCL statement
The two-character delimiter specified by a DLM parameter on this DD statement The input stream runs out of card images.
Use a DATA parameter instead of the * parameter if any of the data records start with //.
Considerations for an APPC Scheduling Environment
The * parameter has no function in an APPC scheduling environment. If you code *, the system will check it for syntax and otherwise ignore it.
1.Syntax//ddname DD *[,parameter]... [comments]
When you do not code BLKSIZE and LRECL, JES uses installation defaults specified at initialization.
Note: If the input stream is from NJE (network job entry), JES uses the size specified at the sending node.
3.Relationship to Other Parameters
You may specify the following DD parameters with the DD * and DD DATA parameters. All other parameters are either ignored or result in a JCL error.
Restrictions When Coding LRECL
If you code LRECL with the * parameter, you cannot submit a data set to JES3 with a record length greater than 80 bytes.
You cannot use the TSO/E SUBMIT command to submit a data set to JES2 or JES3 with a record length greater than 80 bytes.
You can submit a data set to JES2 or JES3 with a record length greater than 80 bytes by submitting the following JCL:
In this example, IBMUSER.LONGDATA.JCL contains the data with a record length greater than 80 bytes.
In a JES3 system, the record length limit is the size of the installation-defined spool buffer, minus 44. (For example, if the buffer size is 4084, the record length limit is 4040.) JES3 fails any job that exceeds this limit.
If the records longer than 80 bytes include JCL to be transmitted to a remote system using JES3 // XMIT or //*ROUTE XEQ, or JES2 /*ROUTE XEQ or /*XMIT with JES3 in the network, the records are truncated to 80 bytes.
For JES3 SNA RJP Input
For 3540 Diskette Input/Output Units
VOLUME=SER, BUFNO, and DSID on a DD * statement are ignored except when they are detected by a diskette reader as a request for an associated data set. On a DD * or DD DATA statement processed by a diskette reader, you can specify DSID and VOLUME=SER parameters to indicate that a diskette data set is to be merged into the input stream following the DD statement.
4.Relationship to Other Control Statements
Do not refer to an earlier DD * statement in DCB, DSNAME, or VOLUME parameters on following DD statements.
5.Location in the JCL
A DD * statement begins an in-stream data set.
In-stream Data for Cataloged or In-stream Procedures
A cataloged or in-stream procedure cannot contain a DD * statement. When you call a procedure, you can add input stream data to a procedure step by placing in the calling step one or more DD * or DD DATA statements, each followed by data.
Multiple In-Stream Data Sets for a Step
You can code more than one DD * or DD DATA statement in a job step in order to include several distinct groups of data for the application program. Precede each group with a DD * or DD DATA statement and follow each group with a delimiter statement.
Omitted Data Delimiters
If you omit a DD statement before the input data, the system provides a DD * statement with the ddname of SYSIN. If you omit a delimiter statement after input data, the system ends the data when it reads a JCL statement or runs out of card images.
If the processing program does not read all the data in an in-stream data set, the system skips the remaining data without abnormally terminating the step.
7.Examples of the * Parameter
This example defines two groups of data in the input stream.
This example defines an in-stream data set with INP3 as the last qualifier of the system-generated data set name. A name such as userid.jobname.jobid.Ddsnumber.INP3 is generated.
This example defines two groups of data in the input stream. The input data defined by DD statement SETUP.INPUT1 is to be used by the cataloged procedure step named SETUP. The input data defined by DD statement PRINT.INP is to be used by the cataloged procedure step named PRINT.
IBM-JCL Related Interview Questions
|VSAM Interview Questions||IBM - VSAM Interview Questions|
|IBM-CICS Interview Questions||JCL Interview Questions|
|IBM DB2 Interview Questions||COBOL Interview Questions|
|DB2 Using SQL Interview Questions||IBM-JCL&VSAM Interview Questions|
|IMS/DB Interview Questions||Mainframe DB2 Interview Questions|
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.