Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Batch Optimizer (Advanced and Standard) 2.9.

Load Utility Report Output Summary

The Load Utility Output Summary Report summarizes the records that the utility selected as output.

Summary Report from the Load Utility

Date 04/05/2008    MainView Batch Optimizer Report                    Page    1
                                 OUTPUT SUMMARY 
    32 NEW JOB INSTANCES ADDED TO HISTORY DATA SET FOR SUBSYSTEM BCSS 
     0 JOB INSTANCES MERGED WITH HISTORY 
     0 JOB INSTANCES REPLACED IN HISTORY 
      0 JOB INSTANCES NOT REPLACED IN HISTORY BECAUSE ACTUAL (NONSMF) DATA EXISTS
       0 HISTORY POPULATE REQUESTS NOT COMPLETED BY ACCESS METHOD
     0 JOB INSTANCES WRITTEN TO SELECT FILE 
 9,223 JOBS DISCARDED BECAUSE THEY DID NOT MEET THE SELECTION CRITERIA 
     0 JOBS DISCARDED WITH ELAPSED TIME LESS THAN MINIMUM 
      0 JOBS DISCARDED BECAUSE OF INCOMPLETE EXECUTION

The following table lists the fields shown in the Load Utility Report.

Field

Description

NEW JOB INSTANCES ADDED TO HISTORY DATA SET FOR SUBSYSTEM ssid

Number of jobs that were written to the History data set that is associated with the identified subsystem (ssid is a MainView Batch Optimizer Subsystem ID)

These jobs did not previously appear in the History data set.

JOB INSTANCES MERGED WITH HISTORY

Number of jobs that match an existing job name in the History data set

The new SMF data is merged with the existing SMF or Job Optimizer data because the job structure is the same

JOB INSTANCES REPLACED IN HISTORY

Number of jobs that match an existing job in the History data set

The new SMF data replaces the existing SMF data because the job structure has changed. Actual Job Optimizer data is not replaced.

JOB INSTANCES NOT REPLACED IN HISTORY BECAUSE ACTUAL (NONSMF) DATA EXISTS

Number of jobs that match an existing job name in the History data set

The new SMF data is discarded because SMF data will not replace actual Job Optimizer data.

HISTORY POPULATE NOT COMPLETED BY ACCESS METHOD

Number of jobs for which errors occurred and, as a result, were not added to the History data set

JOB INSTANCES WRITTEN TO SELECT FILE

Number of jobs that were written to the select file

JOBS DISCARDED BECAUSE THEY DID NOT MEET THE SELECTION CRITERIA

Number of jobs that were not loaded to the History data set because they did not meet the selection criteria

JOBS DISCARDED WITH ELAPSED TIME LESS THAN MINIMUM

Number of jobs that were not loaded to the History data set because their elapsed time was less than the specified minimum execution time

JOBS DISCARDED BECAUSE OF INCOMPLETE EXECUTION

Number of jobs that were not loaded to the History data set because they were not completed successfully



Was this page helpful? Yes No Submitting... Thank you

Comments