Re: Interactive SQL - Command History

[Douglas Handy <dhandy1@xxxxxxxxxxxxx>]

Mike,

>Any ideas what is going on here?

As Martin indicated, it has to do with device(s) from which you run interactive
SQL.  The way it works (I think) it that, provided your profile never has STRSQL
active at more than one session at a time, there is a single history saved for
your profile.  Regardless of which device you next use to start SQL, that
history is restored.

But as soon as you start a second instance of STRSQL (for a given user profile),
it switches to keep the history separate by device name as well as user.  After
that you only see the history saved *at that device*, even if you only run one
instance at a time.

Interactvie SQL is kept in a space object with type 19, subtype EE, in QRECOVERY
with the name ISQLSTusrprf*.  After the user profile name is the device name for
which the session history was created.

Try the following command, assuming the profile name is Mike:

  DMPSYSOBJ ISQLSTMIKE* QRECOVERY  TYPE(19) SUBTYPE(EE)

I expect you'll now find two objects, whereas prior this afternoon there was
only one for your profile.  These objects aren't intended for user access, and I
don't know if simply deleting all but one will make it revert back to the
original method of allowing the session history to float between devices.  Aside
from the ISQLST* spaces which have the session history, there are other ISQLxx
spaces with letters other than ST.  I don't know how they interact.

Doug