Alternative to fnuxi & FORMAT.CONV

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,

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. )

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 

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.