Setting up the web services definition file

After creating the startup configuration member and the started task procedure, you allocate and initialize the web services definition file. This server-side file stores user preferences and dynamic configuration information on the UIM server.  You can share the file between all UIM servers that are on the host, or you can create a file for each UIM that is on the host.

To allocate the web services definition file

The installation process created the hlq.HFS member (where hlq is the high-level qualifier that you specified during installation) in the SAMP library. Installation then customized hlq.HFS with your site specific information. You can submit the customized data set, or you can customize a copy of the data set member in the sample library.

1. Locate the #DEFHFS member in the UIM sample library.
   The following figure shows the #DEFHFS member:

   //ALLPDSE  EXEC PGM=IEFBR14
   //HFSPDSE  DD   DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(1,1)),
   //              DCB=(DSORG=PO,RECFM=VB,LRECL=4096),
   //              DSNTYPE=LIBRARY,
   //              DSN=hlq.HFS

2. Edit the #DEFHFS member by changing the following variables as needed:

   Variable	Definition	Accepted value
   UNIT	Device for placing data sets	See your site standards
   DSN	High-level qualifier	See your site standards

3. Save the edited #DEFHFS member with a new name.
4. Submit the DEFHFSJC member JCL.

To initialize the web services definition file

Before you can share connections in a sysplex, you must initialize the web services definition file that you allocated.

The installation process creates and customizes the HFSLOAD data set with your site-specific information.

1. Locate #LOADHFS in the UIM sample library data set.
   The following figure shows the default #LOADHFS member:

   //*--------------------------------------------------------------
   //*
   //*     Load the BMC HFS PDSE with SAMP library members.
   //*     Optionally convert previous BMC HFS HostList.xml if found.
   //*
   //*--------------------------------------------------------------
   //LOADHFS EXEC PGM=UIMHFSL,REGION=0K,
   //  PARM='=version $UIMHFSL $UIMHFST'
   //*-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
   //* UIMHFSL parameters:
   //*
   //*   memname   Samplib control cards member, default is $HFSLOAD.
   //*             - $HFSLOAD is a Load of default properties files
   //*   -t        Activate tracing to SYSPRINT
   //*
   //* SAS/C Runtime Library parameters:
   //*
   //*   =version  Print Runtime Library release information to SYSTERM
   //*
   //*--------------------------------------------------------------
   //STEPLIB  DD  DISP=SHR,DSN=hlq.LOAD
   //*
   //*  SAS/C DD'S
   //SYSTERM  DD  SYSOUT=*
   //SYSPRINT DD  SYSOUT=*
   //STGRPT   DD  SYSOUT=*
   //*
   //*  STANDARD JOB DD'S
   //SYSUDUMP DD  SYSOUT=*
   //*
   //HFSPDSE  DD  DISP=SHR,DSN=hlq.HFS
   //SAMP     DD  DISP=SHR,DSN=hlq.SAMP
   //CONT     DD  DISP=SHR,DSN=hlq.CONTENT
   //*
2. Edit the #LOADHFS member, and change hlq to the high-level qualifier according to your site standards.

3. Save the edited member as HFSLOAD.

   Note

   This step overwrites the customized data set that installation created.

4. Submit the HFSLOAD member JCL.