Job did not get posted even after negetive dependncy job ran



Unicenter CA-7 Job Management: CA's workload automation tool for managing, visualizing, automating, optimizing applications

Job did not get posted even after negetive dependncy job ran

Postby Bikash_Mishra » Fri Oct 30, 2009 8:37 am

Let Main Job = A
Let Internal Job = B

LQ, JOB=A

A REQ 0276 302/1808 302/1800 302/1820 ALL- 065 SSCN 001 LATE

------------------------- REQUIREMENTS STATUS -------------------------
_______ INTERNAL JOB=/B DATE/TIME=07302/1600

Main job came into Queue at 1800 hrs.

#########################################################################

Internal job B last ran and completed at 1803 with entry mode as RUN

C 07302/1803 J B 0326 001 COMP RUN 0000 07302/1737 07302/1803

##########################################################################

If we see for details for job A in DB.3.2 we see as below

------------------------ CA-7 CPU JOB PREDECESSORS -------------------------
FUNCTION: LIST (FORMAT,LIST,UPD) PAGE 0001
PRED FOR JOB: A LIST-SCHID:
OPT SCHID LEADTM PRED-JOB NEXT-RUN
0 0000 /B YES

That is Job B has look back time of 0 hrs or job A has Lead time of 0 hrs

As per Defination for 0 hrs lead time -The Main job will not look back for the completion of its internal job; Main job should see the completion of its internal job. Which was true for our case.

###########################################################################

The problem is Main Job A did not get posted Even if Internal job B completed after job A came into queue. Please help me in with a logical reason as to why the job A was not posted even after successful completion of job B ?
Bikash_Mishra
 
Posts: 2
Joined: Fri Oct 30, 2009 7:52 am
Has thanked: 0 time
Been thanked: 0 time

Re: Job did not get posted even after negetive dependncy job ran

 

Re: Job did not get posted even after negetive dependncy job ran

Postby ca706410 » Fri Feb 12, 2010 7:34 pm

Hello,

Problem here is explained by the following statement;

Internal job B last ran and completed at 1803 with entry mode as RUN

A job that is brought to the CA-7 queues via the RUN command (Entry Mode As RUN) does not post its job dependencies . The RUN Command is used to be able to cause an extra run of a CA-7 job without interfering with the CA-7 logic (dependencies and triggering) .
Job must either be triggered (Entry Mode AS Auto) or Scheduled (Entry Mode As SSCN) or Demanded (Entry Mode as DMD).

Hope that somewhat clarifies ...

Thanks,
Eric
ca706410
 
Posts: 6
Joined: Thu Oct 08, 2009 7:04 am
Has thanked: 0 time
Been thanked: 0 time


Return to CA-7