On Thu, Sep 5, 2019 at 7:59 AM ITschak Mugzach <imugz...@gmail.com> wrote:
> I wouldn't allow a cics to submit jobs on behalf of the user. not as a copy > to internal reader, nor by exec interface. I expect the jcl pass a change > management process and be stored in a production jcl dataset. the formal > and recommended way for jobs is to schedule them by a scheduler. all of the > job scheduler products I know allow turning a condition on, including > support for CICS transactions. > > If the job depends on data supplied by the transaction, it can read it from > a DB2 table, VSAM or any other data store. this way, multiple requesters > with different requirements (aka sysin) can run. on successful end, the > program can delete the entry from where it was read from. > > My two Israeli shekels. > I completely agree. Unfortunately, we have a number of batch jobs which are submitted by CICS transactions run by users. The JCL is contained in an ASSEMBLER non-CICS program in the DFHRPL. These modules do go through change control, but I don't really know how close they are examined. > > ITschak > > -- I find television very educational. The minute somebody turns it on, I go into the library and read a good book -- Groucho Marx Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
