... And I may add that if VSE JCL was so good, it wouldn't have so many private extensions (and I've seem some of them).
ITschak On Tue, Jul 10, 2018 at 2:37 PM Dana Mitchell <mitchd...@gmail.com> wrote: > My memories of VSE JCL are dated, and quite possbily incorrect with > current VSE, but I recall that I felt it was more complicated that MVS > jcl. It had more types of statements (although fewer parms per type), > JOB, * $$ JOB, UPSI, OPTION, LIBDEF, PAUSE, and EXEC statements. To > describe a disk file, potentially required at least 3 statements, ASSIGN, > DLBL, and EXTENT. Tape required ASSIGN and TLBL, tape, disk and inline > files were not interchangeable as far as programs were concerned. > > An interesting 'feature' was that syntax checking was done at execution > time, so when a JCL error was encountered, a console message was issued > that required a reply, allowing you to retype the errant statement. So in > the days of real card readers, if you needed to make a quick one time > change to a job, you could just flip the card around backwards, causing > 'Invalid Statement' console message prompt, allowing you to type in the > statement you really wanted. > > Dana > > On Mon, 9 Jul 2018 16:41:40 -0300, Clark Morris <cfmt...@uniserve.com> > wrote: > > How does z/OS JCL compare with VSE JCL? My memories of DOS360 JCL > probably are > >irrelevant. > > > >Clark Morris > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
