Aravind -

As I alluded, the essence of the sessions is recorded in the
dsmaccnt.log file, which everyone should have turned on, for
historical reporting.  I provide a sample reporting program in my Web
area for processing, if you have nothing else, which you can readily
modify to expose all the info you want.  Or, you can simply examine
its textual content.

Session numbers are not recorded in the accounting file, but whereas
the Producer's life encompasses that of its Consumer "children", the
association is rather apparent within the timespan for the client -
particularly for scheduled processes, in that client scheduling is
serial.  See the Admin Guide manual for the authoritative
documentation on the accounting log, and my dsmaccnt.log notes in
ADSM QuickFacts for accumulated notes on contents.

  Richard Sims   http://people.bu.edu/rbs

On Oct 30, 2006, at 2:11 PM, Aravind Kurapati wrote:

Richard,
An initial test shows that the commands return data only for active
sessions. Is this maintained historically anywhere? Also, how can I
determine which "Producer" process the various "Consumer" processes
are tied
to?
Thanks
Aravind

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of
Richard Sims
Sent: Monday, October 30, 2006 2:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Sessions in Actlog

On Oct 30, 2006, at 8:02 AM, Aravind Kurapati wrote:

Is there any way to query the relationship between Session numbers
in actlog
and a TSM job? It is quite common to find multiple sessions for the
same job

Aravind -

There's no ready way that I know of to relate the Producer and
Consumer sessions resulting from RESOURceutilization > 1.  The
Producer, being the session in charge, will show a start time (in
'select * from sessions') which is as early or earliest of any
session for that node, and will typically show a LAST_VERB of Ping,
rather than BackInsNormEnhanced or the like.  In 'SHow SESSions'
output, the Producer will show SessType=5 for a scheduled process,
with its Consumer "children" being SessType=4; and the Producer will
not transfer data, so its Backup and Archive object count will be
zero.  (But, in a manual 'dsmc', the sessions will all be
SessType=4.)  You will also see these session type numbers in the
dsmaccnt.log records.  So, to the best of my knowledge, this is all a
matter of discerning, rather than readily determining.

    Richard Sims