Skip to main content

Testing

If Mainframe Connector has been able to connect to TCP/IP and complete the outbound connection test to the Bravura Security Fabric server (if requested), the following console messages will be issued:

  PSYNC001I - MAINFRAME CONNECTOR SUBSYSTEM INTERFACE ENABLED.

  PSYNC020I - MAINFRAME CONNECTOR 7.0.3 INTERFACE ENABLED.

  PSYNC113I - LISTENER SOCKET MAXIMUM IS 256

  PSYNC101I - MAINFRAME CONNECTOR LISTENER SERVER TASKS SUCCESSFULLY ATTACHED.

  PSYNC112I - MAINFRAME CONNECTOR LISTENER IS ACTIVE.

Allow an initialization period for the process to complete, however it should rarely take more than a minute from the time the start command was entered until the "ACTIVE" message is issued to the z/OS console.

If Mainframe Connector is unable to establish a connection to the Bravura Security Fabric server, the following messages will be issued:

 *PSYNC960E - UNABLE TO ESTABLISH COMMUNICATION WITH PASSWORD/ID MANAGER

                SERVER.  MAINFRAME CONNECTOR SUBSYSTEM TERMINATING.

  PSYNC961I - CONNECT TO PASSWORD/ID MANAGER SERVER FAILED.

  PSYNC041I - MAINFRAME CONNECTOR TERMINATED.

The network connection has not been established properly. The Bravura Pass server may be inoperative or one of the Mainframe Connector subsystem startup configuration parameters may be incorrect.

A simple test that can be used to help validate the status is to issue a TELNET TSO command to the Bravura Pass server IP address or name using the port number specified in the TCPPORT# Mainframe Connector startup parameter. For example, if your Bravura Pass server name was pwd.manager.server and its pushpass port number was 3333 (note - pushpass is one of the outbound services available on the Bravura Pass server) you could use the following TSO command to test the status:

TELNET pwd.manager.server 3333

This should return a random string of hexadecimal characters. If it does, the most likely cause of the PSYNC960E message is an incorrect key. If the request fails, see the list that follows for possible causes.

The most likely causes for failing to establish connection to the Bravura Security Fabric server are:

  • The KEY value specified in the start parameters does not match the Bravura Pass masterkey specified on the Bravura Pass server.

  • The TCPPORT# value specified in the start parameters does not match the pushpass service port number on the Bravura Pass server.

  • The pushpass service on the Bravura Pass server is disabled or not functioning properly.

  • The DNS value specified in the start parameters is not the correct IP address or server name for the Bravura Pass server.

  • The userid that the Mainframe Connector started task is running under has not been created with proper OMVS segment information.

If problems persist, you may be directed by Bravura Security technical support to enable Mainframe Connector for more detailed diagnostic information. This will be done using the DEBUGLEVEL parameter described in Configuration Process .

In this section: