CA7 Calendar Maintenance

442 views
Skip to first unread message

Jags

unread,
Sep 29, 2013, 8:00:37 AM9/29/13
to mainfr...@googlegroups.com


Hi All,

I have a query on CA7 calendar maintenance. It might be a basic question but still I don't have knowledge on this.
I have worked in CA7 monitoring for sometime.

I wanted to know
1) why do we do CA7 calendar maintenance ? I heard its done twice a year but am not sure why we need to do that.If a job is being added to the calendar say with particular day/time its going to run until we have a change in the scheduled time. (or) Is it done only because of the change in holidays every year ?


I tried searching through internet but none helped me.Thanks

Quasar Chunawala

unread,
Sep 29, 2013, 12:11:36 PM9/29/13
to mainfr...@googlegroups.com
Jagadeesh,

Transplant yourself temporarily in the mindset of the 70's. Pretend that we still live in that bygone era. Computer processing power was expensive at the time. Programs and their input data(on punched cards) were stacked together and processed in a batch. The process was called Batch processing. Critical business processing for example - payroll processing, billing was done in batch mode. 

Batch jobs process large amounts of data. So, it's not practical to expect immediate output. However, pre-defined deadlines known as Service Level Agreement(or SLA's) are set either by a business requirement or simply because another dependent batch job has to start. For example, a group of batch jobs of an organization that generate payroll may need to complete by 06.00 am EST, so that the bank(say Citibank) has enough time to transfer funds/salary into employee accounts.

Typically, a job scheduler executes a series of batch jobs, without manual intervention. It allows you to launch a job at a set time. It allows you to re-submit failed jobs. These products offer a console, sometimes a GUI interface to monitor job streams. On the z/OS platform, there are many scheduling products - Computer Associate's CA-7, OPC, BMC's Control-M, Cybermation's ESP, IBM's Tivoli Workload scheduler(TWS) etcetera.

See, calendars allow jobs to share a common scheduling pattern. A calendar includes all the working days and public holidays in the year. You can attach one or more jobs to a calendar. I guess, you must be knowing about base calendars in CA-7.

HTH..

Regards,
Quasar

--
You received this message because you are subscribed to the Google Groups "Mainframes 360" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mainframes36...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mainframes360/58a3d29e-cc42-462f-ac03-7c8f713e71b6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Jagadeesh Sekaran

unread,
Sep 29, 2013, 12:59:00 PM9/29/13
to mainfr...@googlegroups.com
Thanks Quasar..

Not sure If I made you to understand my query right..

I just have a little knowledge on calendars..I have seen base calendars..People create different calendars with different SCAL ID as per the requirement..But I don't understand one thing why do they do something called Calendar maintenance twice a year..even if it's once a year I can believe that holidays,days,leap year,etc going to change so they are doing it...


1) I wanted to know what actually happens on calendar maintenance ?
2)why do they do it twice a year ? (CA recommends it to do twice, but why)

I am just a learner in  CA Calendars so do not mistake if these query seems to be very basic..



For more options, visit https://groups.google.com/groups/opt_out.



--
Thanks & Regards,
 Jagadeesh Sekaran

Quasar Chunawala

unread,
Sep 29, 2013, 1:32:06 PM9/29/13
to mainfr...@googlegroups.com
I see your point. It's simple - schedules usually expire in June or 31st December. Post that, you've got to resolve the schedule (SCHID) with a base calendar, so that CA-7 can create the actual schedule date(s) and time(s). That's why, the resolution has got to be done twice a year.

HTH...

Jagadeesh Sekaran

unread,
Sep 29, 2013, 1:41:03 PM9/29/13
to mainfr...@googlegroups.com

Ok. So it's simply for this reason (since its been set to expire on these dates) we are doing it twice..Thanks...

                  -
$ent from HTC Desire S

Quasar Chunawala

unread,
Sep 29, 2013, 1:56:28 PM9/29/13
to mainfr...@googlegroups.com
You got that! June to December is also that time of the year, when the calendar for the next year is available. Makes sense to do the global resolve twice a year, once at the start of the year, once after the calendar for the new year has been published, post-June. And of course, if the schedule(SCHID) for a certain job is modified, you can do a resolve anytime.
Reply all
Reply to author
Forward
0 new messages