|
Hi Ouldare,
Anything is "possible", but will it work
properly once you have done this? The answer is NO, it will not. If it was so
simple to just do a *MAP *DROP copy of files instead of a conversion, then
believe me, SSA would have told users to do that, instead of bothering to
write a conversion utility.
You must use the conversion utililty to make
sure that all fields in all files are properly converted, or the SSA
Helpline will not support you should you have any application problems resulting
from your bad data conversion. Potentially not every field in every file is
brought directly over to a file of the same name - data may be moved from 1 file
to another file instead.
You will save yourself a lot of headaches if you
just follow the instructions and do it properly from day 1, rather than
wondering in 4 weeks if the problems you have are a result of bad data
conversion or some other application error and then getting frustrated when it
takes someone weeks to untangle the mess and testing is stopped on the new
release while you wait for this to happen.
You need to convert 6002 to 6100 using the free
SSA utility. This is a small conversion and from all reports has been painless
and relatively fast (compared to for example the 2.0.09 conversion up to 6002 in
the early days of BPCS version 6).
Then you should install the 6101 release over
6100 following those instructions, and do the DBUPDATE to update the 6100
database to 6101 (as some work files are changed). This is very fast, taking
only a few minutes to complete the DBUPDATE.
You can not use the SSA conversion
utility to convert directly to 6101, because the conversion was written at
the 6100 file level. A notice on OGS Online is posted regarding this
matter.
Thanks
Genyphyr Novak
SSA GT
|
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.