Activating authorized functions (Beta SVC) in z/OS

Activating authorized functions (Beta SVC) in z/OS

Overview

Two methods can be used to activate authorized functions after they have been specified to z/OS. Either activate the SVC in LPA by performing an IPL with CLPA (IPL method), or follow the instructions listed below to activate the SVC dynamically by running job SVCUPDTE (dynamic method).

IPL method

Perform an IPL with CLPA in order to activate the Beta SVC in LPA and/or the authorized library

Note: If you install one or more Beta products at the same time as BSA, remember to go through the product installation steps before performing the IPL, as an IPL also activates the product subsystem entries.

Dynamic method

  1. Stop all Beta product subsystems, started tasks and batch jobs that are using this SVC number.
  2. If z/OS has not yet recognized the BETA.APFLOAD as an APF-authorized library, define this load library to z/OS as follows:
    1. Add an entry for the BETA.APFLOAD to the PROGxx member of the SYS1.PARMLIB.
    2. Issue the operator command SET PROG=xx to activate this change.
  3. Modify the SVCUPDTE job to match your installation naming conventions. Make sure that the SVC number in the PARM field contains the correct number of the Beta SVC you designated.

    The sample job is found in member SVCUPDTE in the BSA.CNTL:

    +-----------------------------------------------------------------------+
    |//INIT EXEC PGM=BST01MST,  |
    |// PARM='REPLACE,212'  |
    |//* PARM='DELETE,212'  |
    |//*  |
    |//*STEPLIB DD DISP=SHR,  |
    |//* DSN=BETA.APFLOAD |
    |//*  |
    |//LOADLIB DD DISP=SHR, |
    |// DSN=BETA.APFLOAD |
    |//SYSUDUMP DD SYSOUT=*  |
    +-----------------------------------------------------------------------+

  4. Submit the modified SVCUPDTE job to dynamically activate or update the Beta SVC.

EXEC parameter

REPLACE,nnn

Replaces the Beta SVC (nnn is the SVC number)

DELETE,nnn

Deletes the Beta SVC (nnn is the SVC number)

DD statements

LOADLIB

APF‑authorized load library from which the Beta SVC is loaded

Return codes

0

Beta SVC successfully replaced or deleted

4

This return code can have the following causes:

  • RACF resource not defined
  • Deleted SVC has been used for the initialization of one or more existing subsystems, which are no longer useable; warning message 9109W is output for each affected subsystem

8

Syntax error

12

This return code can have the following causes:

  • Not enough storage
  • CSA is full

16

This return code can have the following causes:

  • Cannot find/load the Beta SVC member
  • Open error in Beta SVC library
  • ESTAE failure
  • Task not APF‑authorized
  • No input parameter specified

20

Task abended

RACROUTE macro

To prevent unauthorized access to the program SVCUPDTE, the RACROUTE macro is issued when a user submits this job. The RACF request is:

REQUEST=AUTH,CLASS='FACILITY',ACCESS=READ

The entity name is BETA.SVC.keyword.nnn, where keyword is either REPLACE or DELETE, depending on the SVCUPDTE function to be performed, and nnn is the Beta SVC you designated.

What to do next

You have completed steps 1 to 4 above, and BSA has been successfully installed. Your BSA environment has been set up with the default options and you can now customize it.