In article <[EMAIL PROTECTED]>, Roman V. Shaposhnik <[EMAIL PROTECTED]> wrote:
>ron minnich wrote:
>> more useless crap from memory:
>>
>> the actual correct usage is
>> //GO.SYSIN DD *
>>
>> but of course the * would make things messy.
>>
>> See this and realize this stuff is still being taught!
>
Now, if I can figure out how to do the over punch on this keyboard. :)
Job control language was more like assembler with very, very simple
operations. The problem was that a lot of verby things got put into the
operands.
DD means data definition. The first symbol, SYSIN in this case, is the
> bundles are implemented by here documents,
> and the end marker for the document must not appear
> in the data
vague recollection (1982), it was something like:
//SYSIN DD *
data
records
go
here
/*
Charles Forsyth wrote:
JCL == Java Control Language?
the Job Control Language for System/360
Yeah, I kind of knew that ;-) I was trying to come
up with the best joke I could. If this is not it, I have
no clue what could be funny about JCL ;-)
bundles are implemented by here documents,
>JCL == Java Control Language?
the Job Control Language for System/360
if you follow the link i gave you'll see more.
bundles are implemented by here documents,
and the end marker for the document must not appear
in the data, and IBM JCL syntax (even if it were strictly correct)
was unlikely to
> Job Control Language, I am not sure, but I belive was/is used in batch
> proccessing in the IBM Mainframes.
if invented today, it would be called cobolscript.
- erik
Job Control Language, I am not sure, but I belive was/is used in batch
proccessing in the IBM Mainframes.
Roman V. Shaposhnik escribió:
ron minnich wrote:
more useless crap from memory:
the actual correct usage is
//GO.SYSIN DD *
but of course the * would make things messy.
See this and rea
ron minnich wrote:
more useless crap from memory:
the actual correct usage is
//GO.SYSIN DD *
but of course the * would make things messy.
See this and realize this stuff is still being taught!
http://www.coba.unt.edu/itds/courses/bcis3690/bcis3690.ht
So... for the dense ones (like myself), w
more useless crap from memory:
the actual correct usage is
//GO.SYSIN DD *
but of course the * would make things messy.
See this and realize this stuff is still being taught!
http://www.coba.unt.edu/itds/courses/bcis3690/bcis3690.htm
ron
Charles, Rob, Greg,
Thanks for the context.
Greetings, Sander.
In article <[EMAIL PROTECTED]>,
Sander van Dijk <[EMAIL PROTECTED]> wrote:
>Does anyone know what the meaning/origin of "//GO.SYSIN DD" in
>bundle(1) is? I've seen this on other unix-likes as well, but I
>thought I'd ask here since the awareness of historical context seems
>to be quite a bit above
I first saw it used in bundling software created by James Gosling,
and liked the (relevant, I might add) joke so much I put it in the
Plan 9 version.
-rob
see these manual pages:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA1B640/12.0?DT=2718114500
--- Begin Message ---
Hi 9fans,
Does anyone know what the meaning/origin of "//GO.SYSIN DD" in
bundle(1) is? I've seen this on other unix-likes as well, but I
thought I'd ask here si
Hi 9fans,
Does anyone know what the meaning/origin of "//GO.SYSIN DD" in
bundle(1) is? I've seen this on other unix-likes as well, but I
thought I'd ask here since the awareness of historical context seems
to be quite a bit above average on this list.
Thanks, Sander.
14 matches
Mail list logo
