Valence 52+ Installation dashboard in empty

[patricevincent]

Hello CNX Team,
I have just downloaded and installed the new version 52+ in order to test the new functionalities. I'm running in V7R1, the installation has been done correctly and Valence is running on the actjob. When i log a pc using VVADMIN or an other profile, the dashboard is empty (no apps). When i look on the CGI jobs, i have the following error :
Y de type *FILE dans *LIBL non trouvé.
VVSECURE_ISAUTHORIZEDA de type *N dans *LIBL non trouvé.
Do i need to do something with my PTF ?
Thanks

[robert.swanson]

Hello Patrice,

It appears the SQL function VVSECURE_ISAUTHORIZEDA failed to create during the installation process. Let's try to create it manually there to isolate the problem...

Go into source member VVSQLFUNC in VALENCE52/QSQLSRC, verify each library reference is VALENCE52 (not VVLIBRARYX), then run it with this command:
RUNSQLSTM SRCFILE(VALENCE52/QSQLSRC) SRCMBR(VVSQLFUNC) NAMING(*SQL)

I suspect it's going to give you some sort of an error message, which will show in the spool file the process generates. Let us know what you see and then we'll decide what to do next. I believe there is an SQL bug in some versions of the OS that can cause this.

-Rob

[patricevincent]

Hello Robert,
Thanks for your prompt reply.
Each library is ok in this sql source.
When i run the sql, the error i get is :
SQL7966 0 60 Position 1 GRANT de droits pour VVSQLUDF de VALENCE52
exécutée.
SQL7997 0 64 Position 1 La fonction VVIN_CHAR a été créée dans
VALENCE52.
SQL7966 0 72 Position 1 GRANT de droits pour VVSRVPGM de VALENCE52
exécutée.
SQL0104 30 78 Position 17 Elément syntaxique 30,9 n'est pas correct.
Eléments possibles : ( SELECT VALUES.
SQL7961 0 Invalidation exécutée.

But it works with this command :
RUNSQLSTM SRCFILE(VALENCE52/QSQLSRC)
SRCMBR(VVSQLFUNC)
NAMING(*SQL)
DECMPT(*PERIOD)

So something like French specificities ...

Thanks for your help,
Patrice

[robert.swanson]

Ahhh, thanks Patrice! That makes total sense now -- VVIN_NUM() is a recently added SQL function, and the first one we've created with a decimal return value (30,9).

We'll be sure to add DECMPT(*PERIOD) to the install routine so this doesn't happen again on future builds.

Have a good weekend!
-Rob

[patricevincent]

Thanks again for your help and have a nice we too !