Ir al contenido principal

Valores de fstat

Fstat
fstat is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction.

Syntax

fstat

Examples

# MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL
# Create a record in the table MYTABLE with they key value 1 if it doesn't exist 
Local File MYTABLE [MYT]
Read [MYT]KEY1=1
If fstat
   [MYT]KEYVAL=1 : Write [MYT]
   If fstat
      MSG="The key was created in the mean time"
   Else
      MSG="Key created"
   Endif
Else
   MSG="Key already exists"
Endif

Details

fstat is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error:
Note that the use of literal numbers should be avoided: dedicated constants exist for this purpose.
ConstantValueExplanation
[V]CST_AOK0Operation succeeded.
[V]CST_ALOCK1Record is locked.
[V]CST_AOUTSEARCH2In <= or >= read mode, indicates that read succeeded, but the key found is not equal to the value.
[V]CST_ADUPKEY3Duplicate value on unique index.
[V]CST_AOUTKEYS4Attempt of reading a key value that is smaller or greater than all existing key values.
[V]CST_ANOREC5Record not read (no current record exists).
[V]CST_ARECTICKUPD6Update conflict: the line no longer exists with the right updtick value (concurrency error during an update operation).
[V]CST_ARECTICKDEL7Delete conflict: The line no longer exists with the right updtick value (concurrency error during a delete operation).

Entradas populares de este blog

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

Sage X3 Create a new CLOB Text

Here how to create a CLOB text Funprog F_CRELOB ( YABRFIC , YTEXTE ) Value Char YABRFIC Value Char YTEXTE Local Char XXRTFTXT ( 250 ) ( 3 ) XXRTFTXT ( 0 ) = "{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 MS Sans Serif;}}\viewkind4\uc1\pard\f0\fs17 " XXRTFTXT ( 1 ) = YTEXTE XXRTFTXT ( 2 ) = "\par}" Local Char X_RET Local Integer XXOK Local Char XCHAMPLIEN : XCHAMPLIEN = "YYYY" Global Char YYYY : YYYY = YABRFIC Local Clbfile WWCLOB Local Mask ACLOB [ M :ACL ] Setlob WWCLOB With XXRTFTXT [ M :ACL ] CLOB = WWCLOB Call CRE_CLOB_ACL ( XCHAMPLIEN , XXOK ) From TRTX3TEX Close Local Mask [ M :ACL ] X_RET = YYYY Kill YYYY End X_RET