Creating the STEPLIB_NAME member for a broker

This is part of the larger task of creating a broker on z/OS.

Before you start

Before starting this step, you must have completed Customizing the broker.

The mqsicustomize command creates a template STEPLIB member in the component PDSE called BIPSLIB. You can copy this to a member that matches the STEPLIB_NAME in the Customization Input File and update it accordingly.

Alternatively, you can create your own member, using the same STEPLIB_NAME. This member will contain the data set names of the system libraries to be concatenated in the STEPLIB of the started task procedure and utility jobs. The purpose of this member is to make it easier to apply service to, and migrate, corequisite libraries, without having to recustomize the brokers and User Name Server that use those resources. Select a logical name, for example WMQISTEP. This name can used by all your brokers and your User Name Server. If required you can create this member as described below.

You need:
  • If you are using Event Notification, the supplied SBIPAUTH Library.
  • The WebSphere MQ libraries: you can copy them from the queue manager JCL procedure.
  • The DB2 libraries and the libraries containing DSNTIAD, DSNTEP2, or equivalent.
  • The LE libraries: if these are already in the LINKLIST, you do not need to specify them.
  • ISPF libraries used by the DUMP formatter.
An example is shown below:
//*        Delete Libraries that are in the LNKLST concatenation
//*
//*        Adapt this member to your needs and copy it to a member with
//*        the name specified by key STEPLIB_NAME in mqsicompcif.
//*        Then copy STEPLIB_NAME to your USER_PROCLIB_PDS library.
//*
//*        LE Runtime Library
//STEPLIB  DD DISP=SHR,DSN=PP.ADLE370.ZOS140.SCEERUN
//         DD DISP=SHR,DSN=PP.ADLE370.ZOS140.SCEERUN2
//*
//*        DB2 Runtime Libraries
//         DD DISP=SHR,DSN=SYS2.DB2.V710.SDSNEXIT
//         DD DISP=SHR,DSN=SYS2.DB2.V710.SDSNLOAD
//         DD DISP=SHR,DSN=SYS2.DB2.V710.SDSNLOAD
//         DD DISP=SHR,DSN=DB2.V710.RUNLIB.LOAD
//*
//*        WebSphere MQ Runtime Libraries
//         DD DISP=SHR,DSN=MQM.V530.SCSQANLE
//         DD DISP=SHR,DSN=MQM.V530.SCSQAUTH
//         DD DISP=SHR,DSN=MQM.V530.SCSQLOAD
//*
//*        ISPF and concatenated USS Runtime Libraries
//ISPPLIB  DD DISP=SHR,DSN=SYS1.SBPXPENU
//ISPSLIB  DD DISP=SHR,DSN=SYS1.SISPSENU
//         DD DISP=SHR,DSN=SYS1.SISPSLIB
//ISPTLIB  DD DISP=SHR,DSN=SYS1.SISPTENU
//ISPMLIB  DD DISP=SHR,DSN=SYS1.SBPXMENU
//         DD DISP=SHR,DSN=SYS1.SISPMENU
//*
//*        Library containing USS related REXX procedures (OCOPY)
//SYSEXEC  DD DISP=SHR,DSN=SYS1.SBPXEXEC
//*

If you want to use SMF to provide statistics and accounting, all the libraries listed in the broker STEPLIB must be APF authorized.

Some of these libraries might exist in LINKLIST or in Link List Look Aside (LLA). If they do, you do not need to have them in the STEPLIB concatenation. For example, the SCEERUN data set is usually in the LINKLIST.

Related concepts
Broker
Broker domain
Related tasks
Creating a broker on z/OS
Customizing the broker
Creating the broker database