Once a job is scheduled /triggered or manually added in CA7, it will start a process of moving through various QUEUES in CA7. CA7 will manage it until its completion.
Below is the diagram which shows in brief the lifecyle of the job inside a CA7 Scheduler.
Lets have a quick look into the Queues:
Request Queue: When a job enters CA7, it will reside in the request queue until all its requirements have been satisfied. Examples of requirements can be cited like :
Data set requirements
Ready Queue: When a job's requirement have been satisfied, it will move to the ready queue. It will wait until initiators are available and any virtual resource or workload manager requirement is satisfied to enable it to execute.
Active Queue: When job can run it is moved to the active Q where it will remain whilst the job is executing within JES2. Once the job has completed successfully on JES2 the job will be marked completed within CA7 and is removed from the active Q.
Failure list: If the job fails the it will be moved back to the requirement queue but will need correction prior to rerun. JCL errors are returned to ready Q and other failures are moved to request Q.
How to login to CA7.
Differnet systems use different methods to get into CA7. Some system allow the users to access the CA7 from ISPF menu while others use varied methods. Once we go inside the interface all remains the same.
Refer to This link for list of CA7 Commands.