Ir al contenido principal

Compile adonix source from a program

FUENTE ORIGINAL DEL ARTÍCULO 

BY  · PUBLISHED  · UPDATED 

We all know the main way to compile an adonix source:
in Sage X3 version 6.x and earlier, in fact, there is a special editor (ADOTRT function) available,
from where you can compile with the F7 function key or with the appropriate menu.

From 7.x, in the web interface there is still the ADOTRT function available, with the “Compile” button available,
but the F7 key is no longer available, and ESC-F7 escape sequence can not be used.

From version 7.x we also have Eclipse available through the pluging Safe X3.

But if for some reason we needed to compile a source from a program?
Or if we wanted to recompile all the sources starting with Y?

(By the way, you know that the changes made by the end customer should they start with the Z?
The Y would be reserved for consultant developments…)

To do this, the following call is helpful:

Call VALID(FOLDER,SOURCE, DOSSIER, OK) From VALMSKSUB

Where:

  • FOLDER is the folder where the file to be compiled is contained
  • SOURCE is the name of the file, which must have extension src, to be compiled (but the name must be indicated without extension, for example “SPESOH”)
  • DOSSIER is the name and dossier in which the folder is located: put nomap and it’s ok, except for special uses
  • OK is a variable of integer type to indicated if the compilation was successful

To compile all customized sources, we can do:

Local Char DIR(GDIMFIC), FILELIST(GDIMFIC)(1..100)
Local Integer LENG
DIR="C:\SAGE\"+nomap+"\TRT\Y*.src"
Call SYSTEME2 (adxmac(0),"dir /b "-DIR,"",LENG,FILELIST) From ORDSYS
Local Integer OK
For I=1 To LENG
  Call VALID("TRT",seg$(FILELIST(I),1, instr(1,FILELIST(I),".src")-1), nomap, OK) From VALMSKSUB
  Next
End

Some comments:

  1. nomap o nomap(0), it’s the same, returns the name of the current dossier
  2. seg$(STR, start, end) returns a substring of STR that starts from the character in start position, up to index character end
  3. instr(start, STR, find) search the string find in STR from index start and returns the position

Summing up

seg$(FILELIST(I),1, instr(1,FILELIST(I),".src")-1)

need to remove “.src” from the file name.

You could use other dos commands to already have just the name directly, but it was less fun!

 

Entradas populares de este blog

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: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

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...
Leer más

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
Leer más