Can the same SPNPARM for CAP, CMEW and the Web Services be used ?
search cancel

Can the same SPNPARM for CAP, CMEW and the Web Services be used ?

book

Article ID: 46395

calendar_today

Updated On:

Products

Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench

Issue/Introduction

Can the same SPNPARM for Concurrent Action Processing, CMEW and the Web Services be used ?

Environment

Release:
Component: ENTCCM, ENDBAS

Resolution

If  Concurrent Action Processing (CAP), CMEW and/or the Web Services are active, it is strongly recommended to use a separate SPNPARM and STC for each application/interface.

Additional Information

IMPORTANT NOTE:

If SIGNON/NOPASSCHK=SERVICE is set in your Spawn Parameter for CMEW, the PASSWORD check is being bypassed!


Here are the Location of Sample SPNPARM and STC for each application:

For the CONCURRENT ACTION PROCESSING (CAP):

SPAWN PARM (SPNPRM):    IPRFX.IQUAL.CSIQOPTN(CAPCCI)

SPAWNED TASK (STC):      IPRFX.IQUAL.CSIQJCL(ENDEVOR)


For CA Change Manager Enterprise Workbench (CMEW):

SPAWN PARM (SPNPRM):    IPRFX.IQUAL.CSIQOPTN(NDVSPAWN)

SPAWNED TASK (STC):      IPRFX.IQUAL.CSIQJCL(EAPISVR)


FOR THE WEB SERVICES:

SPAWN PARM (SPNPRM):    IPRFX.IQUAL.CSIQOPTN(WSEWSCCI)

SPAWNED TASK (STC):      IPRFX.IQUAL.CSIQJCL(WSEWSSTC)

 

Note:
For any questions or concerns, contact thel CA Endevor Support Team.