ADSM-L

Re: Attention: Admin Event Successful or not

2003-04-18 17:26:00
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: Fri, 18 Apr 2003 14:25:33 -0700
Possibly, if your script starts commands without using WAIT=YES. I don't
know a whole lot about how script processing works, but I suspect that the
script status may be based on the status of the last command that ran,
even if WAIT=YES is used. So if you have a script with two commands, and
the first command fails but the second command is successful, then the
status will be successful. But that is just a best guess.

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.




Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/18/2003 05:47
Please respond to "ADSM: Dist Stor Manager"


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



I've also noticed that if you schedule a SCRIPT to run you almost always
get
Successful from the event. We have a BACKUP_SERVER script that does all
the
stgpool backups, DBBackups and initiates migration. If you get a task in
the
script that Fails, you still get a Successful for the event RUN
BACKUP_SERVER Is this due to the same "launching" technique?

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andrew Raibeck
Sent: Thursday, April 17, 2003 11:48 PM
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