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.

Figure 1. Daily planning reports - Summary of completed applications
ABCD COMPANY                                  PAGE 0024
 REPORTS FOR SUBSYS EIDA                                    11 JUN 03
                                                                16:30

                     SUMMARY OF COMPLETED APPLICATIONS  ( 03/06/10 01.00 - 03/06/11 01.00 )
                     ======================================================================
                   NO OF      NO OF   NO OF    APPL WITH  AVERAGE  APPL     AVERAGE   APPL     AVG
         APPL      COMPLETED  RERUN   DELETED  LATE       INPUT    MISSING  DEADLINE  EARLY  DEADL
         PRIORITY  APPL       APPL    APPL     INPUT      DELAY    DEADLINE DELAY     COMPL. EARLY
         --------  ---------  ------  -------  ---------  -------  -------- --------  -----  -----
             9
             8
             7          2                 1        1       19.54       1     15.55        1  03.59
             6
             5          1                                              1     46.18
             4
             3
             2
             1
         -----------------------------------------------------------------------------------------
                        3                 1        1       19.54       2     31.06        1  03.59

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.

Figure 2. Daily planning reports - Completed applications
ABCD COMPANY                                       PAGE 0025
 REPORTS FOR SUBSYS EIDA                         11 JUN 03
                                                     16:30

                              COMPLETED APPLICATIONS  ( 03/06/10 01.00 - 03/06/11 01.00 )
                              ===========================================================
APPLICATION ID     APPLICATION TEXT            PLANNED   ACTUAL  INPUT           ACTUAL  OUTPUT ERROR ADD
 OPERATION ID       OPERATION TEXT         PRI  INP ARR  INP ARR DELAY  DEADLINE COMPLETE DELAY  CODEFUNC
                     USER DATA
---------------- ------------------------- --- -------- -------- ------ -------- -------- -----  ----
APP6               test variable dep         7 08 07.53    07.55  00.00    23.00 DELETED   00.00 DIALOG
CP                 Current plan              7 09 12.00    07.54  19.54 09 16.00    07.55  15.55
 CPU1_050 XRAYNERC                             09 12.00    07.54  19.54 09 16.00    07.55
CP                 Current plan              7    12.00    12.00  00.00    16.00    12.01  00.00
 CPU1_050 XRAYNERC                                12.00    12.00           16.00    12.01
PAYDAILY           Daily payroll jobs        5 08 08.00 08 07.34  00.00 08 16.00    14.18  46.18
 WTO1_005 PAYDAILY  PAYX CLOSE DATASET         08 08.00 08 07.34        08 16.00 08 13.11
        USER DATA:
 SETP_010 PAYDAILY  Job setup for paydaily              08 07.36        08 16.00 08 07.36
 CPU1_020 PAYDAILY  Runs pay04 and pay06                   12.14        08 16.00    14.18

                              COMPLETED APPLICATIONS  ( 03/06/11 01.00 - 03/06/11 16.30 )
                              ===========================================================
APPLICATION ID     APPLICATION TEXT            PLANNED   ACTUAL  INPUT            ACTUAL OUTPUT ERROR ADD
 OPERATION ID       OPERATION TEXT         PRI  INP ARR  INP ARR DELAY  DEADLINE COMPLETE DELAY CODE FUNC
                     USER DATA
---------------- ------------------------- --- -------- -------- ------ -------- -------- ----  ----
PAYBACKP           Backup payroll database   5 08 12.00 10 12.18  48.18 09 06.00    09.36  51.36
 CPU1_015 PAYBACKP  Daily payroll backup                10 12.18        09 06.00 10 14.18
 WTO1_030 PAYBACKP  PAYX OPEN DATASET                   10 12.18        09 06.00    09.36

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.

Note: The completion time used in the report is either the real completion time for the application or operation or DELETED for deleted applications. The real complete time for an application is defined as the time of the last completed operation with no specified input arrival or deadline. If the occurrence or operation has been manually completed, the real completion time is set to the time of the manual completion.
Figure 3. Daily planning reports - Error statistics on completed applications
ABCD COMPANY                                               PAGE 0031
 REPORTS FOR SUBSYS EIDA                                   11 JUN 03
                                                               16:30

     ERROR STATISTICS ON COMPLETED APPLICATIONS  ( 03/06/10 01.00 - 03/06/11 01.00 )
     ===============================================================================
APPLICATION ID     PRI INP  ARR APPLICATION TEXT           ERROR   RERUN   NUMBER OF
   OPR    JOBNAME                OPERATION TEXT             DUR     DUR     ERRORS
--------- -------- --- -------- ------------------------- ------- ------- -----------
PAYDAILY            5  08 08.00 Daily payroll jobs
 CPU1_020 PAYDAILY               Runs pay04 and pay06       0.01    0.00
-------------------------------------------------------------------------------------
TOTAL FOR ERROR CODE :                                      0.01    0.00     1
-------------------------------------------------- ERROR CODE : S0C4 ----------------
 CPU1_020 PAYDAILY               Runs pay04 and pay06       0.01    0.00
-------------------------------------------------------------------------------------
TOTAL FOR ERROR CODE : S0C4                                 0.01    0.00     1
-------------------------------------------------------------------------------------
TOTAL FOR ALL ERRORS                                        0.02    0.00     2

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.

The error duration (time lost due to errors) is printed if not zero. The rerun duration (time lost when rerunning completed applications) is printed for any application that has been added into the long-term current plans with a rerun (error) code. The report is listed in error-code order. It gives the total error duration, rerun duration, number of errors for each error code, and the total number of errors.
Note:
  1. Applications included in this report are not included in the completed applications report.
  2. 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.
Figure 4. Daily planning reports - Operations in error
ABCD COMPANY                                               PAGE 0027
 REPORTS FOR SUBSYS EIDA                                11 JUN 03
                                                            16:30

                 OPERATIONS IN ERROR   (                - 03/06/11 16.30 )
                 =========================================================
APPLICATION ID APPLICATION TEXT                  INPUT   STARTED  ENDED IN DEFINED LATEST OP ERROR  CATM
 OPERATION ID   OPERATION TEXT     JOBNAME  PRI ARRIVAL    AT     ERROR AT DEADLINE OUT DUR  CODE  STAT
                 USER DATA
-------------- ------------------- -------- --- -------- -------- -------- -------- ---------
PAYM1          MONTHLY PAYROLL JOBS          5  10 08.00 10 08.09          10 18.00
 CPU1_040      Monthly payroll job PAYMONTH     10 08.00 11 16.14 11 16.14 10 18.00   00.01 S0C4
PAYW           Weekly payroll jobs           5  09 14.00 10 10.37          09 16.00
 CPU1_020      pay07, pay10, pay16 PAYWEEK      09 14.00          10 10.37 09 16.00   00.00 OJCV

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.

Figure 5. Daily planning reports - Missed feedback report
ABCD COMPANY                                                PAGE 0017
 REPORTS FOR SUBSYS EIDA                                    06 MAY 03
                                                                12:33

                      MISSED FEEDBACK REPORT           (                -                )
                      ====================================================================
APPL ID            APPLICATION    PLANNED   ACTUAL    PLANNED   ACTUAL   REASON FOR
 OPERATION ID      INPUT ARRIVAL  DURATION  DURATION  DEADLINE  DEADLINE MISSED FEEDBACK
-----------------  -------------  --------  --------  --------  -------- ---------------
APPLMVS              29 09.10                         00 12.00  29 11.30 OUTSIDE LIMITS
 CPU1_050                           01.00   0000.02                      OUTSIDE LIMITS
 CPU1_052                           01.00   0000.02   00 11.30  29 11.15 OUTSIDE LIMITS

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 report lists all occurrences and operations where the feedback of the actual duration and deadline to the application description data set has not been possible.
Note:
  1. 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.
  2. 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.
The reasons for missed feedback include:
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.
Figure 6. Daily planning reports - Actual resource usage
ABCD COMPANY                                 PAGE 0038
 REPORTS FOR SUBSYS EIDA                                03 JUN 03
                                                            06:03
                             ACTUAL RESOURCE UTILIZATION  (03/06/01 20.00 - 03/06/02 20.00)
                             ==============================================================
RESOURCE NAME    : PAYROLL.DATABASE                 DESCRIPTION: Serializes access to Paymore database
DYNAMICALLY ADDED: NO
INTERVAL START | INTERVAL   END |    AVAILABILITY   |        UTILIZATION        | ALLOCATION | CONTENTION 
|    IDLE
DATE      TIME | DATE      TIME | PLANNED |  ACTUAL | PLANNED MAX | ACTUAL  MAX |   FAILURES 
|       TIME |    TIME
==============================================================================================
03/06/01 20.00 | 03/06/02 08.00 |   YES   |    100% |           1 |           1 |          0 
|         0% |      4%
03/06/02 08.00 | 03/06/02 10.00 |   YES   |    100% |           0 |           1 |          0 
|         0% |     80%
03/06/02 10.00 | 03/06/02 12.30 |   YES   |    100% |           1 |           1 |          1 
|        12% |     17%
03/06/02 12.30 | 03/06/02 20.00 |   YES   |    100% |           1 |           1 |          0 
|         0% |     20%
You see this data on the actual resource usage report:
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.