RE: ASYNC device problems

I'm aware of a problem that IBM is (hopefully) working on that we've
found on V4R2 and V4R3 systems that manifests itself in async comms
jobs. Comms jobs that otherwise ran normally on previous releases can
now just hang. You can tell if this is a similar problem by doing a
DSPJOB on the job and checking the program stack. If you see QICPUT stmt
056E and QIFPUT stmt 027B then this is the same problem.       

> -----Original Message-----
> From: Julie [SMTP:jfrancis@voyager.net]
> Sent: Monday, February 01, 1999 7:13 PM
> To:   Midrange
> Subject:      ASYNC device problems
> 
> Hi Everyone....we have a problem where I work.  (Not my expertise so
> bear with me).  The system is (new) a RISC Model 620 V4R2.  The ASYNC
> devices seem to cause the C pgms, Progress pgms, & AS400 ICF file pgms
> to come to a complete halt.  This happens with the time clock devices,
> the Zebra printers, and the Expedite (Advantis) for EDI.  Has anyone
> experienced this and were able to fix it?  Thanks in advance.  Julie
> 
> +---
> | 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
> +---
+---
| 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
+---