Introduction to CA7 job support
CA Technologies sold software package of CA-7 is workflow automation or job scheduling. It is used by banks. In a variety of scheduled and ways to run Jobs can be manipulated. Any job triggering by this job will be done and any dependencies of this job on other jobs will be posted. Using to run ad-hoc jobs under CA 7 thoroughly along with manual methods by the Event and Date or Time and driven scheduling methods are discussed. Forcing the job as having completed successfully and a job complete tells CA-7 to treat to continue processing.
Overview of CA7 Job support
This course explains how CA 7 keeps track of data sets used by jobs under its control and describes job attributes required when defining a job in CA 7 job support. When it does not require an immediate remedy or the job stream can continue and a job is forced complete when it returns an acceptable condition code. However, the job dependency, will not be posted if the dependent job does not complete successfully. Also, both mean to the CA-7 queue remove a job from the terms “cancel” and “force complete”. Any job triggering by this job will be done and any dependencies of this job on other jobs will be posted. The job waiting in the queue will be submitted upon successful completion of the preceding job. But the results are completely different. Any dependencies of this job on others will not be posted, no job triggering will be done but the job will be removed from the CA-7 queue. This command is used to stop a job stream. “Job dependency” and “job triggering” are two common terms that have caused confusion. Before the job waiting in the queue can run a job dependency is a job that must complete. The queue does just the opposite from canceling a job.