RE: Is there a answer for this?

Tom,
Aside from Don's motivational speech <big grin> look at your programs;
especially the one giving the error.  Your I/O should trap errors.  In RPG,
you should be putting an indicator in the LO columns or using the (E) opcode
extender.  In CL, use MONMSG.  Once you've trapped the error, don't ignore
it - do something with it, even if it's DUMP and terminate.  The post-mortem
is valuable in and of itself.

Buck 

> -----Original Message-----
> From: Don 
> Sent: Monday, February 26, 2001 6:49 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Is there a answer for this?
> 
> Yeah, tell the sales idiod that if he/she can't learn to signoff properly
> that their replacement will be given a shot at trying...!
> 
> On Mon, 26 Feb 2001 tkennedy@harcourt.com wrote:
> 
> > Someone in the Telesales department shuts down there AS/400 session
> without
> > properly signing off the system, when this occurs that session
> > will consume more than 65% of the CPU unless the job is manually ended.
> > 
> > Does anyone have any ideas or suggestions to combat this problem? Our
> > system is at V4R4...
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---