Re: Performance
In a message dated 4/8/2004 12:20:45 PM Pacific Daylight Time, [EMAIL PROTECTED] writes: 1.) Application files have all been analyzed and sized correctly. 2.) IBM U2 support analyzed Universe files, locking, swap space and all have been adjusted accordingly or were 'ok'. 3.) We are running RAID 5, with 8G allocated for Universe 4.) We are already running nmon, which is how we identified the paging faults and high disk I/O Indexes created without suppressing NULLs -- 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...
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...
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
Personal UD6.0 Max number of users reached.
I just installed it and got to login with out issues. After I messed up my database and had to reload it I'm getting the error telling me that the Max number of users has been reached. When I go into the ADMIN tool and look, there is no one logged in. I got 2 our of the 2 connections free. Is there something else I should look for? Is there a different kind of connection that will take a license but not show under the users? Jeffrey Lettau ERP Systems Manager polkaudio -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Personal UD6.0 Max number of users reached.
Ok, I disabled the Redback utility service and Redback scheduler. I'm guessing that this took my 2 accounts? Jeffrey Lettau ERP Systems Manager polkaudio -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lettau, Jeff Sent: Friday, April 09, 2004 12:04 PM To: U2 Users Discussion List Subject: Personal UD6.0 Max number of users reached. I just installed it and got to login with out issues. After I messed up my database and had to reload it I'm getting the error telling me that the Max number of users has been reached. When I go into the ADMIN tool and look, there is no one logged in. I got 2 our of the 2 connections free. Is there something else I should look for? Is there a different kind of connection that will take a license but not show under the users? Jeffrey Lettau ERP Systems Manager polkaudio -- 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: Connection to account failure!
Thanks Colin, I found it that we had a '[' in our password and this caused the failure in the system. Frank [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, April 08, 2004 3:46 PM To: [EMAIL PROTECTED] Subject: RE: Connection to account failure! In VSG did you make sure the user your are connecting as has the required SQL privileges to access the files. Do they also have the required OS permissions to access the files? I've done this with a Win 2000 Dell PC with MS Access 2000 (and Excel 2000 - with which I had more trouble) accessing UD 6.02, 6.07, 6.0.12 on Win 2000 servers. Our Aix box is in the middle of an upgrade to 6.0 something and I haven't had a chance to test with it. hth -- Colin Alfke Calgary, Alberta Canada Just because something isn't broken doesn't mean that you can't fix it Stu Pickles -Original Message- From: Bright, Frank [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 12:41 PM To: U2-Users Group (E-mail) Subject: Connection to account failure! Good Afternoon All! I am setting up an ODBC query and I get the error Connection to 'whatever account' failure after the listing of ODBC files to choose from. I am testing this out with MS Access 2000 on Win 2000 Dell PC. The same problem occurs on other PCs running Win XP. We are using Unidata 6.03 on an IBM P630 Box with AIX 5.2.02. Has anyone else encountered this problem and was able to solve it? Thanks in advance! Frank [EMAIL PROTECTED] ___ Frank M. Bright -- 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...
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...
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: Performance
Kevin, When you finally get this solved, let us know what the answer was. I am sure all responders would be interested. re. /tmp: I've seen marginal but not incredible inprovement moving UVTEMP onto our EMC storage rather than on the system's local disk (/tmp) re. file sizing: since you are porting from D3, I assume yoou made everything type 18, which is the standard Pick hashing algorithm? That ought to behave about the same as it did on D3. How about Separation? Does D3 have that concept? I don't think Jeff mentioned it. For most files you want to set separation such that you get integer number of groups for each OS disk read. If a sigle disk read grabs 8K, then separation 4 (512*4= 2K/group) means filescans will ask for a group, the OS will read in 4 groups, and the next 3 times the process asks for the next group, it's probably still sitting in memory. So if the OS does read 8K at a time, separations of 1,2,4,8,16,12 make sense, depending on the nature of the records. 4 is typical. re. locks: I notice the lock table is pretty small, and there are a lots of 'CLR.OM.LOCK proceses. Is this one of those PICK aps where people developed their own record locking scheme because they didn't trust PICK's record lock handling? If so, maybe that is a source of ineffeciency. It's not clear how that would manifest itself with paging, though. What about loading programs into shared memory? Do you have an absolutely huge program that many users use? By default they each load their own copy of the object file into their private memory. But you can change that so only one copy is loaded. The same with small utility routines that get called by everyone throughout the day. Load them once in shared memory, then all users will run off that copy. Again, we're talking incremental, not incredible, performance improvements. I'm grasping here. I'm sure IBM's Hdwr, AIX, U2 support has gone through all this already. You will post the answer once you know it, won't you? cds -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Performance
Thanks to everyone for the performance suggestions...I will report to the board as soon as we resolve it. Kevin Kevin D. Vezertzis Project Manager Cypress Business Solutions, LLC. 678.494.9353 ext. 6576 Fax 678.494.9354 [EMAIL PROTECTED] Visit us at www.cypressesolutions.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stevenson, Charles Sent: Friday, April 09, 2004 4:24 PM To: U2 Users Discussion List Subject: RE: Performance Kevin, When you finally get this solved, let us know what the answer was. I am sure all responders would be interested. re. /tmp: I've seen marginal but not incredible inprovement moving UVTEMP onto our EMC storage rather than on the system's local disk (/tmp) re. file sizing: since you are porting from D3, I assume yoou made everything type 18, which is the standard Pick hashing algorithm? That ought to behave about the same as it did on D3. How about Separation? Does D3 have that concept? I don't think Jeff mentioned it. For most files you want to set separation such that you get integer number of groups for each OS disk read. If a sigle disk read grabs 8K, then separation 4 (512*4= 2K/group) means filescans will ask for a group, the OS will read in 4 groups, and the next 3 times the process asks for the next group, it's probably still sitting in memory. So if the OS does read 8K at a time, separations of 1,2,4,8,16,12 make sense, depending on the nature of the records. 4 is typical. re. locks: I notice the lock table is pretty small, and there are a lots of 'CLR.OM.LOCK proceses. Is this one of those PICK aps where people developed their own record locking scheme because they didn't trust PICK's record lock handling? If so, maybe that is a source of ineffeciency. It's not clear how that would manifest itself with paging, though. What about loading programs into shared memory? Do you have an absolutely huge program that many users use? By default they each load their own copy of the object file into their private memory. But you can change that so only one copy is loaded. The same with small utility routines that get called by everyone throughout the day. Load them once in shared memory, then all users will run off that copy. Again, we're talking incremental, not incredible, performance improvements. I'm grasping here. I'm sure IBM's Hdwr, AIX, U2 support has gone through all this already. You will post the answer once you know it, won't you? cds -- 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...
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
