RE: Interactive SQL - Command History

["Norbut, Jim" <Jim.Norbut@xxxxxxxxxxxxxxx>]

Gotcha....well I always wondered where that was kept anyway.
Now I know.....not that I will ever use it for anything.

Thanks for the info.


Jim Norbut
Systems Administrator
Grubb & Ellis Company
Phone   (847) 753-7620
Fax     (847) 753-9854

 -----Original Message-----
From:   Douglas Handy [mailto:dhandy1@bellsouth.net]
Sent:   Tuesday, November 06, 2001 11:40 AM
To:     midrange-l@midrange.com
Subject:        Re: Interactive SQL - Command History

Jim,

>Anyway....I see it....but it's an ugly mess.
>
>Any way to get all those hex codes out of there ?

It is not intended for user access, so there is no API to access it etc.
You
can either:

 - DMPSYSOBJ, then CPYSPLF, then parse the printed output
 - Use MI to access the space directly

In either case, IBM is publicly documenting the layout nor is there any
guarantee it will remain the same.  Swm at your own risk.  YMMV.

The other method is to just use DMPSYSOBJ to find the device name of the
session
history you want.  Then sign on at the device, run STRSQL, and exit saving
the
history to a source member.

My point in posting the names was to allow a means to verify the claim it
had to
do with two concurrent STRSQL sessions for the same user, and the device
names
associated with each.

Doug

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