It is currently 18 Nov 2018 11:10


Post new topic  Reply to topic  [ 6 posts ] 
Author Message
PostPosted: 19 Apr 2011 5:05 
Offline
Nouveau
Nouveau
User avatar

Joined: 26 Sep 2008 12:00
Posts: 13
Hi All,

We have a bunch of jobs that loads at midnight (00:00) current day and runs/executes the next day once in conditions are satisfied. When using late time in Post Proc tab to send a shout alert, the alert being sent is not accurate, probably due to the 24 hr limit value on the late time. Is there a workaround on this issue? Any help is greatly appreciated. Thanks in advance.


Top
   
PostPosted: 20 Apr 2011 7:37 
Offline
Nouveau
Nouveau
User avatar

Joined: 11 Oct 2007 12:00
Posts: 161
Location: Melbourne
Can you give some more specifics:
Is your new day time midnight? When do they run? What is the late time alert?
You don't need to order in all jobs at new day time. It may be that you can solve your problem by using a different user daily for these tables and running the ctmudly job (to order these tables) at a later time. But I can't be sure until I have specific information.


Top
   
 Post subject:
PostPosted: 20 Apr 2011 11:47 
Offline
Nouveau
Nouveau
User avatar

Joined: 26 Sep 2008 12:00
Posts: 13
Our newday load is at midnight (00:00). 1 of our user daily e.g. named A1DAILY loads at 10:00 a.m. same day.

It includes for example jobs:

A
B
C
D

- Job A runs between 22:00 to 23:00 of same day, once successfully done passes out condition to job B.
- Job B runs from 23:01 to 03:00 of (next day), once successfully done passes out condition to job C and D.
- Job C and D are tagged critical jobs by business and it needs a late time shout. If I put a late time shout of 0900 on Post Proc tab for jobs C and D, we do not get late time alerts for jobs C and D which are currently scheduled to run but we get alerts of late time shout for jobs C and D once user daily A1daily loads on its scheduled time of 10:00 a.m. for jobs C and D which are scheduled to run for the next day.

I hope I have explained the issue and have given the specifics clearly.


Top
   
 Post subject:
PostPosted: 23 Apr 2011 9:45 
Offline
Nouveau
Nouveau
User avatar

Joined: 07 Jan 2010 12:00
Posts: 149
be_incontrol ,

There is basically no smart solution to your problem, for the time frame for shout is from 00 :00 to 23 :59, and is strictly a HHMM on 4 chars (no day type delay)

1°) There is a possibility, available since version 630 and called Time Synonyms, and which can extend the time frame from 00:00 to virtually 49:59. This is based on the actual new day time and does not apply to your case, for your newday time is 00:00.

2°) Another solution would be to order jobs C and D one day after job B, and use PREV in the condition dates. In that situation, SHOUT WHEN LATE 0900 would work for C and D, but ..
This is another problem if your jobs are not daily jobs, since PREV does not consider the ODATE of the predecessor, but the date of the current job .
To overcome that new problem, you should change the condition date in C and D definitions to B_C_OK **** and B_D_OK ****, and do not forget to delete these conditions in the OUT of C and D.

An inconvenient of this implementation is that you lose the ODATE consistency between your 4 jobs.

3°) Another solution is to create another job to check at 09:00 whether D or C are still in Wait status for any reason, and send the actual SHOUT if one of these 2 are still waiting. This job would be ordered one calendar day after A, B, C and D, and it should do something like.


ctmpsm -listall | egrep (C | D) | grep Wait | grep <ODAT> | wc -l

If the result is 0, that means that C nor D are not in Wait status anymore
If the result is 1 or 2, that means that C or D or both are still in Wait status.

The <ODAT> value matches the ODAT of C or D, and can be obtained in the script of the new job by something like:
ctmstvar 0 "%%$CALCDATE %%$ODATE -1".

The advantage of this solution is that you maintain the date consistency of you ABCD chain.
The inconvenient is that the control is made external to the chain


Cheers
Nicolas Mulot


Top
   
 Post subject:
PostPosted: 27 Apr 2011 6:57 
Offline
Nouveau
Nouveau
User avatar

Joined: 26 Sep 2008 12:00
Posts: 13
nicolas_mulot,

Thank you very much for your detailed solutions to my problem. I have implemented number 2 and it is working perfectly.

Regards,

be_incontrol


Top
   
 Post subject:
PostPosted: 06 Jul 2012 10:22 
Offline
Nouveau
Nouveau
User avatar

Joined: 05 Jul 2012 12:00
Posts: 2
Search engine optimization can increase the visibility of the website in the search engine. SEO companies know all combination of SEO techniques like social media marketing, link building etc.

seo expert
seo consultant
seo expert india


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 6 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited
The site created by Franck YOT. Images, logo, content and trademarks about Control-M products are property of BMC Software.
All the comments are property of their posters. Images, logo, content and design are © copyright by Scheduler-Usage.com. All Rights Reserved