Secondary address space startup procedure

Figure 1 is a sample DFSMShsm secondary address space startup procedure.

Figure 1. Sample Aggregate Backup and Recovery Startup Procedure

//**********************************************************************/
//* SAMPLE AGGREGATE BACKUP AND RECOVERY STARTUP PROCEDURE THAT STARTS */
//* THE ABARS SECONDARY ADDRESS SPACE.                                 */
//**********************************************************************/
//*
//DFHSMABR PROC
//DFHSMABR EXEC PGM=ARCWCTL,REGION=0M
//SYSUDUMP DD SYSOUT=A
//MSYSOUT  DD SYSOUT=A
//MSYSIN   DD DUMMY
//*

The private (24-bit) and extended private (31-bit) address space requirements for DFSMShsm are dynamic. DFSMShsm’s region size should normally default to the private virtual address space (REGION=0).

To run ABARS processing, each secondary address space for aggregate backup or aggregate recovery requires 6 megabytes (MB). Three MBs of this ABARS secondary address space are above the line (in 31-bit extended private address space). The other three MBs are below the line (in 24-bit address space). An option that can directly increase this requirement is the specification of SETSYS ABARSBUFFERS(n). If this is specified with an ‘n’ value greater than one, use the following quick calculation to determine the approximate storage above the line you will need:

 2MB + ('n' * 1MB)           'n' = number specified in SETSYS ABARSBUFFERS

As you add more functions and options to the DFSMShsm base product, the region-size requirement increases. You should therefore include the maximum region size in your setup procedure.

For a detailed discussion of the DFSMShsm primary address space startup procedure, the ABARS secondary address space startup procedure, and the startup procedure keywords, see DFSMShsm procedures.