1 reply to this topic

[barry kavanagh]

So, here's our problem... after changing the filedef for a CISAM file (e.g. in our dev area) we need to be able to transfer the filedef to a higher environment (e.g. UAT or Live) and at the same time, convert the data in the physical file of the receiving environment to match the new filedef.

We don't want to build a unique conversion function to process the files specific to each release; we want a generic process that can handle any of our files.

We currently have something that works fine in our Native development environment but we are moving to VIP and need something similar. Our current version accesses the Native bootstraps in order to create/gen/run a one-off update function that reads-in the old data using the old filedef and writes-out the new data using the new filedef.

It may be that we have no option than to get the relevant VIP bootstrap filedefs from Proiv and create a suite of functions to mimic what we currently do against the Native bootstraps but we'd rather avoid that if possible - it would also involve updating and/or rebuilding the underlying Native bootstraps too of course.

Question - does anyone else handle the conversion of CISAM data in this kind of generic manner as part of a VIP import? or do you just write something unique for each release that you do?

I'd be grateful for any comments/suggestions/recommendations etc.

Regards - Barry

Environment is Proiv kernel 5.5r517, VIP 5.5927 on a Unix platform.

[Rob Donovan]

Hi,

You should still be able to use your same utility, even if you decide to move to VIP.

ProIV still gens from and source is still kept in the native boots. VIP just copies the data to its own version of the boots (which are prety much the same, just called VIPBMxxx to confuse us all and make us 'think' we need to move to VIP cause its all so new).

Then when you build in VIP i just builds the native code, and then the gen function works off the native boots.

So you should be fine to still run your utility off the native boots....

We have a conversion generator also, and it looks like it works fine in V6 purely in native (but I have not done a huge amount of testing in that area, but there is no reason why it should not work).

HTHs

Rob.