Skip to main content
Skip table of contents

f$trace_db


f$trace_db

With this function, ePOS is prompted to write all actions that are executed after this function in the database tables T_Ablauf_Start and T_Ablauf_Zeile. The table shows the name of the decision table, the action taken and its text. Furthermore, the start, the end and the fulfilled condition of a decision table are written in the table. In addition, if desired, the values of ePOS parameters can also be output.

Syntax:

Status = f$trace_db ( usage , 'Parameternames' )

 

Argument

Typ

Bedeutung

 

Usage

Integer

This parameter specifies if the trace file also logs the execution of the decision tables in metalanguage.

-1 – stop trace

0 – without metalanguage

1 – metalanguage DT call is included in trace file

2 – entire metalanguage DT is included in trace file

 

Parameternames

String

Comma-separated list of ePOS parameters whose values are to be produced in the trace file.

Result:

Integer

00 - logging was successful-1 - the table could not be written Possible causes: Incorrect database connection specified.


Description of the Tables

T_Ablauf_Start:

Name

Data type

Meaning

ID

integer

Unique ID. This will be used in the table T_Ablauf_Zeile as AblaufID.

Anwender

String

Name of user

Start

Date

Timestamp

Parameter

String

Comma-separated list of ePOS parameters whose values are to be produced in the trace file.


T_Ablauf_Zeile:

Name

Data type

meaning

ID

Integer

Unique ID.

AblaufID

Integer

ID of Table T_Ablauf_Start

VBG

String

Group

VB

String

Compound

ET

String

Name of decission table

WAS

String

Mark the entry: Start , End for Begin and End of DT, C for condition, ELSE , A for Action.

Inhalt

String

Contentof current cell in DT

Aufruftiefe

Integer

Current stack

Stand

Date

Timestamp

Zeile

Integer

Current Line in DT

Spalte

Integer

Current Col in DT

Werte

String

List of Parameternames and their Values in the form:

Name=Value;Name=Value


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.