ADSM-L

Re: Attention: Admin Event Successful or not

2003-04-21 04:09:47
Subject: Re: Attention: Admin Event Successful or not
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 20 Apr 2003 19:36:07 -0700
Keep in mind, though, that when you specify WAIT=YES, the command has to
complete before the next command is issued. So if you have a script like
this:

   backup stgpool primary1 copypool
   backup stgpool primary2 copypool

The two commands are launched, one immediately after the other, and will
run concurrently. On the other hand, if you modify the script like this:

   backup stgpool primary1 copypool wait=yes
   backup stgpool primary2 copypool wait=yes

then the first "backup stgpool" command will have to run to completion
before the next "backup stgpool" command is launched. thus these commands
will run sequentially rather than concurrently.

The first version of the script is useful when you want multiple
operations to run at the same time. You can use the SUMMARY table to get
completion status.

The second version of the script is more useful when you require that the
commands run sequentially. You can also use the SUMMARY table to get
completion status.

When scripting involves multiple operations, it is probably best to use
the SUMMARY table to determine the status of each operation.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Rick Harderwijk <rharderwijk AT FACTOTUMMEDIA DOT NL>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/20/2003 11:50
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Attention: Admin Event Successful or not



Andrew,

Sounds logical to me. I'd better go alter those scripts now :-)

Regards,

Rick

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andrew Raibeck
Sent: vrijdag 18 april 2003 23:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Attention: Admin Event Successful or not


No, you don't need to do anything special. The stuff about "attached"
versus "detached" explains what is going on "under the covers", but it is
otherwise transparent to you. The point is, if you schedule a command and
include the WAIT=YES option (for those commands where WAIT=YES is
available), then the scheduler will get the result of the command.
Otherwise it will just indicate that it successfully launched the command.

If you run the command from the Admin CLI without WAIT=YES, then the
command will start, and you will be immediately returned to the Admin CLI
prompt so you can enter other commands. The BACKUP STGPOOL process runs in
the background, and you will need to check the activity log when it is
done to see the results.

If you run the command from the Admin CLI with WAIT=YES, then the command
will start, and the Admin CLI will appear to just sit there; you will not
be returned to the prompt. The Admin CLI will wait for the process to
complete, at which time it will display the results of the command for
you.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Rick Harderwijk <rharderwijk AT FACTOTUMMEDIA DOT NL>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/18/2003 13:08
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Attention: Admin Event Successful or not



Andrew,

Does one need to detach (sp?)the process after one has checked the result
of
the process?

Regards,

Rick

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andrew Raibeck
Sent: vrijdag 18 april 2003 5:48
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Attention: Admin Event Successful or not


Commands like

   backup stgpool backuppool copypool

run in the background, detached from the initiator of that process. All
the initiator gets back is a status of success because the command was
successfully launched. But you can look in the SUMMARY table for records
where ACTIVITY='STGPOOL BACKUP'.

On the other hand, you can launch the command like this:

   backup stgpool backuppool copypool wait=yes

This will cause the process to remain attached to the initiator of the
process. The initiator gets control after the process completes, and at
that time, the initiator gets the actual status of the process. You can
continue to look in the SUMMARY table, but you'll also find that the QUERY
EVENT TYPE=ADMINISTRATIVE will now show you the actual result of the
process (i.e. "Failed" if the BACKUP STGPOOL command failed).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Stefan Holzwarth <stefan.holzwarth AT ADAC DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
04/17/2003 01:23
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT vm.marist DOT edu
        cc:
        Subject:        Attention: Admin Event Successful or not



Hi,

after 2 years of ADSM usage i realized that
q event type=admin is not sufficent for daily reportings.

q event says nothing about the process itself. You have to check the
actlog
every day for your admin schedules!

I realized a failure of a copy of a storagepool, that had problems with
too
less scratch tapes. For this admin event the eventlog showed successful,
actlog said failed.
IBM says, works as designed.

Regards
Stefan Holzwarth
----------------------------------------------------------------------------
--
Stefan Holzwarth
ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste)
Am Westpark 8, 81373 M|nchen, Tel.: (089) 7676-5212, Fax: (089) 76768924
mailto:stefan.holzwarth AT adac DOT de