BSA TCP/IP server as a standalone STC (Beta 02)

Overview

The BSA TCP/IP server can be activated as a standalone started task in Beta 02 (the installed Beta product level is not relevant).

TCPIP as independent STC (B02)

Procedure

To set up Beta 02 as a standalone started task, you will need to do the following:

  • Create JCL for the Beta 02 STC

    A sample procedure for the standalone Beta 02 started task can be found in member BETA02 in the BSA.SAMPLIB.

  • Customize LST member B02LSTxx

    Code the appropriate LST parameters for TCP/IP support in the B02LSTxx member of the Beta 02 started task. A sample can be found in member B02LST00 in the BSA.SAMPLIB. If a product is installed on a different LPAR, additional OCF definitions are required.

  • Assemble and link the BSA TCP/IP server logon exit B02UXSIN

    For more information on B02UXSIN, see "BSA TCP/IP server logon exit (B02UXSIN)".

  • Create a member B02SSIxx (parameters for initializing the subsystem)

    An sample member with SSI parameters can be found under the name B02SSI00 in the BSA.SAMPLIB (see "SSI parameters").

  • Define the subsystem ID and run BST01ARI

Required libraries

The Beta 02 started task needs access to the following. Concatenate the required libraries in the STEPLIB statement if they are not included in the linklist.

  • BSA.LOAD
  • BSA TCP/IP server logon exit B02UXSIN (typically in the BETA.APFLOAD)
  • BETAnn.LOAD of each product that is to be serviced by the Beta 02 STC

SSI parameters

Keyword

Value

Description

Option

UXSRT

BST00STH

Security router

The value of the parameter must always be BST00STH.

required

UXSIN

name

Name of the BSA TCP/IP server logon exit

We recommend that you do not change the name B02UXSIN.

Do not specify a name if no check is to be performed when a user logs on. The user might be able to work with the system anyway, depending on the specific product and/or add-on.

optional