Messages

Explanation

The Mainframe Connector initialization process has completed. The Mainframe Connector subsystem is up and fully functional.

System Action

Mainframe Connector processing begins.

Operator Response

None.

System Programmer Response

None.

Explanation

The MODIFY command interface to Mainframe Connector was enabled as part of Mainframe Connector initialization. Mainframe Connector is now capable of accepting MODIFY and STOP command requests.

System Action

Mainframe Connector continues initialization.

Operator Response

None.

System Programmer Response

None.

Explanation

A STOP MFC command was issued and Mainframe Connector has recognized the request.

System Action

Mainframe Connector termination begins.

Operator Response

None.

System Programmer Response

None.

Explanation

An active Mainframe Connector subsystem has been disabled as the result of a STOP MFC command.

System Action

Mainframe Connector continues with termination.

Operator Response

None.

System Programmer Response

None.

Explanation

Termination of Mainframe Connector has been requested through a STOP MFC command. The Mainframe Connector command processing subtask is being terminated as a result of the STOP command.

System Action

Mainframe Connector continues with termination.

Operator Response

None.

System Programmer Response

None.

Explanation

Termination of Mainframe Connector has been requested through a STOP MFC command. The Mainframe Connector command processing subtask has been successfully terminated.

System Action

Mainframe Connector continues with termination.

Operator Response

None.

System Programmer Response

None.

Explanation

A STOP MFC command was issued and Mainframe Connector has shutdown successfully.

System Action

Mainframe Connector has ended.

Operator Response

None.

System Programmer Response

None.

Explanation

A Mainframe Connector subsystem function routine is currently active while Mainframe Connector is attempting to terminate.

System Action

Mainframe Connector will wait for up to two minutes for the active function routine to complete. If the active function routine has not completed in this wait period, Mainframe Connector will continue with termination.

Operator Response

None.

System Programmer Response

None.

Explanation

A Mainframe Connector subsystem function routine is currently active while Mainframe Connector is attempting to terminate.

System Action

Message PSYNC042I has been previously issued indicating an active Mainframe Connector function routine. The active function routine has not completed in two minutes and Mainframe Connector will continue with termination processing.

Operator Response

None.

System Programmer Response

None.

Explanation

The Mainframe Connector listener server has been successfully created.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

An abend has occurred in one of the server subtasks. An internal restart of the server subtask environment was successful.

System Action

None.

Operator Response

If the message persists, contact the system programmer.

System Programmer Response

If the cause of the subtask abend cannot be determined and the condition persists, contact Bravura Security for technical support.

Explanation

The Mainframe Connector listener failed to bind to the socket specified on the LISTENPORT# start parameter.

System Action

The bind failure code indicates that the port is currently in use and Mainframe Connector will try to bind every two seconds for a period of one minute.

Operator Response

If the message persists, contact the system programmer.

System Programmer Response

If the Mainframe Connector listener fails to bind to the specified port, determine if the port is in use by another application or if it has been reserved for use elsewhere.

Explanation

The Mainframe Connector listener has successfully activated and is waiting for incoming requests.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

The Mainframe Connector listener socket maximum has been set to the value specified by ’nnn’.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

An error occurred in the main listener task for Mainframe Connector . The main listener task is unable to communicate on the TCP/IP network.

System Action

Mainframe Connector will attempt to re-establish communication with TCP/IP.

Operator Response

Notify the system programmer.

System Programmer Response

Determine if there are any problems with TCP/IP. The most likely cause of this message is that the TCP/IP stack has been terminated. If this message has been issued and the TCP/IP stack appears functional, contact Bravura Security for technical support.

Explanation

Termination of Mainframe Connector has been requested through a STOP MFC command. The Mainframe Connector listener subtask is being terminated as a result of the STOP command.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

Termination of Mainframe Connector has been requested through a STOP MFC command. The Mainframe Connector concurrent listener subtasks are being terminated as a result of the STOP command.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

The Mainframe Connector concurrent server listener subtasks have terminated successfully.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to stop Mainframe Connector is in progress. Shutdown processing has recognized the existence of a listener subtask environment and the associated task is being terminated.

System Action

Mainframe Connector is terminating its subtask environment. There may be requests currently being processed for a Bravura Pass and/or Bravura Identity server. These requests will be allowed to complete or are gracefully terminated (userid or group list requests) and as a result, listener task termination may take upwards of a minute to complete.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to stop Mainframe Connector is in progress. The listener subtask environment has been terminated.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

The Mainframe Connector transparent listener has detected a connection loss with the TCP/IP stack and communication will attempt to be re-established.

System Action

The Mainframe Connector transparent listener will attempt to dynamically reconnect to the TCP/IP stack.

Operator Response

Notify the system programmer.

System Programmer Response

Investigate the cause of the problem. The output from the Mainframe Connector subsystem should contain more information regarding the error condition. If the cause of the error cannot be determined, contact Bravura Security for technical support.

Explanation

The creation of the Mainframe Connector concurrent listener environment has failed.

System Action

The Mainframe Connector subsystem will terminate.

Operator Response

Attempt to restart Mainframe Connector and notify the system programmer of the error condition.

System Programmer Response

Investigate the cause of the problem. The output from the Mainframe Connector subsystem should contain more information regarding the error condition. If the cause of the error cannot be determined, contact Bravura Security for technical support.

Explanation

The Mainframe Connector server listener process has failed.

System Action

The Mainframe Connector subsystem will terminate.

Operator Response

Attempt to restart Mainframe Connector and notify the system programmer of the error condition.

System Programmer Response

Investigate the cause of the problem. The output from the Mainframe Connector subsystem should contain more information regarding the error condition. If the cause of the error cannot be determined, contact Bravura Security for technical support.

Explanation

An unrecoverable error has occurred in a Mainframe Connector listener parallel function task. This error has rendered the parallel Mainframe Connector listener component inoperative. The errno value ’nn’ further describes the offending condition.

System Action

The Mainframe Connector subsystem will not accept incoming client connection requests.

Operator Response

Notify the system programmer of the error condition. If the problem persists, Mainframe Connector will need to be restarted.

System Programmer Response

Investigate the cause of the problem. The output from the Mainframe Connector subsystem should contain more information regarding the error condition. If the cause of the error cannot be determined, contact Bravura Security for technical support.

Explanation

A password change request has been recognized by Mainframe Connector and validation to the Bravura Pass server has been initiated.

System Action

An attempt will be made to contact the Bravura Pass server to validate the current password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

None.

Explanation

A password change request has been recognized by Mainframe Connector and validation from the Bravura Pass server is pending.

System Action

An attempt has been made to contact the Bravura Pass server to validate the current password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

None.

Explanation

A password change request has been recognized by Mainframe Connector and validation from the Bravura Pass server has indicated that the password change is appropriate.

System Action

The Bravura Pass server has indicated that the requested password change is acceptable. The MVS security product should be allowed to make the password change. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

None.

Explanation

A password change request has been recognized by Mainframe Connector and validation from the Bravura Pass server did not occur within the Mainframe Connector timeout limit.

System Action

The current request to Mainframe Connector has timed out. The MVS security product will continue with the password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

None.

Explanation

A password change request has been recognized by Mainframe Connector and the Bravura Pass server has indicated that the current password is not acceptable.

System Action

The current password change request has failed Mainframe Connector validation. The MVS security product will fail this password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

None.

Explanation

A password change request has been recognized by Mainframe Connector but a failure occurred in establishing the socket connection to the Bravura Pass server.

System Action

The Mainframe Connector subsystem was unable to establish a socket connection with the Bravura Pass server. The MVS security product should proceed with the password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

A determination needs to be made regarding the status of the Bravura Pass server. The Bravura Pass server may be inoperative or network connectivity to the Bravura Pass server may have been severed.

Explanation

A password change request has been recognized by Mainframe Connector but a failure occurred in the validation process.

System Action

An unknown failure occurred during the password validation process. The MVS security product should proceed with the password change request. This message will be issued to the terminal of the user making the password change request unless the password change request is occurring in a background job. This message will be issued to the background job log in that case.

Operator Response

None.

System Programmer Response

The cause of the problem needs to be investigated. This error message should rarely, if ever, be issued. If the cause of the problem cannot be determined, contact Bravura Security technical support.

Explanation

A request has been make to change a password. The Mainframe Connector subsystem is not currently active and Mainframe Connector will not process this request.

System Action

The MVS security product will continue with the password change request with no influence from Mainframe Connector .

Operator Response

If this message is reported or detected, validate the status of the Mainframe Connector subsystem. If it is not currently active, the message has been issued appropriately. Determine if Mainframe Connector should be activated. If Mainframe Connector is active, report this condition to the system programmer for further investigation.

System Programmer Response

If this message is issued while the Mainframe Connector subsystem is active, it is possible that the Mainframe Connector subsystem control block or function routines have become corrupted. Attempt to restart Mainframe Connector . If the problem persists, contact Bravura Security technical support for assistance.

Explanation

A MODIFY MFC command has been issued but the modify request is not a recognized Mainframe Connector request.

System Action

Mainframe Connector continues normal operation.

Operator Response

A valid modify command should be entered.

System Programmer Response

None.

Explanation

A MODIFY MFC,TIMEOUT=nnn command has been issued but the value specified for nnn is not valid.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for nnn. Valid values for nnn are 20 – 120.

System Programmer Response

None.

Explanation

A MODIFY MFC,D=value or MODIFY MFC,DISPLAY=value command was issued but value was not PARMS.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. The only valid entry for value is PARMS.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENMAX=value command was issued but value was not in the range 1 – 99.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. Values for value can be in the range 1 – 99.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENMAX=value command was issued but value is equal to the current LISTENMAX value.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value that is different from the current setting. Values for value can be in the range 1 – 99.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENONLY=value command was issued but value was not YES or NO.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. Valid values are YES or NO.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTCHECK=value command was issued but value was not INOUT, INBOUNDONLY, or OUTBOUNDONLY.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. Valid values are INOUT, INBOUNDONLY, or OUTBOUNDONLY.

System Programmer Response

None.

Explanation

A MODIFY MFC,ENCRYPTION=value command was issued but value was not IDEA or AES.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. Valid values are IDEA or AES.

System Programmer Response

None.

Explanation

A MODIFY MFC,ENTROPYFALLBACK=value command was issued but value was not YES or NO.

System Action

Mainframe Connector continues normal operation.

Operator Response

Re-enter the command with a valid value for value. Valid values are YES or NO.

System Programmer Response

None.

Explanation

A MODIFY MFC,SOCKETCLOSEWAIT=value command has been issued but value was not a numeric in the range 0 - 5.

System Action

The SOCKETCLOSEWAIT is left unchanged.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,OUTBOUNDPWCASE=value command has been issued but value was not ASIS, LOWER or UPPER.

System Action

The OUTBOUNDPWCASE is left unchanged.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,TIMEOUT=nnn command has been issued and the Mainframe Connector TIMEOUT value has been reset.

System Action

The Mainframe Connector TIMEOUT value has been changed to nnn.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENMAX=nn command has been issued and acknowledged by Mainframe Connector .

System Action

Mainframe Connector is attempting to update internal tasks to support the new LISTENMAX value, nn.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENONLY=value command has been issued and Mainframe Connector has successfully updated the LISTENONLY status.

System Action

Mainframe Connector has updated the LISTENONLY value to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTENMAX=nn command has been issued and Mainframe Connector has successfully updated the LISTENMAX status.

System Action

Mainframe Connector has updated the LISTENMAX value to nn.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,CONNECTTEST command has been issued and Mainframe Connector is attempting a handshake connection with the Bravura Pass server.

System Action

Mainframe Connector is attempting a test connection with the Bravura Pass server.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,CONNECTTEST command has been issued and Mainframe Connector has completed a successful test connection with the Bravura Pass server.

System Action

Mainframe Connector successfully completed a test connection with the Bravura Pass server.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,LISTCHECK=value command has been issued and Mainframe Connector has successfully updated the LISTCHECK option.

System Action

Mainframe Connector has updated the LISTCHECK value to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,DEBUGLEVEL=value command has been issued but value was not a numeric in the range 0 - 9.

System Action

The DEBUGLEVEL is left unchanged.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,DEBUGLEVEL=value command has been issued and the Mainframe Connector DEBUGLEVEL has been reset to value.

System Action

The DEBUGLEVEL has been changed to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,DEBUGLEVEL=value command has been issued and the requested value exceeds the maximum allowable value as specified in the DEBUGMAX parameter.

System Action

The DEBUGLEVEL has been changed to the maximum value permitted by the DEBUGMAX parameter.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,ENCRYPTION=value command has been issued and the Mainframe Connector ENCRYPTION has been reset to value.

System Action

Mainframe Connector has updated the ENCRYPTION value to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,ENTROPYFALLBACK=value command has been issued and the Mainframe Connector ENTROPYFALLBACK has been reset to value.

System Action

Mainframe Connector has updated the ENTROPYFALLBACK value to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,SOCKETCLOSEWAIT=value command has been issued and the Mainframe Connector SOCKETCLOSEWAIT has been reset to value.

System Action

The SOCKETCLOSEWAIT has been changed to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A MODIFY MFC,OUTBOUNDPWCASE=value command has been issued and the Mainframe Connector OUTBOUNDPWCASE has been reset to value.

System Action

The OUTBOUNDPWCASE has been changed to value.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to dynamically deactivate or reactivate one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) has successfully completed.

System Action

Mainframe Connector has updated the status for the corresponding list.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to dynamically add a userid or groupid entry to one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) detected that the requested add entry already existed in the corresponding table.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to dynamically delete a userid or groupid entry from one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) detected that the requested delete entry did not exist in the corresponding table.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

A request to dynamically reactivate an INLIST or EXLIST detected that the opposing list was already active.

System Action

The request is rejected. INLIST and EXLIST can not be active simultaneously.

Operator Response

None.

System Programmer Response

None.

Explanation

The DDNAME indicated by ddname has more than 32 DD statements in its concatenation.

System Action

If a dynamic reload request is performed for the indicated DDNAME, ddname, only the first 32 DD statements will be processed.

Operator Response

Notify the system programmer of this message.

System Programmer Response

Assess the datasets used in the concatenation for the indicated DDNAME and attempt to limit the concatenation to 32 DD statements. If more than 32 DD statements are used, the results of dynamic reload requests will not deliver the expected results.

Explanation

A request to dynamically deactivate or reactivate one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) has determined that the requested list does not exist.

System Action

The requested action is bypassed.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to reload one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) from the JCL defined datasets.

System Action

Mainframe Connector will attempt to create an updated in-storage list from the JCL defined datasets.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to reload one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) from the JCL defined datasets and the request has successfully completed.

System Action

Mainframe Connector has created an updated in-storage list from the JCL defined datasets.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to reload one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) from the JCL defined datasets and the requested DDNAME did not exist in the startup JCL or an opposing list is already active.

System Action

Mainframe Connector rejects the request.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to reload one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) from the JCL defined datasets and the request failed to complete successfully.

System Action

Mainframe Connector rejects the request.

Operator Response

Notify the system programmer.

System Programmer Response

The most likely cause of a reload failure would be a problem in dynamic allocation. Determine if message PSYNC385E has also been issued and if so, check the dynamic allocation error codes in the message. If you are unable to determine the cause of the reload failure, contact Bravura Security technical support for assistance.

Explanation

A dynamic allocation error has occurred. The request type ftype indicates the type of the request. If ftype is PALLOC, this indicates that a failure occurred attempting to allocate a member of a PDS. If ftype is FALLOC, this indicates that a failure occurred attempting to allocate a sequential dataset. If ftype is CALLOC, this indicates that a failure occurred attempting to concatenate a dataset into a DDNAME allocation. If ftype is UALLOC, this indicates that a failure occurred unallocating a DDNAME. The value in errcd and infcd provide information regarding the nature of the dynamic allocation failure.

System Action

Mainframe Connector rejects the request.

Operator Response

Notify the system programmer.

System Programmer Response

This condition is unexpected. Contact Bravura Security technical support for assistance.

Explanation

A request has been made to add an entry to one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) and the request has successfully completed.

System Action

Mainframe Connector has created an updated in-storage list that includes the add request entry.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to delete an entry from one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) and the request has successfully completed.

System Action

Mainframe Connector has created an updated in-storage list that removes the delete request entry.

Operator Response

None.

System Programmer Response

None.

Explanation

A request has been made to add an entry to one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) and an environment problem prevented the entry from being added.

System Action

Mainframe Connector has not updated the specified in-storage list.

Operator Response

Notify the system programmer.

System Programmer Response

Mainframe Connector is most probably experiencing a storage availability problem. If the cause of the problem can not be determined, contact Bravura Security technical support for assistance.

Explanation

A request has been made to delete an entry from one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) and an environment problem prevented the entry from being deleted.

System Action

Mainframe Connector has not updated the specified in-storage list.

Operator Response

Notify the system programmer.

System Programmer Response

Mainframe Connector is most probably experiencing a storage availability problem. If the cause of the problem can not be determined, contact Bravura Security technical support for assistance.

Explanation

A request has been made to update one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) but the format of the ADD/DEL request is invalid.

System Action

None.

Operator Response

Notify the system programmer.

System Programmer Response

Mainframe Connector Operator Commands provides examples of the correct syntax for ADD/DEL requests.

Explanation

A request has been made to reload one of the in-storage lists (INLIST, EXLIST, or ADMINIDS) from the JCL defined datasets but a valid DDNAME could not be determined.

System Action

None.

Operator Response

Notify the system programmer.

System Programmer Response

Mainframe Connector Operator Commands provides examples of the correct syntax for RELOAD requests. Valid DDNAME’s are INLIST, EXLIST, and ADMINIDS.

Explanation

An abend xxx occurred in the PSNCCMDM subtask.

System Action

Mainframe Connector will attempt to recover. If recovery is successful, Mainframe Connector will continue with normal operation. If recovery is not successful, Mainframe Connector will need to be terminated and restarted.

Operator Response

None.

System Programmer Response

The cause of the abend should be investigated.

Explanation

An abend xxx occurred in the PSNCLDRV subtask.

System Action

Mainframe Connector will attempt to recover. If recovery is successful, Mainframe Connector will continue with normal operation. If recovery is not successful, Mainframe Connector will need to be terminated and restarted.

Operator Response

None.

System Programmer Response

The cause of the abend should be investigated.

Explanation

PSNCCMDM was unable to obtain local working storage.

System Action

Mainframe Connector command processing is terminated.

Operator Response

An attempt should be made to terminate the current Mainframe Connector subsystem. After the current subsystem is terminated, Mainframe Connector should be restarted. Notify the system programmer of the error.

System Programmer Response

Examine Mainframe Connector job log and dump to determine the storage obtain problem.

Explanation

PSNCLDRV was unable to obtain local working storage.

System Action

Mainframe Connector command processing is terminated.

Operator Response

An attempt should be made to terminate the current Mainframe Connector subsystem. After the current subsystem is terminated, Mainframe Connector should be restarted. Notify the system programmer of the error.

System Programmer Response

Examine Mainframe Connector job log and dump to determine the storage obtain problem.

Explanation

PSNCT254 was unable to obtain local working storage.

System Action

Mainframe Connector function routine subtask processing is terminated.

Operator Response

None.

System Programmer Response

Examine Mainframe Connector job log and dump to determine the storage obtain problem.

Explanation

An abend xxx occurred in the PSNCT254 subtask. A z/OS password change event was in progress and password synchronization may not have been successfully performed if this message has been issued.

System Action

Mainframe Connector will attempt to recover. If recovery is successful, Mainframe Connector will continue with normal operation. If recovery is not successful, Mainframe Connector will need to be terminated and restarted.

Operator Response

None.

System Programmer Response

The cause of the abend should be investigated.

Explanation

An entry was being written to the AUDIT dataset but the dataset is full.

System Action

Mainframe Connector continues to function with AUDIT disabled.

Operator Response

None.

System Programmer Response

The current log information should be captured and saved. A new log dataset should be allocated (or a JES spooled dataset should be used) and Mainframe Connector should be restarted.

Explanation

An entry was being written to the AUDIT dataset but an I/O error occurred during the write operation.

System Action

Mainframe Connector continues to function with AUDIT disabled.

Operator Response

None.

System Programmer Response

The current log information should be captured and saved. A new log dataset should be allocated (or a JES spooled dataset should be used) and Mainframe Connector should be restarted.

Explanation

An entry was being written to the SYNCHLOG dataset but the dataset is full.

System Action

Mainframe Connector continues to function with SYNCHLOG logging disabled.

Operator Response

None.

System Programmer Response

The current log information should be captured and saved. A new log dataset should be allocated (or a JES spooled dataset should be used) and Mainframe Connector should be restarted.

Explanation

An entry was being written to the SYNCHLOG dataset but an I/O error occurred during the write operation.

System Action

Mainframe Connector continues to function with SYNCHLOG logging disabled.

Operator Response

None.

System Programmer Response

The current log information should be captured and saved. A new log dataset should be allocated (or a JES spooled dataset should be used) and Mainframe Connector should be restarted.

Explanation

Dataspace creation or logging encountered an error.

Where:

label identifies the source code location of the error

message is one of the following:

’TCBTOKEN’ ERROR - DATASPACE NOT CREATED

DSPSERV CREATE’ ERROR - DATASPACE NOT CREATED

’ALESERV ADD’ ERROR - DATASPACE NOT CREATED

INVALID REQUEST CODE

INVALID RECORD TYPE

INVALID RECORD LENGTH

r15 and r0 are the respective contents

of the return and reason code registers

System Action

Dataspace creation does not proceed and/or logging is disabled.

Operator Response

Report the condition to the system programmer.

System Programmer Response

If no other preceding or accompanying Mainframe Connector or system conditions exist which might explain the error, contact Bravura Security technical support for assistance.

Explanation

An event occurred for which dataspace logging had been requested. The dataspace has been successfully established.

System Action

The event is logged to the dataspace.

Operator Response

None.

System Programmer Response

None.

Explanation

Attaching the PSNCCMDM subtask resulted in a xxxxxxxx failure.

System Action

Mainframe Connector terminates.

Operator Response

Attempt to restart Mainframe Connector . If the problem persists, contact the system programmer.

System Programmer Response

Determine the cause of the xxxxxxxx failure. If the problem cannot be resolved, contact Bravura Security technical support.

Explanation

Attaching the PSNCLDRV subtask resulted in a xxxxxxxx failure.

System Action

Mainframe Connector terminates.

Operator Response

Attempt to restart Mainframe Connector . If the problem persists, contact the system programmer.

System Programmer Response

Determine the cause of the xxxxxxxx failure. If the problem cannot be resolved, contact Bravura Security technical support.

Explanation

The dataset specified in the INLIST DD contains an invalid include list control card in record nnnn.

System Action

Mainframe Connector continues processing with the next INLIST control card.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Check record nnnn in the INLIST dataset. Valid control cards for include list processing are INCLUDEUSER=username and INCLUDEGROUP=grpname.

Explanation

The dataset specified in the EXLIST DD contains an invalid exclude list control card in record nnnn.

System Action

Mainframe Connector continues processing with the next EXLIST control card.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Check record nnnn in the EXLIST dataset. Valid control cards for exclude list processing are EXCLUDEUSER=username and EXCLUDEGROUP=grpname.

Explanation

PARMLIB dataset parameter validation has detected a DEBUGLEVEL parameter statement after a prior valid DEBUGLEVEL statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a DEBUGLEVEL parameter statement. Valid data for DEBUGLEVEL is numeric in the range 0 - 9. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for DEBUGLEVEL.

Explanation

PARMLIB dataset parameter validation has detected a DATASPACE parameter statement after a prior valid DATASPACE statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation detected at least one error condition in the DATASPACE parameter values. Valid parameter values for DATASPACE are SMF, AUDIT, SYNCHLOG, nnnnn where ’nnnnn’ is a decimal number between 1 and 524,288. Dataspace logging will not be enabled. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include appropriate values for DATASPACE.

Explanation

PARMLIB dataset parameter validation has detected a RESETAUTH parameter statement after a prior valid RESETAUTH statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a RESETAUTH parameter statement. Valid values for RESETAUTH are APF or STCID. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for RESETAUTH.

Explanation

PARMLIB dataset parameter validation has detected a REPORTSYSID parameter statement after a prior valid REPORTSYSID statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a REPORTSYSID parameter statement. Valid values for REPORTSYSID are YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for REPORTSYSID.

Explanation

PARMLIB dataset parameter validation has detected a DEBUGMAX parameter statement after a prior valid DEBUGMAX statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a DEBUGMAX parameter statement. Valid data for DEBUGMAX is numeric in the range 0 - 9. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for DEBUGMAX.

Explanation

PARMLIB dataset parameter validation has detected a KEYDISPLAY parameter statement after a prior valid KEYDISPLAY statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a KEYDISPLAY parameter statement. Valid values for KEYDISPLAY are ASIS or MASK. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for KEYDISPLAY.

Explanation

PARMLIB dataset parameter validation has detected a KEYENCRYPT parameter statement after a prior valid KEYENCRYPT statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a KEYENCRYPT parameter statement. Valid values for KEYENCRYPT are YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for KEYENCRYPT.

Explanation

PARMLIB dataset parameter validation has detected a ENCRYPTION parameter statement after a prior valid ENCRYPTION statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for an ENCRYPTION parameter statement. Valid values for ENCRYPTION are IDEA or AES. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for ENCRYPTION.

Explanation

PARMLIB dataset parameter validation has detected an ENTROPYFALLBACK parameter statement after a prior valid ENTROPYFALLBACK statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for an ENTROPYFALLBACK parameter statement. Valid values for ENTROPYFALLBACK are YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for ENTROPYFALLBACK.

Explanation

PARMLIB dataset parameter validation has detected a SOCKETCLOSEWAIT parameter statement after a prior valid SOCKETCLOSEWAIT statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for an SOCKETCLOSEWAIT parameter statement. Valid data for SOCKETCLOSEWAIT is numeric in the range 0 - 5. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for SOCKETCLOSEWAIT.

Explanation

PARMLIB dataset parameter validation has detected an OUTBOUNDPWCASE parameter statement after a prior valid OUTBOUNDPWCASE statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for an OUTBOUNDPWCASE parameter statement. Valid values for OUTBOUNDPWCASE are ASIS, LOWER, or UPPER. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for OUTBOUNDPWCASE.

Explanation

PARMLIB dataset parameter validation has detected a USERIDFASTDEL parameter statement after a prior valid USERIDFASTDEL statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a USERIDFASTDEL parameter statement. Valid values for USERIDFASTDEL are YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for USERIDFASTDEL.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a TSSTARGET parameter statement. Valid values for TSSTARGET are = or *. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for TSSTARGET.

Explanation

An abend has occurred in the Mainframe Connector subsystem address space. The ESTAE recovery routine is determining whether any outstanding events are currently active.

System Action

The ESTAE routine will check outstanding event conditions.

Operator Response

None.

System Programmer Response

None.

Explanation

An abend has occurred in the Mainframe Connector subsystem address space. The ESTAE recovery routine has determined that there is an active function routine.

System Action

The ESTAE routine will post the outstanding function routine WAIT ECB.

Operator Response

None.

System Programmer Response

None.

Explanation

An abend xxx occurred in the Mainframe Connector driver task.

System Action

Mainframe Connector is terminated.

Operator Response

An attempt to restart Mainframe Connector should be made.

System Programmer Response

The cause of the abend should be investigated.

Explanation

An attempt has been made to start a Mainframe Connector subsystem address space but a Mainframe Connector subsystem address space with subsystem name ssss is already active.

System Action

The second Mainframe Connector subsystem address space using subsystem name ssss is terminated.

Operator Response

None.

System Programmer Response

None.

Explanation

Mainframe Connector subsystem address space initialization detected a problem with the specified initialization parameters. The parameters specified in the PARMLIB dataset are incomplete or in error.

System Action

The Mainframe Connector subsystem address space is terminated.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Examine earlier startup message to determine the problem parameter. The PARMLIB dataset must contain a parameter value for DNS, TCPPORT#, KEY, and SUBSYSNAME.

Explanation

PARMLIB dataset parameter validation detected an unrecognized parameter value. Run-time parameters discusses valid parameter values. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Determine the statement that is in error and make appropriate changes.

Explanation

PARMLIB dataset parameter validation has detected a TCPPORT# parameter statement after a prior valid TCPPORT# statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a KEY parameter statement after a prior valid KEY statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a SUBSYSNAME parameter statement after a prior valid SUBSYSNAME statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a TIMEOUT parameter statement after a prior valid TIMEOUT statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a HOSTID parameter statement after a prior valid HOSTID statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a LISTENPORT# parameter statement after a prior valid LISTENPORT# statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected a LISTENMAX parameter statement after a prior valid LISTENMAX statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a TCPPORT# parameter statement. Valid data for TCPPORT# is a numeric value in the range 1–65535. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to an appropriate value within the acceptable range.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a KEY parameter statement. Valid data for KEY is 32 hexadecimal characters (0-9 and A-F). See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to an appropriate value within the defined criteria.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a SUBSYSNAME parameter statement. Valid data for SUBSYSNAME must not exceed four bytes in length. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to an appropriate value within the defined criteria.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a TIMEOUT parameter statement. Valid data for TIMEOUT is numeric in the range 20–120.See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to an appropriate value within the acceptable range.

Explanation

PARMLIB dataset parameter validation has detected no data for a DNS parameter statement. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate DNS value.

Explanation

PARMLIB dataset parameter validation has detected no data for a HOSTID parameter statement. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate DNS value.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a LISTENPORT# parameter statement. Valid data for LISTENPORT# is a numeric value in the range 1–65535. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to an appropriate value within the acceptable range.

Explanation

PARMLIB dataset parameter validation has detected no data for a LISTENMAX parameter statement. Valid data for LISTENMAX is a numeric in the range 1–99. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate DNS value.

Explanation

The parameters specified in the PARMLIB dataset are incomplete or in error. Parameter initialization statements must exist for DNS, TCPPORT#, KEY, SUBSYSNAME, and LISTENPORT#.

System Action

Mainframe Connector startup will be terminated.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Examine the PARMLIB dataset to determine the missing parameter values.

Explanation

Parameter processing detected no TIMEOUT parameter. A default network timeout value of 20 seconds has been activated.

System Action

Mainframe Connector startup will continue.

Operator Response

Report this condition to the system programmer.

System Programmer Response

If a TIMEOUT value greater than 20 seconds is required, a parameter statement should be included in the PARMLIB dataset.

Explanation

Parameter processing detected invalid data for PARMLIB dataset record nnnn.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Examine PARMLIB dataset record nnnn to determine the cause of the error.

Explanation

The values indicated in the message were specified in the PARMLIB dataset parameter initialization statements or represent the status of the indicated influence tables.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

The values indicated in the message are the current values in effect. They may differ from the startup values as a result of dynamic changes to the environment.

System Action

None.

Operator Response

None.

System Programmer Response

None.

Explanation

PARMLIB dataset parameter validation has detected a SMFREC parameter statement after a prior valid SMFREC statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a SMFREC parameter statement. Valid data for SMFREC is a numeric in the range 200–255. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for SMFREC.

Explanation

PARMLIB dataset parameter validation has detected a PASSIVESTART parameter statement after a prior valid PASSIVESTART statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a PASSIVESTART parameter statement. Valid data for PASSIVESTART is YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for PASSIVESTART.

Explanation

PARMLIB dataset parameter validation has detected a LISTENONLY parameter statement after a prior valid LISTENONLY statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a LISTENONLY parameter statement. Valid data for LISTENONLY is YES or NO. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for LISTENONLY.

Explanation

PARMLIB dataset parameter validation has detected a LISTCHECK parameter statement after a prior valid LISTCHECK statement has already been processed. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The redundant parameter statement should be removed from the initialization parameter dataset.

Explanation

PARMLIB dataset parameter validation has detected invalid data for a LISTCHECK parameter statement. Valid data for LISTCHECK is INOUT, INBOUNDONLY, or OUTBOUNDONLY. See message PSYNC932I for more information.

System Action

Parameter validation continues with the next PARMLIB statement.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The parameter should be changed to include an appropriate value for LISTCHECK.

Explanation

Mainframe Connector subsystem address space initialization has determined that a previous copy of the Mainframe Connector subsystem was active and did not perform proper cleanup.

System Action

Mainframe Connector will clean up the remnants of the previous subsystem address space.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Determine why the previous Mainframe Connector address space termination did not do proper cleanup. If no determination can be made as to the cause of the improper cleanup, contact Bravura Security technical support for further assistance.

Explanation

Mainframe Connector subsystem address space initialization has determined that the subsystem name specified in the SUBSYSNAME initialization parameter is already in use by another subsystem. jobname is the name of the Mainframe Connector address space that is attempting initialization

System Action

Mainframe Connector startup will terminate.

Operator Response

Report this condition to the system programmer.

System Programmer Response

The subsystem name specified in the SUBSYSNAME initialization parameter must be unique. Make sure that no other subsystems currently use the subsystem name that is to be used for Mainframe Connector .

Explanation

Mainframe Connector subsystem address space initialization has determined that a previous SSVT can be used for this startup.

System Action

Mainframe Connector continues with initialization.

Operator Response

None.

System Programmer Response

None.

Explanation

Mainframe Connector subsystem address space initialization has determined that an SSCVT entry for the subsystem name specified on the SUBSYSNAME initialization parameter statement does not exist in the MVS SSCVT chain.

System Action

Mainframe Connector will attempt to format a new SSCVT entry and insert it into the current SSCVT chain.

Operator Response

None.

System Programmer Response

None.

Explanation

Mainframe Connector subsystem address space initialization has determined that an SSCVT entry for the subsystem name specified on the SUBSYSNAME initialization parameter statement does not exist in the MVS SSCVT chain. An attempt has been made to dynamically add an SSCVT entry but the attempt to obtain the common area storage required for the SSCVT has failed.

System Action

Mainframe Connector startup will terminate.

Operator Response

Report this condition to the system programmer.

System Programmer Response

Determine if there are any issues with common storage availability, specifically subpool 241. If no issues exist and the problem persists, contact Bravura Security technical support for assistance.

Explanation

The resource manager setup routine determined that an existing PSNCRMGR at address xxxxxxxx would satisfy requirements for this instance of Mainframe Connector .

System Action

Mainframe Connector resource manager initialization continues.

Operator Response

None.

System Programmer Response

None.

Explanation

The resource manager setup routine is loading a new PSNCRMGR at address xxxxxxxx to satisfy requirements for this instance of Mainframe Connector .

System Action

Mainframe Connector resource manager initialization continues.

Operator Response

None.

System Programmer Response

None.

Explanation

The resource manager setup routine encountered a failure while performing operation xxxxxxxx. The return code from the operation was xx.

System Action

Mainframe Connector resource manager setup is discontinued, however, Mainframe Connector system initialization proceeds. In the absence of any further errors, the remainder of system initialization and operation should be unaffected. In the event of subsequent Mainframe Connector abnormal termination of this instance, resource cleanup may be incomplete.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred with the Mainframe Connector started task. If you are unable to determine the cause of the return code indicated by ’xx’, contact Bravura Security technical support for assistance.

Explanation

Mainframe Connector subsystem address space initialization has attempted a connectivity test with the Bravura Security Fabric server. The Mainframe Connector subsystem was unable to contact the Bravura Security Fabric server.

System Action

Mainframe Connector startup will terminate.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The DNS, TCPPORT#, and KEY values should all be checked to verify their accuracy. The Bravura Security Fabric server should be checked to determine if it is available. There must be an available TCP/IP network path between this MVS system and the Bravura Security Fabric server.

Explanation

An attempt was made to establish a dialogue with the Bravura Security Fabric server but the Bravura Security Fabric server did not respond to the request.

System Action

The active request will terminate.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The DNS, TCPPORT#, and KEY values should all be checked to verify their accuracy. The Bravura Security Fabric server should be checked to determine if it is available. The pushpass service must be installed and active on the Bravura Security Fabric server. There must be an available TCP/IP network path between this MVS system and the Bravura Security Fabric server. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

A socket connection was established with the Bravura Pass server but no response was detected.

System Action

The active request will terminate.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The Bravura Pass server may have failed or the pushpass service became unavailable. Network connectivity problems could also cause communication to the Bravura Pass server to terminate. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

PASSIVESTART=YES was specified in the Mainframe Connector start parameters and Mainframe Connector has not successfully test connected with the Bravura Pass server.

System Action

Mainframe Connector will attempt a test connection with the Bravura Pass server every five minutes until a connection is established or until Mainframe Connector is stopped with an operator command.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The Bravura Pass server may not be functional or the pushpass service is unavailable. Network connectivity problems could also cause communication to the Bravura Pass server to fail. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

A MODIFY mfc,CONNECTTEST command was issued and the test connection with the Bravura Pass server failed.

System Action

None.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The Bravura Pass server may not be functional or the pushpass service is unavailable. Network connectivity problems could also cause communication to the Bravura Pass server to fail. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

A password reset request timed out in the subsystem funtion routine (PSNCF254) while waiting for a response from the Bravura Pass server.

System Action

The password reset request continues.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The Bravura Pass server may have failed or the pushpass service became unavailable. Network connectivity problems could also cause communication to the Bravura Pass server to terminate. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

A password reset request experienced a network connection failure.

System Action

The password reset request continues.

Operator Response

Report this condition to the system programmer.

System Programmer Response

A number of factors can contribute to this condition. The Bravura Pass server may have failed or the pushpass service became unavailable. Network connectivity problems could also cause communication to the Bravura Pass server to terminate. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector listener doaccept function routine experienced an error in a select function call. The errno value ’nn’ further describes the offending condition.

System Action

The current inbound listener request terminates.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in select processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector listener doaccept function routine experienced an error in an accept function call. The errno value ’nn’ further describes the offending condition.

System Action

The current inbound listener request terminates.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in accept processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector listener failed to establish a socket connection on the socket specified on the LISTENPORT# Mainframe Connector start parameter.

System Action

The listener function of Mainframe Connector terminates.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in socket processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector listener failed to establish a bind on the socket specified on the LISTENPORT# Mainframe Connector start parameter.

System Action

The listener function of Mainframe Connector terminates.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in bind processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector listener failed to establish a listen status on the socket specified on the LISTENPORT# Mainframe Connector start parameter.

System Action

The listener function of Mainframe Connector terminates.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in listen processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector outbound client failed to establish a socket connection on the socket specified on the TCPPORT# Mainframe Connector start parameter.

System Action

The outbound request returns to the subsystem function caller.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in socket processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector outbound client failed to establish a connection on the socket specified on the TCPPORT# Mainframe Connector start parameter.

System Action

The outbound request returns to the subsystem function caller.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred in connect processing. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector address space has terminated without properly disabling its subsystem.

System Action

The active subsystem function routine has disabled the Mainframe Connector subsystem.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred with the Mainframe Connector started task. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector address space has terminated without properly disabling its subsystem.

System Action

The active subsystem function routine has disabled the Mainframe Connector subsystem.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred with the Mainframe Connector started task. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector address space has terminated without properly disabling its subsystem.

System Action

The active subsystem function routine has disabled the Mainframe Connector subsystem.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred with the Mainframe Connector started task. If you are unable to determine the cause of the message, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector main driver task failed to successfully create the NAME/TOKEN entry associated with this subsystem activation.

System Action

The activation of this Mainframe Connector subsystem is terminated.

Operator Response

Report this condition to the system programmer.

System Programmer Response

An unexpected condition has occurred with the Mainframe Connector started task. If you are unable to determine the cause of the return code indicated by ’xx’, contact Bravura Security technical support for assistance.

Explanation

Multiple Mainframe Connector subsystems are operational. A password reset request is being processed through either a Mainframe Connector security product "new password" exit or a PSNCSSC API call and no UIDENTRY exists in the PSNCUIDT table to match the userid indicated by ’xxxxxxxx’.

System Action

The current request is abandoned by Mainframe Connector .

Operator Response

Report this condition to the system programmer.

System Programmer Response

This may be an acceptable condition. If the specified userid is not to be processed by any of the active subsystems, then the message can be ignored. If the userid should be processed by one of the active Mainframe Connector subsystems, a UIDENTRY for this userid should be supplied in the PSNCUIDT source deck. If a UIDENTRY does exist for this userid in the PSNCUIDT table, contact Bravura Security technical support for assistance.

Explanation

Multiple Mainframe Connector subsystems are operational. A password reset request is being processed through either a Mainframe Connector security product "new password" exit or a PSNCSSC API call and a PSNCUIDT table has been located, but the table has a format that is not recognized as valid.

System Action

The current request is abandoned by Mainframe Connector .

Operator Response

Report this condition to the system programmer.

System Programmer Response

This would represent a highly unusual condition. If the PSNCUIDT table was created using the supplied UIDSSN macro, contact Bravura Security technical support for assistance.

Explanation

Multiple Mainframe Connector subsystems are operational. A password reset request is being processed through either a Mainframe Connector security product "new password" exit or a PSNCSSC API call, a PSNCUIDT table has been located, a UIDENTRY table entry for userid ’uuuuuuuu’ has been located, but the corresponding Mainframe Connector subsystem is not currently active.

System Action

The current request is abandoned by Mainframe Connector .

Operator Response

Report this condition to the system programmer.

System Programmer Response

This is most likely a valid condition and the specified subsystem is simply not currently operational. If the subsystem specified by ’xxxx’ is operational, contact Bravura Security technical support for assistance.

Explanation

Multiple Mainframe Connector subsystems are operational. A password reset request is being processed through either a Mainframe Connector security product "new password" exit or a PSNCSSC API call and a PSNCUIDT table was not located.

System Action

The current request is abandoned by Mainframe Connector .

Operator Response

Report this condition to the system programmer.

System Programmer Response

If multiple Mainframe Connector subsystems are operational and the Mainframe Connector security product new password exit is active or the PSNCSSC API call is being used, a PSNCUIDT table is required to direct the request to the proper Mainframe Connector subsystem.

Explanation

A password reset request is being processed through either a Mainframe Connector security product "new password" exit or a PSNCSSC API call, a PSNCUIDT table has been located, a UIDENTRY table entry for userid ’uuuuuuuu’ has been located, but the specified default Mainframe Connector subsystem is not currently active.

System Action

The current request is abandoned by Mainframe Connector .

Operator Response

Report this condition to the system programmer.

System Programmer Response

This is most likely a valid condition and the specified subsystem is simply not currently operational. If the subsystem specified by ’xxxx’ is operational, contact Bravura Security technical support for assistance.

Explanation

The Mainframe Connector main task has terminated and recovery termination discovered that the Mainframe Connector subsystem had not been properly disabled.

System Action

The Mainframe Connector subsystem is disabled by the Mainframe Connector resource manager.

Operator Response

Report this condition to the system programmer.

System Programmer Response

This message would indicate a very unusual condition for Mainframe Connector . In general, it could only happen if a catastrophic abend occurred in the Mainframe Connector main task and the corresponding ESTAE was not invoked. Notify Bravura Security technical support immediately.

Explanation

The ICHPWX01 RACF exit installed to support Mainframe Connector was not able to locate the RACF anchor control block, the RCVT.

System Action

Mainframe Connector new password processing will not be active.

Operator Response

Report this condition to the system programmer.

System Programmer Response

If Mainframe Connector has been installed on a system running RACF contact Bravura Security technical support. The internal control block structures for RACF have been compromised.