Processing Options are gone

[MagarG]

We are making changes to values to processing options (PO). For
example, we took the Supplier Master Information, P04012, created a new
version and changed some PO. Everything is fine in DV. We then
promoted the project to PY. We built a package, put P04012 and the
versions in it. After deploying the package, when we right click to
prompt for values, the processing option tabs are blank and many of the
labels say EverestEventPoint01.

We are using Jiti with partial packages. After looking a the F98306
table, it looks like the processing options are there in the PY. If I
go to the workstation and delete the potext files, it works fine. Any
thoughts on what is going on here? Are the processing options all
stored in the F98306 table? Are they stored within the versions table
also? Thanks, Grant

AS400 Ent V4R5 SP16.1 OneWorld Xe
NT 6a Deployment



AS400 V4R5 Coexist CO-NT Xe SP16.1
Websphere 3.5.4 on AS400 JAS SP16.1

 

[Zoltan_Gyimesi]

Hi,

Just an idea:
Check through the detailed log of the promotion action in Full Text view. Sometimes objects/versions does not transfered because the time-stamp is newer on the target.
Example:
1.) ZGYZ0001 version created both on DV and PY.
2.) The version modified on DV.
3.) The version modified on PY.
4.) The project which holds the version promoted from DV to PY.
5.) Possibly, the version hadn't been transfered because its timestamp is newer on PY. OMW will let you to promote the project without any error or warning. As far as I know, the previously described method is the only way to verify the transfers after promotions.

Good luck and let us know your results,

Zoltán
P.S.: Check your Logging System for OMW in Object Management Configuration (GH9081/P98230) that is it enough detailed to show when an object didn't transfered because time-stamp.

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)

 

[ijc]

We've had the same problem with partial clients. Including the processing
option template in package resolves the problem








Xe, Oracle 8, NT