Demand job list for PCS
Relevant to you?
Do you have unscheduled jobs that should be part of the battle plan and be processed by PCS? This features allows you to tell PCS what jobs to expect to be demanded in, and that they should be treated as part of the battle plan. In general these jobs would not have SET=NTR and therefore not be subject to the job recognition options. If however you do use SET=NTR, the job recognition options would apply.
How it works
PCS expects the jobs, in a particular battle plan, that have been detected by the PCS Forecast Collection Utility. Since jobs that are "demanded in" aren't scheduled, the utility doesn't add them to the battle plan.
You can control this by adding the "demanded in" jobs to the Demand Job List. Jobs in the list are expected by the battle plan. PCS processes them as any other battle plan jobs.
During the active battle plan, jobs on the Demand Job List are considered unconfirmed until they are submitted. Once they are submitted they are considered confirmed and processed by PCS like any other scheduled job.
Specification
You add the header jobs of the "demanded in" trees to the Demand Job List. In the following example the workload is available to run again as SCHID=002 jobs. Individual header jobs could be demanded in as needed.
From this panel | select |
|---|---|
ThruPut Manager Main Lobby | 5 PCS |
Primary Options | 3 Application Management Database (AMD) Services |
CA Communication Setting | <relevant CA 7 Instance> |
Application Management Database (AMD) Services | 1 Use an Existing File |
AMD file pop-up | “Enter” to accept “active” file |
Main Selection Menu | 1 Defaults/Options and Lists |
Defaults/Options and Lists | 7 Demand Job List |
You can add to or delete from the list here. Remember you only add the header job of a tree; PCS detects all the jobs triggered by the header job.
If you have many header jobs to add, consider the bulk update facility available under the Action menu. This facility allows you to enter a few header jobs into the list as a template and then export them to an editable data set where you can make your changes using the usual editing features. When you are ready you can import the updated list. (This facility follows the same conventions used for the bulk export and import of defaults and options.)
Runtime
On the View/Edit Active Battle Plan panel, notice the option to select 5 List of Unconfirmed Demand Job Instances. This might remind someone to demand in the header job for a tree that should be run during this battle plan.
Whether you are looking at the unconfirmed or all job instances on the View/Edit Active Battle Plan Job Instances panel, notice:
- The Job Instance ID has a D (or DEM if there is room) at the right hand end of the field if this job (or its header job) is from the Demand Job List.
- The defaults and options are inherited and propagated in the usual way.
- PCS recognizes the structural type of these jobs (H-header, M-middle, T-trailer, or S-single) in the same way it does other expected jobs.