• Subject: RE: Where does SEU store Work In Progress
  • From: Tim McCarthy <timm@xxxxxxxxxxxx>
  • Date: Fri, 14 Apr 2000 15:24:18 -0400

Dave, you're on your own - never done this before. However I do know
that SEU creates a number of objects in QTEMP. For each instance of SEU
you start it creates a permanent misc space (19 EE) with a name
something like QSU_WSUCOM____xxxxxxx. This seems to act as some sort of
an index and contains the line numbers currently in the window. You also
get a temporary space called QSEU2_CMDLxx. Then there are a number of
other MSCSP spaces created on certain events. How these spaces are laid
out and what they contain I have no idea. You can access them in MI but
may run into level 40 issues. Use DMPSYSOBJ with a hex offset of 40 to
see everything in your QTEMP.        


TrailBlazer Systems, Inc.
http://www.as400ftp.com
AS/400 Communications & E-Commerce Solutions

Errors have been made. Others will be blamed.


> -----Original Message-----
> From: David Keck [SMTP:dkeck@idt.net]
> Sent: Friday, April 14, 2000 10:40 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Where does SEU store Work In Progress
> 
> Tim,  It sounds to me that you've done this, and I'm chomping at the
> bit to
> get there.  Is there anything further you could share on this ?  I get
> the
> impression it is accessible only via MI, and that the "space" you
> refer to
> is not a *USRSPC but some other object type.  Anything further you
> could
> offer would be greatly appreciated.  Thanks - Dave K
> 
> ----- Original Message -----
> From: Tim McCarthy <timm@as400ftp.com>
> To: <MIDRANGE-L@midrange.com>
> Sent: Thursday, April 13, 2000 3:38 PM
> Subject: RE: Where does SEU store Work In Progress
> 
> 
> > Well...it's contained in a space called QSEU2.BRWS01 in QTEMP. You
> don't
> > have direct access to it unless you dive under the covers.
> >
> > TrailBlazer Systems, Inc.
> > http://www.as400ftp.com
> > AS/400 Communications & E-Commerce Solutions
> >
> > Errors have been made. Others will be blamed.
> >
> >
> > > -----Original Message-----
> > > From: David Keck [SMTP:dkeck@idt.net]
> > > Sent: Thursday, April 13, 2000 4:53 PM
> > > To: MIDRANGE-L@midrange.com
> > > Subject: Re: Where does SEU store Work In Progress
> > >
> > > I am trying to gain access to the entire text of the source
> currently
> > > under development via a command key. To access it using the method
> > > you describe would necessitate placing a user defined option on
> the
> > > first and last lines of source, which will not meet my needs. That
> > > being said, we know the full source is stored somewhere ... but
> where
> > > oh where ... ? -Dave
> > >
> > >
> > > ----- Original Message -----
> > >
> > > From: Leland, David <mailto:dleland@Harter.com>
> > > To: 'MIDRANGE-L@midrange.com' <mailto:'MIDRANGE-L@midrange.com'>
> > >
> > > Sent: Thursday, April 13, 2000 10:02 AM
> > > Subject: RE: Where does SEU store Work In Progress
> > >
> > >
> > > It's accessible thru an SEU Exit Point Program. The API
> > > reference manuals have additional info.
> > >
> > > Dave
> > >
> > > -----Original Message-----
> > > From: David Keck [ <mailto:dkeck@idt.net>]
> > > Sent: Thursday, April 13, 2000 1:35 PM
> > > To: MIDRANGE-L@midrange.com <mailto:MIDRANGE-L@midrange.com>
> > > Subject: Where does SEU store Work In Progress
> > >
> > >
> > > Where does SEU store source code before the programmer saves it
> > > to a source member ? Is the entire body of source (as defined to a
> > > surrent SEU session) programmatically accessible ? -Dave
> > >
> > +---
> > | 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.