Barry_O
Member
Just installed SP22 P1 (which I hoped wou fix runube but didn't) and found another interesting feature.
P1 has the option to download a SAR which will encrypt the password in F98owsec with more strength. I did not apply this SAR. I started the services on Enterprise Server, did my runube test then shut it down.
This morning my (current SP) DV and PY environment would not start properly due to Security Failure of the JDE Account. Strangely the SP22 instance started and stoppped OK.
What happens with SP22_P1 is that it will further encrypt your Password in F98owsec when you log in, without telling you. Thus if you roll back to your current SP, it will not start because it won't authenticate the JDE account or your account either. We had to restore F98owsec from backup to get JDE account going again.
The resolution to this is of course set up different System Datasources and/or adjust the user in JDE.INI and RunOneWorld startup for SP testing.
Remember this if you are going to use the same system Datasource for your SP testing.
Barry
XE on RS6000
P1 has the option to download a SAR which will encrypt the password in F98owsec with more strength. I did not apply this SAR. I started the services on Enterprise Server, did my runube test then shut it down.
This morning my (current SP) DV and PY environment would not start properly due to Security Failure of the JDE Account. Strangely the SP22 instance started and stoppped OK.
What happens with SP22_P1 is that it will further encrypt your Password in F98owsec when you log in, without telling you. Thus if you roll back to your current SP, it will not start because it won't authenticate the JDE account or your account either. We had to restore F98owsec from backup to get JDE account going again.
The resolution to this is of course set up different System Datasources and/or adjust the user in JDE.INI and RunOneWorld startup for SP testing.
Remember this if you are going to use the same system Datasource for your SP testing.
Barry
XE on RS6000