Certainly. We are just trying to utilize new avenues for disseminating
information. One size never fits all. In a recent LinkedIn post, I documented
all of the DFSMShsm RFEs that are included in V2R4:
RFE 121915: (SHARE MVSS) Quiesce window for interval and on-demand migration
Request: HSM automatic migration via interval or on-demand migration sometimes
runs during peak CPU utilization times. We are looking for the ability to
provide windows in which we can turn off both types of automatic migration. It
is already disabled during primary space management (PSM) processing; we look
for additional times to disable it. We want to keep command migration available
at all times. Disabling automatic migration should not prevent command
migration.
Response: New SETSYS EventDrivenMigrationQuiese and HOLD/RELEASE
EventDrivenMigrationQuiese commands.
RFE 114044: HSM should include which parameters are valid/invalid during startup
Request: When DFSMS starts up, it produces messages on parms in ARCCMDxx either
being valid or invalid. It would be good to know which parm was verified (or
not). So it could be ARC0100I SETSYS COMMAND COMPLETED for - XXXXX or ARC0104I
INVALID INITIALIZATION COMMAND - YYYY
Response: Provided
RFE 130361: Empty data set during backup flag
Request: In the Data Areas manual there is MCDFMPTY field that when set to 1,
the data set was empty at the time of migration. Would like the same for a
backup.
Response: MCCFMPTY added.
The following messages are now issued to SYSLOG to enable automation:
RFE 116187: ARC0019I CELLPOOL cellpool ENCOUNTERED A SHORTAGE
RFE 126300: ARC0263I DUMP VOLUME volser DELETED now issued to SYSLOG
RFE 132117: ARC1814I FAST REPLICATION BACKUP HAS COMPLETED SUCCESSFULLY AND
DUMP IS NOW STARTING
RFE 119146: Improve FREEVOL messaging
Request: During FREEVOL of an ML1 volume, if an ARC0560E condition exists where
migration to ML2 is limited due to lack of ML2 tape/DASD, datasets that should
be migrated to ML2 stay on the ML1 volume. The corresponding ARC0734I message
indicates that the dataset moved "TOVOL ******", but the return code is zero
and the reason code is zero. They should be RC5 REAS8.
Response: Provided
RFE 115386: ARC1001I messages routed to activity log
Request: BACKDS fails, we would like to see the failing ARC1001I message issued
to the backup activity log.
Response: Provided
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
