RE: SEU Bombing

["Shaw, David" <dshaw@xxxxxxxxxxx>]

Terry,

There have been fixes at various times for both Client Access and SEU to correct
problems with them interacting.  If you haven't done it already, make sure
you're on the current Client Access service pack for whichever version you're
using, and look at SF97430 for any PTF's to 5769PW1 that mention display
problems.  I understand that SEU is a bit odd because it uses User-Defined Data
Stream display support, rather than DDS, UIM, or the display API's.  Don't
assume that because you have a recent cume package that you have all the PTF's
that may be relevant - in past releases, I've seen some rather old PTF's for SEU
that weren't on any cumes.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Terry@VTINFO.COM [mailto:Terry@VTINFO.COM]
> Sent: Wednesday, March 29, 2000 9:29 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: SEU Bombing
> 
> 
> 
> Actually, we're using client access (personal communications).
> 
> Terry Richardson
> Vermont Information Processing, Inc.
> terry@vtinfo.com
> 
> 
>                                                               
>                                                       
>                     bdietz@3x.com                             
>                                                       
>                     Sent by:                   To:     
> MIDRANGE-L@midrange.com                                      
>                     owner-midrange-l@mi        cc:            
>                                                       
>                     drange.com                 Subject:     
> Re: SEU Bombing                                         
>                                                               
>                                                       
>                                                               
>                                                       
>                     03/29/00 08:33 AM                         
>                                                       
>                     Please respond to                         
>                                                       
>                     MIDRANGE-L                                
>                                                       
>                                                               
>                                                       
>                                                               
>                                                       
> 
> 
> 
> 
> You wouldn't happen to be using OEM terminals?  I ran into 
> similar things
> after a RISC upgrade.  It seems that the OEM tubes
> did not like the new WSC's.
> 
> 
> Bryan Dietz
> 
> 
> 
> 
> 
>                     Terry@VTINFO.COM
> 
>                     Sent by:                   To:
> MIDRANGE-L@midrange.com
>                     owner-midrange-l@mi        cc:
> 
>                     drange.com                 Subject:     
> SEU Bombing
> 
> 
> 
>                     03/28/00 04:45 PM
> 
>                     Please respond to
> 
>                     MIDRANGE-L
> 
> 
> 
> 
> 
> 
> 
> Hi all--  I searched the archives, but didn't see any 
> postings about this
> problem I'm having.  I have bombed out of SEU a couple of 
> times today.  I
> go into any source member, exclude a line or multiple lines, 
> and press page
> up, the system dumps and puts you back to PDM.  The QPSRVDMP 
> spool file has
> the line " Space offset X'00000000' is outside current limit 
> for object
> <filename.membername>.
> 
>  We're on V4R3 and are pretty current on PTF's, so it's 
> probably not that.
> Has this been happening to anyone else?
> 
> Thanks--
> 
> Terry Richardson
> Vermont Information Processing, Inc.
> terry@vtinfo.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
> +---
> 
> 
> 
> +---
> | 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
> +---
> 
+---
| 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
+---