Neoview ODBC Drivers Manual (R2.2 SP1)

1. Check the integrity of the library:
• Verify MD5SUM
md5sum library
Compare the output with the contents of /etc/hpodbc/MD5SUM.
• Find the version of the driver:
— On Linux:
nm libhpodbc.so | grep HPODBC
or
nm libhpodbc_drvr.so | grep HPODBC
— On x86–64 Linux:
nm libhpodbc64.so | grep HPODBC
or
nm libhpodbc_drvr64.so | grep HPODBC
— On HP-UX(IA-64) and HP-UX(PA-RISC):
nm libhpodbc.sl | grep HPODBC
or
nm libhpodbc_drvr.sl | grep HPODBC
— On HP-UX(IA-64) 64–bit:
nm libhpodbc64.i.sl | grep HPODBC
or
nm libhpodbc64_drvr.i.sl | grep HPODBC
— On IBM AIX®:
nm libhpodbc.a | grep HPODBC
or
nm libhpodbc_drvr.a | grep HPODBC
— On IBM AIX® 64–bit:
nm libhpodbc64.a | grep HPODBC
or
nm libhpodbc_drvr64.a | grep HPODBC
— On Sun SPARC®:
nm libhpodbc.so | grep HPODBC
or
nm libhpodbc_drvr.so | grep HPODBC
— On Sun SPARC® 64–bit:
nm libhpodbc64.so | grep HPODBC
or
nm libhpodbc_drvr64.so | grep HPODBC
The nm command returns this version information:
_###HPODBC_x_y_z_yymmdd
The “x_y_z” string is the version number (for example, 1_0_0).
The “yymmdd” string is the build date, where yy is the year, mm is the month, and dd is the
day (for example, 060419).
Troubleshooting 41