***************************************************************************
**                 COPYRIGHT (c) 2004 BY TRI-8, INCORPORATED.            ** 
**                    A L L  R I G H T S  R E S E R V E D.               **
***************************************************************************

OneStep Charge Upgrade Process Instructions
-------------------------------------------

Generally speaking, the OneStep Charge upgrade process is a
straightforward matter of updating source code.

1) Make a backup copy of your current OneStep Charge distribution.  This
should be a simple directory named OneStepCharge (referred to as $OSC in
documentation).  Move your current OneStepCharge directory to, say,
OneStepCharge.bak.  Untar/unzip the new OneStepCharge distribution.

2) You must perform a manual analysis of the differences between the new
tri8osc/oscapi and your current tri8osc/oscapi.  Differences between
releases can happen, and there may also be custom modifications that have
been made by your development team to your tri8osc/oscapi.  Therefore
utilities such as the Unix "diff" command must be used to compare and then
merge the changes.  Typically, changes are minimal.  Any fields that you
have added to the trExec temp-table should be re-added in the new release,
and any other custom logic that you have placed in tri8osc/oscapi must
also be copied into your new tri8osc/oscapi.

3) Upgrades within minor versions (x.y to x.z) do not require a settlement
before the upgrade, but it is always recommended that you settle your
current batch to be on the safe side.  Upgrades between major versions
(x.y to z.a) should ALWAYS be preceded by a batch settlement.  In major
version upgrades, it is also recommended that you synchronize your stored
(permanent) versions of transactions first, as well.  In major version
upgrades, your old transactions are not guaranteed to be available after
the upgrade, and so it is, as always, recommended that you keep your
database in sync rather than relying on historical information pulled from
the OneStep Charge Engine, such as via the QTRANS command.

4) Once you have merged tri8osc/oscapi, you may copy the tri8osc directory
into your propath (remove the old one first, making a backup if you
desire), recompile any and all programs that use OneStep Charge, and
compile tri8osc/oscengin.p.  Please note that, in cases where NO changes
to tri8osc/oscapi are present, recompiling is not necessary but is still
recommended.



PLEASE SEE $OSC/doc/RELEASE_NOTES.txt for further information and any
special caveats related to this release.