Menu
▾
▴
#67 Jitterbug Migration Creating an AS400() connection
Date: Wed, 10 May 2000 09:51:27 -0500
From: joepluta@plutabrothers.com
Body:
When creating an AS400() object, what parameters are necessary in different
situations? For example, I know that running from a PC requires a system, user
ID and password, or else the signon window pops up. But what about the
following situations:
1. Logging on from a servlet.
I'd think you could connect using just AS400() and you'd be connected to the
AS/400 that's running the servlet, but that doesn't work. Is there a
"localhost"/"*current" userid combination that will work from a servlet? And if
so, what user ID do we get?
2. Logging on from the AS/400.
Here the empty constructor works fine, but some folks in the field are saying it
doesn't work with security level 40 (or at least that seems to be the case). Is
that true? (I've yet to go to level 40, so I can't answer this myself.)
The errors reported when we don't specify a user ID and password from the AS/400
at level 40 are "User ID not set" or "Password not set".
***********************
Reply:
***********************
From: Chris Smith <jt400-bugs@oss.software.ibm.com>
Date: Thu May 11 08:47:01 2000
Please see the Notes section that is part of this bug for answers
This is working as designed. The AS400 object always needs a system name,
userid
and password. Any combination of the three can be supplied by your Java
program. If all three are not supplied by the program, the following happens:
1) If on a non-AS/400 client, the AS400 object prompts for the missing values.
If prompting is turned off, an exception is thrown.
2) If on an AS/400:
a) If system name is not specified, the current system is used
b) If userid is not specified, the current job's userid is used
c) If password is not used, the current job's password is used
By default, prompting is turned off when on the AS/400 so if any of these fail
an exception is thrown.
The most common problem area is (c) under #2 -- the program does not specify a
password so the AS400 object gets it from the current job. At times, the
current job does not have a password (servlets often run under the QTMHHTTP
profile with no password). Connecting to a host server with no password will
fail.
Using "localhost" or "*CURRENT" or "<AS400hostname>" on your AS400 object
when
running on the AS/400 achieves the same effect as just using the empty AS400()
constructor.
As for the level 40 question, I don't know of any reason why the Toolbox
wouldn't work at 40. But I will investigate it further.
05/11/2000:
More on the level 40 question. I ran our testcases to some of the systems out
here in the the lab that I IPL-ed to level 40 and saw no differences between
level 40 and level 50 (we normally test at level 50). The default AS400()
constructor works fine. If someone has more information on this phenomenon,
please send a note to csmith4@us.ibm.com or post to the JTOpen forum at
http://www.as400service.ibm.com