The Save command in the File menu explicitly copies the configuration file from memory to disk, but keeps it in memory so you can keep working. The Save command also saves the IODF, and tags the configuration file and IODF with matching tokens.
After having updated the configuration, the Close command saves both the IODF and the configuration file, then closes both files. When you close the IODF with Close or Exit, the Activity Log dialog will appear if activity logging has been enabled for the IODF (see Creating a new configuration from scratch).
Closing an MCF-enabled configuration also updates the associated MCF on the host.
You can enable automatic activity logging by entering the following keyword into the HCD profile:
CHANGE_LOG = YESWith this setting, HCD uses a subset of the change log entries to generate automatic entries into the activity log for updates on configuration data, like for example for add/delete or connect/disconnect activities. These entries are HCD proposals which you can edit.
For more information, refer to the z/OS HCD User's Guide.
For z/OS, use the HCD dialog to view the complete activity log. For z/VM, use BROWSE or XEDIT to view the activity log. See Creating a new configuration from scratch for this file's naming convention.
File → Exit performs a Save before exiting HCM.
If HCM terminates because of a host abend, a loss of network connection, or an HCM abend, then the next time you open your configuration file HCM may need to resynchronize it with the IODF. Furthermore, whether a resync is required or not, the last modification made before the termination may need to be made again.