Counter
Thursday, February 19, 2009
Dependency
Dependency
As work is defined in the CA-7 database, dependencies (pre-execution or predecessor requirements) can be established so that work is not initiated until these dependencies are satisfied. Any job under the control of CA-7 can have predecessor requirements. CA-7 does not submit the job until all requirements are satisfied even though time scheduling criteria has been met.
The main categories of predecessor requirements are as follows:
· Successful completion of predecessor jobs
· Availability of data sets
· Date/time window
· Completion of an input network
· Mutual exclusivity with other jobs
· Specified manual activities such as JCL overrides and manual verifications
· Presence of other jobs in the CA-7 queues
What does the LEADTM value on the Requirement Definition mean?
LEADTM - Specifies satisfaction lead time in hours.
Values are the following:
· 0 - Specifies that the predecessor job must have started and completed successfully since the last run of the dependent job.
· Nn - Specifies that since the last run of this job, the predecessor job has started and completed successfully within the last nn hours.
Values for nn can be 1 to 98.
· 99 - Specifies that the requirement is never considered initially satisfied when this job enters the request queue. The dependent job must complete normally while this job is in the request queue.
As work is defined in the CA-7 database, dependencies (pre-execution or predecessor requirements) can be established so that work is not initiated until these dependencies are satisfied. Any job under the control of CA-7 can have predecessor requirements. CA-7 does not submit the job until all requirements are satisfied even though time scheduling criteria has been met.
The main categories of predecessor requirements are as follows:
· Successful completion of predecessor jobs
· Availability of data sets
· Date/time window
· Completion of an input network
· Mutual exclusivity with other jobs
· Specified manual activities such as JCL overrides and manual verifications
· Presence of other jobs in the CA-7 queues
What does the LEADTM value on the Requirement Definition mean?
LEADTM - Specifies satisfaction lead time in hours.
Values are the following:
· 0 - Specifies that the predecessor job must have started and completed successfully since the last run of the dependent job.
· Nn - Specifies that since the last run of this job, the predecessor job has started and completed successfully within the last nn hours.
Values for nn can be 1 to 98.
· 99 - Specifies that the requirement is never considered initially satisfied when this job enters the request queue. The dependent job must complete normally while this job is in the request queue.
Tuesday, February 17, 2009
CA7 - Work Scheduling
Work Scheduling:
CA-7 uses both date/time-driven and event-driven facilities to cause work to be scheduled and initiated. In CA-7, work is defined as CPU jobs, preprocessing and postprocessing workstation networks.
Event-driven scheduling, known as trigger scheduling, is a far more efficient technique than date/time oriented schedules.
For CPU jobs and preprocessing networks, date/time-driven schedules are generated through definition of base calendars and definition of schedules relative to base calendars. Once defined, work is automatically scheduled based on defined schedules and current date and time values within the CA-7 system. For postprocessing networks, output workstations are scheduled based on the scheduling of the CPU job to which the networks are connected.
Event-driven scheduling causes jobs to be scheduled or initiated based on completion of a previous activity or event. Event mechanisms are the creation of required data sets, completion of predecessor jobs, or completion of a preprocessing network.
Time-driven and event-driven facilities can be used in combination when scheduling and initiating work. For example, a CPU job can have a timed schedule for processing but can also have dependencies on data sets created by another job. When combined, time and event requirements must be satisfied before work is initiated.
The user should be aware that the schedule ID offers a powerful scheduling tool. Requirements, networks, JCL overrides, job triggers, etc can all be varied through the use of different schedule IDs.
For example, if a given job is to run on Monday through Friday but the requirements vary on Fridays, this same job could have a different schedule ID defined for its Friday run. Multiple schedule options can be chosen for a single schedule ID (daily and monthly). However, a job that is scheduled automatically on a defined date/time basis is not scheduled more than once per day for a given schedule ID.
CA-7 uses both date/time-driven and event-driven facilities to cause work to be scheduled and initiated. In CA-7, work is defined as CPU jobs, preprocessing and postprocessing workstation networks.
Event-driven scheduling, known as trigger scheduling, is a far more efficient technique than date/time oriented schedules.
For CPU jobs and preprocessing networks, date/time-driven schedules are generated through definition of base calendars and definition of schedules relative to base calendars. Once defined, work is automatically scheduled based on defined schedules and current date and time values within the CA-7 system. For postprocessing networks, output workstations are scheduled based on the scheduling of the CPU job to which the networks are connected.
Event-driven scheduling causes jobs to be scheduled or initiated based on completion of a previous activity or event. Event mechanisms are the creation of required data sets, completion of predecessor jobs, or completion of a preprocessing network.
Time-driven and event-driven facilities can be used in combination when scheduling and initiating work. For example, a CPU job can have a timed schedule for processing but can also have dependencies on data sets created by another job. When combined, time and event requirements must be satisfied before work is initiated.
The user should be aware that the schedule ID offers a powerful scheduling tool. Requirements, networks, JCL overrides, job triggers, etc can all be varied through the use of different schedule IDs.
For example, if a given job is to run on Monday through Friday but the requirements vary on Fridays, this same job could have a different schedule ID defined for its Friday run. Multiple schedule options can be chosen for a single schedule ID (daily and monthly). However, a job that is scheduled automatically on a defined date/time basis is not scheduled more than once per day for a given schedule ID.
CA7 - Introduction
CA-7 is an automated production control system. It is an online system that automatically controls, schedules, and initiates the production workload according to time-driven and event-driven activities. By using the CA7 job triggering feature a series of production jobs can be submitted based on the successful completion of one single job. CA7 supports both internal and external security.
CA7 capabilities include but are not limited to the following:
1. Work Load Scheduling – CA7 can schedule all activities associated with the production workload.
2. Job Restart – by using the CA11 option, jobs that fail can be restarted from a certain step or rerun as a production job through CA7.
3. Security – a security matrix is provided with CA7 to allow or restrict access to jobs in the database.
4. Help Facility – is an online function available at any CA7 terminal.
Queues in CA7 are PRE, DQT, REQ, RDY, ACT, PST, PRN and TRL
CA-7 supports two different formats for transaction input and output.
Online Format:
The Online format is used in CA-7 online terminal sessions. Online terminal sessions support command line input and output as well as data transfer using formatted panels. A command transaction begins with the command name and can be followed by parameters. Certain functions require formatted panel transactions. Most database maintenance functions require transactions in this mode.
Batch Format:
The Batch format is used by CA-7 external communicators such as the Batch Terminal Interface (BTI) and the CCI Terminal Interface. Command transactions are entered in batch format just as they would be in an online terminal session. Functions that use formatted panels in the online environment have special syntax requirements in batch, because formatted panels cannot be displayed in batch.
CA7 capabilities include but are not limited to the following:
1. Work Load Scheduling – CA7 can schedule all activities associated with the production workload.
2. Job Restart – by using the CA11 option, jobs that fail can be restarted from a certain step or rerun as a production job through CA7.
3. Security – a security matrix is provided with CA7 to allow or restrict access to jobs in the database.
4. Help Facility – is an online function available at any CA7 terminal.
Queues in CA7 are PRE, DQT, REQ, RDY, ACT, PST, PRN and TRL
CA-7 supports two different formats for transaction input and output.
Online Format:
The Online format is used in CA-7 online terminal sessions. Online terminal sessions support command line input and output as well as data transfer using formatted panels. A command transaction begins with the command name and can be followed by parameters. Certain functions require formatted panel transactions. Most database maintenance functions require transactions in this mode.
Batch Format:
The Batch format is used by CA-7 external communicators such as the Batch Terminal Interface (BTI) and the CCI Terminal Interface. Command transactions are entered in batch format just as they would be in an online terminal session. Functions that use formatted panels in the online environment have special syntax requirements in batch, because formatted panels cannot be displayed in batch.
Welcome Message
Hi Friends,
Welcome to the CA7 World Homepage !!!
This blog will help you to...
Welcome to the CA7 World Homepage !!!
This blog will help you to...
- Download/add Basic & Advanced CA7/CA11 materials,
- Find CA7/CA11/Contro-M/OPC/Autosys openings in Bangalore, Chennai, Hyderabad, all over India and Overseas
- Other important IT news, events, H1B / HSMP related info
Subscribe to:
Posts (Atom)
Posts
