ObSchiller "Mit der Dummheit kämpfen Götter selbst vergebens" Pistol. Foot.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Tom Brennan <t...@tombrennansoftware.com> Sent: Thursday, November 19, 2020 7:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Is there a JES2 command to submit a job? Let's say the started task is setup as SURROGAT for multiple userids. As one of those id's, if I am given access to the JCL I could submit a job as if I was another one of those id's. No? On 11/19/2020 4:12 PM, Seymour J Metz wrote: > Sure, but why do you think that specifying the userid will do them any good? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > ________________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of > Tom Brennan <t...@tombrennansoftware.com> > Sent: Thursday, November 19, 2020 2:16 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Is there a JES2 command to submit a job? > > I just thought of one more problem with my scenario. If the JCL can be > updated by the user, then they could set USER= to whatever they want, > spoiling the idea of using a single STC for multiple users. > > On 11/19/2020 11:13 AM, Tom Brennan wrote: >> So if the JCL dataset can be updated by the user and they decide to >> remove the USER= parm, then the STC userid would get control. And in >> that case the unique userid set up for that STC would have little access >> and would likely fail on the first dataset. >> >> Do I have that about right? >> >> On 11/19/2020 11:04 AM, David Spiegel wrote: >>> Hi Skip, >>> "... the default SAF userid for STCs will be propagated to the >>> submitted job ..." >>> If the submitted job has a USER= on the Job Card and the RDR STC's >>> Userid has SURROGAT to all owner of SUBMIT'd Jobs, this is not a problem. >>> (I also would not give RDR the default STCID.) >>> >>> Regards, >>> David >>> >>> On 2020-11-19 13:45, Jesse 1 Robinson wrote: >>>> We use a similar process. The supplied RDR proc is a bit clumsy with >>>> stuff coded that would work as is for pretty much no one. So like >>>> many other shops, ages ago we wrote our own version with customized >>>> data set and unit parameters. >>>> >>>> The big problem with an RDR-like solution is that the default SAF >>>> userid for STCs will be propagated to the submitted job. That might >>>> be wildly inappropriate for the average user. >>>> >>>> . >>>> . >>>> J.O.Skip Robinson >>>> Southern California Edison Company >>>> Electric Dragon Team Paddler >>>> SHARE MVS Program Co-Manager >>>> 323-715-0595 Mobile >>>> 626-543-6132 Office ⇐=== NEW >>>> robin...@sce.com >>>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >>>> Behalf Of Herring, Bobby >>>> Sent: Thursday, November 19, 2020 8:26 AM >>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>> Subject: (External):Re: Is there a JES2 command to submit a job? >>>> >>>> *** EXTERNAL EMAIL - Use caution when opening links or attachments *** >>>> >>>> We have a rather simple solution we use. >>>> >>>> We have this command in the JES commands member: >>>> >>>> $TA,T=23.00,''$VS,''''S JOB,J=CLEANJES''''''' >>>> >>>> That starts a started task called JOB. It is in a library that is in >>>> the JES PROCLIB concatenation. >>>> >>>> It looks like this: >>>> >>>> //JOB PROC J=XXX, /* MEMBER NAME TO SUBMIT */ >>>> // L='SYS1.TXFZ.OPERJOBS.TZ' /* LIBRARY TO SUBMIT FROM */ >>>> //*----------------------------------------------------------------*/ >>>> //*@ STARTED TASK TO SUBMIT JOBS */ >>>> //*----------------------------------------------------------------*/ >>>> //STEP1 EXEC PGM=IEBGENER >>>> //SYSPRINT DD SYSOUT=* >>>> //SYSUT2 DD SYSOUT=(A,INTRDR) >>>> //SYSUT1 DD DISP=SHR,DSN=&L.(&J.) >>>> //SYSIN DD DUMMY >>>> >>>> The JES command formats out like this: >>>> >>>> S JOB,J=CLEANJES >>>> >>>> Which starts JOB and it submits CLEANJES from the >>>> SYS1.TXFZ.OPERJOBS.TZ library to the queue. >>>> >>>> The commands member gets submitted each day at midnight to refresh >>>> the commands. >>>> >>>> //CMDSTXFZ JOB (HSKP),'CMDSTXFZ',CLASS=K,MSGCLASS=9, >>>> // MSGLEVEL=(1,1),REGION=0M >>>> //* >>>> //* LIB: SYS1.TXFZ.OPERJOBS.TZ(CMDSTXFZ) >>>> //*@ COMMANDS TO ISSUE AT IPL TIME AND EVERY 24 HOURS >>>> //* >>>> // COMMAND '$CA,ALL' >>>> // COMMAND '$TA,T=05.00,''$VS,''''S JOB,J=CLEANJES''''''' >>>> // COMMAND '$TA,T=24.00,''$VS,''''S JOB,J=CMDSTXFZ''''''' >>>> // COMMAND '$SA,ALL' >>>> //STEP1 EXEC PGM=IEFBR14 >>>> /* >>>> >>>> Bobby Herring >>>> Texas Farm Bureau Insurance >>>> Waco, Tx >>>> >>>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >>>> Behalf Of Charles Mills >>>> Sent: Thursday, November 19, 2020 9:34 AM >>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>> Subject: Re: Is there a JES2 command to submit a job? >>>> >>>> I was and am under control on the $TA part and fully intend to use that. >>>> It's not the whole solution, though. My question was "what can the >>>> $TA schedule that will run a job" and these replies have provided the >>>> answer. >>>> The answer is something like >>>> >>>> $T A,xxxx,86400,'$VS ''S RDR,DSN=MY.PDS(MYJOB)'' ' >>>> >>>> I may not have the syntax and all the quotes perfect, but that's the >>>> idea. >>>> >>>> Charles >>>> >>>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >>>> On Behalf Of Jeremy Nicoll >>>> Sent: Thursday, November 19, 2020 1:20 AM >>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>> Subject: Re: Is there a JES2 command to submit a job? >>>> >>>> On Thu, 19 Nov 2020, at 00:19, Charles Mills wrote: >>>>> Right! I remember that. I remember that was how you ran anything. You >>>>> started a real reader: it fired up the 2540 and read in the job. And >>>>> then you did a S WTR (?) to print the output. OS/360 on a 360/40. >>>> But the S RDR... command doesn't start a real reader. It's just >>>> starting a >>>> started task. The previous reply talking about $TA etc was for >>>> faking a >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, send >>>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>> >>>> [https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.txfb-ins.com%2FTFBICImages%2Fjdpower.jpg&data=04%7C01%7C%7Cdbe10b7b8aec4101bfa808d88cbb5cf6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637414083644530352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FYz%2BlCiv3iZUyAe2nX4slghEUb0KeeVXqP5N0XIf9e4%3D&reserved=0] >>>> >>>> https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.txfb-ins.com%2F&data=04%7C01%7C%7Cdbe10b7b8aec4101bfa808d88cbb5cf6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637414083644530352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JNd1ZAKxaoP09C8pfNjmBaumN7bDzppD3Yw4dTTetLo%3D&reserved=0<https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.txfb-ins.com%2F&data=04%7C01%7C%7Cdbe10b7b8aec4101bfa808d88cbb5cf6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637414083644530352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JNd1ZAKxaoP09C8pfNjmBaumN7bDzppD3Yw4dTTetLo%3D&reserved=0> >>>> >>>> >>>> CONFIDENTIALITY STATEMENT: The foregoing message (including >>>> attachments) is covered by the Electronic Communication Privacy Act, >>>> 18 U.S.C. sections 2510-2521, and is CONFIDENTIAL. If you believe >>>> that it has been sent to you in error, do not read it. If you are not >>>> the intended recipient, you are hereby notified that any retention, >>>> dissemination, distribution, or copying of this communication is >>>> strictly prohibited. Please reply to the sender that you have >>>> received the message in error, then delete it. Thank you. >>>> ' >>>> >>>> ---------------------------------------------------------------------- >>>> 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 >>> >>> ---------------------------------------------------------------------- >>> 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 >> >> > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
