Visual LANSA Forum

Hi Tim,

I tried that too, but for some reason the import froze. I canceled the job through Windows Taskmanager after a few minutes.

Best regards, Peter

Recently my client decided to split the VBA (dev/test) partition into a VBA (test) and VBD (Dev) partition on a new LANSA instance.

All data on the DC@PGMLIB instance was exported and then Imported on the new DCOPGMLIB. After that all data on the VBA partition was copied to VBD.

So far so good ...

Today I recieved a JSon message with an UTF8 string containing ''.

As a quick fix I used the following stop-gap:
Define_Com Class(#PRIM_REGX) Name(#uRegEx)
Define_Com Class(#PRIM_ALPH) Name(#uPattern)
Define_Com Class(#PRIM_DC.UnicodeString) Name(#uMatch)
Define_Com Class(#PRIM_DC ...

I use this simple script now to restart the identity column:

Hi Don,

After some further Googling, I agree. Thank you for the pointer in the right direction.

I think Lansa should do this automatically. But until they fix it, this is a good work around.

Best regards, Peter

A quick search on CPYF and identity columns returns this tip.
1. Lock the table
2. Query, selecting the max-value of the identity column
3. Alter the table, using the identity column reset clause to set the next value the max-value plus one
4. Unlock the table


Could it be that Lansa forgets to ...

I'm experimenting with the "Identity column" field. The generated column looks like this:
CREATE TABLE DEVLIB/VBSTRG (
TRGID BIGINT GENERATED ALWAYS AS IDENTITY (
START WITH 1 INCREMENT BY 1
NO MINVALUE NO MAXVALUE
NO CYCLE NO ORDER
CACHE 20 )
. . .
I had a table with some data which ...

I really love Qualified DataStructures in RPG ILE. So I'm searching for a way to create something similar in Lansa.

I can fill models in Web Api's with the instruction:
Define_Com Class(#Com_Home.modelObject) Name(#model)

Set Com(#model) Com_Fields(*ALL)

I'd like to use this to fill my own ...

Hi Rene,

I knew it was something simple. But at that moment I just couldn't recall what the answer was.

Thank you for confirming the answer to myself.

Is simply putting TPTH=%TEMP% in the .STR file enough?

Lansa decided to create their own temp location, which annoys our security to no end. Is there an easy way to return the default location back to the %temp% folder?

Theo de Bruin wrote: Wed Jan 25, 2023 12:02 am This is the normal way the evaluation is done, once value1 is changed, the next eveluation will use the new value.

Thanks. Good to know that ASSIGN is executed for each variable in the list separately. The documentation doesn't mention this.

Oops. I forgot to reply. Logging for this job was almost completely turned off in the job description. Thank you for your pointer.

In noticed some unexpected behaviour:
Function Options(*DIRECT)

Define Field(#value1) Type(*INT)
Define Field(#value2) Type(*INT)
Define Field(#value3) Type(*INT)

#value1 := 1
#value2 := 2
#value3 := 3

#value1 #value2 #value3 := #value1 + #value2 + #value3

Use Builtin(MESSAGE_BOX_ADD) With_Args ...

Thanks a lot for this pointer. I'll look into this.

I get an Fatal X_RUN_EXECUTE error occurred on a If (#Operation.TryBind( #Context )) .

{
"error":{
"messages":[
"Fatal X_RUN_EXECUTE error occurred."
]
}
}

There's nothing in the X_ERR.LOG.

I read someting about debugging by adding lines to some WebAdministrator dialog, but wouldn't that ...

On the IBMi we have a function that is running for a long time. So I'd like to display a message in the joblog at some key points in the program.

I tried:

Message MsgTxt('...') Type(*INFO)
Message msgid(CPF9898) msgf(QCPFMSG) Msgdta('...') Type(*INFO)
Use Builtin(ISSUEMESSAGE) With_Args ...

This morning we received an a new error from Microsoft:

- 421 4.7.66 TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2. Visit https://aka.ms/smtp_auth_tls.

So it looks like Lansa Integrator still uses TLS 1.0

I also found a new link which might be a clue ...

I got the following suggestion from Lansa Support Benelux.

---
a) Perhaps you will need to adjust the time-out value of the SSL handshake.

The main configuration for the SSL timeout is in the IBM file, as described here:
https://www.ibm.com/support/pages/setting-ssltimeoutmillisec-environment ...

We're having the exact same problem on our IBM i, so I'll add my findings here.

The error I get is: Could not convert socket to TLS

It started around october 5 with 1 error on that day, but it grew to around 25% errors over the following days.

I found a TLS tip from Lansa here: https://www.lansa ...