RE: Communications Console

[batthish@xxxxxxxxxx]

Chris,

There seems to be a bit of confusion, I was answering a post you place a
couple of weeks ago  (catching up on some older e-mail :-)  ).
Ad for your debugging question,  I'll see what I can find out.
What I meant be the below, is:
If you kill the daemon process (or close the daemon), restart it manually
(rather than let the CODE tools start it automatically) and wait a minute
before trying to use CODE.

Thanks,
Violaine Batthish
CODE Project Lead
batthish@ca.ibm.com          IBMCA(BATTHISH)

WDT/400 page:  http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support




                    Chris Proctor
                    <cproctor@gartspor       To:     "'code400-l@midrange.com'" 
<code400-l@midrange.com>
                    ts.com>                  cc:
                    Sent by:                 Subject:     RE: Communications 
Console
                    code400-l-admin@mi
                    drange.com


                    09/17/2001 02:04
                    PM
                    Please respond to
                    code400-l





This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thanks, for the reply, Violaine.  I'm a little confused though. Are you
saying that this is possible? I've never tried this before, so I have yet
to
create a communications daemon to the production box. So, should I just
create the daemon, and try to start the debugger?

Thanks for any input!

Chris

-----Original Message-----
From: batthish@ca.ibm.com [mailto:batthish@ca.ibm.com]
Sent: Monday, September 17, 2001 12:09 PM
To: code400-l@midrange.com
Subject: Re: Communications Console


Hi Chris,

I have discovered a timing issue with the Communications Daemon.  If you
close the daemon, CODE will attempt to restart it as soon as its needed
again.  At this point it seems that a communications request is allowed to
"go through" before the daemon can complete its initialization (thus the
library list information is not yet available to the comm layer).
I have already placed a fix for this in the next V5R1M0 service pack (SP3).
The best way to avoid the problem is to manually start the daemon, and then
wait a minute before making a request.

Thanks,
Violaine Batthish
CODE Project Lead
batthish@ca.ibm.com          IBMCA(BATTHISH)

WDT/400 page:  http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support




                    Chris Proctor
                    <cproctor@gartspor       To:     "CODE400-L (E-mail)"
<CODE400-L@midrange.com>
                    ts.com>                  cc:
                    Sent by:                 Subject:     Communications
Console
                    code400-l-admin@mi
                    drange.com


                    09/04/2001 05:10
                    PM
                    Please respond to
                    code400-l





This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi all,

I had a question regarding setting up the libl for a server via the
communications console. Earlier today I posted a question, because it
appeared that files were not being found during a verify because my libl
did
not reflect what I had set up for the server. It appears that it is ONLY
using the initial libl associated with my user profile. If I look at the
communications console for that server it has the following values:

Code Server:         SERVER4
Current Library: *usrprf
User Libraries:           xmldev
                     mm4r4lib
                     mm4r4ctl
                     cfilelib

None of the user libraries are appearing in the library list when I open a
project associated with that server and attempt to verify the code. Can
anyone offer any ideas as to what the problem might be?

Thanks in advance

Chris
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.




_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.