What's new?

V2.8.2 - July 2023

Added

BMC AMI Cloud

Finalization performance

The finalization process that is performed after each resource processed by a BMC AMI Cloud policy run, is now enhanced to be a more scalable process. This new enhancement reduces the total elapsed time of all backup policy run types.

New CLI DELVOL command

The BMC AMI Cloud command line interface now allows the removal of full-volume backups directly from z/OS using the DELVOL command. This new feature expands the native z/OS interface provided as part of the BMC AMI Cloud agent installation. For more information, see DELVOL.

Agent Java version verification

BMC AMI Cloud now verifies the minimal Java version is in place during its initial loading. This new verification would reduce the risk of hitting known Java issues when using outdated versions.

Checkpoint data set support

The Cloud Data Set backup policy and CLI BACKDSN command now allow the backup of z/OS checkpoint data sets. The new enhancement adds two new agent parameters to control the FORCECP parameter value. For more information, see Updating-the-BMC-AMI-Cloud-agent-configuration-files.

New resources page delete action

The BMC AMI Cloud GUI new resources page will now allow deleting a resource version from the drop-down menu.

BMC AMI Cloud Data

Cloud data sets enabled programs

The BMC AMI Cloud Cloud data set feature now enables by default two new programs, IEBCOPY and IDCAMS. Both the target and the source of these utilities can utilize cloud object storage. This new enhancement enables you to leverage cloud data sets more broadly.

Archive verify backup existence

The BMC AMI Cloud archive policy backup existence verification option has been enhanced to follow the z/OS Storage Management Subsystem (SMS) storage and management class settings when requested. This new feature allows archiving data sets with storage group and management class auto backup set to no. For more information about archive options, see Creating-a-new-policy.

Fixed

  • Fixed an issue where the BMC AMI Cloud server Java settings weren't applied during the server start time when running on s390x (Linux on Z or zCX). For Linux on Z, see Task 6: To create a BMC AMI Cloud environmental variables file, and for zCX, see Task 6: To start the BMC AMI Cloud server.
  • Fixed an issue with the CDS debug message formatting. This caused excessive CPU consumption, especially for data sets with large amounts of blocks.
  • Fixed an issue where the restore activity was not being created on the new resources page when refreshing the screen at the same time. This caused the restore activity not to run.
  • Fixed the BMC AMI Cloud CLI archive command data set active backup verification issue. This fix verifies the current backup existence in the object storage and that the data set change bit is off.
  • Fixed a wrong data set indexing issue when performing a full dump containing VSAM AIX. This blocked the ability to recover the AIX from a full dump copy.
  • Fixed missing simulate run log messages issue that caused the run log to not contain the report information of the simulated run.
  • Fixed an occasional hibernate convertHibernateAccessException when running data set restore and recall. This causes the operation to fail thus not recovering the data set.
  • Fixed a wrong resource type issue in the restore message when restoring a data set from the new resources page.
  • Fixed ZM9NK033E RSN=000080E error when deploying Cloud Data Sets on z/OS V2R2.

Other improvements

  • Starting from this release, the backup verification for data set archive performance is not dependent on the number of backups a data set has.
  • The policy expiration process now validates backup existence in the object storage before removing the previous expired generations.
  • Starting from this release, by default resource specific discovery failures will not fail a policy run. For more information, see the discovery.missing_property.message.level parameter in agent.yml.
  • Sync with storage action on the Agents page now doesn't refresh the entire web page.
  • With this release, the 3rd party packages used by the different BMC AMI Cloud components were upgraded to the latest. This new enhancement helps to keep the container's infrastructure up to date to avoid security exposures.

V2.7.0 - March 2023

Added

BMC AMI Cloud

Policy concurrent copy support

The Cloud Data Set backup and full dump policy types now allow setting the concurrent copy option. This new feature will allow the storage administrator to enable or disable the concurrent copy option at the policy level. For more information and known limitations, see creating a new policy.

Server API edit policy

The BMC AMI Cloud server API (M9SAPI) edit command now accepts requests for dataset archive and full volume dump policy types. This new capability provides more automated control over the BMC AMI Cloud policies using standard JCL and JSON.

Agent load-balancing performance

The BMC AMI Cloud management server agent load-balancing capabilities were enhanced to ensure improved distribution of work between the different agents within the same agent group. This improvement is expected to improve policies' total elapsed times and would also improve load balancing where one or more agents running on a weaker logical partition.

Resource search results page

The BMC AMI Cloud web UI resources page was enhanced to support larger amounts of managed resources. This improvement will reduce the amount of time the resources search results page loading time dramatically to allow users a better experience and usability.

Podman support

The BMC AMI Cloud server can now be deployed on the podman container platform. This improvement provides the administrators with the flexibility of choosing the container platform they are required to use.

BMC AMI Cloud Data

Controlling cloud dataset VDEV address space

The BMC AMI Cloud VDEV address space now accepts a new MODIFY parameter that allows disabling its functionality which will allow the shutdown of BMC AMI Cloud VDEV. This new feature will allow the storage administrator to disable the BMC AMI Cloud VDEV functionality in cases normal shutdown is rejected.

Cloud data set resource information

BMC AMI Cloud Data will now present the original label creation date for cloud data sets resource types.

CLI DELBACK improvement

The BMC AMI Cloud command line interface (CLI) DELBACK now allows the deletion of policy-originated backup versions. This new capability allows CLI users with proper permission to remove expired backup versions directly from z/OS.

Fixed

  • Fixed a data set backup issue when running the policy by volume or storage group where the selected data set was cataloged using system symbols. This caused the backup to end with an error thus not creating a backup version.
  • Fixed the wrong volume name presented when backing up data sets by pattern which were cataloged with system symbols. This caused both the UI and CLI to present the system symbol instead of the actual volume name the data set resides on.
  • Fixed a policy finalization issue where the policy takes an extensive amount of time to remove expired versions of VSAM data sets. This was caused by a missing index within the BMC AMI Cloud database.

Other improvements

  • Improved restore and recall operation zIIP consumption, where the backup and archive versions were created using gzip or lz4 compression methods.

The BMC AMI Cloud agent's parameter volume Backup_dfdss_warn_to_ok_msg_codes default value no longer contains ADR735W message. This may cause full volume dump backup run to end in a warning status in case concurrent copy is not available. For more information, see Updating-the-BMC-AMI-Cloud-agent-configuration-files.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*