Specifying the individual auxiliary storage pool devices in the above example can be a bit cumbersome, especially if you have a large number of secondary auxiliary storage pool devices in the group. If the objects on these auxiliary storage pool devices can be saved using save while active, you can use the *SETASPGRP backup item to attach the device to the job. To do so, add a *SETASPGRP backup item and specify the primary auxiliary storage pool device name in the Auxiliary Storage Pool Device prompt for this backup item. Then use the *CURASPGRP special value for the Auxiliary Storage Pool Device prompt on all subsequent backup items to be backed up from that primary auxiliary storage pool device and any of its associated secondary auxiliary storage pool devices as shown in the following panel.
Edit Backup Control Group Entries RCHAS400 Group . . . . . . . . . . : ASPS Default activity . . . . . FIIIIII Text . . . . . . . . . . . Backs up the switched ASPs Type information, press Enter. Weekly Retain Save SWA Backup List ASP Activity Object While Message Sync Seq Items Type Device SMTWTFS Detail Active Queue ID 10 *EXIT ******* 20 *SETASPGRP PAYROLL FIIIIII 30 *ALLUSR *CURASPGRP FIIIIII *YES *NO 40 *LINK *CURASPGRP FIIIIII *YES *NO 50 *SETASPGRP *SYSBAS FIIIIII 60 *EXIT ******* Bottom F3=Exit F5=Refresh F10=Change item F11=Display exits F12=Cancel F14=Display client omit status F24=More keys
Using the *SETASPGRP and *CURASPGRP special value combination is the preferred method of backing up objects on auxiliary storage pool devices. BRMS has many operations which need access to the objects during the save processing. Using these options assures the objects are available to BRMS. This may not be the case when saving the objects using named auxiliary storage pool devices.
You cannot use *SETASPGRP if you are saving to TSM servers. You must explicitly name the auxiliary storage pool device on the backup item. The restriction is due to the way the operating system has implemented these types of saves. The save command is not processed in the same job as the backup. The command is run in a server job. Hence, any SETASPGRP command run in the backup job does not affect the save processed in the server job.