Ir al contenido principal

Sage X3 how get a list of client running processes


The following Subprog returns into an Integer array the list of all running processes of clients connected to X3 application server.
The Subprog needs this two local variables as parameters:
XPROCID, an Integer array in which are inserted the numbers of running processes
XNUM, an Integer which returns the count of running processes
  1. #
  2. #Restituisce una lista con tutti gli ID dei processi attivi sul server
  3. #
  4. Subprog GET_ALLPROCESS(XPROCID,XNUM)
  5. Variable Integer XPROCID
  6. Variable Integer XNUM
  8. Local Char RESULT(250)(1..dim(XPROCID))
  9. Local Integer STAT
  10. Local Char ORDSYS(250)
  11. Local Integer J , I, T
  12. Local Char CHAINE(250)
  14. Local Char PROCESS(250)
  16. ORDSYS = "psadx -afghimnopxt -l"-GLANGUE
  17. Call SYSTEME2(adxmac(0),ORDSYS,"",STAT,RESULT) From ORDSYS
  19. I = 3
  20. XNUM = 0
  21. While I<=STAT-1
  22. If I>=dim(RESULT) Then
  23. Call ERREUR(mess(161,115,1)) From GESECRAN : # Trop de lignes
  24. Break
  25. Endif
  26. CHAINE = RESULT(I)
  27. PROCESS = vireblc(mid$(CHAINE,1,instr(1,CHAINE," ")),2)
  28. If PROCESS <> "" Then
  29. T = val(PROCESS)
  30. If T > 0 Then
  31. XPROCID(XNUM) = T
  32. XNUM += 1
  33. Endif
  34. Endif
  35. I += 1
  36. Wend
  38. End
Here an example how to use the Subprog
  1. Local Integer XNUM
  2. Local Integer XPRCID(100)
  4. Call GET_ALLPROCESS(XPRCID,XNUM)
  6. Infbox "there are " + num$(XNUM) + " running client processes"
and a second one that show how delete records of a work table for all non-running processes
  1. #
  2. #Delete record not owned by running processes:
  3. #YVP is a table used as temporary container for cosultations and/or report,
  4. #the field YADXUID contains the value of variable adxuid(1)
  5. #
  6. Local Integer XNUM
  7. Local Integer XPRCID(100)
  9. Call GET_ALLPROCESS(XPRCID,XNUM)
  11. Delete [F:YVP] Where find(YADXUID,XPRCID(0..XNUM))=0

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

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más