Page 1 of 2
ERROR when tring to list the file fields in the autocomplete
Posted: Wed Nov 17, 2021 3:48 pm
by jac53
I receiving the error I copied in the word document attached.
This is happening in TEST BOX in the PRODUCTION BOX it is working.
In both Boxes we are using external memory (IASP) for the libraries.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Wed Nov 17, 2021 4:47 pm
by Scott Klement
If you type the fields manually (instead of having Genie list them and let you select them by hand) does it work?
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Thu Nov 18, 2021 6:20 pm
by jac53
When I typed the field manually, save the screen and when I try the autocomplete does not work and in the green screen session the job log shows:
Library list changed.
Library QTEMP added to library list.
Library LN1TSTSEC not found.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Thu Nov 18, 2021 7:09 pm
by jac53
Also
This the job in QHTTPSVR serving Genie
PROFOUNDUI QTMHHTTP BATCHI ACTIVE PGM-QZSRCGI
The library list shows
Opt Library Type
RBTSYSLIB SYS
QSYS SYS
QHLPSYS SYS
QUSRSYS SYS
QSYS2 SYS
SYSBASGPL SYS
QHTTPSVR CUR
QTEMP USR
QGPL USR
But in the interactive genie screen shows the library list
QTEMP USR
LN1TSTSEC USR
LN1TSTCOM USR
LN1TSTDTA USR
LN1TSTMOD USR
LN1TSTOBJ USR
Is there any special place for some settings?
The profiles
QTMHHTP1
QTMHHTTP
are identical to the ones in Production Box using the same JOBD "QDFTJOBD" with Initial ASP group . . . . . . . . . . . . . . . : *NONE
In my profile my JOBD is "QDFTJOBDI" with this Initial ASP group . . . . . . . . . . . . . . . : DBDEV pointing to the external database
I do not understand why is OK in the Production Box and not in Test Box
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Thu Nov 18, 2021 7:29 pm
by Scott Klement
What version of Profound UI are you running?
The "autocomplete" makes a connection to a separate job to run it's database queries. Recent versions of Profound UI will look up the ASP job of the interactive job and try to set the library list and ASP group the same way so that they can use all of the same libraries.
However, if your test box is running an old version of Profound UI, it might be before this behavior was added to the product.
Also, I don't know how you are checking the library lists... but keep in mind that the database job will only change its library list temporarily... so it will change it, run the query, and then change it back. Unless you catch it while it's running the query, it may have already changed back to the default values.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Fri Nov 19, 2021 4:10 pm
by jac53
In Both Production Box and in Test Box the Genie version is 4.7.0.
Again in Production it is working.
In both cases the libraries list are setup when I signed in the JDE software.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Fri Nov 19, 2021 4:30 pm
by Scott Klement
What you are seeing on your test box is the expected behavior with 4.7.0. 4.7.0 is from 2013, and there was no IASP support in the product at that time.
I don't know why this would work on your production box. It should not be. My best guess is that you configured the operating system to somehow have the IASP always mounted and available. But, I have no clue how you'd do that.
Please update to the current version of Profound UI so that we can support you going forward.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Mon Nov 22, 2021 6:06 pm
by jac53
Which version do you recommend which support previous 4.7.0?
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Wed Nov 24, 2021 3:42 pm
by Scott Klement
I always recommend the current version. There's no reason to run old ones.
Re: ERROR when tring to list the file fields in the autocomplete
Posted: Mon Nov 29, 2021 5:41 pm
by jac53
I upgrade to the latest version as you recommended but the Database autocomplete is still not working.
I sent to support the issue on 11/26 and today again and I have not received any answer.