Where are interactive SQL sessions saved?
geof...@my-dejanews.com
interactive session. It seems to me that the statements must be saved in a
member somewhere that corresponds to the workstation session name. Any help
would be appreciated!
Geoff Stirling
Resolution Inc.
Sr. Systems Analyst/Programmer
Burlington VT
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
Denis Seiler
user profile, a bit like PDM "remembers" the last source file you used.
But you can always explicitly save your session to a source file...
-Denis
geof...@my-dejanews.com wrote in article
<70i1ru$f9e$1...@nnrp1.dejanews.com>...
Charles R. Pence
> I am looking for the file that contains the SQL statements entered during and
> interactive session. It seems to me that the statements must be saved in a
> member somewhere that corresponds to the workstation session name. Any help
> would be appreciated!
They are a composite of internal <ie. not an externalized object type> objects in
library QRECOVERY.
Regards, Chuck
All comments provided "as is" with no warranties of any kind whatsoever.
Charles R. Pence
> In our QRECOVERY library, I only see a journal receiver and a journal
> file. Given your explanation, is there any way to extract the
> information from the internal objects?
What do you wish to extract and/or accomplish; perhaps we <in NG> can help for a
specific request. Otherwise....Internal objects are not available to commands which
act on external object types. FWiW there is F13=Session Services which allows saving
session requests to a source physical file member. With regard to the internal object
types, you can use DMPSYSOBJ <DMPOBJ only supports external object types; and can be
used on the *LIB to see the object I note> to see them. Use DMPSYSOBJ *ALL QRECOVERY
19 EE while in restricted state -- the seize <like a lock> on that library from such a
request, may adversely impact a system's operation.
Geoff
file. Given your explanation, is there any way to extract the
information from the internal objects?
On Tue, 20 Oct 1998 14:53:21 -0500, "Charles R. Pence"
<crp...@vnet.ibm.com> wrote:
>geof...@my-dejanews.com wrote:
>
>> I am looking for the file that contains the SQL statements entered during and
>> interactive session. It seems to me that the statements must be saved in a
>> member somewhere that corresponds to the workstation session name. Any help
>> would be appreciated!
>
>They are a composite of internal <ie. not an externalized object type> objects in
>library QRECOVERY.
>
Njal Fisketjon (Njål Fisketjøn)
>Geoff wrote:
>
>> In our QRECOVERY library, I only see a journal receiver and a journal
>> file. Given your explanation, is there any way to extract the
>> information from the internal objects?
>
>What do you wish to extract and/or accomplish; perhaps we <in NG> can help for a
>specific request. Otherwise....Internal objects are not available to commands which
>act on external object types. FWiW there is F13=Session Services which allows saving
>session requests to a source physical file member. With regard to the internal object
>types, you can use DMPSYSOBJ <DMPOBJ only supports external object types; and can be
>used on the *LIB to see the object I note> to see them. Use DMPSYSOBJ *ALL QRECOVERY
>19 EE while in restricted state -- the seize <like a lock> on that library from such a
>request, may adversely impact a system's operation.
>
>Regards, Chuck
>All comments provided "as is" with no warranties of any kind whatsoever.
>
>
If you're only interested in the SQL objects containing the statements you can use
DMPSYSOBJ ISQLST<usrprf>* QRECOVERY
The spaces are named ISQL<prefix><usrprf><job><seq>
4+2+10+10+4=30 characters (seq is normally '0000')
QRECOVERY also contains the work spaces for SEU and SDA among other things.
Njål Fisketjøn
e-mail: nfis...@hesgrp.com
http://www.robin.no/~nfisketj
geo...@my-dejanews.com
looking for. Another aspect of the AS/400 I had no idea about. Thanks for
the help.
Geoff Stirling
In article <362d9535...@news.allianse.no>,
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Charles R. Pence
> <<SNIP>> ... was
> looking for. Another aspect of the AS/400 I had no idea about.
That of course is because it is an implementation detail subject to change, so you
should never need to know <assuming there is a way to accomplish what you want w/out
knowing it :-)>; as such it's not something that you would find any formal published
documentation on. Glad we could assist.