Original Message:
Sent: Mon July 22, 2024 10:47 AM
From: Francisco arano
Subject: Failed to locate JVM in the PST Configuration File
Hi Rick,
Thanks a lot this worked for me:
pstlocal.cfg: pstdir OPD SQLServer 2019 dbo_optim optodbc optim dbo_optim xxxxxx
pstserv.cfg: pstdir OPD SQLServer 2019 dbo_optim optodbc optim dbo_optim xxxxxx
dbalias:
pstlocal.cfg:dbalias OPD optodbc optim dbo_optim xxxxxx
pstserv.cfg: dbalias OPD opTodbc optim dbo_optim xxxxxx
Just one question in pstlogon I put client and from what I understand you shouldn't put username and password in the pst parameters?
Thanks
Francisco Arano
ADVERTENCIA. Este correo se envía del Banco de México y puede contener información sensible. Si usted no es el destinatario del mismo, por favor notifique al remitente inmediatamente y borre este mensaje y cualquier copia del mismo, así como los archivos adjuntos. Debido a que las comunicaciones por internet no son seguras, en el caso de que usted no sea el destinatario de este correo, Banco de México no acepta responsabilidad u obligación alguna por el contenido del mismo. La información de este mensaje, incluyendo, en su caso, los archivos adjuntos, se encuentra protegida por la ley. Su reproducción, parcial o total, revisión, uso, revelación, y/o distribución indebida o no autorizada puede constituir un delito y/o contravenir diversas disposiciones legales. Con independencia de lo anterior, el Banco de México se reserva el derecho de ejercer las acciones que correspondan, entre otros, por daños y perjuicios, con motivo del empleo indebido y/o no autorizado de la propia información. Banco de México ha tomado precauciones para prevenir que el presente correo esté infectado por virus, por lo que no acepta, entre otros, responsabilidad alguna por daños o pérdidas causadas por el uso del mismo o de los archivos adjuntos.
Asimismo, le informamos que Banco de México es responsable de la protección de los datos personales que trate. Dicho tratamiento se llevará a cabo conforme a los principios y deberes previstos en la Ley General de Protección de Datos Personales en Posesión de Sujetos Obligados, con sujeción a las atribuciones y facultades que la normatividad aplicable le confiere, y para finalidades acordes a estas. Le invitamos a consultar nuestros avisos de privacidad en nuestra página de internet (www.banxico.org.mx), en la sección "Ley de Transparencia", subsección "Avisos de Privacidad".
°°°°
NOTICE. This message is being sent from Banco de México and may contain sensitive information. If you are not the intended recipient, please advise the sender immediately and delete this message, and any copies of it, including its attachments. As internet communications are not secure, in case you are not the intended receiver, Banco de México does not accept any responsibility for the content of this message. All information contained in this message, including attached files, is protected by Mexican law. Partial or total reproduction, modification, use, disclosure, and/or inappropriate or unauthorized distribution of any information without the prior consent of the sender may be prosecuted under Mexican law. Banco de México reserves the right to pursue in any form of legal action, including any damages, that could result from the inappropriate or unauthorized use of the information contained herein. Banco de México has taken reasonable precautions to prevent viruses from being present through this e-mail. We do not accept responsibility for any loss or damages arising from the use of this e-mail or its attachments. °°°°
Additionally, we inform you that Banco de México is responsible for the personal data it processes. Such process will be conducted under the principles and obligations provided in the General Law for the Protection of Personal Data in the Posession of Obliged Subjects, observing the atributions and faculties that are conferred by applicable legislation, and for the purposes related to them. We invite you to visit our website (www.banxico.org.mx) where you can consult our Privacy Notices, through section "Ley de Transparencia", subsection "Avisos de Privacidad". °°°°
2024, Año de Felipe Carrillo Puerto, Benemérito del Proletariado, Revolucionario y Defensor del Mayab
Original Message:
Sent: 7/22/2024 9:40:00 AM
From: Rick Spagna
Subject: RE: Failed to locate JVM in the PST Configuration File
Hi @Francisco arano,
Please, when you reply, just select Reply so it goes to this topic, and not directly to me.
Here is the latest reply I received directly from you:
Hi Rick,
If I followed the procedure to create the alias as stated in the documentation, I think my error lies in the definition of pstdir in the Pstserv and pstlocal configuration files. I defined it as follows:
Pstserv.cfg
pstdir OPTIMDIR SQLServer 2019 dbo_optim connect-str optimdirodbc
dbalias OPTIMDIR OPTIMALIAS optimdirodbc
pstlocal.cfg
pstdir OPTIMDIR SQLServer 2019 dbo_optim connect-str optimdirodbc dbo_optim passwrod32d**
dbalias OPTIMDIR OPTIMALIAS optimdirodbc dbo_optim passwrod32d**
optimdirodbc is the DSN definition in the odbc.ini file. I also think it could be the driver's environment variables.
[root@etc]# isql -v optimdirodbc dbo_optim passwrod32d**
[01000][unixODBC][Driver Manager]Can't open lib '/opt/IBM/InfoSphere/Optim/rt/bin/OOsqls28.so' : file not found
[ISQL]ERROR: Could not SQLConnect
Do you have an example of how to define pstdir and pstalias? Did you define the driver's environment variables?
Thanks a lot
------------------------------
Francisco arano
------------------------------
The first thing I notice is that you have connect-str as the value of the DBMS Connection String parameter. Did you really name the connection string connect-str?
Here's an example pstdir statement (with password x'd out):
pstlocal.cfg:pstdir SQL2019 SQLServer 2019 johnd DEVMSQL2019 DEVMSQL2019 johnd xxxxxxxx
pstserv.cfg:pstdir SQL2019 SQLServer 2019 johnd DEVMSQL2019 DEVMSQL2019 johnd xxxxxxxx
So, our connect-str is DEVMSQL2019, as is the dbname, and the statements are the same in both files.
Here is DBAlias:
pstlocal.cfg:dbalias SQL2019 DEVMSQL2019 DEVMSQL2019 johnd xxxxxxxx
pstserv.cfg:dbalias SQL2019 DEVMSQL2019 DEVMSQL2019 johnd xxxxxxxx
Here is some of the information in our odbc.ini for SQL Server 2019:
# [SQL Server Wire Protocol]
[DEVMSQL2019]
Driver=/home/o11702/IBM/InfoSphere/Optim/rt/bin/OOsqls28.so
Description=DataDirect 8.0 SQL Server Wire Protocol
Hope this gets you going.
------------------------------
Rick Spagna
Optim Development Director
UNICOM Global
973-755-4092
Original Message:
Sent: Mon July 22, 2024 07:55 AM
From: Rick Spagna
Subject: Failed to locate JVM in the PST Configuration File
Hi @Francisco arano,
I received this (between the ---- lines) in the Community in a private message from you, which, again, I see no way to reply to it:
----
Hi Rick Spagna,
I no longer see the JVM error but I still have the optim directory error. but I still have the optimdirectory and alias error
Thanks a lot
DBMS: RDB Internal
Date: 07/19/2024 14:35:24
ErrData: RDB generated error
ErrMsg: DB Alias - DirDB - is missing the Sybase/Informix/MSSQLServer Database Name
PN0RDB00 RDBCUTIL.C RDBRecordRDBErr(00420-0004F6E2)
Unknown Unknown Unknown(?????-EEB4BC26)
PN0RDB00 RDBCCONN.C RDBIntOpenConnection(03053-00015E08)
PN0RDB00 RDBCCONN.C RDBOpenConnectionSet(00737-000086AF)
pr0serv SERVPST.CPP ServOpenPstDirStatic(01263-000195EA)
pr0serv SERVPST.CPP ServOpenPstDir(01456-0001A373)
pr0serv SERVPST.CPP ServOpenDirByName(02197-0001C562)
pr0rcci RTSERV.H RtServOpenDirByName(01277-0008CB01)
pr0rcci RTRCCSVR.CPP RtRccServer SetupPstDir(00919-0008EB25)
pr0rcci RTRCCSVR.CPP RtRccServer Create(00646-0008DD41)
pr0ctls RTTHREAD.CPP RtThread InitInstance(01729-001610E8)
Unknown Unknown Unknown(?????-F62FEA5C)
Unknown Unknown Unknown(?????-F5C77E69)
Unknown Unknown Unknown(?????-F5BD3EC4)
Unknown Unknown Unknown(?????-F57DB185)
DSQCM7CN DSQLMSQLOpenConnection (0897) EXCP 07/19/2024 14:35:24 000020 00000D53 0000005A
ErrMsg: Return Error at line=241)
RetCode: RDBERR_DBERR(07500) General DBMS Error
RDBCCONN RDBIntOpenConnection (4163) EXCP 07/19/2024 14:35:24 000021 00000D53 0000005A
DBMS : SQL Server
DBMSVer : (null)
ApplVer : (null)
Date - Time : 07/19/2024 - 14:35:24
DBAlias : - DirDB -
Connect String : optimdirodbc
DB Qualifier :
Connect UserId : dbo_optim
DBMS UserId : (null)
DBMSType : G
DBMSDLLVer : 50 (17.0)
Connection Type : Normal
Connect Status : DBMSOpenConnection
DBMS Attributes : CmpCaseSen=N CatIDCase=? Auth=N
: IfxLog=Y IfxPublic=N IfxANSI=N
Workstation CP : 1252
Connection CB CP : 0
DBMS Server Char CP : 0
DBMS Server Char Set : (null)
DBMS Server NChar CP : 0
DBMS Server NChar Set: (null)
DBMS Client CP : 0
DBMS Client Char Set : (null)
DBMS Client NCHAR CP : 0
DBMS Client NCHAR Set: (null)
----
It looks to me like you have not properly setup the DB Alias. Did you use the Optim Configuration program to do Create DB Aliases?
Cheers,
------------------------------
Rick Spagna
Optim Development Director
UNICOM Global
973-755-4092
Original Message:
Sent: Fri July 19, 2024 02:51 PM
From: Rick Spagna
Subject: Failed to locate JVM in the PST Configuration File
Hi @Francisco arano,
I received your message to my inbox here on the Community, but do not see how to reply to it.
Did you add sourcing rtsetenv to the user's profile (in my case, using bash, it is in .bash_profile) per the instructions in the Configuration topic?
Cheers,
Rick
------------------------------
Rick Spagna
Optim Development Director
UNICOM Global
973-755-4092
Original Message:
Sent: Fri July 19, 2024 01:48 PM
From: Rick Spagna
Subject: Failed to locate JVM in the PST Configuration File
Hi @Francisco arano,
You should follow the Configure the server on UNIX or Linux instructions in the Optim Documentation,
Under the Configuration topic, there is discussion of the RTSETENV script which is where you set JRE_HOME and JVM. Here are what mine are set to:
JRE_HOME=/opt/java_i586/jre1.8.0_271
JVM=/opt/java_i586/jre1.8.0_271/lib/i386/client/libjvm.so
Hope this helps!
Rick
------------------------------
Rick Spagna
Optim Development Director
UNICOM Global
973-755-4092
Original Message:
Sent: Fri July 19, 2024 01:29 PM
From: Francisco arano
Subject: Failed to locate JVM in the PST Configuration File
Hi Rick Spagna,
I am installing on a redhat 8.8 and I installed runtime, web Web Applications and data privacy, and I do not have the JVM path in the files you mentioned IBM/InfoSphere/Optim/rt/OptimConfigClient.pst and IBM/InfoSphere/Optim/rt/ OptimConfigServer.pst My question is: should I specify the path of the JVM? If so, should it point to the libjvm.so file? I have the following paths of that file
/opt/ibm/java-i386-80/jre/bin/classic/libjvm.so
/opt/ibm/java-i386-80/jre/bin/j9vm/libjvm.so
/opt/ibm/java-i386-80/jre/lib/i386/classic/libjvm.so
/opt/ibm/java-i386-80/jre/lib/i386/default/libjvm.so
/opt/ibm/java-i386-80/jre/lib/i386/j9vm/libjvm.so
which one of those would it be?
Thanks
------------------------------
Francisco arano
Original Message:
Sent: Fri July 19, 2024 01:17 PM
From: Rick Spagna
Subject: Failed to locate JVM in the PST Configuration File
Hi @Francisco arano,
The Web Applications, also know as the Shared package, installation has the JVM Location input field disabled. So, if that is what you are installing, then it is expected. It would probably be better, and less confusing, if the JVM Location was not present for the Web Applications installation, rather than disabling it.
If you are installing any of the other packages, Designer or Runtime Services, then the JVM Location should be enabled. If not, then it is an issue.
So, which are you installing?
Have you gotten it installed?
Do you have an errors now?
Regards,
Rick
------------------------------
Rick Spagna
Optim Development Director
UNICOM Global
973-755-4092
Original Message:
Sent: Fri July 19, 2024 12:38 AM
From: Francisco arano
Subject: Failed to locate JVM in the PST Configuration File
Hi Rick Spagna,
I have the same error, in my case from the installation I do not enable the box to write the JVM path, do you know why this is? I am installing again but the text box does not enable me to write the path where the is JVM.
Thanks
------------------------------
Francisco arano
Original Message:
Sent: Wed December 13, 2023 04:08 PM
From: Rick Spagna
Subject: Failed to locate JVM in the PST Configuration File
Hi Fredrik,
Please check the value of the JVM entry in both IBM/InfoSphere/Optim/rt/OptimConfigClient.pst and IBM/InfoSphere/Optim/rt/OptimConfigServer.pst. It should have the location of a valid JVM. For example, mine has /opt/java_i586/java-se-8u41-ri/lib/i386/client/libjvm.so and this does exist:
[optimbuild@opdvl3-op-utp-local rt]$ ls -al /opt/java_i586/java-se-8u41-ri/lib/i386/client/libjvm.so
-rwxr-xr-x. 1 10 143 7750167 Jan 15 2020 /opt/java_i586/java-se-8u41-ri/lib/i386/client/libjvm.so
[optimbuild@opdvl3-op-utp-local rt]$
Regards,
------------------------------
Rick Spagna
Optim Development Manager
UNICOM Global
Original Message:
Sent: Wed December 13, 2023 10:58 AM
From: Fredrik Holm
Subject: Failed to locate JVM in the PST Configuration File
Hi!
Just installed on Linux: OptimRelease:11.7.0.0 Build:6041.
When running a Extract-job
/opt/IBM/InfoSphere/Optim/rt/bin/pr0cmnd -R TYPE=EXTRACT REQUEST=STISPROD.ADPMAKUT SERVER=optimProd DIRECTORY=TDMPDIR P+ OV=/tdm/prod/ov/STISPROD.ADPMAKUT_20231213_103456
it return with exitcode 12
Extract Process Errors
Generation of XML MetaData for an Archive/Extract file failed
Fatal error during creation of process report. See the log file for more
details.
When checking the log : ( Failed to locate JVM in the PST Configuration File )
Metadata MetaDataXML::convertJsonObjectTo(1957) EXCP 12/13/2023 16:34:18 000694 00057668 000000F2
File Metadata JSON length = 2153987
Metadata MetaDataXML::convertJsonObjectTo(2002) EXCP 12/13/2023 16:34:18 000695 00057668 000000F2
Going to convert json to xml
XMLGenerationHel XMLGenerationHelper::registerFac(0080) EXCP 12/13/2023 16:34:18 000696 00057668 000000F2
Failed to locate JVM in the PST Configuration File
Metadata MetaDataXML::convertJsonObjectTo(2010) EXCP 12/13/2023 16:34:18 000697 00057668 000000F2
Failed to locate JVM in the PST Configuration File
Metadata MetaDataXML::writeRuntimeMetaDat(2555) EXCP 12/13/2023 16:34:18 000698 00057668 000000F2
File Metadata was empty.
PswrXtrc XtrcWorker::DoWork (7533) EXCP 12/13/2023 16:34:18 000699 00057668 000000F2
Generation of XML MetaData for an Archive/Extract file : '/tdm/prod/extract/ADPMAKUT/AKUT/ADPMAKUT_R
ADERA_20231213_103454.XF' Failed
pr0svce.out:Reading Configuration File '/opt/IBM/InfoSphere/Optim/rt/etc/pstserv.cfg'
Cant find anything regardin JVM in this file..
All logfiles i uploaded
Best regards
Fredrik
------------------------------
Fredrik Holm
------------------------------
