Andy wrote:
*Isn't the goal here to identify jobs that have been submitted, but not
started? Long-running jobs don't fit that criteria, having already started
- or have I missed the point?Andy Stylesz/Series System Programmer*
*As I said, the utility could be modified to check arrival on the input
queue.*
*If it's an SDSF shop, RGEN will provide a useful skeleton from the I
(Input) panel.*
*The code snippet goes along the lines of:*
*Do ix=1 to JNAME.0 *
*/* if JNAME.ix = IPARM & QUEUE.ix = "EXECUTION" & ACTSYS.ix <> "", */ *
* if JNAME.ix = IPARM , *
* then Do *
* /* Issue the ? (JDS) action against the */ *
* /* row to list the data sets in the job. */ *
*Address SDSF "ISFACT ST TOKEN('"TOKEN.ix"') PARM(NP ?)" , *
*So substitute EXECUTION for whatever (INPUT?).*
*I don't have time to spend on this right now. However, I just submit a job
that runs all the time and it loops around every n minutes and checks
what's in the system.*
*If a job is INPUT, not EXECUTION, just compare the time it hit the queue
with current time and issue your WTO for automation to act on.*
*JESMSGLG is all you need to look at, for example:*
*23.49.05 JOB05080 ---- TUESDAY, 25 AUG 2020 ---- *
*23.49.05 JOB05080 IRR010I USERID BDB204 IS ASSIGNED TO THIS JOB. *
*For a job that is running/already ran, JESMSGLG has more information:*
*02.20.05 JOB05074 $HASP373 BDB204D STARTED - INIT 1 - CLASS A *
On Wed, Aug 26, 2020 at 7:11 AM R.S. <[email protected]> wrote:
> W dniu 25.08.2020 o 23:00, Styles, Andy (ITS zPlatform Services) pisze:
> > Classification: Public
> >
> > Isn't the goal here to identify jobs that have been submitted, but not
> started? Long-running jobs don't fit that criteria, having already started
> - or have I missed the point?
>
> Good point.
> IMHO you either use batch scheduler with all the facilities like
> late_sub, etc. or you just submit jobs into the queue and assign some
> INITs to it. Obviously the proper method is batch scheduler, but it is
> not free. Unless you already have scheduler.
>
> BTW: Long time ago I was a consultant in some shop and I was asked to
> clarify why job XYZ was running a lot of time, much longer than
> expected. First view in the output and few hours difference between "job
> submitted" and "job started".
> After that I was teaching JCL, teaching folks from that company - and I
> remebered to clarify dates in the output.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
> ======================================================================
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
> www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2020 r. wynosi 169.401.468 złotych.
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
>
> mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
> Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.401.468 as at 1 January 2020.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
Wayne V. Bickerdike
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
