And that is why I asked. I was making it too complicated.
Thank you very much > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Barkow, Eileen > Sent: Friday, October 19, 2018 10:16 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SDSF and z/OSEM and Automation > > You really do not need automation for this except to kick off a task that > uses SDSF/REXX to issue an "I" command to see the input queues and Then > select each entry to see the date/time the job was submitted. > You can find sample SDSF/REXX clists in the manual which do similar things or > I have some written which I can share with you. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Friday, October 19, 2018 12:37 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SDSF and z/OSEM and Automation > > So I want to create a process that "notices" that a job has been in the JES2 > Input queue for over 24 hours and not run. > > Sometimes this is legitimate and sometimes not. > > With z/OSEM we add resource names so the users do not need to code /*ROUTE > XEQ lpar to run. > > What I find is sometimes the resource name created in the JCL is not valid > for the environment. > > I know I can issue $DJxxxx,LONG and find out what resource it is waiting on. > > What I am struggling with is how can I see the INPUT queue and determine how > long a job has been waiting. > > I am thinking something with ISFEXEC (SDSF) that I can pass to automation to > make the determination and/or cancel of the task. > > I am just in the design phase, so no real details other than this sketch of > the process. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund Popper > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ________________________________ > > This e-mail, including any attachments, may be confidential, privileged or > otherwise legally protected. It is intended only for the addressee. If you > received this e-mail in error or from someone who was not authorized to send > it to you, do not disseminate, copy or otherwise use this e-mail or its > attachments. Please notify the sender immediately by reply e-mail and delete > the e-mail from your system. > > ---------------------------------------------------------------------- > 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
