CAICCI Configuration › Peer-to-Peer Communication with Remote Computers › Verify Changes

Verify Changes

To verify that the changes made to CA NSM are working, issue the following command on your remote CA NSM distributed computer:

ccii

The z/OS sysid appears in this list. It can take a minute to get the connection, so wait before issuing the command. If it does not appear, verify:

• Is the CCISSLGW task active on z/OS?

  Yes—Check the SYSPRINT for a connection message from the NT computer. This example is a sample ccirmtd.rc file on a Windows computer:

  LOCAL = BARNA03W2K BARNA03W2K 32768 startup ALIAS=BARNA03W
  REMOTE = 141.202.204.93 a93s 32768 startup PORT=7000
  REMOTE = 141.202.36.71 a71senf 32768 startup PORT=7000
  REMOTE = usilca11 a11senf 32768 startup PORT=7000
  REMOTE = 141.202.204.97 a97s 4096 startup PORT=7000
  

  Using this example, you can expect to see the following message on mainframe hostname usilca11:

  CAS9603I - CAICCI A11SENF  CONNECTED TO CAICCI BARNA03W
  

  No—Check that the CAICCI PARMs contain a protocol statement:

  PROTOCOL(TCPIPGW) 
  

  PROTOCOL(TCPSSLGW)
  

• Look at the ccirmtd.rc file in your NT NSM/caiusr directory. There is an entry for the z/OS computer. The entry looks like:

  REMOTE = hostname ccisysid 32768 startup PORT=portnumber
  

  hostname specifies the TCP/IP name or ipaddress for the z/OS computer, ccisysid specifies the SYSID of the z/OS computer, and portnumber specifies the port number from the CAS9850I message.

  Correct any mistakes and recycle CAICCI remote again.

  You can obtain these z/OS computer values by inspecting the CCISSLGW started task JOBLOG, and by issuing the following z/OS console command:

  ENF DISPLAY,SYSID
  

• Are there any active receivers on z/OS? Issue the following console command to see what local receivers are available:

  F ENF,DISPLAY,RECEIVER
  

  Example display:

  CAS9626I - CAICCI SUBSYSTEM IS OPERATIONAL
  CAS9701I - CCI # RCVRS(00000009) LOCAL(00000009) REMOTE(00000000)
  CAS9700I - +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  CAS9702I - CCI RESOURCE RECEIVER(#A93S     CA-TOP-SECRET       )
  CAS9703I - CCI RESOURCE SENDER(                              )
  CAS9704I - CCI RESOURCE OWN(A93S    ) RCVI(00000001) SND(00000000) T(L)
  CAS9707I - CCI RESOURCE ROUT(Y) DOLRI(2003.300) TOLRI(09:16:51.62) D(N)
  CAS9708I - CCI RESOURCE QUE(Y)  DOLSI(2003.300) TOLSI(09:16:51.62)
  CAS9700I - +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  CAS9702I - CCI RESOURCE RECEIVER(@A93S     W410_SPAWN_SERVER   )
  CAS9703I - CCI RESOURCE SENDER(@A93S     SPAWN_INQY_SERVICES )
  CAS9704I - CCI RESOURCE OWN(A93S    ) RCVI(00000003) SND(00000002) T(L)
  CAS9707I - CCI RESOURCE ROUT(Y) DOLRI(2003.300) TOLRI(12:54:18.47) D(N)
  CAS9708I - CCI RESOURCE QUE(N)  DOLSI(2003.300) TOLSI(12:52:11.72)
  CAS9700I - +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  CAS9702I - CCI Resource Receiver(#USI273ME CA_STARUNIX_SERVER  )
  CAS9703I - CCI Resource Sender(                              )
  CAS9704I - CCI Resource Own(USI273ME) RcvI(00000001) Snd(00000000) T(L)
  CAS9707I - CCI Resource Rout(Y) DOLRI(2003.300) TOLRI(16:11:40.36) D(N)
  CAS9708I - CCI Resource Que(Y)  DOLSI(2003.300) TOLSI(16:11:40.36)  
  CAS9700I - +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  CAS9702I - CCI RESOURCE RECEIVER(#A93S     CAI_OPR_DAEMON      )      
  CAS9703I - CCI RESOURCE SENDER(                              )        
  CAS9704I - CCI RESOURCE OWN(A93S    ) RCVI(00000002) SND(00000001) T(L)
  CAS9707I - CCI RESOURCE ROUT(Y) DOLRI(2003.300) TOLRI(15:33:10.06) D(N)
  CAS9708I - CCI RESOURCE QUE(Y)  DOLSI(2003.300) TOLSI(15:33:10.03)    
  

  Important! Check for CAI_OPR_DAEMON and CA_STARUNIX_SERVER on the list of receivers. For Event Management running on z/OS to communicate with a CA NSM running on a distributed platform, these two receivers must be present.