Step 1: Defining the ISPF environment

BBVINIT should include the product libraries that are distributed with ISPF and PDF products; these libraries include the ISP (and ISR, if separated) libraries, but it should not contain any user or application libraries. (See your ISPF documentation for more information about ISPF libraries.)

An active TSO session and an active TAS session cannot share the same ISPF profile data set concurrently; therefore, BMC recommends a separate ISPF profile data set name format for the ISPF environment. See To define ISPF profile data sets for concurrent TSO and BBV sessions for more information about running TSO and BBV sessions under the same user ID within the same sysplex.

If you want to specify a distinct location for dynamic allocation of your session data sets, see information about the TAS parameter, DEVGROUP, in Understanding-TAS-initialization-parameters.

To define the ISPF environment

1. Create hlq.UBBSAMP member BBVINIT.

   Note

   • You must name your new member BBVINIT. Do not use a different name because MainView Alternate Access will not initialize sessions.
   • The UBBSAMP data set must have the following attributes:
     • DSORG=PO
     • LRECL=80
     • RECFM=F or RECFM=FB (FBS is not supported)
2. Copy BBSAMP member BBVINIT to the new member.
3. Follow the instructions at the top of the UBBSAMP(BBVINIT) member to customize the REXX EXEC.

4. Add unit and volume information to the allocation statement of the ISPF profile data set if your site does not support SMS. (Refer to the appropriate IBM book for REXX to find out how unit and volume parameters should be coded on the ALLOCATE statement for the ISPPROF data set.)

   Warning

   BMC recommends that you make only the modifications to the REXX EXEC that are listed in these instructions and in the instructions at the top of the BBVINIT member. BMC does not support other changes to the REXX EXEC.

To define ISPF profile data sets for concurrent TSO and BBV sessions

The BBVINIT sample provides an instruction for defining the name of the ISPF profile data set for BBV sessions through the ALLOCATE statement for ISPPROF. Also, an optional SYSPREF parameter can be defined in the TAS parameter member (see Understanding-TAS-initialization-parameters) when sites require a high-level qualifier that is different from the user ID name for the ISPF profile data set name.

The resulting default ISPF profile data set name formats for concurrent TSO and BBV sessions using the same user ID on the same system are:

• userID.ISPF.PROFILE for a TSO session
• userID.BBVISPF.PROFILE or syspref.BBVISPF.PROFILE for a BBV session