Re: None

[Ata510@xxxxxxx]

The full list of BMRs delivered on the July cumulative are listed in the 
documentation for the July cume, so just order that and read the Net Change 
documentation, which is inside the DOC directory when you install the client 
software. 

Why don't you provide more details about your problem? Is it really Newi - 
can you get into DFS (ALAUNCH)? Did you read the install documentation? 
Because there is more documentation on how to set up the configuration with 
the July cume than was previously ever delivered on that release, so if you 
are having a problem, you should go over the documentation again and re-check 
every single step carefully. The July cume MUST be installed into an existing 
Newi library, because it does not update or replace every object - so if you 
loaded it into an empty library, you are missing objects. 

Also, make sure you are ever reaching the AS/400 to begin with -- if the 
error comes up almost instantly after typing the name and password, you 
probably are not. Check the IP address, and make sure there are no spaces 
before or after the numbers. The only 2 entries in your workstation settings 
which are absolutely required to make 2nd generation (Newi) connections work 
are the IP address and the Service Port to which the daemon is started. All 
else can be blank, unless you are using 1st generation (COM, OLM, CEA). But 
if you do type in any data in the other spaces in Workstation settings, such 
as runtime path etc., it must be correct, or that also will lead to an error 
when the server program trys to start - but that is usually the "Cannot start 
phyisical server" error, because the PC can't find the run-time libraries. If 
you leave those blank, it will use the daemon's library list to find it, so 
that is generally easier.

Make sure from the PC you can 'ping' the AS/400's IP address, and it is 
valid. Make sure you have *LOOPBACK properly defined and started on the 
AS/400 in the CFGTCP menu. Only first generation programs (COM, CEA, OLM) 
have problems with user IDs of over 8 characters. Newi does not. Not sure 
what you mean by 'unique' user profile in BPCS and what that would have to do 
with anything. That doesn't make much sense as a cause of any problem 
relating to connecting to the server. The AS/400 does not allow duplicate 
profiles to begin with. And any user in BPCS MUST be an AS/400 user profile. 
You can have the same profiles allowed to access various BPCS environments 
without any problem, so again rule out that possibility. Try to get it to 
work with the default configuration before doing anything fancy with new 
subsystems, JOBDs and JOBQs. Then, experiment later from a known good point 
if you want to change things.

Problems with Newi configurations are usually something mis-typed or 
mis-configured in the subsystem/jobqe/routing entry/jobd, the workstation 
settings mistyped, or the NWIDCFG or CONFIG files. There are no BMRs for Newi 
(2nd generation) that have to do with Invalid Log on problems - those are 
always mis-configuration or really invalid profiles or expired passwords. 
There is nothing different in the type of user profile required to log into 
BPCS between the April 1998 cume and the July 1999 cume, or in fact since 
6.0.04 was released, so if you are having a problem it must lie elsewhere, 
not in the user profile - especially if that profile can log into a different 
BPCS environment without a problem. Also, there have been no BMRs against 
Newi since the July cume, except one for an enhancement to control the way 
jobs are submitted by the daemon. Meaning, if you have the July cume, you 
already have all the Newi BMRs, and you simply have a configuration problem, 
not a missing BMR. 

Thanks

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---