Commands › LDTM Command › LDTM Usage Notes

LDTM Usage Notes

The purpose of the LDTM command is not to tell you what requirements to post manually. Its purpose is to streamline that process by eliminating requirements that obviously do not fit the outage criteria that you provided it. The final determination of whether a requirement should be manually posted or not depends on the type of outage that occurred, how you have built your production workload, and the reasons why a fixed satisfaction lead time was specified for the requirement in the first place.

The LDTM command attempts to analyze the processes that occurred when the job first came into the queue and the determination was made whether to satisfy a requirement initially, or leave it outstanding. When an outage duration or an outage window is supplied, the process can panel out requirements that obviously do not match the outage criteria. This leaves you with fewer requirements to be manually evaluated based on the type of outage that occurred and your knowledge of the workload you are running.

The command selects outstanding requirements for jobs in the request queue that is based on the following criteria:

• Outstanding job, data set, and input network requirements with a fixed satisfaction lead time are selected.
• The difference between the look back point and the last run point is compared with the outage duration. If the difference is greater than the outage, then the requirement is not marked as matching the outage. If the requirement is for a job, the last run date/time used during initial requirement satisfaction process is carried in the requirement segment itself. For data sets and networks, this information is obtained from the appropriate database record.
• The following qualifications are made only if the outage is specified as a specific date/time range (an outage window). If the outage was specified as a simple duration, further checks cannot be made because there is no specific outage date/time range to reference.
• If the deadline date and time is less than the beginning of the outage window, the requirement is not marked as matching the outage. If the job entered the system before the outage occurred, then it had no effect on the initial requirement satisfaction calculations.
• If the required element has no last run date/time, the requirement is not marked as matching the outage. This is because now there is no date/time reference to compare with the outage window.
• If the look back point minus the outage duration does not reach back to some part of the outage window, the requirement is not marked as matching the outage.