RE: Objectcall headache...
First, let me qualify this by saying we are not yet up on UD6 on our production box. We are testing UD6 on our development box on Solaris and seeing none of these problems. Is this just an AIX issue? It would be good to know before we go live. Thanks Rod -Original Message- From: David Litzau [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 2:04 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... One last note on the AIX/UD6/DataStage issue; it appears that logging set at 32 is indeed the only work around that I can get working, but IBM has beat me to the punch when it comes to "what to do with the log files". Apparently defining dev/null in uniapi_admin as the log directory ends up dropping the log files into /tmp. There must be a check to ensure that the target is actually a "d"irectory, else it goes to /tmp. Anyway, redirected logging to a nice fat volume and cron is flushing them from there. Please let me know if anybody hears of another way around until we get our DS jobs rebuilt. Thanks. Dave -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
One last note on the AIX/UD6/DataStage issue; it appears that logging set at 32 is indeed the only work around that I can get working, but IBM has beat me to the punch when it comes to "what to do with the log files". Apparently defining dev/null in uniapi_admin as the log directory ends up dropping the log files into /tmp. There must be a check to ensure that the target is actually a "d"irectory, else it goes to /tmp. Anyway, redirected logging to a nice fat volume and cron is flushing them from there. Please let me know if anybody hears of another way around until we get our DS jobs rebuilt. Thanks. Dave -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Hona, David S wrote: >Yes, I can confirm - we have two "live" client 'C' >applications on Solaris >and HP-UX servers - utilising the IBM UniCall Interface (UCI) >library, to >interface to another Solaris host server (where the UV DBMS resides). > >The interface works quite well, albeit with a couple quirks. :-) Excellent David. Thanks. When they pulled ObjectCall, the only alternative offered for connection from a UNIX client was InterCall which was, at the time, far less robust. Having looked at the Client APIs supplement, it does indeed look like UO and UOJ use InterCall instead of UCI. Hopefully then, they'll have made the whole shebang more solid and reliable. Cheers, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
>Ken Wallis wrote: >>Hona, David S wrote: >> >>Well, we've been using UCI on Solaris and HP-UX for a number >>of years, so it is definitively available. >Sorry David, can you just confirm that for me? You have client 'C' or other >language programs running on Solaris and HP-UX which use UCI as the API >which allows them to connect into UniVerse on the same or another box? This >is outside of UOJ - a direct interface to UCI (not BCI) that is available >for UNIX platforms? Yes, I can confirm - we have two "live" client 'C' applications on Solaris and HP-UX servers - utilising the IBM UniCall Interface (UCI) library, to interface to another Solaris host server (where the UV DBMS resides). The interface works quite well, albeit with a couple quirks. :-) Regards, David -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Hona, David S wrote: >Well, we've been using UCI on Solaris and HP-UX for a number >of years, so it is definitively available. Sorry David, can you just confirm that for me? You have client 'C' or other language programs running on Solaris and HP-UX which use UCI as the API which allows them to connect into UniVerse on the same or another box? This is outside of UOJ - a direct interface to UCI (not BCI) that is available for UNIX platforms? Cheers, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
>Ken Wallis wrote: >InterCall definitely is available for UD. In my earlier post I think I >erroneously called it UniCall. >I do not believe that InterCall is the underlying interface for UO or UOJ. >Those are based on UCI AFAIK. There is no UNIX client piece for UCI that I >know of. Last time I looked, InterCall did not seem to plug into UCI at >all. Ken, Well, we've been using UCI on Solaris and HP-UX for a number of years, so it is definitively available. InterCall is the UV version of the old INFORMATION Calling Interface (ICI) transmuted/ported over to UNIX and Windoze. It has direct equivalents to BASIC functions and statements. UCI does not. UCI being ODBC compliant API, I doubt it has any relationship to UO or UOJ. But it is definitive the first cousin to UV/ODBC and UniOLEDB. ;-) Regards, David -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Hona, David S wrote: >Isn't InterCall available for UD? It's supposedly the >underlying interface to UV for UO and UOJ. David, InterCall definitely is available for UD. In my earlier post I think I erroneously called it UniCall. I do not believe that InterCall is the underlying interface for UO or UOJ. Those are based on UCI AFAIK. There is no UNIX client piece for UCI that I know of. Last time I looked, InterCall did not seem to plug into UCI at all. Cheers, Ken >Ken Wallis wrote: > >I could be way off here, but I strongly suspect that ObjectCall has one >important feature that these guys make use of that UniObjects gets nowhere >near to - it runs on UNIX. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Isn't InterCall available for UD? It's supposedly the underlying interface to UV for UO and UOJ. Regards, David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ken Wallis I could be way off here, but I strongly suspect that ObjectCall has one important feature that these guys make use of that UniObjects gets nowhere near to - it runs on UNIX. Isn't InterCall available for UD? It's supposedly the underlying interface to UV for UO and UOJ. Regards, David -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Thanks David. My hope is that we will be able to drop ObjectCall totally soon The application which we needed to get working is DataStage; unfortunately the work involved in converting all the DS jobs to use the UniData 6 stage is considerable but the good news is that our experience over the last week gives more weight to my argument that more resources should be invested in this project. Of course, my advice to anyone trying to interface to U2 from the outside world) is to either use the OLEDB or UniObjects interface than to suffer the pain of ObjectCall Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of djordan Sent: Friday, April 09, 2004 7:20 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... Hi Martin It is a while since I use dobjectcall, but as far as I remember UniObjects has all the functionality and more that objectcall and is a lot simpilar. You should be able to convert the application to UniObjects reasonably quickly, unless it is done by some third party, possibly quicker than trying to get ObjectCall to work. They are reasonably close in concept that you should be able to replace the ObjectCall functions with UniObjects equivalent Regards David Jordan Managin Consultant [EMAIL PROTECTED] Dacono Holdings Pty Ltd Business & Technology Consulting PO Box 909 Lane Cove NSW 2066 Australia Ph 61 2 9418 8329 Fax 61 2 9427 2371 www.dacono.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Canty Sent: Friday, 9 April 2004 1:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.as p, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
David Jordan wrote: > It is a while since I used objectcall, but as far as I remember > UniObjects has all the functionality and more that objectcall and is a > lot simpilar. You should be able to convert the application to > UniObjects reasonably quickly, unless it is done by some third party, > possibly quicker than trying to get ObjectCall to work. They are > reasonably close in concept that you should be able to replace the > ObjectCall functions with UniObjects equivalent David, I could be way off here, but I strongly suspect that ObjectCall has one important feature that these guys make use of that UniObjects gets nowhere near to - it runs on UNIX. UniObjects (Not UOJ) is a Windows only piece of COM flim-flam that allows relatively easy access to either U2 product from the MS toolsets. ObjectCall had a similar piece of COM flim-flam called EasyX which tried to do the same thing but didn't manage as well. When it came to making decisions about common middleware, EasyX versus UniObjects was a no-brainer. Unfortunately the rich and robust 'C' API that ObjectCall provided on both Windows and UNIX got EOL-ed along with the EasyX flim-flam that nobody used, and the only cross-platform replacement 'C' API available is the extremely flimsy UniCall that nobody in their right mind wants to build a commercial product with. Cheers, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Hi Martin It is a while since I use dobjectcall, but as far as I remember UniObjects has all the functionality and more that objectcall and is a lot simpilar. You should be able to convert the application to UniObjects reasonably quickly, unless it is done by some third party, possibly quicker than trying to get ObjectCall to work. They are reasonably close in concept that you should be able to replace the ObjectCall functions with UniObjects equivalent Regards David Jordan Managin Consultant [EMAIL PROTECTED] Dacono Holdings Pty Ltd Business & Technology Consulting PO Box 909 Lane Cove NSW 2066 Australia Ph 61 2 9418 8329 Fax 61 2 9427 2371 www.dacono.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Canty Sent: Friday, 9 April 2004 1:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.as p, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Correct...crying "fixed" may have been a little premature, but getting the DataStage job running after being down for a week felt like a victory. I am hoping that since the log data is going straight to the bit bucket that there will be little or no hit on performance. Suspect I'll here about it if it slows things down too much. -Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney Sent: Friday, April 09, 2004 12:18 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... Logging really slows everything down though. Sounds like a timing issue from what you discovered. Your performance may end requiring you to do additional investigation. But I am glad you got this far. - Rod -Original Message- From: David Litzau [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 2:05 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... It's fixed! So here's how it happened. Turned logging on to level of 9 to see what we would catch, used objping to test the connection and the error changed. Nothing meaningful in the log file, but since it was the first change we had seen, decided to turn the logging up to 99 and found that it worked...no errors. Tinkered with the logging level and found that 32 seemed to be the magic number. Load tested it with DataStage and all seems well. Maybe there's some timing issue...but the logging makes it work. To keep from having to clean up log files, had them change the log path to /dev/null. Thanks for the input. David Litzau -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney Sent: Friday, April 09, 2004 5:58 AM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... We have DataStage talking to Unidata 6.0.9 via objectcall. But this is on Solaris 8.0. I thought I heard that 6.0.3, AIX and Datastage were a problem. But I do not remember the source. We have another application (home grown) using objectcall as well. It is tough with objectcall not supported. But maybe there is something in 6.0.9 that makes a difference. - Rod -Original Message- From: Martin Canty [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Logging really slows everything down though. Sounds like a timing issue from what you discovered. Your performance may end requiring you to do additional investigation. But I am glad you got this far. - Rod -Original Message- From: David Litzau [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 2:05 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... It's fixed! So here's how it happened. Turned logging on to level of 9 to see what we would catch, used objping to test the connection and the error changed. Nothing meaningful in the log file, but since it was the first change we had seen, decided to turn the logging up to 99 and found that it worked...no errors. Tinkered with the logging level and found that 32 seemed to be the magic number. Load tested it with DataStage and all seems well. Maybe there's some timing issue...but the logging makes it work. To keep from having to clean up log files, had them change the log path to /dev/null. Thanks for the input. David Litzau -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney Sent: Friday, April 09, 2004 5:58 AM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... We have DataStage talking to Unidata 6.0.9 via objectcall. But this is on Solaris 8.0. I thought I heard that 6.0.3, AIX and Datastage were a problem. But I do not remember the source. We have another application (home grown) using objectcall as well. It is tough with objectcall not supported. But maybe there is something in 6.0.9 that makes a difference. - Rod -Original Message- From: Martin Canty [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
It's fixed! So here's how it happened. Turned logging on to level of 9 to see what we would catch, used objping to test the connection and the error changed. Nothing meaningful in the log file, but since it was the first change we had seen, decided to turn the logging up to 99 and found that it worked...no errors. Tinkered with the logging level and found that 32 seemed to be the magic number. Load tested it with DataStage and all seems well. Maybe there's some timing issue...but the logging makes it work. To keep from having to clean up log files, had them change the log path to /dev/null. Thanks for the input. David Litzau -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baakkonen, Rodney Sent: Friday, April 09, 2004 5:58 AM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... We have DataStage talking to Unidata 6.0.9 via objectcall. But this is on Solaris 8.0. I thought I heard that 6.0.3, AIX and Datastage were a problem. But I do not remember the source. We have another application (home grown) using objectcall as well. It is tough with objectcall not supported. But maybe there is something in 6.0.9 that makes a difference. - Rod -Original Message- From: Martin Canty [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Boy, since I sent this email out, our virus software has been busy protecting me. I think some people on this list server have been infected and are sending out these messages. I got about ten of these notifications. They were mixed in with the 'I am out of the office' emails I get from people here. Fortunately, my virus software appears to be one leg up. I don't now how dangerous the netsky virus is. But I sure hope I don't get it. - Rod An e-mail was sent to you that included a virus. The virus was successfully stripped and the sender was notified. No action is necessary. Contact the CBH Help Desk if you have any questions. VIRUS: Virus Scanner found the W32/[EMAIL PROTECTED] virus in the attached file: order3.pif -Original Message- From: Baakkonen, Rodney Sent: Friday, April 09, 2004 7:58 AM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... We have DataStage talking to Unidata 6.0.9 via objectcall. But this is on Solaris 8.0. I thought I heard that 6.0.3, AIX and Datastage were a problem. But I do not remember the source. We have another application (home grown) using objectcall as well. It is tough with objectcall not supported. But maybe there is something in 6.0.9 that makes a difference. - Rod -Original Message- From: Martin Canty [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
We have DataStage talking to Unidata 6.0.9 via objectcall. But this is on Solaris 8.0. I thought I heard that 6.0.3, AIX and Datastage were a problem. But I do not remember the source. We have another application (home grown) using objectcall as well. It is tough with objectcall not supported. But maybe there is something in 6.0.9 that makes a difference. - Rod -Original Message- From: Martin Canty [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:00 PM To: U2 Users Discussion List Subject: RE: Objectcall headache... On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Ken is correct that we have end-of-lifed ObjectCall - after years of
advanced warnings.
Regardless - we haven't removed it from the product. It is still there. You
can still try to use it. We have stopped engineering work on it.
Epicor does have an open case with U2 support. We are working with them to
try to get it functioning for them. There are a number of sites (including
Epicor sites - if I'm not mistaken - Martin/David - feel free to correct me
if I'm misremembering) where ObjectCall is working with UniData 6.0.x and
AIX, so why this particular system is having problems is under
investigation and likely to be successfully resolved. It does rely on
tcp/ip so the problems may not be with ObjectCall itself.
Ascential does have a new version of DataStage that no longer uses
ObjectCall. I'll let the ASCL folks elaborate if they choose.
Wally Terhune
Manager - U2 Advanced Technical Services
IBM DB2 Information Management Software
Tel: 303.294.4866 Fax: 303.294.4832
[EMAIL PROTECTED]
www.ibm.com/software/data/u2/support - Open, Query, Update, Search -
Online!
Don't miss out on the IBM DB2 Information Management Technical Conference
September 19-24, 2004 - Las Vegas, NV
Martin Canty
<[EMAIL PROTECTED]
m> To
Sent by: U2 Users Discussion List
u2-users-bounces@ <[EMAIL PROTECTED]>
oliver.com cc
Subject
04/08/2004 09:00 RE: Objectcall headache...
PM
Please respond to
U2 Users
Discussion List
On behalf of Dave, let me expand.
We have a DataStage job which is still relying on ObjectCall (until we can
rewrite it to utilise the new UniData6 stage), unfortunately, after the
UniData upgrade ObjectCall ceased to function & no matter what we do we
just
cannot get it to work again
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ken Wallis
Sent: Thursday, April 08, 2004 5:05 PM
To: 'U2 Users Discussion List'
Subject: RE: Objectcall headache...
> Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can
> no longer get an Objectcall connection to that server.
Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship
it.
IBM also end-of-lifed AIX 4.3 mid last year IIRC.
Having just checked the availability matrix at
https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp,
I
see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1
definitely isn't mentioned.
Moving beyond this bunch of uncertainty I have about the supportability of
your client's platform set, it might be worth asking what they upgraded
from
and what you are trying to connect with. ObjectCall is a highly version
dependent beast. If they upgraded from an early UniData version like 3.3.2
or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you
used to be able to connect with would now be incompatible.
Anyway, how to resolve this? First push the server and client logging
levels up high (level 9?), then start off on the AIX box with objping and
see if you can get a connection on the same box. Once you have that
working, see if you can connect an external client.
HTH,
Ken
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
Re: Objectcall headache...
In a message dated 4/8/2004 8:01:13 PM Pacific Daylight Time, [EMAIL PROTECTED] writes: > We have a DataStage job which is still relying on ObjectCall (until we can > rewrite it to utilise the new UniData6 stage), unfortunately, after the > UniData upgrade ObjectCall ceased to function & no matter what we do we just > cannot get it to work again Maybe "until" has arrived ... -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
On behalf of Dave, let me expand. We have a DataStage job which is still relying on ObjectCall (until we can rewrite it to utilise the new UniData6 stage), unfortunately, after the UniData upgrade ObjectCall ceased to function & no matter what we do we just cannot get it to work again Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis Sent: Thursday, April 08, 2004 5:05 PM To: 'U2 Users Discussion List' Subject: RE: Objectcall headache... > Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can > no longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
> Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I > may, I can no > longer get an Objectcall connection to that server. Well, IBM end-of-lifed ObjectCall a while ago, but I still think they ship it. IBM also end-of-lifed AIX 4.3 mid last year IIRC. Having just checked the availability matrix at https://www-927.ibm.com/software/data/u2/support/u2techconnect/matrix.asp, I see that 6.0.3 and 6.0.8 ARE both certified for AIX 4.3.3, but 4.3.1 definitely isn't mentioned. Moving beyond this bunch of uncertainty I have about the supportability of your client's platform set, it might be worth asking what they upgraded from and what you are trying to connect with. ObjectCall is a highly version dependent beast. If they upgraded from an early UniData version like 3.3.2 or 4.0 and went straight to 6.0, then whatever ObjectCall client piece you used to be able to connect with would now be incompatible. Anyway, how to resolve this? First push the server and client logging levels up high (level 9?), then start off on the AIX box with objping and see if you can get a connection on the same box. Once you have that working, see if you can connect an external client. HTH, Ken -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Objectcall headache...
Hi Dave :) Sayhopefully you'll get some expert responses...(disregard the fact that IBM doesn't support object call anymore, but.) there's a couple of simple things to check that's gotten me before 1) make sure it's licensed w/ VERSION (if it's even still listed at 6?) 2) In uniapi_admin, under administer servers, make sure you've got a valid Log dir... 3) make sure unirpcd daemon is running.. Other than that...you might be able to find something in the unidata documentation...what uniclose is looking for, at position one...? Good luck!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Litzau Sent: Thursday, April 08, 2004 3:08 PM To: [EMAIL PROTECTED] Subject: Objectcall headache... I just recently found you folks...this is good stuff! Maybe you can help me with this one (sorry if there has been previous discussion)... Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can no longer get an Objectcall connection to that server. I have used uniapi_admin to recreate the server and database, Verified that $UDTBIN, $UDTHOME, etc are valid and matches what I input in uniapi_admin, I recreated the uniapi.ini on the remote workstation to ensure that it has no munged text, I can "telnet 4343" to the server and it connects...doesn't do anything of course but it connects (verified using netstat), Tried objping as root on the server and get the same errors as I do from a remote workstation: ERROR ON CLIENT in UniOpenPos: Server terminated unexpectedly. ERROR ON CLIENT in UniClose: Argument at position 1 has NULL handle. Any thoughts? David Litzau -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Objectcall headache...
I just recently found you folks...this is good stuff! Maybe you can help me with this one (sorry if there has been previous discussion)... Client upgraded UD to 6.0.3 on an AIX 4.31 box. Try as I may, I can no longer get an Objectcall connection to that server. I have used uniapi_admin to recreate the server and database, Verified that $UDTBIN, $UDTHOME, etc are valid and matches what I input in uniapi_admin, I recreated the uniapi.ini on the remote workstation to ensure that it has no munged text, I can "telnet 4343" to the server and it connects...doesn't do anything of course but it connects (verified using netstat), Tried objping as root on the server and get the same errors as I do from a remote workstation: ERROR ON CLIENT in UniOpenPos: Server terminated unexpectedly. ERROR ON CLIENT in UniClose: Argument at position 1 has NULL handle. Any thoughts? David Litzau -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
