Entry mode in these cases we're refering to are SSCN and DEMD. REQ is the queue name, not an entry mode. Jobs also can be demanded with triggers or maybe on hold, in which cases they might not start to run right away. ------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 792 809 198
2015-05-31 21:54 GMT-03:00 Rajesh Kumar <herowith.z...@gmail.com>: > if jobs are demand , you can see entry mode of job isDEMD .......... not > REQ ; Also if job is demand to ca7 it will not waiting for time or date > request , it will immediately start running. > > On Sun, May 31, 2015 at 5:53 PM, Lucas Rosalen <rosalen.lu...@gmail.com> > wrote: > > > Are you sure the other jobs are being added by SSCN? Maybe they have/had > > been demanded? > > > > Lucas > > On May 31, 2015 11:19 PM, "Rajesh Kumar" <herowith.z...@gmail.com> > wrote: > > > > > Hi Tony, > > > > > > I could see span value is *SPAN = 120 and INCREMENT = 60 from sscan* > ; > > > Span=120 is 2 hrs yearly, (span value must be less than increment) > > > > > > > > > SPAN= - CHANGES NUMBER OF HOURS SCHEDULE SCAN IS TO LOOK > > > FORWARD, DURING EACH WAKE-UP, FOR JOBS THAT MUST > > > BE ADDED TO THE QUEUES. VALUE MUST BE A NUMBER OF > > > HOURS FROM 1 TO 24. SPAN VALUE MUST NOT BE LESS > > > THAN THE INCR VALUE. > > > > > > > > > Hope now you understood yearly showing of job now.... > > > > > > Regards, > > > Rajesh > > > > > > On Sun, May 31, 2015 at 4:06 PM, Tony Thigpen <t...@vse2pdf.com> > wrote: > > > > > > > I was hoping someone was watching the list today that could help me > get > > > > over the hump on this one. > > > > > > > > I know there is some pattern, but it's just not clicking. Some jobs > > seem > > > > to jump in several hours early, while other jump in only 30 minutes > > > before > > > > their time. > > > > > > > > Tony Thigpen > > > > > > > > > > > > Lizette Koehler wrote on 05/31/2015 04:06 PM: > > > > > > > >> I might recommend that, if you have not done so, join the CA > Community > > > >> for CA7. Or open a case with CA. You may get a much faster > response. > > > >> > > > >> Lizette > > > >> > > > >> > > > >> -----Original Message----- > > > >>> From: IBM Mainframe Discussion List [mailto: > IBM-MAIN@LISTSERV.UA.EDU > > ] > > > >>> On Behalf Of Tony Thigpen > > > >>> Sent: Sunday, May 31, 2015 12:53 PM > > > >>> To: IBM-MAIN@LISTSERV.UA.EDU > > > >>> Subject: CA-7 question > > > >>> > > > >>> I am trying to better understand why jobs show up in the REQ when > the > > > >>> show up. > > > >>> For example, I have a job with the following: > > > >>> ID=003 ROLL=D INDEX=+000 > > > >>> SCAL= DOTM=1640 LEADTM=0010 SUBTM=1630 STARTM=1630 > > > >>> WEEKLY DAY=SUN > > > >>> > > > >>> And it already in the queue two hours early: > > > >>> LQ,SEQ=JOB > > > >>> XXXXXXX REQ 0823 151/1630 151/1630 151/1640 ALL- 003 SSCN 001 > > > >>> SLIF-00 REQUEST COMPLETED AT 14:44:59 ON 15.151 > > > >>> > > > >>> Yet, other jobs don't seem to appear until almost the time they > need > > to > > > >>> run. I > > > >>> think it has to do with the SSCAN values, but nothing seems to be > > > making > > > >>> sense at this point: > > > >>> SSCAN > > > >>> CURRENT SCHEDULE SCAN VALUES > > > >>> ---------------------------- > > > >>> SPAN = 120 INCREMENT = 60 > > > >>> QUEUE DWELL = 30 SKELETON RETRY = 0 > > > >>> REPROMPT = 10 > > > >>> LEAD TIME = 0 > > > >>> STATUS: REQQ IS ACTIVE ABR MSGS = NO > > > >>> RDYQ IS ACTIVE HOLD JOBS = NO > > > >>> NEXT SCAN WAKE-UP = 15151 AT 1517 > > > >>> NEXT SCAN PERIOD START TIME = 15151 AT 1647 > > > >>> > > > >>> -- > > > >>> Tony Thigpen > > > >>> > > > >>> > > > >> > ---------------------------------------------------------------------- > > > >> 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
