All the AS/400 SQL you'll need for a ENT server rename

Note that this is AS/400 SQL syntax.

update svm7333/f98611 set omsrvr = 'NEWSERVER' where omsrvr =
'OLDSERVER'

31 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omll = 'NEWSERVER' where omll =
'OLDSERVER'

31 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omdatp = 'NEWSERVER - B7333 Server Map'
where omdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F98611 in SVM7333.

update svm7333/f98611 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

1 rows updated in F98611 in SVM7333.
update svm7333/f986101 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

6 rows updated in F986101 in SVM7333.

SYS7333 F98611
update sys7333/f98611 set omdatp = 'NEWSERVER - Logic'
where omdatp = 'OLDSERVER - Logic'

1 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatb = 'NEWSERVER - B7333 Server Map '
where omdatb = 'OLDSERVER - B7333 Server Map '

3 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omsrvr = 'NEWSERVER' where omsrvr =
'OLDSERVER'

43 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omll = 'NEWSERVER' where omll =
'OLDSERVER'

44 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatp = 'NEWSERVER - B7333 Server Map'
where omdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F98611 in SYS7333.

update sys7333/f98611 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

1 rows updated in F98611 in SYS7333.
update sys7333/f986101 set omdatp = 'NEWSERVER'
where omdatp = 'OLDSERVER'

24 rows updated in F986101 in SYS7333.

update sys7333/f986101 set omdatp = 'NEWSERVER - Logic'
where omdatp = 'OLDSERVER - Logic'

11 rows updated in F986101 in SYS7333.
update sys7333/f9650 set mmmkey = 'NEWSERVER' where mmmkey = 'OLDSERVER'

1 rows updated in F9650 in SYS7333.

update sys7333/f9650 set mmdatp = 'NEWSERVER - B7333 Server Map'
where mmdatp = 'OLDSERVER - B7333 Server Map'

1 rows updated in F9650 in SYS7333.

update sys7333/f9651 set mdmkey = 'NEWSERVER' where mdmkey =
'OLDSERVER'

5 rows updated in F9651 in SYS7333.

Make sure EDRSQL TCP service is running "STRTCPSVR SERVER(*EDRSQL)". Make sure that it starts automatically (use iSeries nav for this)

AS/400 issues

I like AS/400 issues... Why, because there are always so many logs... I really love job logs... As far as an OS is concerned, does logging get any better? Event viewer is good, but not great. stdin and stdout is okay, but job logs... They boil my potato!

I was configuring a DR AS/400 today and was getting a really strange error "Cannot resolve to object QBFCPRCED". When we looked for that object on the DR machine, it did not exist... YET, when I looked at the object on the prod machine it did... what does that tell you? Not a good start to a DR machine it tells me. How do people expect this thing to work without the correct foundation... Anyways... Despite this, there were a bunch of PTF's that were installed but not applied. We IPL'd the 400 (30 mins later, brand new 520!) to install the PTFs - Bob's your uncle and fanny is your aunt (I said aunt) She started working!

Remember if you want to build up an ent server (or change the name), you gotta do the following:
JDE.INI on the server - old to new
update SY and SVM F98611 and F986101
Update F9650 and F9651
Update client ini files

All of the fat client ODBC's needed to be changed, export the ODBC part of the reg and do a search and replace - much easier.

Remember that the web servers (despite maybe having a fat client), do not use ODBC - all JDBC. These are loaded up on the fly from F98611 - so you don't gotta worry about them.

WebDev client for OAS

Remember that if the web dev is not working, you can go to the deployment server under OneWorld Client install\WebDevFeature and run the installer from there. You'll know if it's working because it'll finish (ironic!). If the installer does not finish, reinstall your fatty and then run that again.

JDE and LDAP

It's not the best implementation of LDAP authentication I've come across... But, lets have a more honest look at things, is it the worst... Hmmm, it might be.

What about some of the limitations:

1 domain only
username < 10 chars
password < 10 chars WTF!!!! This is a crock!

okay, and now the best stuff...

So I work as a site with a large AD implementation, 5000 users... something like that... Not that many JDe users... Each time a user tries to login to JDE, the security kernel is saying "Cannot find username XXXX in LDAP"... But, any LDAP browser or MAD tool can. I don't know how it's running it's queries, or if it's binding to the correct member - but it's bad!

If you can't get into the em console, try this

D:\product\10.1.3.1\OracleAS_1\opmn\bin>opmnctl startproc process-type=home application=ascontrol
opmnctl: starting opmn managed processes...

then http to:
http://machinename.domain.etc/em/console/ias/cluster/topology

opmnctl usage

usage: opmnctl [verbose] [] []

verbose: print detailed execution message if available

Permitted // combinations are:

scope command options
------- --------- ---------
start - Start opmn
startall - Start opmn & all managed processes
stopall - Stop opmn & all managed processes
shutdown - Shutdown opmn & all managed processes
[] startproc [= ..] - Start opmn managed processes
[] restartproc [= ..] - Restart opmn managed processes
[] stopproc [= ..] - Stop opmn managed processes
[] reload - Trigger opmn to reread opmn.xml
[] status [] - Get managed process status
[] dmsdump [=&..] - Get DMS stats
[] set [= ..] - Set opmn log parameters
[] query [=] - Query opmn log parameters
ping [] - Ping local opmn
validate [] - Validate the given xml file
config [] - Modify the opmn xml file
help - Print brief usage description
usage [] - Print detailed usage description

Clustering in OAS

Make sure that you name your OAS instances (when doing the initial install through the oracle installer 0 YUK!!) differently. They need to have different names for the cluster to work. Thansk Rhys.