Looking for a solution/trick/etc... for the following scenario:
We're running a UniVerse 10.1.22 application on AIX 5.3.0. But want to offload a certain module for real-time processing to a new Centos Stream server on a VMware platform running UniVerse 14.1.1. The plan is to have the "core " files needed NFS mounted and exported to the other server. So that they are viewed as local files to UniVerse and the rest of the application.
To move the data, I've been using rsync and planned to continue using it to keep the Centos server data current, for my purposes it was very efficient. The problem is each time the data is synced, I have to perform a "fnuxi" on the data to perform the byte-swap. Any alternatives to doing this fnuxi each time data is synced ? Is there a certain File type I can use (Type 1 or 19) to avoid this ?
Regards,
Algis Zyle
------------------------------
Al Zyle
Senior PICK Developer/Consultant
Rocket Forum Shared Account
------------------------------
Al,
There are limited options due to the old version of UniVerse on the AIX system. UniVerse 10.1.22 went EOLS in 2017, and I believe IBM set AIX 5.3 to EOL in 2016.
Have you reached out to your Rocket MultiValue Sales rep and/or the Application provider?
There is an option where Rocket Direct End Users, and Partners can "Talk to an Expert, and request a MultiValue Discovery Assessment", to help with your modernization planning. If you receive your MultiValue Solution from a Partner, please contact them for assistance. ( If you are not sure who hat is or are having issues contacting them, please send me a direct message. )
------------------------------
Mike Rajkowski
MultiValue Product Evangelist
Rocket Internal - All Brands
US
------------------------------
Al,
There are limited options due to the old version of UniVerse on the AIX system. UniVerse 10.1.22 went EOLS in 2017, and I believe IBM set AIX 5.3 to EOL in 2016.
Have you reached out to your Rocket MultiValue Sales rep and/or the Application provider?
There is an option where Rocket Direct End Users, and Partners can "Talk to an Expert, and request a MultiValue Discovery Assessment", to help with your modernization planning. If you receive your MultiValue Solution from a Partner, please contact them for assistance. ( If you are not sure who hat is or are having issues contacting them, please send me a direct message. )
------------------------------
Mike Rajkowski
MultiValue Product Evangelist
Rocket Internal - All Brands
US
------------------------------
The big/little endian difference is at the processor level. The PowerPC chip was big endian. The intel chips are little endian. The only way you're going to avoid converting it between your two systems is to keep them on the same processor architecture. That means either putting your new module on a PowerPC box or converting your main application off of your IBM machine to something Linux based.
Since Mike mentioned that your current setup is past it's end of life date, I'd convert from AIX to Linux. Unless you're an IBM shop I don't see any reason to continue with the AIX platform.
------------------------------
Joe Goldthwaite
Consultant
Phoenix AZ US
------------------------------
Looking for a solution/trick/etc... for the following scenario:
We're running a UniVerse 10.1.22 application on AIX 5.3.0. But want to offload a certain module for real-time processing to a new Centos Stream server on a VMware platform running UniVerse 14.1.1. The plan is to have the "core " files needed NFS mounted and exported to the other server. So that they are viewed as local files to UniVerse and the rest of the application.
To move the data, I've been using rsync and planned to continue using it to keep the Centos server data current, for my purposes it was very efficient. The problem is each time the data is synced, I have to perform a "fnuxi" on the data to perform the byte-swap. Any alternatives to doing this fnuxi each time data is synced ? Is there a certain File type I can use (Type 1 or 19) to avoid this ?
Regards,
Algis Zyle
------------------------------
Al Zyle
Senior PICK Developer/Consultant
Rocket Forum Shared Account
------------------------------
I'm pretty sure both type 1 and 19 files should work as they are essentially directories of text files in the OS filesystem. I would choose type 19 over type 1.
The main consideration with these file types is that they do not benefit from the database's hashing and so can be slow for files with many items in them.
------------------------------
Martin Shields
Senior Technical Consultant
Meier Business Systems PTY LTD
Carnegie VIC AU
------------------------------
I'm pretty sure both type 1 and 19 files should work as they are essentially directories of text files in the OS filesystem. I would choose type 19 over type 1.
The main consideration with these file types is that they do not benefit from the database's hashing and so can be slow for files with many items in them.
------------------------------
Martin Shields
Senior Technical Consultant
Meier Business Systems PTY LTD
Carnegie VIC AU
------------------------------
Thanks Martin, I've figured that out and that solves 1/2 my problem !
Regardless, in regards to Mike's response, unfortunately Rocket hasn't
been very receptive and cost prohibitive with any upgrade path...ever
since Device Licensing came into play.
I moved happily to OpenQM but now can't even get my developer copy from
Rocket since they acquired it ! Just trying to make do with what I have
available.
Regards,
Al
Thanks Martin, I've figured that out and that solves 1/2 my problem !
Regardless, in regards to Mike's response, unfortunately Rocket hasn't
been very receptive and cost prohibitive with any upgrade path...ever
since Device Licensing came into play.
I moved happily to OpenQM but now can't even get my developer copy from
Rocket since they acquired it ! Just trying to make do with what I have
available.
Regards,
Al
Al,
I am sorry if you have had issues contacting someone in the past.
I will send you a direct message, so that I can help you get in contact with the correct person.
---
As for the NFS option: While I agree that the use of Type 1/19 files would work well with NFS transfer between AIX and CentOS, I can not recommend it due to the outdated AIX version, since I believe you would be forced to use an older NFS version, and could run into quite a few issues.
As for cost, UniVerse upgrades are free to those on maintenance. I also recommend upgrading the OS as well. This would not only remove some of the issues when dealing with the old NFS version supported by the OS, but would open up additional solutioning options.
------------------------------
Mike Rajkowski
MultiValue Product Evangelist
Rocket Internal - All Brands
US
------------------------------
