How Common Services CCI concepts applies to CA OPS/MVS and CA Automation Point September, 2014

Copyright © 2012 CA. All rights reserved. How Common Services (CCS) CCI concepts applies to CA OPS/MVS (OPS/MVS) and CA Automation Point (AP). AGENDA Basic Common Services CCI concepts How to define and activate MFS Links in OPS/MVS How to configure CCI and MFS links in AP Troubleshooting CCI on the Mainframe Troubleshooting CCI on the PC Summary September 19, 2018 Copyright © 2012 CA. All rights reserved.

Basic Common Services CCI concepts What is CCI? CCI stands for Common Communications Interface. Why do I need it? It is important because it enables a bi-directional communication between CA Technologies applications. Products like OPS/MVS and AP use it running across multiple Mainframe LPARs and/or between distributed servers. What mainframe started tasks are involved when I am using CCI? ENF and CCITCPGW What parameters should I look for in the mainframe ENF started task for cross LPAR communications and where? Look at the output produced by the started task ENF for the control statements: SYSID, PROTOCOL, NODE and CONNECT What are the Mainframe CCI key parameters that enable communications from the AP product to the mainframe? Look at the CCI SYSID, the PROTOCOL(TCPIPGW) control statements and the CCITCPGW Started Task IP address and port number to use. September 19, 2018 Copyright © 2012 CA. All rights reserved.

CCI ENF parms: SYSID, PROTOCOL, NODE, CONNECT SYSID defines a name for the local CAICCI system. One through eight character identifier that is unique throughout the CAICCI network. This parameter is required, for example: SYSID(A97SYSID). Also look at the mainframe ENF STC DDNAME in the ENFPARMS under the concatenation for the CCI parm symbolic. PROTOCOL(protocol,netparm,retry,sysid,maxru,start/stop) The PROTOCOL control option is used to specify the communications protocol that is supported by this local host node and its associated network parameters to access remote CAICCI nodes. Example: PROTOCOL(TCPIPGW,1721,1,USI273ME) Default: retry=10, maxru=4096, start/stop=START/SHUT. NODE(protocol,netparm,retry,sysid,maxru,start/stop,netparm2) The NODE control option is used to define a remote CAICCI node to the local host. Example: NODE(TCPIPGW,141.202.1.114:1721,1) Default: retry=10, maxru=4096, start/stop=START/SHUT. CONNECT This control option connects one or more remote CAICCI nodes (previously defined by a GATEWAY or NODE control option) to the local host. The unique one through eight character identifier of the remote CAICCI system to be connected. A maximum of seven CAICCI SYSIDs can be connected using a single CONNECT statement. Example: CONNECT(A73CVC01,A93CVC01) September 19, 2018 Copyright © 2012 CA. All rights reserved.

What is a OPS/MVS Multi-System Facility (MSF) Link ? What is a MSF link? The Multi-System Facility (MSF) extends the facilities of CA OPS/MVS into the multiple-CPU and multiple-site environment. The MSF establishes VTAM, XCF, or TCP/IP sessions between copies of CA OPS/MVS, permitting any copy to issue a command to any other copy and to receive its response. MSF supports the cross-system communication services provided by the Common Communications Interface (CCI). It is one of the CA Common Services for z/OS. MSF Links can also be defined via VTAM definitions. For the purpose of this document, the CCI TCP/IP Gateway protocol was used for cross LPAR and for Distributed Systems to Mainframe communications. The MSF Links also provides the connection to the AP product through a TCP/IP connection using the CCI services. September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to define MSF Links on OPS/MVS ? Define one or multiple MSF links to OPS/MVS via these parameters : Copy the sample MSFINIT member from the library hlq.CCLXSAMP to hlq.CCLXEXEC and add the following control statements MSF ids: address OPSCTL /* Host commands to OPSCTL */ "MSF DEFINE MSFID(MSF_Link1) APPLID(CCI_SYSID_1) CCI" "MSF DEFINE MSFID(MSF_Link2) APPLID(CCI_SYSID_2) CCI" “MSF DEFINE MSFID(MSF_Link3) APPLID(CCI_SYSID_3) AP” Uncomment the following line: /* call InitMSF */ Uncomment the call of MSFINIT at the bottom of the REXX OPSTART2 so that MSF is automatically started at OPS initialization. Uncomment the following line: /*call MSFINIT*/ Set the OPS/MVS parameters to enable MSF to run under CCI. Edit your current active member from hlq.CCLXEXEC(OPSSPAxx) and include the following lines: T = OPSPRM_Set("INITMSF","YES") T = OPSPRM_Set("INITCCI","YES") T = OPSPRM_Set("MSFNONVTAMONLY","YES") September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to activate MSF links in OPS/MVS ? Recycle the OPSMAIN started task Via a OPS/REXX program issue a WTO message: Address WTO "TEXT('This is a test message from system XXXX to system YYYY') MSGID(TEST001) SYSTEM(MSF_Link1)" Confirm the MSF Links are available and active. Find the following messages in SYSLOG or OPSLOG (OPSVIEW panel 4.2) :   OPS3487O MSF HAS ESTABLISHED COMMUNICATION WITH CAICCI OPS3500I MSF NOW ACTIVE OPS3504I SYSTEM ID SYSID WILL BE SENT AN CCI SESSION ACTIVATE REQUEST OPS3092H READY OPS3504I SYSTEM ID SYSID - ACCEPTING CCI SESSION ACTIVATE REQUEST OPS3486O MSF/CCI system SYSID IS NOW ACTIVE - hh.mm.ss September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to display MSF Links: use OPSVIEW (4.2) The Local and Remote MFS Links status in the OPSVIEW of system XE38 September 19, 2018 Copyright © 2012 CA. All rights reserved.

Establishing MSF Links between OPS/MVS and AP When establishing a connection between a Mainframe LPAR and an AP server running under a distributed system, it’s recommended not to code a NODE and CONNECT control statement for the LPAR in the ENFPARMS DD concatenation of the ENF Started Task. It is recommended to let the connection to be established and managed by the distributed system running CCIPC. This system is identified by the REMOTE control statement in the CCIRMTD.RC file. September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to configure CCI and MSF Nodes (Links) in AP ? Open the Windows Start Menu and click on Configuration Manager. Expand Expert Interface -> Automation as shown below. September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to configure CCI and MSF Nodes (Links) in AP ? Click CA OPS/MVS EMA September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to configure CCI and MSF Nodes (Links) in AP ? Click the CCI Settings Button September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to configure a remote node and a local CCI name ? Enter the Local CCI name and Click the Edit button to configure remotes September 19, 2018 Copyright © 2012 CA. All rights reserved.

Edit CCIRMTD.RC File in AP LOCAL = TCP/IP_name CCI_name buffersize startup_options [alias_options] port_options retry_interval REMOTE = TCP/IP_name CCI_name buffersize startup_options [alias_options] [heartbeat_options] port_options retry_interval September 19, 2018 Copyright © 2012 CA. All rights reserved.

Edit CCIRMTD.RC File in Automation Point LOCAL = TCP/IP_name CCI_name buffersize startup_options [alias_options] port_options retry_interval Definitions: TCP/IP_name: host name or IP address of the AP Server CCI name: The local CCI Sys ID (defined in previous dialog) REMOTE = TCP/IP_name CCI_name buffersize startup_options [alias_options] [heartbeat_options] port_options retry_interval TCP/IP_name: host name or IP address of the remote mainframe LPAR CCI_name: SYSID of the LPAR September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to view available MSF Nodes (Links) in AP ? The available MSF nodes will be shown, as below, when your CCI link has been established with the remotes specified in your CCIRMTD.RC file. September 19, 2018 Copyright © 2012 CA. All rights reserved.

How to Select MSF Nodes (Links) in AP Select the MSF Nodes and they will appear in the ‘Selected MSF nodes’ list as shown below. You can then close this dialog. September 19, 2018 Copyright © 2012 CA. All rights reserved.

Troubleshooting for Mainframe CCI Check the ENF task for the following messages and make sure first that the CAICCI subsystem is fully operational: CAS9620I - CAICCI Subsystem initializing - CAS9626I - CAICCI Subsystem is operational The following messages should help you determine what is the correct CCI SYSID you should be using: CAS9214I - CA-ENF Command: SYSID(xxxxxxxx) - CAS9603I - CAICCI - Local SYSID has been updated Also verify that you have valid NODE and CONNECT pairs control statements for your other LPARs: CAS9214I - CA-ENF Command: NODE(…etc. - CAS9603I - CAICCI NODE entry has been Created CAS9214I - CA-ENF Command: CONNECT(.. etc. - CAS9603I - CAICCI - CONNECT has been Processed A valid PROTOCOL statement must be used and the same port number should be used across all your LPARs: CAS9214I - CA-ENF Command: PROTOCOL(TCPIPGW,1721) - CAS9603I - CAICCI PROTOCOL has been created Check the CCITCPGW started task for messages that a valid Hostname/IP address and Port are being used: CAS9850I - Port = 1721 - CAS9850I - Addr = mainframe_hostname_or_IP_address Make sure no CONNECT statements are coded for the AP Server. It is recommended that sessions are controlled from the distributed server via the REMOTE statement located in the CCIRMTD.RC file. The preferred CCI protocol to establish MSF Links is the CCI Gateway protocol implemented via TCP/IP. September 19, 2018 Copyright © 2012 CA. All rights reserved.

Troubleshooting CCI on the PC Try issuing the following command at a DOS prompt: c:>ccicntrl start You should see the following results: Starting Service "CA-Unicenter (Transport)“ Started Service "CA-Unicenter (Transport)" Starting Service "CA-Unicenter (NR-Server)" Started Service "CA-Unicenter (NR-Server)" Starting Service "CA-Unicenter (Remote)" Started Service "CA-Unicenter (Remote)" September 19, 2018 Copyright © 2012 CA. All rights reserved.

Troubleshooting CCI on the PC When you enter this command: c:>ccicntrl status You should see the following results: Service "CA-Unicenter (Transport)", STATUS is "Running" Service "CA-Unicenter (NR-Client)", STATUS is "Not Installed" Service "CA-Unicenter (NR-Server)", STATUS is "Running" Service "CA-Unicenter (Remote)", STATUS is "Running" Check to see what results do you get from each. September 19, 2018 Copyright © 2012 CA. All rights reserved.

Troubleshooting CCI on the PC Enter this command to verify your CCI communication: C:>ccii You should see OID output statements for both the local and remotes that are defined in your ccirmtd.rc file: Local: Oid(APPSRVR,CAI_OPR_DAEMON ) Did( , ) type(L) Oid(APPSRVR,OPS/MVS.APPSRVR ) Did( , ) type(L) Remote: Oid(A11SENF,OPS/MVS.OPS11K ) Did( , ) type(R) Oid(A11SENF,OPS/MVS.OPS11L ) Did( , ) type(R) Below is what you get when you run this status command: C:\Documents and Settings\Administrator>rmtcntrl status SUCCESS: (information returned) Sysid State Last Send Time Last Receive Time ----------------|----------------------|-------------------------------|------------------------------ A31SENF ACTIVE Mar-14-2013 09:49:57 Mar-14-2013 09:50:30 A11SENF ACTIVE Mar-14-2013 09:49:58 Mar-14-2013 09:50:31 September 19, 2018 Copyright © 2012 CA. All rights reserved.

Troubleshooting CCI on the PC You should review the ccilog_mmddyyy.txt file. The most recent log file is probably what you want. You can find these log files in this default path: C:\Program Files (x86)\CA\CA_APPSW September 19, 2018 Copyright © 2012 CA. All rights reserved.

Copyright © 2012 CA. All rights reserved. Summary CA Common Services’ CCI is necessary to connect applications Automation Point and OPS/MVS. Common Communications Interface (CCI) provides protocols to allow bi-directional communication between Mainframe LPARs and/or between distributed servers. OPS/MVS uses MSF Links and the CCI TCPIP Gateway provided by the Common Communications Interface (CCI). The VTAM protocol is also supported. Automation Point uses MSF nodes (Links) and the CCI TCPIP Gateway protocol provided by the Common Communications Interface (CCI) for Mainframe communications. CCI troubleshooting information is available for both Mainframe and Distributed Systems. September 19, 2018 Copyright © 2012 CA. All rights reserved.