SP22_Y1

Implementing SP22_Y1 from SP22_B1, multi-foundation on a sandpit box.

Followed all the instructions:
1. Created copy of F98OWSEC.
2. Mapped to server map on sandpit box.
3. Applied JD21799 to sandpit environment.
4. Pkg build and deployed.
5. Changed OCM for F98OWSEC mapping.
6. Changed JDE.INI file for [SECURITY] stanza and new port (M/F).
7. FAT client test working successfully.
8. Changed user passwords without failure.
9. No issues here...

Followed all the SP22J_Y1 instructions:
1. At generation get an error indicating SEC-06: No F0092 OCM. Checked KG and this indicates an issue with database drivers. This has not changed and the jas.ini has been verified.

2. Attempt sign on (with old serialised objects) and get:
2004-11-11 12:25:27.653 [Servlet.Engine.Transports:10] JAS : trying prime user (F986101, F98611)
java.sql.SQLException: [SQL0204] F986101 in SYS7333 type *FILE not found.

OW Developer
LPAR V5R2, Sandpit, Xe U7, SP22_B1 (attempting --> SP22_Y1)

Right...

Answer found...

DO NOT RUN LPAR systems!

No really...don't.

If you do...make sure your JAS.INI always points System to the correct machine!

Sorry to hear of your issues, but saying "don't run LPAR's" is not really the core of the issue. Many are running LPAR's with great success, in fact I know of clients running multiple iSeries each with multiple LPAR's using MIMIX (unsupported) for DR/HA.

While LPAR's add a layer of complexity, they are a useful tool to segregate E1 instances for many...not all...but many.

Regards,

Apologies all, if not immediately visible, but my previous comment was tongue in cheek...hence the blushing muppet.

We are are at H1 and will be applying Y1 in two weeks. We found through our
research that we need to apply JE7134 not JD 21799. You may want to give this
a shot.
Barb Kramarski