The processor occupancy Communication Link Measurements reports for each of your applications varies significantly since a particular link on one configuration may serve a different function than the same link for another configuration. Furthermore, what is considered to be normal link traffic for one service, for example, DCS, may vary widely from what is considered to be normal link traffic for another service, for example, CMS. Therefore, you must obtain a printed report of what is deemed to be normal traffic for each configuration and use that report for comparison purposes.
This report is of significant value in determining the long term impact processor link traffic has on processor occupancy. You can also use the report to identify certain types of link failure. However, since the report summarizes data at 1-hour time intervals, some types of intermittent problems are not easily recognized with this report. You can more easily identify intermittent transmission problems by reviewing the software error log.
Name |
Description |
Meas Hour |
Measurement hour. The starting time (using 24-hour clock) of the hour during which the data is recorded. Data is listed beginning with the most recently completed hour and extending back for 24-hour intervals. |
Link # |
Link number. The links are identified by numbers 1 through 8, 9 through 16, 17 through 24, or 25. The numbers in each column represent the number of messages traversing the link. Once the system establishes a link and the traffic begins flowing over the link, the system counts the messages automatically and needs no command. |
