Please anyone can let me know how to find how many jobs were loaded into AJF on a day. Is there a direct method for this ? or we can check it somewhere from EM GUI ?
Basically I am trying to find out difference between “Maximum number of jobs in a single day” and “number of jobs loaded into control-m in a single day”
Please someone answer this asap.
Thanks
Abhishek
How to find how many jobs were loaded into AJF on a day
- abhishek_82
- Nouveau
- Posts: 1
- Joined: 27 Sep 2010 12:00
- Location: INDIA
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
abhishek_82,
The complexity depends on what kind of information you intend to obtain.
If you want an instant info on the number of jobs loaded, the GUI is enough: Just build a viewpoint which includes the ODATE as a high hierarchical level, right click on the block representing the current ODATE and hit the “Status summary” option. It will give you the global amount of jobs for that date.
If you intend to maintain long term data, the best is to rely on the contents of the database, and run automatic queries.
The simplest is to count the order messages on the log, which is usually maintained for several days.
Running a query against the log after the new day will give you the exact info about what happened for the previous day.
For example, if you newday time is +0600, the following request will give you on May 12th 2011 the total number of jobs either ordered (code 5065) or created (code 5407) on the production day May 11th 2011 (MS/SQL format. For Oracle replace the concatenation instruction ‘+’ by ‘||’).
select count(*) from CMR_IOALOG where LOGDATE+LOGTIME < '20110512055959' and LOGDATE+LOGTIME > '20110511060000'and MSGID in (5065, 5407)
Of course, this query can be set up automatically as part of your script, to dynamically adapt the date paramaters according to the current date.
You may modify the request, for example by filtering the message text (column MESSAGE) to exclude the Scheduling Groups (if any), which are ordered like the jobs and produce the same log message.
If you intend to count the number of job submissions, the request is the same, but the MSGID is 5105. The number of submissions is usually different because of cyclic jobs.
Cheers
Nicolas Mulot
The complexity depends on what kind of information you intend to obtain.
If you want an instant info on the number of jobs loaded, the GUI is enough: Just build a viewpoint which includes the ODATE as a high hierarchical level, right click on the block representing the current ODATE and hit the “Status summary” option. It will give you the global amount of jobs for that date.
If you intend to maintain long term data, the best is to rely on the contents of the database, and run automatic queries.
The simplest is to count the order messages on the log, which is usually maintained for several days.
Running a query against the log after the new day will give you the exact info about what happened for the previous day.
For example, if you newday time is +0600, the following request will give you on May 12th 2011 the total number of jobs either ordered (code 5065) or created (code 5407) on the production day May 11th 2011 (MS/SQL format. For Oracle replace the concatenation instruction ‘+’ by ‘||’).
select count(*) from CMR_IOALOG where LOGDATE+LOGTIME < '20110512055959' and LOGDATE+LOGTIME > '20110511060000'and MSGID in (5065, 5407)
Of course, this query can be set up automatically as part of your script, to dynamically adapt the date paramaters according to the current date.
You may modify the request, for example by filtering the message text (column MESSAGE) to exclude the Scheduling Groups (if any), which are ordered like the jobs and produce the same log message.
If you intend to count the number of job submissions, the request is the same, but the MSGID is 5105. The number of submissions is usually different because of cyclic jobs.
Cheers
Nicolas Mulot