> The Mainframe version written in Assembler. The PC version is written in C.
Somewhat OT but why? Why not C on the mainframe? Why two code bases, one fairly easy to debug and one relatively hard to debug? I am thrilled with writing software for the mainframe in C (C++ actually) after years of laboring in assembler. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clement Clarke Sent: Monday, July 18, 2011 8:42 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Making Z/OS easier - Effectively replacing JCL with Unix like commands Thanks for all the questions. I'll put the questions and answers together for convenience. Paul Gilmartin wrote: > On Sun, 17 Jul 2011 23:35:30 +1000, Clement Clarke wrote: > > Isn't much of this what SMS is designed to do nowadays? You can still use SMS. Jol uses a simple VSAM file to store the information in. It's easy to add or change information. > Do I understand two separate modes of operation, dynamic and > generative? Yes. It can generate JCL, or use Dynamic Allocation to run the job in Batch, or immediately under TSO. > Does it provide en masse enqueues as JCL does, to avoid deadlocks? I > suppose this would be intrinsic in a generative mode. In Dynamic Allocation mode, there is still some JCL generated to ensure this. In TSO (Immediate mode), it is on a program by program basis. There is also an Enque instruction which you can use to enque on any resource. > How does it interface with JES3 setup processing? It has instructions to interface with JES3. You can also put any JCL statement out as part of the generated JCL. And there is an extremely flexible Macro language you can use to create new English style commands. These commands can effectively do anything from running programs in the compiler phase, or have them run at execution time. Or even generate JCL card images. > In a dynamic mode, are there any restrictions on running > APF-authorized programs? Must the interpreter be APF- authorized? There is a Jol Execution Monitor. It must be APF authorized to allow authorized programs to run. It uses the same style of ATTACH that the Initiator uses. It also allows Jol to put all important information on the Job Log. So, for example, all Catalog and Delete statement results can be found in one place, instead of having to hunt through the JCL listing. > Ia it portable? In at least a generative mode, can it run on a non-z > platform? I keep much of my JCL as here- documents (in-stream files) > in self-tailoring shell scripts on a Solaris platform (could be z/OS > Unix except for performance and flexibility). There are two main versions. The Mainframe version written in Assembler. The PC version is written in C. It will execute on Windows and generate Mainframe JCL to submit. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
