Step 4: Specifying authorized functions to z/OS

Overview

After job I#BSAJ11 has (re)linked the Beta SVC into the SYS1.LPALIB or BETA.APFLOAD, the Beta SVC must be specified and activated in z/OS.

Procedure

  1. Specify the Beta SVC to z/OS.

    Enter the Beta SVC in member IEASVCxx of the SYS1.PARMLIB in the format:

    SVCPARM nnn,REPLACE,TYPE(4),APF(NO),EPNAME(BST01SVC)

    (where nnn must be replaced with the SVC number you designated. For TYPE enter either 3 or 4.)

    Note: The dataset containing the Beta SVC must be available in the LPALIB system concatenation at IPL time. In member IEALPAxx of your SYS1.PARMLIB, enter an appropriate statement that includes the library name and the module name of the Beta SVC.

  2. Specify the BETA.APFLOAD to z/OS.

    Add the name your BETA.APFLOAD to the list of APF-authorized libraries in member IEAAPFxx or PROGxx of your SYS1.PARMLIB.

    The BETA.APFLOAD is normally allocated as a separate library during BSA installation. All modules that require APF authorization are copied into this load library during installation.

    Note: If you specify your BETA.APFLOAD in member PROGxx of your SYS1.PARMLIB, make sure that it has been activated before starting any Beta product.

  3. Strongly recommended: Include your BETA.APFLOAD in the linklist, which is defined in member LNKLSTxx of your SYS1.PARMLIB.

If BETA.APFLOAD is not in the linklist

We strongly recommend that you include your BETA.APFLOAD in the linklist.

Be aware of the following consequences if you decide not to include the BETA.APFLOAD in the linklist:

  • BST01ARI cannot run at IPL time.
  • Your BETA.APFLOAD must be concatenated in the STEPLIB of every Beta product batch job and started task JCL.
  • All the other libraries in the STEPLIB concatenation of each Beta product batch job and started task JCL must also be APF authorized.