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

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

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
6 11-Mar-2022 15:51 4 KB Lilia Urtan to previous
5 26-Nov-2021 10:22 4 KB kparrott to previous | to last
4 26-Nov-2021 10:22 4 KB JMyers to previous | to last
3 26-Nov-2021 10:22 4 KB JMyers to previous | to last
2 26-Nov-2021 10:22 4 KB JMyers to previous | to last
1 26-Nov-2021 10:22 46 bytes UnknownAuthor to last

Page References

Incoming links Outgoing links
DMEX
DMEX

Version management

Difference between version and

At line 1 changed 64 lines
[{TableOfContents }]
!!!View Daily Executions
The View Daily Executions (DMEX) screen is used to show the executions of reports / update processes and any execution run logs that they had produced.
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.
%%warning 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 DMEX 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.
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 DMEX, the correct Execution Log is being reviewed. For workflow tracing this is generated behind the scenes and you won't know it until opening DMEX.
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.
\\ \\\
----
!!Executions
;[MEX ID|MEX_ID]:This field provides the execution ID created when a process is run.
;[Function|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
;[Status|EXECUTION_STATUS]:This field displays the status of the execution. (e.g. pending, in process)
;[Elapsed Time|CPU_ELAPSED_TIME]:This field shows a record of the amount of CPU seconds used.
;[Job Name|JOB_NAME]:This field identifies the specific report execution. This field defaults to the Function+Execution ID. (e.g. RDJB#162852)
;[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\\ \\
----
!!Run Logs tab
;[Sort Grp|SORT_GROUP]:
;[Log ID|P2K_AM_EXECUTION_RUN_LOGS]: The ID of the execution run log record.
;[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.
;[Context 1|CONTEXT_1]: Provides additional information to frame the run log in context.
;[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.
\\ \\
----
!!Parameters tab
;[Parameter Name|PARAMETER_NAME ]:This field uniquely identifies the parameter within the system.
;[Prompt|PARAMETER_PROMPT]:This field uniquely identifies the parameter prompt within the system.
;[Value|PARAMETER_VALUE]:This field displays the value of the parameter.
\\ \\
----
!!Tables Changed tab
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.
;[DML Action|DML_ACTION]: Identifies the type of change made (Insert/Update/Delete)
;[Reference|REFERENCE_ID]: This identifies the [ID] of the record modified by the process, on the table identified
;[Changed|CHANGE_DATE]:The date/time the table was changed is displayed in this field.
----
![Notes|Edit:Internal.DMEX]
[{InsertPage page='Internal.DMEX' default='Click to create a new notes page'}]
!!Sorry, this page has not yet been created
This page (revision-6) was last changed on 11-Mar-2022 15:51 by Lilia UrtanTop