Two thoughts here.
1) Your new tape drives accept data at a faster rate than your old tape
drives. Therfore, you might expect that DFHSM is reading the DASD at a
faster rate; hence, DFHSM gets dispatched more frequently. This would
increase the apparent CPU utilization of DFHSM. However, since your backup
completes in a shorter amount of time, the average CPU utilization of DFHSM
should remain the same (or similar).
2) Check you HSM parameters. Use SETSYS TAPEHARDWARECOMPACT to
notify DFHSM that your tape drives have this feature. And, check your
SETSYS COMPACT parameter:
SETSYS COMPACT(DASDMIGRATE NOTAPEMIGRATE DASDBACKUP
NOTAPEBACKUP)
/* USE COMPACTION FOR: */
/* MIGRATION TO DASD */
/* BACKUP TO DASD */
/* DO NOT USE COMPACTION FOR: */
/* MIGRATION TO TAPE */
/* BACKUP TO TAPE */
You really don't need DFHSM to compact your data; the tape hardware does
this for you. (Of course, if you do compact your tape backup in software,
you're doing much more of this operation per second, since you are processing
more data.)
Of course, this may/may not be your problem; and, as always, YMMV.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
