RE: Prompting of CL commands -- CODE400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Prompting of CL commands
From: Jim Essinger <esinger@xxxxxxxx>
Date: Wed, 26 Mar 2003 19:21:27 -0700
List-archive: <http://archive.midrange.com/code400-l>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

I had to do this today, so it is fresh in my mind. One of my programmers had a lockup while prompting CL. We went to the Comm Deamon and ended all servers, then killed the session with the stuck 5250 screen. Then on the 400 went to wrkactjob and found the server interactive job and killed it. Code then responded and gave us an error that the 5250 did not respond. We then were able to save the code (after starting another server session in a new 5250 window), and reboot (only way to get back that lost session) but at least we did not lose source.

HTH

At 04:50 PM 3/26/2003 -0600, you wrote:
<snip>

Canceling Code/400 was the only way to release both programs.

Jim Essinger
Senior Programmer/Analyst
Student Loan Fund of Idaho
208-452-4058

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