We are having a very busy system as well (for example 15 volume migration tasks, 13 recycle tasks, and 10 recall tasks running) hence couple of things being discussed are :
Time to run HSM's major functions(recycle/migration etc) to ensure you have them spread out as much as possible. consider using the Mutiple Address Space HSM (MASH) function. Using MASH, you can run multiple instances of HSM on an LPAR and assign some of the workload to the additional HSM(s). Use DSS cross-memory mode for HSM procsessing. This will move much of the storage requirements of DSS to cross-memory address spaces and get them out of the HSM user region. (FYI Above DSS Cross memory is a new function drived from zOS1.9 onward more to address 878- 10 issue and going to run new address space for most of the HSM function except Recall and indeed need a kind of whole new setup and to address/implement it a complete new project needed.) Region size increase (check with IEFUTL exit) and also any above the line storage definition in STC Proc of dfhsm. FYI - There's some orphaned tape MVT allocations. These are control blocks that were allocated by HSM for tape processing but do not get freed when the task finished with the tape and being addressed with APAR OA40365. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
