Sender: |
|
Date: |
Wed, 14 Apr 1999 09:46:14 -0400 |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
Content-Type: |
text/plain; charset=us-ascii |
Organization: |
The University of Georgia |
From: |
|
Parts/Attachments: |
|
|
"Michael J. Langum" wrote:
>
> In the meantime, what is the syntax for constructing ListServ
> "Jobs"?
>
> And specifically, what is the meaning of:
> "DD=ddname" ;
> "// ddname DD * {i.e. "//", "ddname", "DD", and "*"}, and
> "/*" {on the last line}
Eric borrowed the format for his job control language from the IBM mainframe
world. This is basically system 370 JCL as used in MVS, or as it is known
today OS/390.
The first statement DD=ddname is strictly listserv. It tells the job
processor the name to be used on the DD (Data Definition) card.
The next line is a standard OS/390 DD card. It starts with two slashes
which indicates it's a JCL card. The next thing on the card is the name
to be associated with this dataset. Actually, there is no space between
the two slashes and the name. It should appear like "//ddname"
Next, is a space delimiter followed by the type of Job control card, in this
case DD or "Data Definition." Another space delimiter, and then comes the
source of the data. In this case, the single asterisk (*) indicates that
the data should be read from the input stream, stoping when a special end
of data card or another JCL card is read. This special card is blank
except for the two characters "/*" in columns one and two.
Actually, in real JCL, you can specify the delimiter so that you can
actually
read in jcl cards with delimiters in them as data.
This format looks something like this
//SYSUT1 DD *,DLM=$$
data card 1
data card 2
data card 3
/*
data card 5
data card 6
$$
Where the two characters $$ become the delimiter. They can be any two
characters which would otherwise not appear in the input data stream.
|
|
|