RE: Completion messages going to wrong PC

Did you change the user profiles each had a unique current library (that is
a user library) in them?  That is all we did and the problem cleared itself
up.  We don't use STRCODE, we just use the communication daemon on the pc
side.

Scott

> -----Original Message-----
> From: Genaro J. Castellanos Castillo [mailto:gcastell@ipasacv.com]
> Sent: Tuesday, January 23, 2001 8:57 PM
> To: CODE400-L@midrange.com
> Subject: Re: Completion messages going to wrong PC
> 
> 
> Hi Scott,
> 
> I got the same trouble and I tried your advice but it didn't work.
> 
> I tried using the complete STRCODE parameters in order to not use the
> default *usrspc values but the command look for it and uses it.
> 
> I tried renaming the strcode *usrspc and defining all the 
> strcode parameters
> but the command tries to find it and gives me an error message.
> 
> Any additional help?
> 
> ----- Original Message -----
> From: "Scott Mildenberger" <Smildenber@Washcorp.com>
> To: <CODE400-L@midrange.com>
> Sent: Monday, December 18, 2000 4:11 PM
> Subject: RE: Completion messages going to wrong PC
> 
> 
> > Jon,
> >
> > We have just had this problem and have stumbled on to an 
> answer that may
> > work for you.  We have the V4R5 version but it may be the 
> same.  Each user
> > must have a current library in their user profile and it 
> must be a user
> > library (not a system library such as QTEMP or QSYS).  We 
> also believe
> that
> > no two Code/400 users can have the same current library.  There is a
> *USRSPC
> > by the name of STRCODE that is used for the feedback to the 
> workstation
> and
> > it gets created in the user's current library.  We had two 
> users whose
> user
> > profile had *CRTDFT as the current library and their 
> messages were getting
> > mixed up because they were both using QGPL as the library for this
> *USRSPC.
> >
> > Hope this solves your problem too!
> >
> > Scott Mildenberger
> >
> >
> > > -----Original Message-----
> > > From: Jon.Paris@hal.it [mailto:Jon.Paris@hal.it]
> > > Sent: Thursday, December 14, 2000 9:13 AM
> > > To: code400-l@midrange.com
> > > Cc: batthish@ca.ibm.com
> > > Subject: Completion messages going to wrong PC
> > >
> > >
> > > I thought I knew most of the possible answers to this 
> problem but I'm
> > > stumped.
> > >
> > > We're teaching on a customer site and Code/400 is busily
> > > trying to convince
> > > them that it is a waste of time.  We're using the V3R3M3 
> try-and-buy
> > > version (the latest release refuses to load on most of the
> > > machines here so
> > > this was our backup plan.)
> > >
> > > They were raving about when we demo'd it and couldn't wait to
> > > try - now
> > > only three in a room of twelve still have the patience to 
> keep trying.
> > > Why? mostly because the *$%! messages keep popping up on 
> the wrong PC!
> > >
> > > We started off using the autostart servers but that causes
> > > real problems
> > > because of the way the library list is defined here (everyone
> > > has the same
> > > CURLIB by default) so we switched to STRCODE servers
> > > (STRCODTCP in fact).
> > > That worked for some of the folks for a while but today there
> > > are three PCs
> > > that it doesn't matter what we do they all send messages to
> > > the same PC.
> > > This in spite of the fact that the job logs clearly show that
> > > the correct
> > > IP address is being used and the fact that we changed
> > > STRCODTCP so that
> > > they each have a unique server name.  The logs clearly show
> > > this server
> > > being used on the submit for the compile but still the
> > > messages go to the
> > > wrong PC.
> > >
> > > We've killed the code servers, we've killed all the 
> EVFEVENT files (is
> > > there another file involved? - there's something at the back
> > > of my mind
> > > that says there is) we killed the daemons and started 
> everything from
> > > scratch and still the messages appear.
> > >
> > > Can anyone give us a clue here - what am I missing?
> > >
> > > +---
> > > | This is the CODE/400 Mailing List!
> > > | To submit a new message, send your mail to 
> CODE400-L@midrange.com.
> > > | To subscribe to this list send email to 
> CODE400-L-SUB@midrange.com.
> > > | To unsubscribe from this list send email to
> > > CODE400-L-UNSUB@midrange.com.
> > > | Questions should be directed to the list owner/operator:
> > > larry@paque.net
> > > +---
> > >
> > +---
> > | This is the CODE/400 Mailing List!
> > | To submit a new message, send your mail to CODE400-L@midrange.com.
> > | To subscribe to this list send email to 
> CODE400-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> CODE400-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator: 
> larry@paque.net
> > +---
> 
> +---
> | This is the CODE/400 Mailing List!
> | To submit a new message, send your mail to CODE400-L@midrange.com.
> | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> CODE400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> larry@paque.net
> +---
> 
+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---