Enable STC Definitions for Web Services

As a CA Common Services administrator, you can configure the CA Common Services components to support Web Services for . Web Services is a prerequisite for the Eclipse-Based UI and user-written programs that connect to the API.
ce18
As a CA Common Services administrator, you can configure the CA Common Services components to support Web Services for
CA Endevor
. Web Services is a prerequisite for the Eclipse-Based UI and user-written programs that connect to the
CA Endevor
API.
CA Common Services components must be installed and configured to enable communication between
CA Endevor
and Web Services. For more information, see CA Common Services for z/OS Components. The following graphic shows how you can enable STC definitions for Web Services:
How to enable STC Definitions for Web Services
How to enable STC Definitions for Web Services
To enable STC definitions for Web Services, complete these steps:
  1. Review the prerequisite information for an understanding of how Web Services works. For more information, see How to Enable Web Services.
  2. Verify that the following CA Common Services components are installed and running on the mainframe:
    • CAIRIM
    • CAIENF
    • CAICCI
  3. (Optional) IPL your system
    You do not need to IPL your system after installation, if it is your initial CAICCI component installation. If it is a subsequent installation, you may need to IPL your system. For more information, see CA Common Services - Installing.
Verify that CA Common Services Components Are Running
Ensure that you install and run the following CCS components:
  • CAIRIM
  • CAIENF
  • CAICCI
These components must be installed and running on your mainframe. If not, install these services according to CA Common Services - Installing.
Follow these steps:
  1. Go to the z/OS System Display and Search Facility (SDSF) status display and enter the prefix ENF*.
    • If you do not see ENF* active on your system, contact your systems programmer to start it.
    • If the ENF job is running, go to step 2.
  2. Select the ENF job and search for (Find) CAICCI within the job.
    • If you find CAICCI, then CAIENF and CAICCI are running. You are done verifying that the CCS components are running. Record the values that you identified while completing these procedures.
    • If you do
      not
      find CAICCI, then go to step 3.
  3. Check your site CAI.CAIPROC library to see if the ENF member has been modified to run CAICCI at your site.
  4. If the ENF member exists, go to the Customize task the ENF Procedure and then start the member. If the ENF member does not exist, contact your local systems support person to determine the status of CAIRIM, CAIENF, and CAICCI on your system. They may also help you complete the tasks in the next section.
Define the Started Task for Web Services
Web Services uses started tasks that are started by the CAICCI SPAWN facility to communicate with the
CA Endevor
API. You define these tasks to the spawn facility by adding a spawn parameter DD statement (
ndvspawn
) to the ENF procedure for CAICCI services. The
ndvspawn
DD statement specifies the name of the started task JCL (based on WSEWSSTC in CSIQJCL) for the
CA Endevor
API. Edit the WSEWSSTC procedure JCL to specify the high-level and second-level qualifiers for the
CA Endevor
data sets. The WSEWSSTC copy is initiated as a started task.
Follow these steps:
  1. Customize the ENF Procedure by adding the Web Services spawn parameter file name to the SPNPARMS DD in the ENF PROC JCL. You can find the ENF procedure in the initial CAI.CAIPROC library. However, your system administrator may have copied the procedure to the system PROCLIB. The following JCL is shown as an example to indicate the two lines that you must add to the JCL.
    //ENF PROC OPTLIB='SYS2.CA90S.PARMLIB', // ENFDB='SYS2.CA31.ENFDB', // ENFPARM=ENFPRM31, // SPNPAR1=SPWNSNMP, //
    SPNPARn=ndvspawn,
    // CCIPARM=CCIPCA31, // ENFCMDS=ENFCMD31, //ENF EXEC PGM=CAS9MNGR,TIME=1440 //CASRT01 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) //CASRT02 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) //CASRT03 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) //CASRT04 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) //CASRT05 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) //SPNPARMS DD DISP=SHR,DSN=&OPTLIB(&SPNPAR1) //
    DD DISP=SHR,DSN=&OPTLIB(&SPNPARn)
    //SPNPRINT DD SYSOUT=X //SPNDEBUG DD SYSOUT=X //SRVDEBUG DD SYSOUT=X //ENFDB DD DISP=SHR,DSN=&ENFDB //ENFPARMS DD DISP=SHR,DSN=&OPTLIB(&ENFPARM) // DD DISP=SHR,DSN=&OPTLIB(&CCIPARM) //ENFCMDS DD DISP=SHR,DSN=&OPTLIB(&ENFCMDS) //SYSPRINT DD SYSOUT=X
    • SPNPAR
      n
      Specifies a symbolic for a CAIENF parameter member. Change
      n
      to the next available sequential number in the list of parameter files.
    • ndvspawn
      Specifies the spawn parameter file. This member contains the CAICCI SERVICE and PROCESS statements. The SERVICE statement identifies the
      CA Endevor
      API. The PROCESS statement identifies the JCL procedure that executes the
      CA Endevor
      API.
  2. Customize the spawn parameters by editing the CAICCI SERVICE and PROCESS statements in the
    ndvspawn
    file. Then save the appropriate file in your site-specific CA90S.PARMLIB as member NDVSPAWN.
    • Keep the statements in the exact format provided, maintaining spaces and column alignments. For more information about defining and using CAICCI statements, see the CA Common Services documentation.
    • For sample CCI definitions for Web Services, see the member WSEWSCCI supplied in the installation source library iprfx.iqual.csiqoptn.
  3. Customize the WSEWSSTC started task procedure. Change the parameters as appropriate for your site.
    • A sample WSEWSSTC procedure is located in the CSIQJCL library that is delivered with
      CA Endevor
      .
    • If you change the WSEWSSTC member name, be sure to update the PROCNAME value in the CCI PROCESS statement of the SPNPARn file to reflect the new procedure name.
    • The wsewsstc value is specified in the JOBNAME parameter of the configuration file.
  4. Copy WSEWSSTC into a PROCLIB defined to JES. WSEWSSTC is initiated as a started task.
  5. If it is your initial installation of these CAICCI components, you do not need to IPL your system after installation. If it is a subsequent installation, you may need to IPL your system. For more information, see the CA Common Services documentation.
Find the
CA Endevor
SYSID
You must know the SYSID of the system where
CA Endevor
is installed. You then need to enter the SYSID in the configuration file. For more information, see Configuration Files.
To find the
CA Endevor
SYSID, open the CCIPARM file member that is located in the library &OPTLIB. Find and make a note of the SYSID parameter.
For example, part of a sample CCIPARM file is shown next. In this sample, the name of the SYSID is A31SENF.
000001 ********************************************* 000002 ** CA EVENT NOTIFICATION/CCI PARAMETER FILE * 000003 ** ---------------------- * 000004 ** CA-ENF/CCI VERSION 1.1 CONTROL OPTIONS * 000005 ********************************************* 000006
SYSID(A31SENF)
000007 PROTOCOL(LU0,A31SENF,01,A31SENF) 000008 PROTOCOL(XES,CCIXES) 000009 PROTOCOL(TCPIP,1202)
Record Your Configuration Values
Record the values that you identified while completing the procedures that are described in this article. Your Web Services administrator uses some of these values to populate the configuration file. Record the following values:
Definition
Source
Default Value
Your Value
Mainframe logon host name:
Specifies the name of the SYSID parameter in your CCIPARM file and
is also used for the configuration HostName parameter.
CCIPARM
none
CA Endevor
mainframe started task procedure:
Specifies the procedure that is associated with the started task that starts
CA Endevor
services when Web Services starts.
The default name for this procedure (WSEWSSTC) may have been
changed to meet site-specific standards.
This value is also used for the configuration file JobName parameter.
NDVSPAWN file
WSEWSSTC
SPNPARn:
Specifies a symbolic for a CAIENF parameter data set.
Systems administrator
SPNPAR2