Paul Gilmartin wrote:
On Thu, 5 Jul 2018 14:23:35 -0400, Hobart Spitz wrote:
I think a more encompassing approach would be for JOL to be a function,
command or environment which could be invoked from REXX.
JOL could be invoked from REXX. Or JCL.
When the JOL *compiler* is invoked from TSO though, the Panels and other
functions can be used to interact with the user, and suggested by the
main screen shown at www.Oscar-Jol.com
The job can then be submitted to batch to run, or executed under TSO.
I wonder how JOL addresses theneed for "parallel ENQs". S99WTDSN requires
APF authorization. Does JOL submit "optimized" JCL, or is it authorized so it
can do all the initiator does to run a mix of authorized and unauthorized steps.
Jol executes user programs in two main ways.
1. Jol can produce JCL which is run under the control of a "monitor"
program that catalogs data sets and runs programs underneath it.
2. It can use Dynamic Allocation and effectively replace the Initiator.
a) When the job is to be executed under TSO, no JCL is produced at all.
b) When submitted to batch, it produces some JCL to invoke the Jol
monitor, which does all the data set allocation and executes the problem
program.
... text deleted
UNIX has never had a separate batch scripting language.
There is a alpha test version of Jol that does run under Linux and
execute user programs, much like Z/OS batch.
That version of Jol is written in "C" and can produce Z/OS JCL, or run
Windows or Linux programs. It could be ported to Z/OS.
It also can produce VSE code, although it is in testing mode only.
Clem
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
