Limited support


BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 Open link .

Saving dynamic changes to the historical database

To permanently save a dynamically added historical data set to the historical database, or to permanently remove a deallocated data set (that was originally added dynamically) from the historical database, issue the SAVE command after allocating or deallocating the data set.

When you use the SAVE command, you affect the contents of the PARMFILE DD data set. The data set names that are currently displayed on the DSLIST view are saved to the PARMFILE data set and become part of the historical database.

Any historical data set names in PARMFILE are permanently part of the historical database because when the PAS is initialized, both the HISTDS nn DD and the PARMFILE DD statements are read--the data sets defined to these statements make up the historical database at PAS initialization.

Therefore, if you add a historical data set and issue SAVE, it becomes part of the historical database, and if you deallocate a historical data set that was dynamically added and issue SAVE, the data set is removed from the historical database.

The SAVE command is issued on the COMMAND line.

If you do not issue the SAVE command, historical data sets that are dynamically added are lost from, and those that are deallocated are added back to, the historical database at the next PAS initialization.

Was this page helpful? Yes No Submitting... Thank you