Support multiple WSBind directories on WSDIR PIPELINE definition (SHARE requirement SSCICS11011) Merged

Each CICS Web Service consists of a CICS program along with a WSBIND file describing among other things the inputs and outputs for the service (program). This is similar to a BMS maps relationship to a program. The WSBind files are stored in an HFS file directory. To expose or register a service to CICS, a directory is defined on the WSDIR parameter of a CICS PIPELINE definition. However, only one HFS directory is allowed on the WSDIR parameter. Think of this as allowing only one PDS for all BMS maps yet allowing multiple PDSs for the programs associated to those BMS maps.

Example:

Assume PDS contains programs exposed as a Web Service. Each PDS should have a corresponding HFS files containing the WSBind files for the service. To run a test, all of the HFS members would have to be copied from the production HFS directory followed by the general-test HFS and my-test HFS. If a program in the my-test PDS is bad and gets deleted, a program Newcopy would be performed and CICS would find the appropriate program from the DFHRPL concatenation.

The corresponding WS Bind file in the my-WSDir HFS directory however would have to be overlaid with the appropriate version from either the general-test or production HFS directory. It would be the developers responsibility to figure out which one to use. As the number of DFHRPL libraries increases, this task gets more time consuming.

DFHRPL DD DSN=my-test lib
DD DSN=general-test lib
DD DSN=production lib

WSDIR=my WSBind lib