Doubt in CA7



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

Doubt in CA7

Postby Balamurugan3 » Thu Nov 05, 2009 4:05 pm

I am new to CA7..........

can anyone say me what is the difference between successor job and triggered job????

I have a job job1................which when listed in CA7 environment shows as.........
*********************************
LJOB,LIST=ALL,JOB=JOB1

Triggered by JOB0...

SUCCESSOR JOBS JOB3
*********************************

I have a another job job2 .......... which when listed in ca7 shows as..............

*********************************
LJOB,LIST=ALL,JOB=JOB2

Triggered jobs JOB3
*********************************
So is that JOB3 is triggered by both the jobs???
If so how??? can any one say me ........


Thanks in advance...............
Many Thanks,
Bala
Balamurugan3
 
Posts: 17
Joined: Tue Sep 29, 2009 11:23 am
Has thanked: 0 time
Been thanked: 0 time

Re: Doubt in CA7

 

Re: Doubt in CA7

Postby dick scherrer » Fri Nov 06, 2009 1:02 am

Hello,

Suggest you invest some time studying the documentation. This is very basic info, but it is info you will use for"ever". . . Better to get a more thorough understanding in the beginning.

If your organization is licensed to use CA-7, all of the documentation is avaliable to download free from CA Support.

A trigger causes something to happen. A successor job follows some other.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: Doubt in CA7

Postby Bikash_Mishra » Mon Nov 23, 2009 2:10 pm

Please go through CA7 Docs this is the very basics of CA7. Self study is the best way to gain knowledge.

Any ways here is the answer to your question.

What is triggered job?

Sol) A is a Scheduled Scan job it triggers B, B in turn triggers C and C in turn triggers D.
That is B comes into queue after completion of A and C comes into queue after completion of B,

B is triggered job for A, C is triggered job for B and D is triggered job for C,

Where as

A is triggered by job for B, B is triggered by job for C and C is triggered by job for D

Triggered Jobs and Triggered By can be viewed with the command.


LJOB,JOB=<JOBNAME>,LIST=TRIG

eg:

JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME

XXXXXXX1 000 ABCDEFG MAXTHORN 000 ALL 013456 *NONE* 018 073 0111 05320/0205

----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS ------------------
JOB=XXXXXXX2 SCHID=002 DOTM=0330 LEADTM=0000 SUBMTM=0000

--------------------------- TRIGGERED JOBS ----------------------------
JOB=XXXXXXX3 SCHID=000 QTM=0010 LEADTM=0000 SUBMTM=0000

I the above command we see all the jobs that triggers XXXXXXX1 and also all the jobs that it( XXXXXXX1 ) triggers (in this case XXXXXXX3)

But the best command to see the down stream jobs or triggered jobs for a particular job is as below (This command can be used when we find multiple jobs under TRIGGERED JOBS for the above command):

FSTRUC,JOB=<JOBNAME>, SCHID=XXXX

eg:

LEV# JOB NAME SYS START DTTM END DTTM TRIGGERING JOB/DSN/SID
--- XXXXXXXA............ 010Y 05327/0229 05327/0229 :001
001 XXXXXXXB.......... 010Y 05327/0259 05327/0303 YYYYYYYA :001
001 XXXXXXXC.......... 010A 05327/0239 05327/0241 YYYYYYYA :001
002 XXXXXXXD........ 010A 05327/0251 05327/0255 YYYYYYYC :001
002 XXXXXXXE........ 010A 05327/0251 05327/0255 YYYYYYYD :001
002 XXXXXXXF........ 010A 05327/1841 05327/1852 YYYYYYYE :001

This will show the complete down stream for the job with the tirgered jobs flowing down like a stream for easy visual understanding.

Next Question: What are successor jobs?

Sol) Consider X is Successor job of A that is X is dependent upon completion of job A to run

Successor jobs will check for the completion of dependent job to start running.

In above case A can itself be a sccan job or a triggered job and has nothing to do with X, however X when comes into queue will look back for completion of A.

The best command to check for successor job is

LJOB,JOB=<JOBNAME>,LIST=DEPJ

eg:

JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME

XXXXXXXA 000 XXXXXXXA MAXTHORN 000 ALL *NONE* *NONE* 035 223 4435 05325/0531

--------------------------- SUCCESSOR JOBS ----------------------------
JOB=/XXXXXXXB SCHID=000
JOB=/XXXXXXXC SCHID=000
JOB=/XXXXXXXD SCHID=001
JOB=/XXXXXXXE SCHID=001
JOB=/XXXXXXXF SCHID=001
JOB=/XXXXXXXG SCHID=006


Additional Information:

Consider job X is in queue but did not run and is showing late and we do not find why it is showing late for all known general reasons. In that case we can try the command LJOB,JOB=<JOBNAME>,LIST=RQMT, For this particular case LJOB,JOB=X,LIST=RQMT this will show all the requirements that needs to be satisfied before X can run so we can back track on those requirements and we will definite reach Job A this usually is called a Lead Time Miss if Job A has already run but Job X could not track it and a Schedule miss is job A has not run at all.

Hope the above helps.
Bikash_Mishra
 
Posts: 2
Joined: Fri Oct 30, 2009 7:52 am
Has thanked: 0 time
Been thanked: 0 time


Return to CA-7

 


  • Related topics
    Replies
    Views
    Last post