× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks.  That seems to work. 

Maybe I'm not remembering right (haven't used it a whole lot), but I thought it 
used to end automatically when I was done debugging. 

Greg

|-----Original Message-----
|From: code400-l-bounces@xxxxxxxxxxxx [mailto:code400-l-
|bounces@xxxxxxxxxxxx] On Behalf Of Violaine Batthish
|Sent: Wednesday, January 18, 2006 12:51 PM
|To: CODE/400 Discussion & Support
|Subject: Re: Host session not ending
|
|Hi Greg,
|
|The proper way to terminate a STRCODE session is to either
|
|1) From DOS, issue the command:
|CODESRV SHUTDOWN server_name
|
|2) From the Communication Console Properties, select the server, and press
|the shutdown button.
|
|There are also options to shutdown all servers, but this will also kill
|your connection that you used to download any members, and you will loose
|the locks that you have in the process.
|
|thanks,
|
|Violaine Batthish
|WebSphere Development Studio Client, IBM Toronto Lab
|
|
|You know you've achieved perfection in design, not when you have nothing
|more to add, but when you have nothing more to take away. - Antoine de
|Saint-Exupéry
|
|
|
|code400-l-bounces@xxxxxxxxxxxx wrote on 01/18/2006 10:06:28 AM:
|
|> I'm using the IBM distributed debugger from Code.
|>
|>
|>
|> If I recall correctly, in the past I could run the STRCODE command from
|> an interactive session, which results in a series of three beeps of
|> ascending pitch and a screen locked up and waiting for the PC side to do
|> something.
|>
|>
|>
|> Then I go do my debugging on the PC side, and my interactive application
|> shows up in the emulation session, I do my stuff there.
|>
|>
|>
|> When my program ends or I halt it from the PC side, I thought the Host
|> session was supposed to end and return my emulation session to a command
|> line, with a series of three beeps of descending pitch.
|>
|>
|>
|> This isn't happening lately.  Everything works OK until I am done
|> debugging, and I get the PC message that the debug session has
|> completed, but the emulation session is still locked up, so I have to
|> unceremoniously kill it.  Then I can't debug again, because the default
|> host is still active.
|>
|>
|>
|> I did, however, accidentally discover a way to end it, which is to
|> attempt to create a new print file in Code Designer, upon which time it
|> gives me an "unable to send data to host server" message, and then
|> finally gives me the three beeps in descending pitch, at which time I
|> can then run STRCODE again and start the whole ball rolling again.
|>
|>
|>
|> I suppose I could leave an emulation session dedicated to debugging all
|> day and just never kill it, but I thought it was supposed to close at
|> the end of the debug session, returning my emulation session to me.  Is
|> there another way to end the host session normally ?
|>
|>
|>
|> Thanks
|>
|>
|>
|> Greg Fleming
|>
|> Programmer/Analyst
|>
|> Everglades Direct, Inc.
|>
|>
|>
|
|
|_______________________________________________
|This is the CODE/400 Discussion & Support (CODE400-L) mailing list
|To post a message email: CODE400-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/code400-l
|or email: CODE400-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/code400-l.
|
|NOTE: WDSc for iSeries discussion has it's own mailing list.
|Information can be found at http://lists.midrange.com/cgi-
|bin/listinfo/wdsci-l



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.