We interrupt this week’s Tuesday’s Tip to bring you breaking news! CA 7 support now has a CHAT feature. When you log in to Support Online to open a case with support, there is a new CHAT button available. If you just have a question or need clarification on some feature within CA 7, instead of opening a case, you can do a quick CHAT with one of us support representatives. We are very excited to be able to communicate with you, our cilents, in this quick and easy way—no need to open a case and wait for a call-back or email—instant answers (or at least very quick :-) ). Now back to our regularly scheduled Tuesday’s Tip: Last week I promised you a tip on how to get job requirements ‘back in sync’ once they have run out of order. When a job enters the queue with a job requirement, the LAST-RUN DATE/TIME is checked to see if the job that is the requirement as run since the job with the requirement last ran. You can see the dates and times that are compared by doing an LJOB command and checking the LAST-RUN DATE/TIME: LJOB,JOB=MARYSUE JOB=MARYSUE DATE=15.202 PAGE 0001 JOB ----JCL--- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME MARYSUE 000 MARYSUE LVL1 000 ALL *NONE* *NONE* 000 000 0000 15202/0836 If the jobs run out of order sometimes you need to get things ‘back in sync’—and that can be accomplished by a command to reset the LAST-RUN DATE/TIME: NXTCYC,JOB=jobname,SET=RUN,LRDATE=yyddd,LRTIME=hhmmssth If you have questions on this feature (or others), you know what to do now—LET’S CHAT! Until next time—Bye,Y’all |