This page (revision-49) was last changed on 11-Mar-2022 15:50 by Lilia Urtan

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
49 11-Mar-2022 15:50 5 KB Lilia Urtan to previous
48 26-Nov-2021 10:22 5 KB kparrott to previous | to last
47 26-Nov-2021 10:22 5 KB RForbes to previous | to last
46 26-Nov-2021 10:22 5 KB RForbes to previous | to last
45 26-Nov-2021 10:22 4 KB RForbes to previous | to last
44 26-Nov-2021 10:22 4 KB RForbes to previous | to last
43 26-Nov-2021 10:22 4 KB RForbes to previous | to last
42 26-Nov-2021 10:22 4 KB RForbes to previous | to last
41 26-Nov-2021 10:22 4 KB JMyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 removed one line
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.
At line 11 removed 4 lines
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 workflow.
At line 16 changed one line
Each line of the process is indicated, therefore by simply going through each line, one can identify where an error occurred.
MEX ID
At line 18 changed one line
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 workflow tracing this is generated behind the scenes and you won't know it until opening VMEX.
Process
At line 20 changed one line
To view the error in its entirety, click on the line and view the information contained in the "Message" field.
User
At line 22 changed one line
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.
Status
At line 24 changed 6 lines
!Header Information
;[MEX ID|MEX_ID]:This field provides the execution ID created when a process is run.
;[Process|FUNCTION_NAME]: This identifies the name of the process that was executed
;[User|USER_NAME]:The user running the process will be identified in this field.
;[Identity|PERSON_CODE]:The identity information of the person running the process will be displayed in this field
;[Start Date|EXECUTION_START_DATE]/ [End Date|EXECUTION_END_DATE]: These fields indicate the beginning and end of the process
Destination Format
At line 31 changed one line
!Execution Information
Destination Type
At line 33 changed one line
;[Status|EXECUTION_STATUS]:This field displays the status of the execution. (e.g. pending, in process)
Start Date
At line 35 changed one line
;[Destination Format|DESTINATION_FORMAT]:This field indicates the format of the output at the destination, for example, PDF, HTML, or TXT.
End Date
At line 37 changed one line
;[Destination Type|DESTYPE]:This field identifies the format for the output, for example, CACHE, file, email, printer. This field is normally set to CACHE.
Report Mode
At line 39 changed one line
;[Start Date|EXECUTION_START_DATE]/ [End Date|EXECUTION_END_DATE]: These fields indicate the beginning and end of the process
Job Name
At line 41 changed one line
;[Report Mode|REPORT_MODE]:This field identifies the style of the report, either bitmap or character.
Destination
At line 43 changed one line
;[Job Name|JOB_NAME]:This field identifies the specific report execution. This field defaults to the Function+Execution ID. (e.g. RDJB#162852)
Destination Name
At line 45 changed one line
;[Destination|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
!!Run Logs Tab
At line 47 changed one line
;[Report History]:This button will bring up a dialog that shows all __your__ executions of that report that are stored on the report server, and you may view them
Log ID
At line 49 changed one line
!!Run Logs tab
Process
At line 51 changed one line
;[Log ID|P2K_AM_EXECUTION_RUN_LOGS]: The ID of the execution run log record.
Context 1
At line 53 changed one line
;[Process|MODULE_NAME]:This field indicates the process that was running when the message was issued (i.e. P2k_pmwrkflw this refers to a workflow action). When tracing, this indicates the program sub unit executing.
Text
At line 55 removed 14 lines
;[Text|TEXT]:This field provides the actual details of what the process was trying to do.
;[Timestamp|RUN_LOG_TIMESTAMP]:This field is used to display the day and time of the run log.
;[Trace Level|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|ERROR_LEVEL ]:This field indicates the error level, e.g. warning, information, error.
;[Context 1|CONTEXT_1]/[Context 2|CONTEXT_2]: Provides additional information to frame the run log in context.
;[Message Code|MESSAGE_CODE ]:This field provides the error in its entirety.
;[Run Log Text|RUN_LOG_TEXT ]:This field that allows you to add notes for the run log.
At line 71 changed one line
;[Parameter Name|PARAMETER_NAME ]:This field uniquely identifies the parameter within the system.
Parameter Name
At line 73 changed one line
;[Prompt|PARAMETER_PROMPT]:This field uniquely identifies the parameter prompt within the system.
Prompt
At line 75 changed one line
;[Value|PARAMETER_VALUE]:This field displays the value of the parameter.
Value
At line 78 changed 2 lines
This tab identifies the tables that are changed by this process. The information comes from the [P2K_AM_EXECUTION_AUDITS] table
;[Table|TABLE_NAME]:This field identifies the table changed.
Table
At line 81 changed one line
;[DML Action|DML_ACTION]: Identifies the type of change made (Insert/Update/Delete)
DML Action
At line 83 changed one line
;[Reference|REFERENCE_ID]: This identifies the [ID] of the record modified by the process, on the table identified
Reference
At line 85 changed one line
;[Changed|CHANGE_DATE]:The date/time the table was changed is displayed in this field.
Changed
At line 87 changed 5 lines
----
![Notes|Edit:Internal.VMEX]
[{InsertPage page='Internal.VMEX' default='Click to create a new notes page'}]
[CLEANUP]