Java Generation

jstooge

VIP Member
We've created two custom environments JPY7333 and JINT7333. Both are WAN
Configured, and when we start our Java generator we can log into both
JPY7333 or JINT7333. When we are in JPY7333, we can then select Direct
Generation and then move on to the generation process, if we are in
JINT7333, when we click on continue, we get an error dialog stating
"Please choose a valid environment" and the list of environments does
include JPY7333, but not JINT7333. We've checked OCM's, the JAS.INI,
machine definitions, everything appears to be set up exactly as it is for
JPY7333.

Two questions....A) If you've seen this before, what did you do to fix
it, or B) Does anyone know where the generator gets it's list of valid
environments...it's not the environment master, because there are entries
for both JPY and JINT.

________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
 
Hi,

I dont actually use this but have seen this happen. Have a look at your gen.bat on the generator machine. It should be located somewhere like b7\tempjar. In there there is a reference to having to set a local jas.ini if you are using direct gen. Firstly you need to have a jas.ini on your generator workstation and it needs to have an entry for valid environments as the one on the web server does.


Good luck,

Maria
 
Maria...

Yep, we have a jas.ini on the generation machine. We can directly
generate a different environment on this machine, so I know the machine
is set up correctly.

Thanks for the input...

Jim
On Thu, 13 Feb 2003 06:28:25 -0800 (PST) MariaG

I dont actually use this but have seen this happen. Have a look


Good luck,

Maria

________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
 
Depending on what db you are using, make sure that you have the proper entries to connect to JINT7333 in either your tnsnames.ora or tnsnames.sql, . For direct generation, make sure you have the proper settings in your jas.ini under the [JDBC URL] section.
 
Thanks for the input.

We're on AS/400 DB2, but since we can connect to the DB for another path
code, I don't think the connection is the problem. We've checked (and
re-checked) the jas.ini, and RL has verified that it appears to be set up
properly. I'm almost thinking that it's maybe something due to a
"non-standard" path code. Our PY and PD generation works just
fine...this is the only custom path code we use currently at this client.
Since the fat client can log into JINT7333 just fine, and since RL can't
tell me where generator looks to validate the environment/path code, I'm
almost ready to believe that it may be hard coded...aw heck...maybe I
should just bite the bullet and move to SP21!! ;)

Thanks again.
On Thu, 13 Feb 2003 07:58:30 -0800 (PST) njcncadmin <[email protected]>
writes:

________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
 
Back
Top