Look-back dependency stopped working

[L.LEONG]

I have a test environment running WLA AE and WCC in a Linux environment and the look-back dependencies on NEW jobs I recently added don't work.  (On existing jobs, look-back dependencies still work.)  In my test jobs, JobB is looking for the completion on JobA in the last 4 hours.  So my condition statement in JobB looks like this:

   condition: s(JobA,04.00)

 

I have created and successfully testing look-back dependencies on jobs built earlier but recently I added 100+ jobs to the test system and noticed that all the new jobs I added with look-back dependencies don't start as they should.  If I remove a look-back dependency on those new jobs - and code "s(JobA)" instead - the follow-on job, JobB, will start right away.

 

Can't figure out why this is happening. I am wondering if I have a database issue because of the addition of a 100+ new jobs.

[Chandru.Venkataraman]

Hi Leo,

Can you please share the AE release and SP level?

Are the new jobs in a box? Was the predecessor job overidden (one time job override) any time?

Increase in job count doesn't lead to look-back dependency issues. I've once seen a similar issue when new jobs were added to an existing box in RUNNING status.

 

Thanks,

Chandru

[L.LEONG]

AE is at R11.3

Jobs are not in a box. 

The predecessor job had not been overridden.

When I loaded the 100+ jobs there were no boxes defined and none of those jobs existed before my load using JIL.

[Kishore Kumar Udathaneni]

Hi,

In your test scenario, Can you try the job_depends to see the current status of the atomic conditions for the job which does not run per look-back? 

job_depends -J JobName -c

 

Regards,

Kishore Kumar Udathaneni

[L.LEONG]

Sorry to take so long replying. I did a job_depends on my problem job. It has a look back of 2 hours on 2 predecessor jobs.  After running those 2 predecessor jobs, I did a job_depends on the follow-on job and it still said "F". I would have expected it to say "T".  So the status of the predecessor jobs are not getting updated properly after they complete.

 

job_depends -J TEST_DEV_LLL_email3 -c gives me this:

 

Atomic Condition                               Current Status   T/F
----------------                                        --------------         ---
s(TEST_DEV_LLL_email1,02.00)     SUCCESS         F
s(TEST_DEV_LLL_email2,02.00)     SUCCESS         F

 

 

However, when I look at the TEST_DEV_LLL_email3 job in the WCC GUI, the statuses don't match:

The following table is based on the condition: s(TEST_DEV_LLL_email1,02.00) & s(TEST_DEV_LLL_email2,02.00)

Atomic Condition	Current Status	Condition Satisfied
s(TEST_DEV_LLL_email1,02.00)	SUCCESS	true
s(TEST_DEV_LLL_email2,02.00)	SUCCESS	true

[Chandru.Venkataraman]

If it's dual event server environment, please ensure both databases are synchronized.

[L.LEONG]

No, I don't have a dual event server environment. Everything is on 1 server as you can see. Looks like they are all running. If I remove the look back dependency it all works again, that is, the T/F indicator changes properly.  It has been very inconsistent.  I have had look backs work on some jobs then when I add new ones - or sometimes even update existing ones - the look back can stop working.

 

CA Services Status Report

Component Name Pid Status
------------------------------------ ------- --------------
WAAE Application Server (ACF)  24702 running
WAAE Scheduler (ACF)      24798 running
WAAE Agent (WA_AGENT)   24628 running
CA-uwccmonitordb Server  4569 running
CA-uwccforecastdb Server 4192 running
CA-uwccconfig Server 3850 running
CA-uwccrmtsvcs Server 9667 running
CA-uwccresources Server 9289 running
CA-uwccquickview Server 8907 running
CA-uwccquickedit Server 8530 running
CA-uwccmonitoringcollector Server 8156 running
CA-uwccmonitoring Server 7776 running
CA-uwcclauncher Server 7399 running
CA-uwccjscservant Server 7016 running
CA-uwccjsc Server 18220 running
CA-uwccha Server 6263 running
CA-uwcceventcpm Server 5885 running
CA-uwcccmdapp Server 5509 running
CA-uwccappeditor Server 5098 running
Postgres 26122 running
CA-diadna Server 27325 running
CA-diaukb Server 27930 running
CA-CCI Server 28129 running
CA-CCI Remote Server 28132 running
CA-CCI Clean Up 28130 running
CA-CCI Legacy Proxy 28131 running
CA-Message Queuing Service 32088 running
AIS RMI Server 32648 running
CA-Doc Help 29180 running
CA-Calendar Server 29264 running
CA-WV Status Server 30181 running
CA-EM Routing Server 28780 running
CA-Event Manager 30658 running
CA-Event SAF Client 30719 running
CA-Event Syslog Reader 30717 running
CA-Event Total Action process(es)   -     0 running
CA-AMS Sender Daemon 31281 running
CA-Star Server 31338 running
CA-SNMP Trap Multiplexer 31472 running
CA-SNMP Trap Manager 31474 running
UBI-Java Service 2217 running
UBI-Logon Server 2263 running
UBI-EM Application Server 2270 running
UBI-EM Tree Server 2275 running

[Steve Carrobis]

Wow all of that running on one server?!

 

 

 

Steve C.

 

 

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

 

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

[L.LEONG]

Yes, lots, huh!  But this is a test environment and nothing is scheduled to run on a regular basis.  We are new to this tool and are using it to test some batch cycles.

[Legacy User]

Hello

 

We have fixed problems with look-back conditions in CA WAAE 11.3 SP1 INCR 4

 

29. JOB HAVING LOOK-BACK CONDITION DOES NOT START

A successor job having a look-back dependency was not triggered when
its predecessor was overridden before the start of the successor.

 

Last patch for CA WAAE 11.3 is 11.3 SP1 INCR4 CUM3

 

Visit our support.ca.com server to download the latest patch that can be applied in your environment

 

Regards

Jean Paul

[L.LEONG]

Thanks, everyone, for the tips. I think the udaki01's suggestion to run the job_depends command helped me get on the right trail to the solution.  Running that command and seeing how the job's status T/F flags did not compare with the flags in the WCC GUI made me wonder why the two didn't match.  This is a test system and has never been maintained because it was not needed until recently.  

 

So my solution was to clean up the database by running the "DBMaint" command.

 

Now my job status flags match in the GUI and when running the job_depends command - and my look back condition works.