It is possible for a sequence of commands within a macro to create problems,
even though the same sequence is successful when the commands are issued
individually from the command line.  Normally, commands within a macro are
executed within the same transaction, and this may cause problems if there
are interactions between commands in a sequence.  If problems occur,
try placing a COMMIT command between the problem commands in the macro or
use the ITEMCOMMIT option when you start the admin client.  See the section
on "Controlling Command Processing in a Macro" in the Admin Reference.

Dave Cannon
ADSM Development
----------------------------------------------------------------------
Martin,
Martin,

My macro is almost exactly like yours except that I am backing up the volhist
first. It goes like this:

 backup volhist file=/sys/logs/adsm/volhist.%1
 del volhist todate=today-7 type=dbbackup
 backup db devc=atl3590 type=full scratch=no vol=%2

When I separated the commands out into one batch command at a time, it works. So
that's how I am running right now. I have called back to IBM and reopened the
PMR. My server is at 2.1.0.9 and my AIX client is at 2.1.0.2.