RE: v5r1 upgrade--converting files

My understanding is that yes, there are some benefits to touching every
file on your system after an upgrade, particularly for those database
physical files flagged to reuse deleted records.  It is also my
understanding that the STROBJCVN command is specifically designed for
upgrading from a CISC to a RISC machine and will have no effect in your
circumstances.

I'm not sure what the best method of accomplishing this is.  I've heard
of people writing code to open every database physical file with a CPYF
command and copy the first few records to a temp file which would then
be deleted.  I don't believe that the STROBJCVN command will have the
desired effect.

Regards,
Andy

> It will prevent any problems when the users are using the system the
> first day, the big issue is that after you run it, all your files will
> have a last change date of the day you ran the Strobjcnv.  If that
> doesn't bother you run it, as per the latest info in the PSP bucket.


> Is the file conversion on first use in v5r1 a big deal?  My boss is
> concerned about potential performance problems after the upgrade.  Is
it
> worth it to run STROBJCVN over production libraries before turning the
> system over to the end users?  (We're going from v4r5 to 5r1 on our
> development machine to start with.)