HLASM Toolkit Feature Installation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Step 3: Load HLASM Toolkit Feature into shared virtual area (SVA)

HLASM Toolkit Feature Installation and Customization Guide
GC26-8711-09

The IDF component of HLASM Toolkit Feature makes extensive use of vendor exits. Therefore some HLASM Toolkit Feature phases must be loaded into the SVA. These phases are:
  • ASMPCKEX
  • ASMPGLEX
  • ASMSVCEX
  • ASMIDFRX
To load these phases into the SVA, do the following:
  1. Modify the SVA statement of the VSE IPL ASI (Automated System Initialization) procedure to allow space for the phases:
    • Increase the SDL parameter by the number of new phases being added to the SVA.
    • Increase the PSIZE parameter by the amount of storage required to contain the new phases being added to the 24-bit and 31-bit SVA.
  2. Modify the z/VSE background (BG) ASI procedure to automatically load the required phases into the SVA:
    • Modify the ALLOC statements for the partitions to ensure that the remaining storage is large enough to contain the phases.
    • Modify the LIBDEF PHASE SEARCH job control statement preceding the SET SDL statement to include the name of the sublibrary containing the HLASM Toolkit Feature phases.
    • The supplied SVA loadlist member, $SVAASMT, contains all the required HLASM Toolkit Feature phases that must reside in the SVA, as listed above. After the SET SDL statement, add the statement:
      LIST=$SVAASMT

    These phases have been built with the option SVAPFIX. When the phases are loaded into the SVA, they will go into PFIXed storage. This has a real storage requirement of at least 3K bytes.

    A sample batch job, ASMTSVA2, is supplied, which will load the phases in $SVAASMT into the SVA. This job must be run in the BG partition.

    For more information about PFIXed storage and loading phases into the SVA, see z/VSE: System Control Statements. and z/VSE: Guide to System Functions.

  3. Shut down and Re-IPL your z/VSE system.
In addition to loading phases into the SVA, to use vendor exits the application must be authorized. The users must be authorized (for example, via DTSECTAB) to access the phase $IJBVEND and the product exit routines. These routines are:
  • ASMPCKEX
  • ASMPGLEX
  • ASMSVCEX

For information about authorization using DTSECTAB, see z/VSE: Administration.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014