Table of Contents
View Execution Logs & Details#
The View Execution Run Logs (VMEX) screen is used to show the executions of reports / update processes and any execution run logs that they had produced.
The MEX ID is indicated in the top left hand corner of the screen. Also indicated, is the name of the process, the user and the date when this process was run.
Each line is information written out by the system specifically for the purpose of debugging problems. The Message and Text contain the information required for deciphering and debugging the issues.
This function is for viewing purposes only; you may not edit the data. This is an important screen for debugging purposes. It allows you to verify whether or not a process ran correctly. Each time a process is run, a log is generated. If an error occurred, the log can be reviewed in VMEX to obtain the reason as to why the error occurred. The information written out here is often of a technical nature and may not be meaningful to the average user but is aimed at a more technical user who is trying to resolve a problem with a work flow.Each line of the process is indicated, therefore by simply going through each line, one can identify where an error occurred.
Each time a process is run, an Execution ID is created (i.e. MEX ID 178309). This ID is important, so that when you go to VMEX, the correct Execution Log is being reviewed. For work flow tracing this is generated behind the scenes and you won't know it until opening VMEX.
To view the error in its entirety, click on the line and view the information contained in the "Message" field.
The definition data for the View Execution Run Logs screen is stored in the P2K_AM_EXECUTIONS, P2K_AM_EXECUTION_RUN_LOGS, P2K_AM_PARAMETER_VALUES and P2K_AM_EXECUTION_AUDITS tables.
- MEX ID
- This field provides the execution ID created when a process is run.
- Process
- This field indicates the process that was run (i.e. P2k_pmwrkflw this refers to a workflow action). CLEANUP
- User
- The user running the process will be identified in this field.
- Status
- This field displays the status of the execution. (e.g. pending, in process)
- Destination Format
- This field indicates the format of the output at the destination, for example, PDF, HTML, or TXT.
- Destination Type
- This field identifies the format for the output, for example, CACHE, file, email, printer. This field is normally set to CACHE.
- Start Date/ End Date
- These fields indicate the beginning and end of the process
- Report Mode
- This field identifies the style of the report, either bitmap or character.
- Job Name
- This field identifies the specific report execution. This field defaults to the Function+Execution ID. (e.g. RDJB#162852)
- Destination
- This field identifies the name of the report server the report will be directed to when launched. Your system administrator will normally set a default for this field. e.g. rep_mercury_AS10G_RL2
- Destination Name
- This field identifies the name of the output. The format of the name will depend upon the Destination Type. (e.g. a file name, an email recipient, etc.)
Run Logs tab#
- Log ID
- The ID of the execution run log record.
- Process
- This field indicates the process that was run (i.e. P2k_pmwrkflw this refers to a workflow action). CLEANUP
- Text
- This field provides the actual details of what the process was trying to do.
- Timestamp
- This field is used to display the day and time of the run log.
- Trace Level
- This field used to indicate the level of trace (messages) that the calculation report should display when performing a trial calculation.
- Error Level
- This field indicates the error level, e.g. warning, information, error.CLEANUP
- Message Code
- This field provides the error in its entirety.
- Run Log Text
- This field that allows you to add notes for the run log.
Parameters tab#
- Parameter Name
- This field uniquely identifies the parameter within the system.
- Prompt
- This field uniquely identifies the parameter prompt within the system.
Tables Changed tab#
- Reference
