Author |
Message
|
rekarm01 |
Posted: Fri May 17, 2013 1:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
DSPS wrote: |
"What does the S65D datasource look like in the $ODBCINI file? "
Code: |
[S65D]
Description = iSeries Access ODBC Driver DSN for BPCS on iSeries
Driver = iSeries Access ODBC Driver
System = S65D
UserID = XXXX
Password = YYYYYY
Naming = 0
DefaultLibraries = BMOSF610D
Database = S65D
ConnectionType = 0
CommitMode = 2
ExtendedDynamic = 0
DefaultPkgLibrary = BMOSF610D
DefaultPackage = A/DEFAULT(IBM),2,0,1,0,512
AllowDataCompression = 1
LibraryView = 0
AllowUnsupportedChar = 0
ForceTranslation = 0
Trace = 1 |
|
There should also be a [ODBC Data Sources] stanza before this, listing S65D as a data source.
The documentation is not really clear as to whether the extra space characters before and after the '=' is going to cause problems, but it might be worthwhile to remove them, (as well as any other extraneous leading/trailing white space), and make sure there aren't other syntax errors before this stanza. |
|
Back to top |
|
|
DSPS |
Posted: Fri May 17, 2013 1:33 am Post subject: |
|
|
Apprentice
Joined: 11 Sep 2008 Posts: 44 Location: Southern England
|
Oh, and the PMR question. I'm working for an IBM business partner, and I would have to get myself added to their customer's support contract, which, from experience with another customer, takes a long time. _________________ Distributed Systems Professional Services
WebSphere and MQ Consulting and Training |
|
Back to top |
|
|
DSPS |
Posted: Fri May 17, 2013 1:44 am Post subject: |
|
|
Apprentice
Joined: 11 Sep 2008 Posts: 44 Location: Southern England
|
There's not much that Google or AltaVista reveals about the stanza you suggest except this
http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.odbc.doc/odbc58.htm
which lead me to prepend this in the odbc.ini file: -
[ODBC Data Sources]
S65D=iSeries Access ODBC Driver
[S65D]
Description=iSeries Access ODBC Driver DSN for BPCS on iSeries
Driver=iSeries Access ODBC Driver
System=S65D
Is that what you meant?
Having tried that, mqsicvp still gives IM002 for ODBC:S65D or S65D on the command-line.
mqsicvp poc_brkr -n ODBC::S65D
For example - Data source name not found and no default driver specified. _________________ Distributed Systems Professional Services
WebSphere and MQ Consulting and Training |
|
Back to top |
|
|
smdavies99 |
Posted: Fri May 17, 2013 2:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Normally, this
Code: |
Driver=iSeries Access ODBC Driver
|
points at the actual driver .so (or similar) file.
I've never used ODBC to iSeries but it strikes me that this might be what is missing _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
|
DSPS |
Posted: Fri May 17, 2013 2:12 am Post subject: |
|
|
Apprentice
Joined: 11 Sep 2008 Posts: 44 Location: Southern England
|
Okay, I tried this: -
[ODBC Data Sources]
S65D=/opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
But the same results with mqsicvp using either ODBC::S65D or DSN::S65D _________________ Distributed Systems Professional Services
WebSphere and MQ Consulting and Training |
|
Back to top |
|
|
DSPS |
Posted: Fri May 17, 2013 2:20 am Post subject: |
|
|
Apprentice
Joined: 11 Sep 2008 Posts: 44 Location: Southern England
|
Whoa. Just tried
mqsisetdbparms poc_brkr -n S65D -u ObscuredUser -p NotTellingEither
and then
mqsicvp poc_brkr -n S65D
Got a whole list of information about the data source back.
That's quite a relief. Thank you very much everyone for the contributions to the settling of this.
Now, all I have to do is get an ODBC reference into the PASSTHROUGH part of the Java Compute Node.
Thanks for helping me see a light in this tunnel. _________________ Distributed Systems Professional Services
WebSphere and MQ Consulting and Training |
|
Back to top |
|
|
rekarm01 |
Posted: Fri May 17, 2013 2:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
DSPS wrote: |
Okay, I tried this: -
[ODBC Data Sources]
S65D=/opt/ibm/iSeriesAccess/lib64/libcwbodbc.so |
It seemed like it would make more sense to put the .so filename after 'Driver=':
Code: |
[S65D]
Driver=/opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
Description=iSeries Access ODBC Driver DSN for BPCS on iSeries
... |
|
|
Back to top |
|
|
DSPS |
Posted: Fri May 17, 2013 2:44 am Post subject: |
|
|
Apprentice
Joined: 11 Sep 2008 Posts: 44 Location: Southern England
|
That starts to look much more like the entry in the odbcinst.ini file, from where I copied the path to the shared object for the iSeries access driver.
Strange though, if I add the particular port number to the S65D stanza
Port=1234
or
PortNumber=1234
It still makes the connection to a different port number.
I'll go and read some more manual pages.
It is looking much more promising now. _________________ Distributed Systems Professional Services
WebSphere and MQ Consulting and Training |
|
Back to top |
|
|
|