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
VMEX
VMEX

Version management

Difference between version and

At line 4 added 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 added 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 11 changed one line
MEX ID
Each line of the process is indicated, therefore by simply going through each line, one can identify where an error occurred.
At line 13 changed one line
Process
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.
At line 15 changed one line
User
To view the error in its entirety, click on the line and view the information contained in the "Message" field.
At line 17 changed one line
Status
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.
At line 19 changed one line
Destination Format
!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
At line 21 changed one line
Destination Type
!Execution Information
At line 23 changed one line
Start Date
;[Status|EXECUTION_STATUS]:This field displays the status of the execution. (e.g. pending, in process)
At line 25 changed one line
End Date
;[Destination Format|DESTINATION_FORMAT]:This field indicates the format of the output at the destination, for example, PDF, HTML, or TXT.
At line 27 changed one line
Report Mode
;[Destination Type|DESTYPE]:This field identifies the format for the output, for example, CACHE, file, email, printer. This field is normally set to CACHE.
At line 29 changed one line
Job Name
;[Start Date|EXECUTION_START_DATE]/ [End Date|EXECUTION_END_DATE]: These fields indicate the beginning and end of the process
At line 31 changed one line
Destination
;[Report Mode|REPORT_MODE]:This field identifies the style of the report, either bitmap or character.
At line 33 changed one line
Destination Name
;[Job Name|JOB_NAME]:This field identifies the specific report execution. This field defaults to the Function+Execution ID. (e.g. RDJB#162852)
At line 35 changed one line
!!Run Logs Tab
;[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
At line 37 changed one line
Log ID
;[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
At line 39 changed one line
Process
!!Run Logs tab
At line 41 changed one line
Context 1
;[Log ID|P2K_AM_EXECUTION_RUN_LOGS]: The ID of the execution run log record.
At line 43 changed one line
Text
;[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.
At line 55 added 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 47 changed one line
Parameter Name
;[Parameter Name|PARAMETER_NAME ]:This field uniquely identifies the parameter within the system.
At line 49 changed one line
Prompt
;[Prompt|PARAMETER_PROMPT]:This field uniquely identifies the parameter prompt within the system.
At line 51 changed one line
Value
;[Value|PARAMETER_VALUE]:This field displays the value of the parameter.
At line 54 changed one line
Table
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.
At line 56 changed one line
DML Action
;[DML Action|DML_ACTION]: Identifies the type of change made (Insert/Update/Delete)
At line 58 changed one line
Reference
;[Reference|REFERENCE_ID]: This identifies the [ID] of the record modified by the process, on the table identified
At line 60 changed one line
Changed
;[Changed|CHANGE_DATE]:The date/time the table was changed is displayed in this field.
At line 62 changed one line
[CLEANUP]
----
![Notes|Edit:Internal.VMEX]
[{InsertPage page='Internal.VMEX' default='Click to create a new notes page'}]
This page (revision-49) was last changed on 11-Mar-2022 15:50 by Lilia UrtanTop