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
