Reports for a previous planning period
Daily planning also provides a set of management reports for a previous planning period. These reports are produced when you run Plan Next Period or Replan Current Period. These reports are created if the PREVRES keyword on the BATCHOPT statement specifies YES. Two of the reports, completed applications and operations ended in error, can also be requested when you submit a daily planning batch job.
A previous planning period is a 24-hour period starting on a fixed-hour boundary as defined by the PLANHOUR keyword of the BATCHOPT statement.
The data is kept in the current plan until the next daily planning run has produced the reports and is then deleted. For example, if you have specified the fixed-hour boundary as 0800 and you are running a Plan Next Period at 0759 on Wednesday morning, you will get reports from the interval 0800 Monday to 0800 Tuesday. If you then run a Replan Current Period at noon Wednesday, you will get the reports from 0800 Tuesday to 0800 Wednesday.
When an occurrence has been reported in any of the previous period reports, it will not be reported again in any subsequent daily plans for the same planning period. This means that the reporting period might not cover a full previous 24 hours when several daily plans have been executed within a planning period.
The report shown in Daily planning reports - Summary of completed applications shows the number of applications processed in the period and gives the number of applications:
- With late input arrival, showing the average input delay
- That missed their deadlines, showing the average deadline delay
- That completed before their deadlines, showing the average deadline earliness
- That were rerun
- That were deleted
It provides a summary of events in the latest daily planning period.
The report shown in Daily planning reports - Completed applications shows all applications completed or deleted in the given period. Also, each operation with a specified input arrival or deadline is printed in the report.
An error code is present if specified when adding an occurrence into the long-term or current plan. This is defined as a rerun of a whole application, whereas a rerun of one or more operations in an application is reported in the error statistics report.
The report is produced automatically if specified at installation time or it might also be requested each time a Plan Next Period, a Replan Current Period, or a Print Current Period Results is run. If the report is requested at run time, a report covering the current period from the fixed-hour boundary of the current plan up to the present time will also be printed.
The report shown in Daily planning reports - Error statistics on completed applications shows applications that have had one or more operations rerun because of an error condition and which are now completed successfully.
- Applications included in this report are not included in the completed applications report.
- Only operations that are rerun after an error are included in this report. If the operation is manually completed, it is included in the completed applications report.
The report shown in Daily planning reports - Operations in error lists all operations that have ended abnormally and are not yet taken care of.
The report is produced automatically if specified at installation time or it might be requested each time a Plan Next Period, a Replan Current Period, or a Print Current Period Results is run.
The report, if produced per shift using, for example, Print Current Period Results, could relieve operators of the task of having to record such information manually, and can also be used by the scheduler or shift supervisor to see where corrective action is necessary.
The report shown in Daily planning reports - Missed feedback report is printed during a Plan Next Period or Replan Current Period run, if the scheduler has not been able to feedback application durations and deadlines.
- The planned deadline is the deadline set in the application description, represented in the format DD HH.MM, where DD is a day offset and HH.MM an absolute time.
- The actual deadline is an absolute day and time, in the format DD HH.MM. For example, if the operation or occurrence completed on 29 March 2006 at 11:15, DD is 29 and HH.MM is 11.15.
- OUTSIDE LIMITS
- Feedback is outside the limit set for feedback.
- APPL IN USE
- Application description was being updated by another user when feedback was attempted.
- I/O PROBLEMS
- AD record not found (if no operation ID printed) or operation not found in AD.
- DL BEFORE IA
- The occurrence completed before the IA was reached.
- NO RUN CYCLE FOUND
- It was not possible to match the occurrence with a run cycle in the application.
- Data
- Explanation
- Dynamically added
- If this is YES, the resource was dynamically added during daily planning or the life of the plan.
- Planned availability
- This is the planned availability, taken from the resource database interval values or the default availability. It does not show the overriding (global) availability, because daily planning does not use this for planning purposes.
- Actual availability
- This is the percentage of time that the resource was available as planned.
- Planned maximum utilization
- This is the maximum number of the resource that was planned to be in use in the interval.
- Actual maximum utilization
- This is the maximum number of the resource that was in use in the interval.
- Allocation failures
- It is increased by one each time HCL Workload Automation for Z tries unsuccessfully to allocate the resource to an operation during this interva; it can be increased many times for each waiting operation.
- Contention time
- This is the percentage of time that operations were waiting for the resource.
- Idle time
- This is the percentage of time that the resource was not allocated.