Use this tab to view the UMF exceptions logged from the data loaded
by the pipelines registered for application monitoring. First, you generate
an on-screen report of UMF exceptions to view. Then you can select a specific
UMF exception and take a closer look at its details; this information may
be helpful in resolving the UMF exceptions in the data files. Once you resolve
one of these errors, you can safely reprocess the corrected records in that
file.
UMF exceptions are data-driven errors. They occur when there are problems
with the UMF data structure in an incoming data source file being processed
by a pipeline. By default, UMF exceptions do not contribute to the error limit
count for the pipeline (set in the pipeline configuration file); so by themselves,
UMF exceptions typically do not shut down the pipeline. You can find a full
listing of UMF exceptions in the UMF_EXCEPT table or in the pipeline_name.msg
log, even UMF exceptions for pipelines that are not registered for application
monitoring.
- On-screen report criteria
- Use these fields to specify the criteria for the on-screen UMF exceptions
report. Once you specify the criteria, click the Search button
to generate the report.
- From Date
- Starting date to report on UMF exceptions within the other criteria specified.
(This field is optional and can be blank. Leaving the field blank means display
UMF exceptions starting with the first day the system became operational within
the other criteria specified.)
- This field defaults to today's date. Type the date using the mm/dd/yyyy format.
- Thru Date
- Ending date to report on UMF exceptions within the other criteria specified.
(This field is optional and can be blank. Leaving the field blank means display
UMF exceptions through today within the other criteria specified. )
- This field defaults to today's date. Type the date using the mm/dd/yyyy format.
- From Node
- Name of the registered pipeline to view UMF exceptions for. (This field
is optional and can be blank. Leaving the field blank means display UMF exceptions
for all registered pipelines within the other criteria specified.)
- Keep in mind that you can only see UMF exceptions on this tab for pipelines
that are registered for application monitoring. If you want to see all UMF
exceptions, refer to the UMF_EXCEPT table or the pipeline_name.msg
log.
- Data Source Code
- Data source code (exact) to view UMF exceptions for. (This field is optional
and can be blank. Leaving the field blank means display UMF exceptions for
all data sources within the other criteria specified.)
- Max Count
- Drop-down list containing options for the maximum number of UMF exceptions
to display within the other criteria specified. Only the number of UMF exceptions
up to and including the maximum number display on-screen. If there are more
UMF exceptions that meet the criteria, the system does not display them.
- Search button
- By clicking this button, the system executes the search - it finds and
display all records matching the criteria entered.
- On-screen report results display
- This section of the window displays the on-screen UMF exceptions report,
based on the criteria you entered. The list is sorted by UMF ID number.
- UMF ID
- Displays the sequential, system-assigned number associated with this UMF
exception. The UMF ID maps directly to the UMF_EXCEPT table, where UMF exceptions
are logged.
- From Pipeline
- Displays the name of the pipeline that was processing the record when
the UMF exception occurred.
- Created On
- Displays the date that the UMF exception occurred.
- Output Document
- Displays the type of UMF output document associated with this UMF exception.
- Data Source Code
- Displays the data source code associated with the incoming data file where
the UMF exception occurred.
- External Reference
- Displays the external reference for the specific data record where the
UMF exception occurred. This information can help pinpoint the record inside
the data file that needs to be corrected.
- Action
- Displays the action associated with the incoming data record where the
UMF exception occurred. (This action is coded into the UMF for the data record.)
- A: Add
- C: Change
- D: Delete