You are right, but i then the chwcker will depend on initiator availability, something i can't asure and the end user can't afford. So i forced the converter to fail. I do understand that thia is not yet a complete job interpetation, but this ia something i can change and think of later. I went directly to parsing because i needed dataset names, dispositions, program names, steplibs and task libs for program access checks.
I almost finished that phase. I hope to have some time soon to do the racf work. ITschak בתאריך 1 באוג 2017 17:06, "Paul Gilmartin" < 0000000433f07816-dmarc-requ...@listserv.ua.edu> כתב: > On Tue, 1 Aug 2017 08:21:53 +0300, ITschak Mugzach wrote: > > > >I took your advice so i placed the IF after a iefbr14 stwp with a fack > >label i can recognize. > >If no jcl error, the job is placed in the input queue and only JESJCLIN is > >listed in the dataset. Stem variable. So the purpose of the jcl error is > to > >move thee job to outout queue. > > > I remain curious. At least the IEFBR14 step should cause the job to be > executed and moved to the output queue. What does the sequence, > in interactive SDSF show: > ST /* show all jobs in all queues, held and not held data sets. */ > INPUT ON /* Show SYSINs */ > ? /* Show all spool files. */ > > >I created different stem variables for each of the stem variables and > using > >isfbrowse service so no datasets are involved. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
