Connecting Tech Pros Worldwide Help | Site Map

Error while connecting to DB2 Z/OS from DataStage

shsandeep
Guest
 
Posts: n/a
#1: Jul 3 '06
We are trying to connect from DataStage to a DB2 database on Z/OS. It
connects fine from the DataStage server, but when connecting from
DataStage client it gives the following error:

DSR.MetaGeta(GET.TABLES)(SQLConnect('USABCCP1','us psxs')): BCI Error:
SQLSTATE=08S01,CODE=0,[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2
Wire Protocol driver]Permanent Agent Error.

Has anybody encountered this before? Any ideas will be very helpful.

Cheers,
San.

Jeroen van den Broek
Guest
 
Posts: n/a
#2: Jul 3 '06

re: Error while connecting to DB2 Z/OS from DataStage



"shsandeep" <sandeeprshah@gmail.comschreef in bericht
news:6eb9ad10fb8a312921881ea270c548ef@localhost.ta lkaboutdatabases.com...
Quote:
We are trying to connect from DataStage to a DB2 database on Z/OS. It
connects fine from the DataStage server, but when connecting from
DataStage client it gives the following error:
>
DSR.MetaGeta(GET.TABLES)(SQLConnect('USABCCP1','us psxs')): BCI Error:
SQLSTATE=08S01,CODE=0,[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2
Wire Protocol driver]Permanent Agent Error.
>
Has anybody encountered this before? Any ideas will be very helpful.
>
Cheers,
San.
>
This isn't as much a DB2 for z/OS problem, as well as a problem with the
DataDirect ODBC driver (in this case the DB2 Wire Protocol driver).
You'll find some related info (for Oracle) here:
http://knowledgebase.datadirect.com/...C?OpenDocument

Probably you will be better off describing your problem on the DataDirect
Support forum:
http://forums.datadirect.com/ddforums/index.jspa

HTH.

--
Jeroen


Pierre Saint-Jacques
Guest
 
Posts: n/a
#3: Jul 4 '06

re: Error while connecting to DB2 Z/OS from DataStage


Question #1
The event monitor data is written to two buffers which you can size in the
event definition at create time.
The data is flushed to file or table when the buffer is full or when the
FLUSH command is issued.
It is possible, because of low activity that an event monitor for connection
or table activity does not see ebough activity on the object for the buffer
to fill and flush.
This may be why you only see activity after the flush even though there are
active connection(s) on the db.

HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Jeroen van den Broek" <jeroen@NOSPAM.demon.nla écrit dans le message de
news: 12aj4ol84nf2i2a@corp.supernews.com...
Quote:
>
"shsandeep" <sandeeprshah@gmail.comschreef in bericht
news:6eb9ad10fb8a312921881ea270c548ef@localhost.ta lkaboutdatabases.com...
Quote:
>We are trying to connect from DataStage to a DB2 database on Z/OS. It
>connects fine from the DataStage server, but when connecting from
>DataStage client it gives the following error:
>>
>DSR.MetaGeta(GET.TABLES)(SQLConnect('USABCCP1','u spsxs')): BCI Error:
>SQLSTATE=08S01,CODE=0,[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2
>Wire Protocol driver]Permanent Agent Error.
>>
>Has anybody encountered this before? Any ideas will be very helpful.
>>
>Cheers,
>San.
>>
>
This isn't as much a DB2 for z/OS problem, as well as a problem with the
DataDirect ODBC driver (in this case the DB2 Wire Protocol driver).
You'll find some related info (for Oracle) here:
http://knowledgebase.datadirect.com/...C?OpenDocument
>
Probably you will be better off describing your problem on the DataDirect
Support forum:
http://forums.datadirect.com/ddforums/index.jspa
>
HTH.
>
--
Jeroen
>
shsandeep
Guest
 
Posts: n/a
#4: Jul 5 '06

re: Error while connecting to DB2 Z/OS from DataStage


Thank you to all who replied.
I managed to sort out the issue. DataStage was using DataDirect drivers
for connectivity. We tried using the native DB2 driver and it worked.
Sometimes the DataDirect driver and DB2 version have some incompatibilty,
etc.
Anyways, now its solved... thanks once again.

Cheers,
San.

Jeroen van den Broek
Guest
 
Posts: n/a
#5: Jul 5 '06

re: Error while connecting to DB2 Z/OS from DataStage



Pierre Saint-Jacques wrote:
Quote:
Question #1
The event monitor data is written to two buffers which you can size in the
event definition at create time.
The data is flushed to file or table when the buffer is full or when the
FLUSH command is issued.
It is possible, because of low activity that an event monitor for connection
or table activity does not see ebough activity on the object for the buffer
to fill and flush.
This may be why you only see activity after the flush even though there are
active connection(s) on the db.
>
HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
I guess this was meant for another thread in this ng, 'event
monitoring' ?!

--
Jeroen

Closed Thread