RE: STRSQl - Recovery of Non Saved Session, can it be done?

It's automatically saved. That's why your STRSQL comes back up with
prior statements.

You can search the archives for the object(s?) that holds the info
which you can dump out. But if STRSQL on one session isn't showning
you the statement you want, you might consider trying to start another
5250 session and another STRSQL session and see brings up the history
you're looking for.

Basically, the session is saved by user profile. So for instance,
you can STRSQL on one 5250 session run some statements, quit then
STRSQL on a different 5250 session and you should see the statements
you did in the other session. A wrench is thrown into the works if
you have STRSQL running on two or more sessions at once. Then the
device name comes into play. Hopefully, you're specifying device
names instead of using system generated QPADEVxxxx names. If you are
specifying device names then you should be able to find your
statements by doing STRSQL on the sessions in the same order as it was
done originally.

Otherwise dumping the object that holds the STRSQL session statements
may be your best bet.

HTH,
Charles

On Fri, Aug 20, 2010 at 1:34 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

If a person fails to 1. Save and exit session and does a 2=Exit

without

saving session, Is there anyway to recovery the previous session?

Thanks
--
Kirk
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.