View previous topic :: View next topic
|
Author |
Message |
vidhyanarayanan
New User
Joined: 23 Dec 2005 Posts: 52
|
|
|
|
Hi all,
why JCL has slashes // in col1 and col2 of each STATEMENT? |
|
Back to top |
|
|
dneufarth
Active User
Joined: 27 Apr 2005 Posts: 419 Location: Inside the SPEW (Southwest Ohio, USA)
|
|
|
|
identifies it as JCL as opposed to inline data or JES control statements |
|
Back to top |
|
|
pspreddy
New User
Joined: 14 Mar 2006 Posts: 24 Location: Chicago
|
|
|
|
The identifier field is the first field in a JCL statement.
Two slashes, //, in positions 1 and 2 instruct the computer to expect a JCL statement.
A slash and an asterisk (/*) in positions 1 and 2 identify a JES2 statement.
If you are entering data, omit the identifier.
Thanks
Shiva |
|
Back to top |
|
|
Bharanidharan
New User
Joined: 20 Jun 2005 Posts: 86 Location: Chennai, India
|
|
|
|
The root goes far back in time!
The pioneers, when designing a language for MVS to interpret which they knew would be used forever, arrived at a consensus that all JCL commands/statements to be appended with // in the punched cards such that card reader would know that the cards necessarilly contain commands to get the job done in mainframe. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
Back when punched cards were used to submit JCL, if the cards were mistakenly loaded into the reader incorrectly, the slashes wouldn't be read first and the card deck would be rejected. |
|
Back to top |
|
|
|