Cloud ASP Support Setup

Starting with the June 2018 BRMS PTFs, BRMS has been enhanced to use ASP and IASP for Cloud transfer operations. BRMS cloud transfers are able to create virtual image catalog entries for backups on an ASP or IASP instead of using *SYSBAS space. When using cloud with ASP support for ASPs 2 -32, and using control groups with the control group attribute Unmount user-defined file systems . . . *YES, the volumes will be left in *TRF after the control group completes. STRMNTBRM needs to be run to transfer the volumes to the cloud.

The ASP for BRMS to use can be specified by running the following command:

CALL PGM(QBRM/Q1AOLD) PARM('CLDTRFASP ' '*SET ' 'nnnnnnnnnn')

where - nnnnnnn is the ASP name.

The ASP value can be displayed by running the following command:

CALL PGM(QBRM/Q1AOLD) PARM('CLDTRFASP ' '*DISPLAY')

The ASP value can be reset to the default value of *SYSTEM by running the following command:

CALL PGM(QBRM/Q1AOLD) PARM('CLDTRFASP ' '*REMOVE')

NOTE:

In 7.4 and later, WRKPCYBRM TYPE(*BKU) the ‘Cloud transfer ASP’ field was added to support this cloud ASP value.

When using an IASP for turnkey operations with Unmounted user-defined file systems … *YES, there is always a default.UDFS associated with an IASP so that UDFS cannot be Unmounted if a span occurs. The BRMS turnkey solution using an IASP image catalog that results in a spanning situation during a *LINK backup when the UDFS is not mounted, will not work.

The possible alternatives are:

use turnkey optical
users must create and manage their own virtual tape image catalogs and virtual tape devices with enough volumes pre-created for the backup and enroll the volumes in BRMS and use that device instead of using the BRMS turnkey solution
use Unmount user-defined file systems … *NO, and switch to add specific UNMOUNT commands as exits in the control group for specific UDFS paths excluding the IASP being used for the backup
use image catalog sizes that are big enough to save the full *LINK without spanning