It wouldn't help; lots of people don't know what they platform that they are running on can do, much less other platforms. If I had $1 for every time somebody told me that, e.g., ISPF, couldn't do that I'd been doing for decades ...
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Tony Thigpen <[email protected]> Sent: Tuesday, July 10, 2018 9:15 AM To: [email protected] Subject: Re: Burroughs WFM vs. z/OS JCl and VSE JCL wasRe: REXX as JCL replacement I wish those of you not current on VSE would remember that we have had just as many years to change things as z/OS has. Oh, wait, we have longer. DOS came out before what ever MVS was called back then. z/VSE has a lot of things in the JCL that z/OS has no equal to. I work both areas and there are many things in z/VSE that I miss in z/OS. There are also some things in z/OS that are not in z/VSE, but the last z/VSE to z/OS conversion I did, the client programmers hated the 'limitations' they found in z/OS and had to go do a lot of program changes due to these limits. Later, when I have time, I will list some of those things. Tony Thigpen ITschak Mugzach wrote on 07/10/2018 08:46 AM: > ... 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 <[email protected]> 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 <[email protected]> >> 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 [email protected] with the message: INFO IBM-MAIN >> > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
