Ray, We applied JE8225. Thanks for checking.
Charles, We built a full dev package & copied the lib file to libv32. Ran diagnos to test vertex & it seemed to work fine. We are using the isam version of the vertex db. How do you go about testing vertex? Do you use multi-foundation?
Maybe we are taking the wrong approach on testing vertex. The approach we have previously used with success and are currently trying to use to test vertex is as follows:
1) Installed vertex 2.6.0 into a new directory with Dec data update
2) Copied new vertex library files (*.sl) to $SYSTEM/libv32
3) Made vertex 2.6.0 the active version for all environments by changing the unix enviornment variable SHLIB_PATH to point to the new version. Note: During this time users know that we are in a testing mode and can only process checks in DEV.
4) Logged into Dev environment and change Quantum Database Connection data source to point to new version
5) Installed Vertex ESU
6) Did only pre-package build ESU special instructions
7) Built full Dev client & server package
8) Deployed full Dev package to server
9) Complete ESU special instructions
10) Users test in DEV
11) Once testing is complete and users give the okay on the new version then we log into Prod & PY and change Quantum Database Connection data source to point to new version also.
12) Promote Vertex ESU to PY & Prod
We were not able to do step 9 and greater because we started having problems with job going to 'S' status in ube queues. Figured out it must be something to do with vertex since that was the only change. So copied old vertex 2.5.4 library file to $SYSTEM/libv32, set SHLIB_PATH to vertex 2.5.4 directory, changed Quantum db connection data source to point to vertex 2.5.4.
Can anyone see any flaws in this approach?
Maria