| 
 | 
| This sounds more like a problem in the 
client/server run time software or some error occuring on the server job that is 
affecting your BPCS connection. The message "Connection Reset by Peer" 
is sent by the Microsoft TCP/IP stack when a connection is broken. Success 42000 sounds like a server-side SQL message is 
bubbling up to the client. I would check (or change the TCPIPJOBD to create one 
if it doesn't exist) the joblog on the server to log at the highest levels 
(Message Level Logging of 4, 00, *SECLVL)  to see what is happening to the 
job there on the server. When you want to add a load, the client has to first 'talk' to 
the server and retrieve the data. Likely the retrieval is done with SQL, either 
via ODBC or more likely via a server program (I am not certain as I don't work 
with OLM very often). It is possible that SQL on the AS/400 side is taking too 
long, and the job times out OR it is also entirely possible that the network 
connection really was broken by something such as network congestion etc., and 
the client software 'times out' because it can't talk to the server, and that is 
why you get the 'reset' error and get booted out. Does it say "Workstation 
reset" (as in your note) or "Connection reset" (as in the 
Microsoft error)? What release of BPCS are you using? Thanks Genyphyr Novak SSA 
 | 
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.