Unreadable Messages sent from OPS/MVS To NSM Console

book

Article ID: 3894

calendar_today

Updated On:

Products

CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS CA OPS/MVS Event Management & Automation CA SOLVE

Issue/Introduction

Occasionally, when a message is sent to the NSM console with ADDRESS USS "WTO TEXT( ) NODE(NSM node)", the message text is not being translated from EBCIDIC to ASCII, which makes the message unreadable on the NSM console.

Cause

The EBCDIC to ASCII translation occurs if the target node is determined to require ASCII. This decision is based on information in a control block build when the target node becomes known to CCI. When the OPSUSS servers are up before CCI this information will not be available in the control block and the translation will not occur.

Environment

Release: PVLA2.00200-12.3-OPS/MVS-Event Management & Automation-for JES2
Component:

Resolution

A quick bypass is to recycle the OPSUSS servers once CCI is up.


When OPSMVS starts before CCI at IPL set the USSMIN parameter to 0 in the OPS startup member so that no OPSUSS servers will be started. Then automate on the 'CAS9850I CAICCI TCP/IP server ready. PORT $$$$ ADDR %%%%%%' message.

When the CAS9850I message is issued with the PORT number of the CCITCPGW task, set the USSMIN from 0 to a value to start the OPSUSS servers.