Automation Point - MSF Link to Automation Point failing
Article ID: 246686
Updated On:
Products
Issue/Introduction
OPSMVS MSF Links failing.
Attempted Fix Actions:
- Recycled CCI Remote
- Rebooted Server
- Deleted/redefined MSF Links in OPSMVS
Environment
Automation Point
OPS/MVS
Resolution
Use the following DOS commands to investigate connectivity issues:
CCII
It should show something like this:
C:\Users\Administrator>ccii
Oid(MXXTEST000600,OPS/MVS.MXXTEST6 ) Did( , ) type(L)
Oid(VOLSER,W410_SPAWN_SERVER ) Did( , ) type(R)
Oid(VOLSER,MVS_START_SERVER ) Did( , ) type(R)
Oid(VOLSER,OPS/MVS.NAME ) Did( , ) type(R)
Oid(VOLSER,XSDS0980GSVXXE38 ) Did( , ) type(R)
Oid(A11SENF,MIMQUERY/MIMI ) Did( , ) type(R)
Type(L) is the local machine, mostly shown..
Type(R) are the remote machines discovered by CCI and they are in the CCIRMTD.RC specified.
If it's connected properly you also see the OPS/MVS type of connection and to what SSID xxxxE0 of OPS/MVS
you also see something similar to:
RMTCNTRL STATUS
C:\Users\Administrator>rmtcntrl status
SUCCESS: information returned
Sysid State Last Send Time Last Receive Time
--------------------------|---------------------|------------------------------|------------------------------
MXXTEST000600 ACTIVE
A11SENF ACTIVE Jul-26-2022 10:38:22 Jul-26-2022 10:38:23
VOL8 ACTIVE Jul-26-2022 10:38:27 Jul-26-2022 10:38:27
In this case the CCIRMTD.RC file showed:
LOCAL = IPA.NNN.NNN.NNN APPSPRI 32768 startup
REMOTE = XXXXXXX.nnnnn.com TEC2 32768 STARTUP PORT=pppp
REMOTE = XXXXXXX0 SYSB 32768 STARTUP PORT=pppp
REMOTE = XXXXXX4 SYSE 32768 STARTUP PORT=pppp
REMOTE = XXXXXX3 SYS1 32768 STARTUP PORT=pppp
......
In the above case, the following needed to be added to all of the remote statements:
HEARTBEAT=YES RETRY=-1
An additional recommendation is to use the entire IP host names as the first parameter at the REMOTE statement, which helps to avoid connectivity issues.
Feedback
