More stuff:

When you do an import, you import the whole node, or at least a whole
filespace.  Can't get any more granular than filespace.
You are essentially reloading everything back into the TSM server DB and
storage pools.  Then you start the regular B/A client and restore whatever
files you want to the client.  So it's a 2-step process with IMPORT, where
with a BACKUPSET you can restore directly from the backupset tape.

Things that are on EITHER an EXPORT or BACKUPSET tape are not governed by
expiration rules.  Whatever is on the tape, stays on the tape.

When you IMPORT a filespace, the data is back in the TSM DB and the inactive
file copies (if you included the inactive data in the export) are again
governed by expiration rules.  Look at HELP IMPORT NODE, the DATES= parm.
It controls whether the imported inactive files start to expire immediately
or not.

EXPORT/IMPORT works on filespaces, so can be used for application data bases
backed up by TSM for Oracle, SQL, etc.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)