Custom module and action names in Shift History

Customers implementing extensions that interact with MVS shifts can record Shift History entries with customized names. Custom names can be specified for shift transactions performed by custom modules or custom actions.

The PersistenceModule and PersistanceAction encapsulating classes can accept these custom names. Custom modules that use APIs that affect Shift History can pass the module or action name to these classes. Custom module names can be passed to the MvsModule enum using the CUSTOM_MODULE string value. Custom action names can be passed to the MvsAction enum using the CUSTOM_ACTION string value. These string values are persisted in Shift History.