kastanek
Well Known Member
Hello List,
I have just installed a new JAS instance on an existing server and it's
doing some weird and wacky things. Here's some background:
Xe B7333, SP22_L1, Update 7 - Co-existence on an AS/400 ES, W2K JAS Server,
WAS 4.0.5
The mission: Upgrade and migrate the users from Coexistence to EO 8.9 on
new AS/400
Issues: Old AS/400 is at V5R1, Can't upgrade to V5R3 without going to
SP23, Can't go to SP23 due to testing concerns so I'm pretty much stuck at
where I'm at for now. Also we aren't getting the new AS/400 until Nov.
The Plan:
- Create a migration environment (MG7333) on old AS/400 by copying the
coexistent PD7333
- Remove Co-existence from MG7333
- Test removal of coexistence
That's all I need to say about this plan since that's as far as we've
gotten. Many of the new machines for this project are Windows XP and
therefore not reliable with OneWorld Xe and we are waiting for Win2000 to
be installed on them before we can reliably install FAT clients.
The only other option to test is Thin client and without Citrix that leaves
us HTML clients. We are using the existing JAS server currently serving
the PY7333 environment and creating a new JAS instance on this machine
using port 81. I tried copying the existing environment (JAS Directory,
WAS config, IIS config, etc.) but this didn't work so I went back to square
one and installed the new JAS instance using a download of SP22J_L1 (since
the CD's we had were at SP18.1). I installed the JAS instance using this
download and was able to get my signon display. I can signon to JAS
JMG7333 and navigate the menus and enter the applications (P01012, P0911,
etc) but when I go into the data I get all kinds of weird messages. The
most pervasive are "Invalid Parameters" and "Invalid Values". When I go
into the UDC tables to validate the values in the database the values are
there. When I go to EDIT the values I get a message that tells me that I
can't have Characters in a Numeric Field even though the field is defined
for Characters (according to the DD).
It seems like the system is trying to validate the data but is not able to
get the correct data type info from the DD or the UDC tables. I have tried
repeatedly to build full packages and do full eGen's. I get no errors in
the builds, eGen's or deploys and the Fat client (I do have a couple of W2K
machines to work with) works just fine. It's just the JAS that is not
behaving.
Side note: I don't know if this has anything to do with my issue but when
I sign into the MG7333 Fat client I get the old "F90701 and F90704 data
sources are set to translate. Set to Do Not Translate and try again." as
well as the "F90703 and F90704 could not be accessed" in the JDE.LOG file.
I have created the four tables (F90701, F90702, F90703 and F90704) in the
Business Data data source and set the OCM's to point to the Business Data -
DNT data source but still I get this error. I do NOT get it in any other
environment but all the OCM's are set the same way. I don't know why the
system is picking on MG7333. It's a complete environment, created using
the correct documentation and I can apply ESU's and fixes to it. The
environment creation workbench ran fine when I created the environment, the
system tables seemed to be updated correctly, the system knows about the
environment, OL is fine and has all the Objects for the environment in it.
Also packages build and deploy correctly. eGen's give me no serious errors.
Just a few "Unable to read specs for table..." but the handful of tables I
get this for don't exist so I've ignored those errors. I always get
"Generation Successful" messages whether I do a FULL eGen in parallel,
sequential or partial eGen's.
I've been at this a week now and think I'm getting too close to see the
issue. Forest for the trees kinda thing. Does anyone have any ideas on
where to look? PSFT has stopped responding to me. I think they're stumped
as well.
Thanks in advance for your help.
Regards,
Gerald.
I have just installed a new JAS instance on an existing server and it's
doing some weird and wacky things. Here's some background:
Xe B7333, SP22_L1, Update 7 - Co-existence on an AS/400 ES, W2K JAS Server,
WAS 4.0.5
The mission: Upgrade and migrate the users from Coexistence to EO 8.9 on
new AS/400
Issues: Old AS/400 is at V5R1, Can't upgrade to V5R3 without going to
SP23, Can't go to SP23 due to testing concerns so I'm pretty much stuck at
where I'm at for now. Also we aren't getting the new AS/400 until Nov.
The Plan:
- Create a migration environment (MG7333) on old AS/400 by copying the
coexistent PD7333
- Remove Co-existence from MG7333
- Test removal of coexistence
That's all I need to say about this plan since that's as far as we've
gotten. Many of the new machines for this project are Windows XP and
therefore not reliable with OneWorld Xe and we are waiting for Win2000 to
be installed on them before we can reliably install FAT clients.
The only other option to test is Thin client and without Citrix that leaves
us HTML clients. We are using the existing JAS server currently serving
the PY7333 environment and creating a new JAS instance on this machine
using port 81. I tried copying the existing environment (JAS Directory,
WAS config, IIS config, etc.) but this didn't work so I went back to square
one and installed the new JAS instance using a download of SP22J_L1 (since
the CD's we had were at SP18.1). I installed the JAS instance using this
download and was able to get my signon display. I can signon to JAS
JMG7333 and navigate the menus and enter the applications (P01012, P0911,
etc) but when I go into the data I get all kinds of weird messages. The
most pervasive are "Invalid Parameters" and "Invalid Values". When I go
into the UDC tables to validate the values in the database the values are
there. When I go to EDIT the values I get a message that tells me that I
can't have Characters in a Numeric Field even though the field is defined
for Characters (according to the DD).
It seems like the system is trying to validate the data but is not able to
get the correct data type info from the DD or the UDC tables. I have tried
repeatedly to build full packages and do full eGen's. I get no errors in
the builds, eGen's or deploys and the Fat client (I do have a couple of W2K
machines to work with) works just fine. It's just the JAS that is not
behaving.
Side note: I don't know if this has anything to do with my issue but when
I sign into the MG7333 Fat client I get the old "F90701 and F90704 data
sources are set to translate. Set to Do Not Translate and try again." as
well as the "F90703 and F90704 could not be accessed" in the JDE.LOG file.
I have created the four tables (F90701, F90702, F90703 and F90704) in the
Business Data data source and set the OCM's to point to the Business Data -
DNT data source but still I get this error. I do NOT get it in any other
environment but all the OCM's are set the same way. I don't know why the
system is picking on MG7333. It's a complete environment, created using
the correct documentation and I can apply ESU's and fixes to it. The
environment creation workbench ran fine when I created the environment, the
system tables seemed to be updated correctly, the system knows about the
environment, OL is fine and has all the Objects for the environment in it.
Also packages build and deploy correctly. eGen's give me no serious errors.
Just a few "Unable to read specs for table..." but the handful of tables I
get this for don't exist so I've ignored those errors. I always get
"Generation Successful" messages whether I do a FULL eGen in parallel,
sequential or partial eGen's.
I've been at this a week now and think I'm getting too close to see the
issue. Forest for the trees kinda thing. Does anyone have any ideas on
where to look? PSFT has stopped responding to me. I think they're stumped
as well.
Thanks in advance for your help.
Regards,
Gerald.
