CA OPSMVS: Service Desk requests get created even if INITSD is set to NO
Document ID :
Last Modified Date :
Show Technical Document Details
CA OPS/MVS Event Management and Automation
CA OPS/MVS can open CA Service Desk Manager (CA SDM) requests automatically for the following types of problems:
Recoverable product abends
Shortages of process blocks, which are necessary for automation
Failure to respond to internal MSF ping requests
Operator Server Facility (OSF) TSO server transactions that exceed their elapsed time or output line limits
Automated Operations Facility (AOF) rules that fail to complete due to errors
This integration provides your organization with an immediately recorded notification of a problem so that it can be addressed before causing more serious problems. For integration, you need to configure the CAICCI and CAISDI services.
In order to correctly implement this interface from OPSMVS side, it is mandatory to include the following statement in your OPSSPA00 program:
var = OPSPRM("SET","INITSD","YES")
This change takes effect when CA OPS/MVS is recycled. To make this change available to the current CA OPS/MVS region, it is necessary to use OPSVIEW Option 4.1.1 to set the parameter in the current region and recycle the CA OPS/MVS CA Service Desk Integration component, SERVDESK.
This can be done using the following operator command:
Specifies the fourth character of the CA OPS/MVS subsystem ID.
It can happen that, despite INITSD is set to NO, so the Interface is not enabled, when any OPSMVS rule fails, a request is still created in Service Desk which 'contains/describes' the failing rule. So, how to debug this situation in order to find the real cause of this wrong behavior?
Z/OS - CA OPSMVS
Windows - CA Service Desk
Here the steps to follow:
Get into OPSVIEW 4.1.1 and set the DEBUG parm to '0100000000000000'
Issue the F OPSS,RESTART(SERVDESK) command.
below the OPSLOG result :
OPS0322H Service Desk interface restart initiated
OPS0329T SDIN - INITSD is OFF - Service Desk interface terminating
OPS1400H FDCNIO OPSS JES2 NONE NONE
SRV198 ILOG dump required for LOG05Æ0
SRV197 ILOG now recording on LOG05Æ1
Recreate a possible error situation in OPSMVS with the DEBUG Parm set to '0100000000000000' and check the OPSLG for any OPS0329T trace message.
If there isn't any OPS0329T message then this means that OPSMVS is not opening the service desk ticket and this task depends on how OPSMVS has been defined to CAISDI interface, so the ServiceDesk interface set for OPSMVS should be reviewed and not vice-versa
Was this information helpful?