Re: ISQL sessions

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

I think this info is associated with a job name and user. We use the 
default naming for PC5250, so I don't always get back to where I was and 
lose what record of work I did. Maybe an option is to save the session 
every time to a source member.

http://archive.midrange.com/midrange-l/200111/msg00343.html is the message 
that explains this.

> Try the following command, assuming the profile name is Mike:
>
>   DMPSYSOBJ ISQLSTMIKE* QRECOVERY  TYPE(19) SUBTYPE(EE)

I did this for myself and got 2 objects dumped to the spooled file. The 
first object was

NAME-        ISQLSTVERN      QPADEV000G0000
LIBRARY-     QRECOVERY

The name actually has the blanks in it - system objects can do that. The 
second was

NAME-        ISQLSTVERN      QPADEV000G0001
LIBRARY-     QRECOVERY

One of my current jobs is QPADEV000G and I see the history for that one. 
The other job is QPADEV000B, and it uses the second one, so I think the 
number at the end is some kind of serial number. The linkage seems to be in 
each job, as there is no other reference to QPADEV000B in either object. So 
you won't know to which job each history is associated. But at least you 
can see all the statements.

At 02:25 AM 3/2/2005, you wrote:

> On 02/03/2005, at 10:56 AM, Chris Bipes wrote:
>
> > Where or where does the system store your sessions, not the ones you save to
> > a source member, but your current session after you exit.  For instance I
> > start three interactive jobs and I start an ISQL session in each.
> > After
> > exiting all three, in which one has the update statement I want, were does
> > or how does the system save these?  Is the first ISQL session saved as user
> > session1, the second as user session2, the third as user session3?  Or is
> > based on User/Job for each interactive user.
>
> Check the archives for Midrange-l or MI400-l. This has been discussed in 
> detail on at least one of those.
>
> > I have a programmer that cannot keep track of where he was but has a hard
> > time finding that statement he build before lunch.
>
> 30-second attention span?  Must be young (or really old ...) or possibly 
> imbibing something at lunch that perhaps he shouldn't?
>
> > Second, can I limit them to one ISQL session?  (Management override to solve
> > confused programmer ;-)
>
> Only by limiting them to one signed-on session. If they have trouble 
> recalling what they were doing an hour ago then multiple sessions are 
> probably too much for them also.
>
> Regards,
> Simon Coulter.
> --------------------------------------------------------------------
>    FlyByNight Software         AS/400 Technical Specialists
>
>    http://www.flybynight.com.au/
>    Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
>    Fax:   +61 3 9419 0175                                   \ /
>                                                              X
>                  ASCII Ribbon campaign against HTML E-Mail  / \
> --------------------------------------------------------------------
>
>
> --
> 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.