Reference

External Interfaces

This section describes external interfaces that either provide functionality beyond the scope of Mainframe Connector and its interfaces to the security products "new password" exits, or provide extensions to how the Mainframe Connector user exits (PSNCUX01 or PSNCUX02 ) can be used.

Requesting Mainframe Connector validation external to new password exits

Up to this point, any reference to establishing a dialogue between Mainframe Connector and the Bravura Pass server for password strength validation and synchronization has used a security product "new password" exit as the trigger. This section discusses an external application programming interface (API) that can be used to invoke Mainframe Connector outside the scope of the z/OS security product. This external API is PSNCSSC , the Mainframe Connector SubSystem Call.

PSNCSSC is an assembler based API and is invoked from an assembler program through a macro interface. It can be used from a stand-alone application or program to determine the validity of a potential new password value. This may be appropriate if an application uses its own internal validation method rather then making use of the installed security product.

Member EXAMPL1 in the Mainframe Connector INSTLIB dataset provides an example assembler program for invoking the PSNCSSC service as well as the linkedit information required. Member PSNCSSC in the Mainframe Connector INSTLIB provides the PSNCSSC macro used to generate the call to the PSNCSSC service. The following are some example PSNCSSC macro calls:

*   Determine if PWD1 passes Bravura Pass strength
*   rules for USRID1
         PSNCSSC USERID=USRID1,                                        X
               NPWD=PWD1,                                              X
               RQSTTYPE=TEST,                                          X
               WORKAREA=WORKA
         B     BRTBL1(R15)
BRTBL1   DS    0H
         B     TESTOK            PSNCSSC RC=0
         B     TESTFAIL          PSNCSSC RC=4
         B     TIMEOUT           PSNCSSC RC=8
         B     CONNFAIL          PSNCSSC RC=12
         B     UNKNOWN           PSNCSSC RC=16
         B     STORFAIL          PSNCSSC RC=20
         B     NOPSYNCH          PSNCSSC RC=24
         B     BADPARMS          PSNCSSC RC=28
         B     BADRQSTT          PSNCSSC RC=32
         .
         .
*   Check PWD1 for Bravura Pass strength rules and
*   synchronize if it does
         PSNCSSC USERID=USRID2,                                        X
               NPWD=PWD2,                                              X
               RQSTTYPE=CHNG,                                          X
               WORKAREA=WORKA
         B     BRTBL2(R15)
BRTBL2   DS    0H
         B     CHNGOK            PSNCSSC RC=0
         B     CHNGFAIL          PSNCSSC RC=4
         B     TIMEOUT           PSNCSSC RC=8
         B     CONNFAIL          PSNCSSC RC=12
         B     UNKNOWN           PSNCSSC RC=16
         B     STORFAIL          PSNCSSC RC=20
         B     NOPSYNCH          PSNCSSC RC=24
         B     BADPARMS          PSNCSSC RC=28
         B     BADRQSTT          PSNCSSC RC=32
         .
         .
USRID1   DC    CL8'TEST01'
PWD1     DC    CL8'GOODPWD'
USRID2   DC    CL8'TEST02'
PWD2     DC    CL8'BADPWD'
WORKA    DC    8F

Any program that uses the PSNCSSC services must be linkedited AC(1).

Using RQSTTYPE=TEST on the macro call requires READ access to the FACILITY class PSYNCAPI profile. Using RQSTTYPE=CHNG on the macro call requires update access to the FACILITY class PSYNCAPI profile. For RACF environments, the following commands would be required to create the PSYNCAPI profile and grant RQSTTYPE=CHNG access to user MTECH01 :

  RDEFINE FACILITY (PSYNCAPI) UACC(NONE)
  PERMIT PSYNCAPI ACCESS(UPDATE) CLASS(FACILITY) ID(MTECH01)
  SETROPTS RACLIST(FACILITY) REFRESH

If multiple Mainframe Connector started tasks were being used and the PSNCUIDT table had been created, the following FACILITY class changes would be required:

  RDEFINE FACILITY (PSYNCAPI.ssn) UACC(NONE)
   
  PERMIT PSYNCAPI.ssn ACCESS(UPDATE) CLASS(FACILITY) ID(MTECH01)
   
  SETROPTS RACLIST(FACILITY) REFRESH

where ssn is the subsystem name of the Mainframe Connector subsystem that is to be used by this requester.

Appropriate security definitions for ACF2 or TopSecret environments would also be required if the PSNCSSC service were invoked under those security products' control.

Determining password value acceptability for RACF environments

Under certain circumstances it would be nice to know whether or not a proposed new password value for a given userid passes the rules for a valid RACF password. These rules include:

Is the password value different from the userid
Is the password value different from the current password
Is the password value different from all password values in the password history list
Does the password value pass one of the RACF password rules regarding length and character content
Does the current day and time fall within the RACF WHEN day and time for the userid
Does the password value successfully pass the ICHPWX01 new password exit rules

The PSNCRCFR API provides this capability for RACF environments.

PSNCRCFR is an assembler based API and is invoked from an assembler program through a macro interface. It can be used from a stand-alone application or program to determine if a password value would pass the selected RACF password rule requirements. By default, all of the rules described above are checked. The PSNCRCFR macro call can disable any of the defined rule checks as necessary for any particular request. The default macro parameter settings for rule checking are:

OLDNEWCHK=YES   - check new password against old
HISTCHK=YES     - check new password against history list
RULECHK=YES     - check new password against RACF
                  length & content requirments
WHENCHK=YES     - check current day and time against RACF
                  WHEN day and time
UIDPWDCHK=YES   - check new password against userid
ICHPWX01CHK=YES - check new password against ICHPWX01
                  requirements

Any of these checks can be disabled by specifying NO for the corresponding parameter.

A useful application of this API is in the PSNCUX01 user exit. By default, Mainframe Connector considers any reset or resetexpire request that has been made from the Bravura Pass server as valid and will proceed in performing a RACF administrative reset of the password value. This reset will bypass any of the RACF rule checks. If this is not appropriate for your site, the PSNCRCFR API could be invoke from PSNCUX01 to determine the appropriateness of the proposed password value for the given userid. If the password value were deemed unacceptable, PSNCUX01 could return a return code of 8 and the reset would be rejected on that target z/OS system.

Member EXAMPL2 in the Mainframe Connector INSTLIB dataset provides an example assembler program for invoking the PSNCRCFR service as well as the linkedit information required. Member PSNCRCFR in the Mainframe Connector INSTLIB provides the PSNCRCFR macro used to generate the call to the PSNCRCFR service. Following are some example PSNCRCFR macro calls:

*   Determine if PWD1 for USRID1 passes the RACF password rules
*   but bypass the WHEN day time check
         PSNCRCFR USERID=USRID1,                                       X
               NPWD=PWD1,                                              X
               WHENCHK=NO,                                             X
               WORKAREA=WORKA
         B     BRTBL1(R15)
BRTBL1   DS    0H
         B     GOODPWD1          PSNCRCFR RC=0
         B     BADPARMS          PSNCRCFR RC=4
         B     OLDNEW            PSNCRCFR RC=8
         B     HISTFAIL          PSNCRCFR RC=12
         B     RULEFAIL          PSNCRCFR RC=16
         B     WHENFAIL          PSNCRCFR RC=20
         B     NOUSERID          PSNCRCFR RC=24
         B     USRIDPWD          PSNCRCFR RC=28
         B     PWX01BAD          PSNCRCFR RC=32
         .
         .
*   Determine if PWD2 for USRID2 passes the RACF password
*   rules but bypass the RACF ICHPWX01 new password exit check
         PSNCRCFR USERID=USRID2,                                       X
               NPWD=PWD2,                                              X
               ICHPWX01CHK=NO,                                         X
               WORKAREA=WORKA
         B     BRTBL2(R15)
BRTBL2   DS    0H
         B     GOODPWD2          PSNCRCFR RC=0
         B     BADPARMS          PSNCRCFR RC=4
         B     OLDNEW            PSNCRCFR RC=8
         B     HISTFAIL          PSNCRCFR RC=12
         B     RULEFAIL          PSNCRCFR RC=16
         B     WHENFAIL          PSNCRCFR RC=20
         B     NOUSERID          PSNCRCFR RC=24
         B     USRIDPWD          PSNCRCFR RC=28
         B     PWX01BAD          PSNCRCFR RC=32
         .
         .
USRID1   DC    CL8'TEST01'
PWD1     DC    CL8'GOODPWD'
USRID2   DC    CL8'TEST02'
PWD2     DC    CL8'BADPWD'
WORKA    DC    8F

Messages

PSYNC001I

PSYNC001I – Mainframe Connector SUBSYSTEM INTERFACE ENABLED

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.

PSYNC020I

PSYNC020I – Mainframe Connector 7.0.3 INTERFACE ENABLED

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.

PSYNC031I

PSYNC031I – Mainframe Connector STOP REQUEST ACCEPTED

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.

PSYNC032I

PSYNC032I – Mainframe Connector SUBSYSTEM DISABLED

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.

PSYNC033I

PSYNC033I – Mainframe Connector COMMAND PROCESSING TASK TERMINATION INITIATED

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.

PSYNC034I

PSYNC034I – Mainframe Connector COMMAND PROCESSING TASK TERMINATION COMPLETE

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.

PSYNC041I

PSYNC041I – Mainframe Connector TERMINATED

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.

PSYNC042I

PSYNC042I – Mainframe Connector TERMINATION WAITING ON FUNCTION ROUTINE PROCESSING

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.

PSYNC043I

PSYNC043I – Mainframe Connector TERMINATING WHILE WAITING FOR FUNCTION ROUTINE PROCESSING

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.

PSYNC101I

PSYNC101I – Mainframe Connector LISTENER SERVER TASKS SUCCESSFULLY ATTACHED.

Explanation	The Mainframe Connector listener server has been successfully created.
System Action	None.
Operator Response	None.
System Programmer Response	None.

PSYNC102I

PSYNC102I – Mainframe Connector LISTENER SERVER TASKS SUCCESSFULLY RESTARTED.

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.

PSYNC111I

PSYNC111I – Mainframe Connector bind() INDICATES EADDRINUSE. ATTEMPT TO BIND WILL CONTINUE FOR ONE MINUTE.

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.

PSYNC112I

PSYNC112I – Mainframe Connector LISTENER IS ACTIVE.

Explanation	The Mainframe Connector listener has successfully activated and is waiting for incoming requests.
System Action	None.
Operator Response	None.
System Programmer Response	None.

PSYNC113I

PSYNC113I – LISTENER SOCKET MAXIMUM IS nnn

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.

PSYNC130E

PSYNC130E – Mainframe Connector LISTENER ENVIRONMENT FAILURE.

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.

PSYNC131I

PSYNC131I – Mainframe Connector LISTENER SHUTDOWN IN PROGRESS.

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.

PSYNC132I

PSYNC132I – Mainframe Connector LISTENER TERMINATION OF SUBTASKS IN PROGRESS.

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.

PSYNC133I

PSYNC133I – Mainframe Connector LISTENER TERMINATION OF SUBTASKS COMPLETE.

Explanation	The Mainframe Connector concurrent server listener subtasks have terminated successfully.
System Action	None.
Operator Response	None.
System Programmer Response	None.

PSYNC141I

PSYNC141I – Mainframe Connector LISTENER TASK TERMINATION INITIATED.

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.

PSYNC142I

PSYNC142I – Mainframe Connector LISTENER TASK TERMINATION COMPLETE.

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.

PSYNC150W

PSYNC150W – CONNECTION TO TCP/IP STACK HAS BEEN SEVERED. ATTEMPTING LISTENER RESTART.

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.

PSYNC151E

PSYNC151E – Mainframe Connector LISTENER SERVER TASK ATTACH FAILED.

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.

PSYNC152E

PSYNC152E – Mainframe Connector LISTENER SERVER ACCEPT PROCESSING FAILED.

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.

PSYNC153E

PSYNC153E – UNRECOVERABLE FAILURE OCCURRED IN PARALLEL PROCESSING. PARALLEL PROCESSING IS TERMINATING __tsched() error nn.

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.

PSYNC201I

PSYNC201I – Mainframe Connector PASSWORD VALIDATION INITIATED

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.

PSYNC202I

PSYNC202I – Mainframe Connector PASSWORD VALIDATION IN PROGRESS

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.

PSYNC203I

PSYNC203I – Mainframe Connector PASSWORD VALIDATION WAS SUCCESSFUL

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.

PSYNC204I

PSYNC204I – Mainframe Connector PASSWORD VALIDATION TIMEOUT

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.

PSYNC205I

PSYNC205I – Mainframe Connector PASSWORD VALIDATION FAILED

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.

PSYNC206I

PSYNC206I – Mainframe Connector SERVER SOCKET CONNECTION FAILURE

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.

PSYNC207I

PSYNC207I – Mainframe Connector PASSWORD VALIDATION UNKNOWN FAILURE

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.

PSYNC209I

PSYNC209I – Mainframe Connector SUBSYSTEM NOT CURRENTLY ACTIVE

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.

PSYNC300I

PSYNC300I – UNRECOGNIZED Mainframe Connector MODIFY REQUEST

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.

PSYNC301I

PSYNC301I – INVALID DATA DETECTED FOR Mainframe Connector MODIFY TIMEOUT. CURRENT VALUE RETAINED

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.

PSYNC302I

PSYNC302I – INVALID OPTION FOR Mainframe Connector DISPLAY REQUEST

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.

PSYNC303I

PSYNC303I – INVALID VALUE FOR LISTENMAX. VALID VALUES ARE 1 – 99.

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.

PSYNC304I

PSYNC304I – LISTENMAX VALUE NOT UPDATED. SPECIFIED VALUE THE SAME AS CURRENT VALUE.

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.

PSYNC305I

PSYNC305I – INVALID LISTENONLY VALUE. VALID VALUES ARE YES OR NO.

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.

PSYNC306I

PSYNC306I – INVALID LISTCHECK VALUE. VALID VALUES ARE INOUT, INBOUNDONLY, OR OUTBOUNDONLY.

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.

PSYNC307I

PSYNC307I – INVALID ENCRYPTION VALUE. VALID VALUES ARE IDEA OR AES.

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.

PSYNC308I

PSYNC308I – INVALID ENTROPYFALLBACK VALUE. VALID VALUES ARE YES OR NO.

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.

PSYNC309I

PSYNC309I – INVALID SOCKETCLOSEWAIT VALUE. VALID VALUES ARE 0 - 5.

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.

PSYNC310I

PSYNC310I – INVALID OUTBOUNDPWCASE VALUE. VALID VALUES ARE ASIS, LOWER, OR UPPER.

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.

PSYNC311I

PSYNC311I – Mainframe Connector TIMEOUT VALUE SUCCESSFULLY RESET

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.

PSYNC312I

PSYNC312I – Mainframe Connector LISTENMAX RESET ACKNOWLEDGED.

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.

PSYNC313I

PSYNC313I – Mainframe Connector LISTENONLY VALUE SUCCESSFULLY RESET.

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.

PSYNC314I

PSYNC314I – Mainframe Connector LISTENMAX VALUE SUCCESSFULLY RESET.

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.

PSYNC315I

PSYNC315I – ATTEMPTING PASSWORD MANAGER SERVER CONNECTION TEST.

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.

PSYNC316I

PSYNC316I – PASSWORD MANAGER SERVER CONNECTION TEST COMPLETED SUCCESSFULLY.

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.

PSYNC317I

PSYNC317I – Mainframe Connector LISTCHECK VALUE SUCCESSFULLY RESET.

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.

PSYNC318I

PSYNC318I – INVALID VALUE FOR DEBUGLEVEL. VALID VALUES ARE 0 - 9.

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.

PSYNC319I

PSYNC319I – Mainframe Connector DEBUGLEVEL SUCCESSFULLY RESET.

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.

PSYNC320I

PSYNC320I – Mainframe Connector DEBUGLEVEL LIMITED TO DEBUGMAX

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.

PSYNC321I

PSYNC321I – Mainframe Connector ENCRYPTION VALUE SUCCESSFULLY RESET.

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.

PSYNC322I

PSYNC322I – Mainframe Connector ENTROPYFALLBACK VALUE SUCCESSFULLY RESET.

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.

PSYNC323I

PSYNC323I – Mainframe Connector SOCKETCLOSEWAIT VALUE SUCCESSFULLY RESET.

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.

PSYNC324I

PSYNC324I – Mainframe Connector OUTBOUNDPWCASE VALUE SUCCESSFULLY RESET.

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.

PSYNC330I

PSYNC330I – COMMAND SUCCESSFUL

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.

PSYNC331I

PSYNC331I – ENTRY ALREADY EXISTS; NOT ADDED

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.

PSYNC332I

PSYNC332I – ENTRY DOES NOT EXIST; NOT DELETED

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.

PSYNC333I

PSYNC333I – REQUEST DENIED - ACTIVATED STATUS NOT PERMITTED FOR INLIST AND EXLIST CONCURRENTLY

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.

PSYNC335I

PSYNC335I – Mainframe Connector MAXIMUM OF 32 ddname CONCATENATION DATA. DATA SETS EXCEEDED, REMAINDER IGNORED

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.

PSYNC340I

PSYNC340I – TABLE NOT PRESENT

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.

PSYNC380I

PSYNC380I – RELOAD REQUESTED.

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.

PSYNC381I

PSYNC381I – RELOAD SUCCESSFUL.

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.

PSYNC382I

PSYNC382I – DD FOR REQUESTED TABLE IGNORED OR NOT INCLUDED IN STARTUP JCL

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.

PSYNC383I

PSYNC383I – RELOAD FAILED.

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.

PSYNC385E

PSYNC385E – ftype FAILURE ERROR=errcd INFO=infcd

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.

PSYNC386I

PSYNC386I – ENTRY ADDED.

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.

PSYNC387I

PSYNC387I – ENTRY DELETED.

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.

PSYNC388E

PSYNC388E – ENTRY NOT ADDED.

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.

PSYNC389E

PSYNC389E – ENTRY NOT DELETED.

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.

PSYNC390I

PSYNC390I – ADD/DEL FORMAT ERROR.

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.

PSYNC395I

PSYNC395I – RELOAD COMMAND FORMAT ERROR.

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.

PSYNC491E

PSYNC491E –ABEND xxx DETECTED DURING Mainframe Connector PSNCCMDM PROCESSING.

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.

PSYNC493E

PSYNC493E –ABEND xxx DETECTED DURING Mainframe Connector PSNCLDRV PROCESSING.

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.

PSYNC501E

PSYNC501E –ERROR OBTAINING WORKING STORAGE FOR PSNCCMDM. PROCESSING TERMINATED

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.

PSYNC503E

PSYNC503E –ERROR OBTAINING WORKING STORAGE FOR PSNCLDRV. PROCESSING TERMINATED

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.

PSYNC521E

PSYNC521E – ERROR OBTAINING WORKING STORAGE FOR PSNCT254. PROCESSING TERMINATED

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.

PSYNC522E

PSYNC522E –ABEND xxx DETECTED DURING Mainframe Connector PSNCT254 PROCESSING.

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.

PSYNC551I

PSYNC551I – AUDIT DATASET IS FULL. LOGGING HAS BEEN DISABLED

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.

PSYNC552E

PSYNC552E – AUDIT I/O ERROR. LOGGING FUNCTION HAS BEEN DISABLED

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.

PSYNC553I

PSYNC553I – SYNCHLOG DATASET IS FULL. LOGGING HAS BEEN DISABLED

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.

PSYNC554E

PSYNC554E – SYNCHLOG I/O ERROR. LOGGING FUNCTION HAS BEEN DISABLED

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.

PSYNC600E

PSYNC600E – LABEL label: message [R15=X’r15’] [R0=X’r0’]

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.

PSYNC600I

PSYNC600I – LABEL label: Dataspace successfully established R15=X’00000000’ R0=X’00000000’

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.

PSYNC725E

PSYNC725E – FAILURE xxxxxxxx INITIATING COMMAND SUBTASK. Mainframe Connector IS TERMINATING.

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.

PSYNC726E

PSYNC726E – FAILURE xxxxxxxx INITIATING LISTENER SUBTASK. Mainframe Connector IS TERMINATING.

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.

PSYNC751I

PSYNC751I– CHECK INLIST DATASET RECORD nnnn FOR INVALID DATA.

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.

PSYNC752I

PSYNC752I– CHECK EXLIST DATASET RECORD nnnn FOR INVALID DATA.

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.

PSYNC861W

PSYNC861W – DEBUGLEVEL PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC862E

PSYNC862E – INVALID DATA DETECTED FOR DEBUGLEVEL. VALID VALUES ARE 0 - 9.

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.

PSYNC863W

PSYNC863W – DATASPACE PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC864E

PSYNC864E – INVALID, MISSING, OR REDUNDANT DATA DETECTED FOR DATASPACE - DATASPACE LOGGING DISABLED.

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.

PSYNC865W

PSYNC865W – RESETAUTH PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC866E

PSYNC866E – INVALID DATA DETECTED FOR RESETAUTH.

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.

PSYNC867W

PSYNC867W – REPORTSYSID PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC868E

PSYNC868E – INVALID DATA DETECTED FOR REPORTSYSID.

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.

PSYNC869W

PSYNC869W – DEBUGMAX PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC870E

PSYNC870E – INVALID DATA DETECTED FOR DEBUGMAX. VALID VALUES ARE 0 - 9.

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.

PSYNC871W

PSYNC871W – KEYDISPLAY PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC872E

PSYNC872E – INVALID DATA DETECTED FOR KEYDISPLAY.

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.

PSYNC873W

PSYNC873W – KEYENCRYPT PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC874E

PSYNC874E – INVALID DATA DETECTED FOR KEYENCRYPT.

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.

PSYNC875W

PSYNC875W – ENCRYPTION PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC876E

PSYNC876E – INVALID DATA DETECTED FOR ENCRYPTION.

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.

PSYNC877W

PSYNC877W – ENTROPYFALLBACK PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC878E

PSYNC878E – INVALID DATA DETECTED FOR ENTROPYFALLBACK.

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.

PSYNC879W

PSYNC879W – SOCKETCLOSEWAIT PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC880E

PSYNC880E – INVALID DATA DETECTED FOR SOCKETCLOSEWAIT. VALID VALUES ARE 0 - 5.

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.

PSYNC881W

PSYNC881W – OUTBOUNDPWCASE PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC882E

PSYNC882E – INVALID DATA DETECTED FOR OUTBOUNDPWCASE.

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.

PSYNC883W

PSYNC883W – USERIDFASTEL PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC884E

PSYNC884E – INVALID DATA DETECTED FOR USERIDFASTDEL.

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.

PSYNC885E

PSYNC885E – INVALID DATA DETECTED FOR TSSTARGET. VALID VALUES ARE ’=’ AND ’*’.

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.

PSYNC890I

PSYNC890I – Mainframe Connector ERROR ROUTINE REVIEWING OUTSTANDING EVENT CONDITIONS

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.

PSYNC891I

PSYNC891I – Mainframe Connector POSTING OUTSTANDING EVENT 254 CONDITION

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.

PSYNC892E

PSYNC892E – ABEND xxx DETECTED DURING Mainframe Connector DRIVER ROUTINE. SUBSYSTEM IS DISABLED.

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.

PSYNC900E

PSYNC900E – Mainframe Connector SUBSYSTEM ssss ALREADY ACTIVE

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.

PSYNC901E

PSYNC901E – ERROR PROCESSING Mainframe Connector INITIALIZATION PARAMETERS

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.

PSYNC902W

PSYNC902W – UNRECOGNIZED INPUT PARAMETER DETECTED

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.

PSYNC903W

PSYNC903W – DNS PARAMETER RECORD ALREADY PROCESSED

Explanation	PARMLIB dataset parameter validation has detected a DNS parameter statement after a prior valid DNS 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.

PSYNC904W

PSYNC904W – TCPPORT# PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC905W

PSYNC905W – KEY PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC906W

PSYNC906W – SUBSYSNAME PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC907W

PSYNC907W – TIMEOUT PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC908W

PSYNC908W – HOSTID PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC909W

PSYNC909W – LISTENPORT# PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC910W

PSYNC910W – LISTENMAX PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC911E

PSYNC911E – INVALID DATA DETECTED FOR TCPPORT#

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.

PSYNC912E

PSYNC912E – INVALID DATA DETECTED FOR KEY

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.

PSYNC913E

PSYNC913E – INVALID DATA DETECTED FOR SUBSYSTEM NAME

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.

PSYNC914E

PSYNC914E – INVALID DATA DETECTED FOR TIMEOUT VALUE. VALID DATA IS NUMERIC IN THE RANGE 20 - 120

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.

PSYNC915E

PSYNC915E – NO VALUE SPECIFIED FOR DNS PARAMETER

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.

PSYNC916E

PSYNC916E – NO VALUE SPECIFIED FOR HOSTID PARAMETER

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.

PSYNC917E

PSYNC917E – INVALID DATA DETECTED FOR LISTENPORT#

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.

PSYNC918E

PSYNC918E – INVALID DATA DETECTED FOR LISTENMAX.

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.

PSYNC921E

PSYNC921E – ALL REQUIRED Mainframe Connector PARAMETERS NOT LOCATED

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.

PSYNC931I

PSYNC931I – NO VALID TIMEOUT RECORD DETECTED. DEFAULT TIMEOUT VALUE OF 20 SECONDS IN EFFECT

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.

PSYNC932I

PSYNC932I – CHECK PARAMETER DATASET RECORD nnnn FOR INVALID DATA

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.

PSYNC933I

PSYNC933I – Mainframe Connector PARAMETER VALUES IN EFFECT:

DNS : cccccccccccccccccccccccccccccccccccccccccc

TCP PORT# : nnnnn

KEY : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

SUBSYSTEM NAME: cccc

HOSTID : cccccccccccccccccccccccccccccccccccccccccc

LISTEN PORT# : nnnnn

LISTEN SRVRMAX: nn

ADMIN ID : ccccccc

SMF Record# : nnn

TIMEOUT : nnn Seconds

PASSIVESTART : ccc

LISTENONLY : ccc

DEBUGLEVEL : n

INLIST table : ssssssss

EXLIST table : ssssssss

ADMINIDS table: ssssssss

Dataspace : ssssssss

RESETAUTH : ccccc

REPORTSYSID : ccc

DEBUGMAX : n

KEYENCRYPT : ccc

KEYDISPLAY : cccc

ENCRYPTION : cccc

ENTROPYFALLBK : ccc

SOCKETCLOSEWT : n

OUTBOUNDPWCASE: cccc

USERIDFASTDEL : ccc

TSSTARGET : c

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.

PSYNC934I

PSYNC934I – Mainframe Connector PARAMETER VALUES IN EFFECT:

DNS : cccccccccccccccccccccccccccccccccccccccccc

TCP PORT# : nnnnn

KEY : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

SUBSYSTEM NAME: cccc

HOSTID : cccccccccccccccccccccccccccccccccccccccccc

LISTEN PORT# : nnnnn

LISTEN SRVRMAX: nn

ADMIN ID : ccccccc

SMF Record# : nnn

TIMEOUT : nnn Seconds

PASSIVESTART : ccc

LISTENONLY : ccc

DEBUGLEVEL : n

INLIST table : ssssssss

EXLIST table : ssssssss

ADMINIDS table: ssssssss

Dataspace : ssssssss

RESETAUTH : ccccc

REPORTSYSID : ccc

DEBUGMAX : n

KEYENCRYPT : ccc

KEYDISPLAY : cccc

ENCRYPTION : cccc

ENTROPYFALLBK : ccc

SOCKETCLOSEWT : n

OUTBOUNDPWCASE: cccc

USERIDFASTDEL : ccc

TSSTARGET : c

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.

PSYNC941W

PSYNC941W – SMFREC PARAMETER RECORD ALREADY PROCESSED

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.

PSYNC942E

PSYNC942E – INVALID DATA DETECTED FOR SMFREC.

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.

PSYNC943W

PSYNC943W – PASSIVESTART PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC944E

PSYNC944E – INVALID DATA DETECTED FOR PASSIVESTART.

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.

PSYNC945W

PSYNC945W – LISTENONLY PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC946E

PSYNC946E – INVALID DATA DETECTED FOR LISTENONLY.

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.

PSYNC947W

PSYNC947W – LISTCHECK PARAMETER RECORD ALREADY PROCESSED.

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.

PSYNC948E

PSYNC948E – INVALID DATA DETECTED FOR LISTCHECK.

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.

PSYNC949I

PSYNC949I – PREVIOUS SUBSYSTEM TERMINATION LEFT SUBSYSTEM IN ACTIVE STATUS

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.

PSYNC950E

PSYNC950E – SUBSYSTEM cccc ALREADY IN USE. jobname IS TERMINATING

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 .

PSYNC951I

PSYNC951I – PREVIOUS SSVT ADDRESS USED FOR Mainframe Connector ACTIVATION

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.

PSYNC952I

PSYNC952I – Mainframe Connector SSCVT NOT FOUND. DYNAMIC BUILD WILL BE ATTEMPTED

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.

PSYNC953E

PSYNC953E – Mainframe Connector SSCVT STORAGE OBTAIN FAILURE. Mainframe Connector SUBSYSTEM TERMINATING

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.

PSYNC957I

PSYNC957I – Resource manager setup using existing PSNCRMGR at X’xxxxxxxx’

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.

PSYNC958I

PSYNC958I – Resource manager setup loading new PSNCRMGR at X’xxxxxxxx’

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.

PSYNC959E

PSYNC959E – Resource manager setup xxxxxxxx operation failed with return code X’xx’

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.

PSYNC960E

PSYNC960E – UNABLE TO ESTABLISH COMMUNICATION WITH PASSWORD/ID MANAGER SERVER. Mainframe Connector SUBSYSTEM TERMINATING.

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.

PSYNC961W

PSYNC961W – CONNECT TO PASSWORD/ID MANAGER SERVER FAILED.

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.

PSYNC962W

PSYNC962W – COMMUNICATION WITH THE PASSWORD MANAGER SERVER TIMED OUT.

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.

PSYNC963E

PSYNC963E – UNABLE TO ESTABLISH COMMUNICATION WITH PASSWORD MANAGER SERVER. RECONNECTION WILL BE ATTEMPTED IN FIVE MINUTES.

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.

PSYNC964W

PSYNC964W – PASSWORD MANAGER SERVER CONNECTION TEST FAILED.

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.

PSYNC965E

PSYNC965E – RESET REQUEST TIMED OUT.

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.

PSYNC966E

PSYNC966E – RESET REQUEST CONNECT FAILED.

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.

PSYNC967E

PSYNC967E – LISTENER doaccept() select() errno nn

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.

PSYNC968E

PSYNC968E – LISTENER doaccept() accept() errno nn

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.

PSYNC969E

PSYNC969E – LISTENER socket() errno nn

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.

PSYNC970E

PSYNC970E – LISTENER bind() errno nn

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.

PSYNC971E

PSYNC971E – LISTENER listen() errno nn

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.

PSYNC972E

PSYNC972E – CLIENT socket() errno nn

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.

PSYNC973E

PSYNC973E – CLIENT connect() errno nn

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.

PSYNC974E

PSYNC974E – Mainframe Connector SUBSYSTEM DISABLED FROM PSNCF254.

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.

PSYNC975E

PSYNC975E – Mainframe Connector SUBSYSTEM DISABLED FROM PSNCF254.

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.

PSYNC976E

PSYNC976E – Mainframe Connector SUBSYSTEM DISABLED FROM PSNCF254.

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.

PSYNC978E

PSYNC978E – NAME/TOKEN CREATE FAILED RC(XX). Mainframe Connector TERMINATING.

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.

PSYNC981I

PSYNC981I – USERID xxxxxxxx NOT LOCATED IN PSNCUIDT

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.

PSYNC982I

PSYNC982I – PSNCUIDT TABLE FORMAT ERROR

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.

PSYNC983I

PSYNC983I – SPECIFIED SUBSYSTEM xxxx NOT ACTIVE FOR USERID uuuuuuuu

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.

PSYNC984I

PSYNC984I – NO PSNCUIDT TABLE LOCATED AND MULTIPLE Mainframe Connector SUBSYSTEMS WERE DETECTED.

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.

PSYNC985I

PSYNC985I – DEFAULT SUBSYSTEM xxxx NOT ACTIVE FOR USERID uuuuuuuu

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.

PSYNC990E

PSYNC990E – Mainframe Connector SUBSYSTEM HAS BEEN DISABLED BY RESOURCE MANAGER.

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.

PSYNC999I

PSYNC999I – Mainframe Connector ICHPWX01 UNABLE TO LOCATE RACF RCVT.

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.

Technical Notes

This section describes specific configuration issues and required fixes for the software that Mainframe Connector interfaces with. Review these items to determine if they apply to your environment.

Mainframe Connector and z/OS Security Product Exits

Mainframe Connector optionally makes use of security product exit points (ICHPWX01 for RACF, NEWPXIT for ACF2, and TSSINSTX for TopSecret) to capture z/OS password change events. If your site will not be using your z/OS system as a transparent synchronization trigger system for Bravura Pass , the use of these exits is optional. Alternatively, the exits can be installed and effectively disabled by specifying LISTENONLY=YES in the Mainframe Connector startup parameters. By taking this approach, you allow for the exits to be dynamically ’activated’ with the MODIFY mfc , LISTENONLY=NO operator command.

TopSecret apar BD10748

If the security product that Mainframe Connector will be interfacing with is TopSecret you must install TopSecret apar BD10748. If BD10748 is not installed, Mainframe Connector can experience sporadic abend0C1 conditions.

TopSecret apar BD34839

If the security product that Mainframe Connector will be interfacing with is TopSecret you must install TopSecret apar BD34839. If BD34839 is not installed, the userlist function that can be triggered from the Bravura Security Fabric server could produce erroneous and incomplete results. For TopSecret 5.1, the corresponding PTF is LO92640.

TCPaccess apar MA06505

If the TCP/IP product that Mainframe Connector will be communicating through is Computer Associates product, TCPaccess (newly renamed to NETWORKIT), you should install TCPaccess apar MA06505. Without this fix, every new socket connection will leave behind a x’828’ byte storage block in the Mainframe Connector address space. If enough socket connections are created, this can lead to abend878 conditions in the Mainframe Connector address space.

U4093-1C abend

Minimally, Mainframe Connector requires a 3MB virtual storage region below the 16MB line. If the Mainframe Connector started task is initiated with insufficient below the line region, the Mainframe Connector listener can fail to initialize and the Mainframe Connector address space will indicate U4093-1C abend conditions.

EDCMTF DD statement

Most sites will not require an EDCMTF DD statement in the Mainframe Connector started task JCL. If a PSYNC153E message indicating a __tsched() error -7 is issued at Mainframe Connector startup, this indicates that the multi-tasking facility was unable to locate the PSNCTTOC parallel load module. If this occurs, the Mainframe Connector load library will have to be specified in the EDCMTF DD statement for Mainframe Connector . This should only occur if the site is using a concatenation of datasets in the STEPLIB DD statement and then only if the datasets have differing block sizes.

Performance Group/WLM Service Class

The Mainframe Connector started task should be assigned to a performance group or WLM service class that is consistent with what is used for the z/OS security product started task. This should provide adequate system resources for Mainframe Connector on heavily loaded z/OS systems.

TCP/IP RESOLVERTIMEOUT

If a site chooses to use the name of the Bravura Pass server instead of the IP address in the Mainframe Connector DNS parameter you must be aware that outbound password reset events may be impacted if inconsistent results are being returned from the name serving environment. If the TCP/IP RESOLVERTIMEOUT is left at its default setting (30 seconds), outbound password reset events could be impacted. If your site is experiencing this type of behavior, consider customizing the dataset being used for the SYSTCPD DD and reduce the RESOLVERTIMEOUT value as it relates to Mainframe Connector . This can be done without impacting any other TCP/IP application on your system.

RACF RRSF

If your site is using RACF as the security product and you are using RRSF to apply updates to remote RACF databases and you would like the updates that have been performed by Mainframe Connector forwarded to other systems in the RRSF complex, you will need to ensure the following:

the RACF RRSFDATA class must be active
RRSF automatic direction of application updates must be enabled. This can be accomplished with the following RACF commands:
```
RDEFINE RRSFDATA (AUTODIRECT.sysname.USER.APPL) UACC(NONE) 
PERMIT AUTODIRECT.sysname.USER.APPL CLASS(RRSFDATA) - 
       ACCESS(READ) ID(mfc) 
         
SETROPTS CLASSACT(RRSFDATA) RACLIST(RRSFDATA) 
SETROPTS RACLIST(RRSFDATA) REFRESH
```
where sysname is the value of the &SYSNAME variable of the corresponding z/OS system and mfc is the userid under which the Mainframe Connector started task is running.

ACF2 CPF

If your site is using ACF2 as the security product and you are using CPF to apply updates to remote ACF2 databases, this capability will not function in its expected fashion for events initiated through Mainframe Connector from requests generated at the Bravura Security Fabric server. The ACF2 ACALT API does not include support for ACF2 CPF. As a result, Mainframe Connector will need to be deployed on at least one z/OS system where a unique ACF2 database is in use. This functional characteristic affects ACF2 releases that support CPF currently up to, and including ACF2 6.4.

The software vendor for ACF2 has indicated they intend to resolve this functional anomaly in a future release.

TopSecret CPF

Triggering Third Party Password Synchronization

If your site is using TopSecret as the security product and the following conditions are in effect:

You use TopSecret CPF to propagate password reset events to other independent TopSecret databases
You will be using Mainframe Connector and the supplied TSSINSTX to initiate transparent password synchronization to the Bravura Pass server

You will need to include an ADMINIDS DD statement in the started task JCL for Mainframe Connector . Password reset events initiated by TopSecret CPF on downstream nodes are initiated as third-party reset events. This necessitates the requirement for the ADMINIDS DD . Optional Run-time parameters describes the requirements for this optional DD statement.

If unrestricted third party password reset requests will be eligible to trigger Bravura Pass transparent synchronization, the dataset used for the ADMINIDS DD will need one parameter record as follows:

ADMINID=-

If restricted third party password reset requests will be eligible to trigger Bravura Pass transparent synchronization, the dataset used for the ADMINIDS DD will need to be appropriately populated. Password reset events initiated by validated users during system logon or on behalf of themselves using the TSS REPLACE command will have those events sent to other TopSecret systems through CPF under the MSCA (Master Security Control ACID) of the originating system. To properly handle these scenarios, the dataset used for the ADMINIDS DD will need a parameter record as follows:

ADMINID=mscacid

where ’mscacid’ is the MSCA for the system sending the request. Multiple ADMINID= control cards may be required if more than one source system MSCA exists in a multi-system CPF environment.

CPF TARGET(*) considerations

If the TopSecret CPF environment is not set up to automatically send TopSecret commands to other systems in the TopSecret CPF environment, the following zap should be applied to direct commands issued by Mainframe Connector to other TopSecret nodes:

 NAME PSNCTTOC PSNCSAFR
 VER  0A78 47F0CA86
 VER  0CF0 47F0CCFE
 REP  0A78 4700CA86
 REP  0CF0 4700CCFE
   
 NAME PSNCTTOC PSNCTSS
 VER  0538 47F0A546
 VER  05AE 47F0A5BC
 VER  0624 47F0A632
 VER  0A8E 47F0AA9C
 VER  0B58 47F0AB66
 VER  0CB8 47F0ACC6
 VER  0DF4 47F0AE02
 REP  0538 4700A546
 REP  05AE 4700A5BC
 REP  0624 4700A632
 REP  0A8E 4700AA9C
 REP  0B58 4700AB66
 REP  0CB8 4700ACC6
 REP  0DF4 4700AE02 
   
 NAME PSNCTTOC PSNCPPHR
 VER  09A6 47F0C9B4
 VER  0B9C 47F0CBAA
 REP  09A6 4700C9B4
 REP  0B9C 4700CBAA

TopSecret and REMOVE ASUSPEND

Mainframe Connector password and password phrase reset events in TopSecret environments will, by default, remove the ASUSPEND attribute for the corresponding acid. If you are using Mainframe Connector in a TopSecret environment and you do not want the ASUSPEND attribute reset, apply the following zap:

 NAME PSNCTTOC PSNCSAFR
 VER  0CE2 4700CCF0
 REP  0CE2 47F0CCF0 
   
 NAME PSNCTTOC PSNCPPHR
 VER  0B8E 4700CB9C
 REP  0B8E 47F0CB9C

ACF2 and Removing the CANCEL Flag

Mainframe Connector password and password phrase reset events in ACF2 environments will, by default, remove the CANCEL flag for the corresponding userid. If you are using Mainframe Connector in an ACF2 environment and you do not want the CANCEL flag reset, apply the following zap:

 NAME PSNCACFR PSNCACFR
 VER  0486 D767D62CD62C
 VER  07DA 41F0004E
 VER  0C9C 0006
 VER  0C9E C3C1D5C3C5D34040
 REP  0486 47F0A5100000
 REP  07DA 41F0003C
 REP  0C9C 8006
 REP  0C9E E2E4E2D7C5D5C440
   
 NAME PSNCACFH PSNCACFH
 VER  032A D767D4D4D4D4
 REP  032A 47F0A3B40000  
   
 NAME PSNCACFU PSNCACFU
 VER  02BA D767D1C4D1C4
 REP  02BA 47F0A3440000

TopSecret and Mixed Case Password Support

To properly support mixed case passwords in a TopSecret environment, TopSecret 8.0 with SP03 and APAR BGD7626 should be installed.

Mainframe Connector ISPF/PDF Interface

This section describes the configuration requirements necessary to activate the Mainframe Connector ISPF/PDF interface. PICS (Mainframe Connector Parallel Information Communication Service) furnishes windows into the Mainframe Connector internal list tables and dataspace log contents. This interface is entirely optional and does not need to be activated for Mainframe Connector to perform its normal function. If your site desires an online, dynamic view into Mainframe Connector events you would choose to activate this interface. The interface works in conjunction with, and in parallel to, the standard logging used in Mainframe Connector

The Mainframe Connector ISPF/PDF interface provides the opportunity to view two different areas of information. The first option is to display the contents of any or all of the in-storage lists that can be used to influence Mainframe Connector operation. The second option is to display recent Mainframe Connector events. The information available with this option is very similar to that which is produced in the AUDIT and SYNCHLOG DD as well as that available in SMF record format. To use this display, the optional Mainframe Connector dataspace collector must be active (see the DATASPACE parameter described in Run-time parameters for details).

To display information, PICS utilizes the ISPF VIEW service which permits the use of the VIEW primary and line commands. This includes SORT, CREATE, REPLACE primary commands or eXlude, Show, Repeat, Delete line commands. SORTing can prove very beneficial if, for example, you want to create a log data display that sorts by log type or in time-stamp descending order.

The version of PICS distributed with Mainframe Connector 7.0.3 is functionally equivalent to the version of PICS distributed with PSYNCH/390 2.1.1 and 2.1.2 or Mainframe Connector 7.0.0, 7.0.1, and 7.0.2. The only fundamental differences are in the panel displays associated with the product rename. If you have installed PICS components from PSYNCH/390 2.1.1 or 2.1.2 or Mainframe Connector 7.0.0, 7.0.1, or 7.0.2, you can continue to use those components without updates from Mainframe Connector 7.0.3. If Mainframe Connector 7.0.2 is an upgrade from a release of PSYNCH/390 prior to PSYNCH/390 2.0.0 (i.e. - any PSYNCH/390 1.x.x version), the installed PICS components are not compatible with Mainframe Connector 7.0.3 and you will need to install version 7.0.3 PICS components to achieve compatibility with Mainframe Connector 7.0.3.

Activating the Mainframe Connector ISPF/PDF Interface

This section discusses the requirements for activating the ISPF/PDF interface for Mainframe Connector .

Mainframe Connector ISPF/PDF Load Modules

During the Mainframe Connector install process, the load modules for the Mainframe Connector ISPF/PDF interface were created in the target Mainframe Connector load library. The following load modules should be found in the target Mainframe Connector load library:

PICSMMC
PICSMSS
PICSMTBA

These load modules will need to be copied to a load library that will be available to the ISPF/PDF session for anyone that requires access to the Mainframe Connector ISPF/PDF interface. The PICSMTBA module is an authorized load module and must reside in an APF authorized dataset.

Mainframe Connector ISPF/PDF Panel and Message Members

The Mainframe Connector ISPF/PDF interface requires that panel and message members be made available to the ISPF/PDF environment. The following panel and message members reside in the .INSTLIB dataset that was created during the installation process:

PICSMLGH
PICSMLGP
PICSMTBH
PICSMTBP
PICSM10H
PICSM10P
PICSM20H
PICSM20P
PICM10

Copy the PICM10 member into a dataset in the ISPMLIB concatenation and copy the remaining members (PICSMLGH, PICSMLGP, PICSMTBH, PICSMTBP, PICSM10H, PICSM10P, PICSM20H, PICSM20P) into a dataset in the ISPPLIB concatenation of the logon procedure.

Updating the IKJTSOxx PARMLIB Member

Update the AUTHTSF section of the active IKJTSOxx PARMLIB member to include the PICSMTBA program name. This indicates to TSO that this program is eligible to execute as an authorized program when invoked from the IKJEFTSR service.

Authorizing PICS Usage

In a multiple (or even single) Mainframe Connector subsystem environment, it may be necessary or desirable to restrict the level of PICS access to appropriate Mainframe Connector subsystem information. PICS 7.0.3 implements resource rule checking, wherein subsystem information access validation is performed at each PICS access to a specified (or defaulted) Mainframe Connector subsystem. To assign the necessary authorizations, resource rules, whose format is dependent upon the security subsystem in use, must be defined as follows:

RACF

Issue the following TSO command for each subsystem to be authorized for PICS access:
```
RDEFINE FACILITY PSYNCH.PICS.ssnm
```
where ssnm is the 1 to 4 character subsystem name assigned to the Mainframe Connector subsystem via the SUBSYSNAME parameter described in Run-time parameters . This defines the specified facility class profile and assigns ALTER authority to the creating userid.
To permit additional users PICS access to a given Mainframe Connector subsystem, issue the following TSO command for each userid to which access is to be granted:
```
PERMIT PSYNCH.PICS.ssnm ACCESS(READ) CLASS(FACILITY) ID(userid)
```

ACF2

For ACF2, a resource rule of the following form must be created, compiled, and stored:
```
$KEY(PSYNCH) TYPE(FAC)
PICS.ssnm UID(uid) SERVICE(READ) ALLOW
```
where ssnm is the name of the Mainframe Connector subsystem with which you wish to communicate, and uid is the desired userid. If you wish to authorize access to multiple concurrently executing Mainframe Connector subsystems, then add further PICS.ssnm UID(uid) SERVICE(READ) ALLOW statements, replacing each ssnm with the associated subsystem name and uid with the appropriate userid.
In addition, a CLASMAP record containing a resource type of FACILITY with a type code of FAC must exist. This can be confirmed by entering the ACF2 environment in TSO (e.g. enter ACF in TSO menu 6) with a sufficient security privilege level (e.g. SECURITY) and entering:
```
SHOW CLASMAP
```
If a resource type of FACILITY with a type code of FAC is displayed, then the necessary environment should already be active. If not, consult the ACF2 Administrator Guide for information on defining and activating CLASMAP records.

TopSecret

define PSYNCH as an IBMFAC. This can be done with the following TSO command:
```
TSS ADD(anydept) IBMFAC(PSYNCH)
```
where anydept is a valid TopSecret DEPT.
to permit users PICS access to a given Mainframe Connector subsystem, issue the following TSO command for each userid to which access is to be granted:
```
TSS PERMIT(acid) IBMFAC(PSYNCH.PICS.ssnm)
```
where acid is the TopSecret ACID you are granting access to and ssnm is the 1 to 4 character subsystem name assigned to the PSYNCH/390 subsystem via the SUBSYSNAME parameter described in Run-time parameters .

The Mainframe Connector ISPF/PDF Primary Selection Panel

The PICS ISPF/PDF interface can accommodate multiple concurrent Mainframe Connector started tasks. PICS should be made available in one of the existing ISPF/PDF primary selection panels as follows:

PICS,'CMD(PICSMSS)'

Entering PICS on the primary command line of the ISPF/PDF primary selection panel where the PICS selection option has been included should result in:

The Mainframe Connector subsystem selection panel being displayed if multiple Mainframe Connector subsystems are detected.
The Mainframe Connector primary selection panel being displayed if only a single Mainframe Connector subsystem is detected.

Mainframe Connector Multiple Subsystem Primary Selection Panel

  -------------------------------------------------------------------------------
 --------  MM  MMM   //   FFFFFFF   RRRRR       AAAAAA     MM  MMM    EEEEEEE  -
 -------  MMMMMMM   //   FF        RR   RR     AA   AA    MMMMMMM    EE       --
 ------  MM M MM   //   FF        RR   RR     AA   AA    MM M MM    EE       ---
 -----  MM   MM   //   FFFFF     RRRRRR      AAAAAAA    MM   MM    EEEEE    ----
 ----  MM   MM   //   FF        RRRR        AA   AA    MM   MM    EE       -----
 ---  MM   MM   //   FF        RR  RR      AA   AA    MM   MM    EE       ------
 --  MM   MM   //   FF        RR    RR    AA   AA    MM   MM    EEEEEEE  -------
 -------------------------------------------------------------------------------
 -------------------------  CCCCC       OOOOOO     NN   NN  --------------------
 ------------------------  CC   CC     OO   OO    NNN  NN  ---------------------
 ----- P arallel -------  CC          OO   OO    NNNN NN  - P arallel ----------
 ---- I nformation ----  CC          OO   OO    NN NNNN  - I nformation --------
 --- C ommunication --  CC          OO   OO    NN  NNN  - C ommunication -------
 -- S ervice 7.0.3 --  CC   CC     OO   OO    NN   NN  - S ervice 7.0.3 --------
 ------------------     CCCCC      OOOOOO    NN   NN  --------------------------
 ------------------------------------------------------------------------------- 
 Command ===>
 Select subsystem(s):   PSS1    PSS2

Figure: Mainframe Connector Primary Selection Panel

 -------------------------------------------------------------- Subsystem: PSS2
 --------  MM  MMM   //   FFFFFFF   RRRRR       AAAAAA     MM  MMM    EEEEEEE  -
 -------  MMMMMMM   //   FF        RR   RR     AA   AA    MMMMMMM    EE       --
 ------  MM M MM   //   FF        RR   RR     AA   AA    MM M MM    EE       ---
 -----  MM   MM   //   FFFFF     RRRRRR      AAAAAAA    MM   MM    EEEEE    ----
 ----  MM   MM   //   FF        RRRR        AA   AA    MM   MM    EE       -----
 ---  MM   MM   //   FF        RR  RR      AA   AA    MM   MM    EE       ------
 --  MM   MM   //   FF        RR    RR    AA   AA    MM   MM    EEEEEEE  -------
 -------------------------------------------------------------------------------
 -------------------------  CCCCC       OOOOOO     NN   NN  --------------------
 ------------------------  CC   CC     OO   OO    NNN  NN  ---------------------
 ----- P arallel -------  CC          OO   OO    NNNN NN  - P arallel ----------
 ---- I nformation ----  CC          OO   OO    NN NNNN  - I nformation --------
 --- C ommunication --  CC          OO   OO    NN  NNN  - C ommunication -------
 -- S ervice 7.0.3 --  CC   CC     OO   OO    NN   NN  - S ervice 7.0.3 --------
 ------------------     CCCCC      OOOOOO    NN   NN  --------------------------
 ------------------------------------------------------------------------------- 
  Command or selection ===> 
 1. Internal tables   2. Dataspace logs

The Mainframe Connector ISPF/PDF List Selection Panel

If you select Option 1 from the Mainframe Connector primary selection panel , a list selection panel will be displayed. This panel can be used to select which Mainframe Connector internal lists are to be displayed. Each of the INLIST, EXLIST, or ADMINIDS list can be selected individually or in any combination. The resulting display will show the current internal list contents for each list.

Note that list activation status, i.e. - ACTIVATED or DEACTIVATED, is not shown in the display; it can be ascertained via the F mfc,D=PARMS operator command.

See:

Mainframe Connector List Selection Panel for a sample display of the list selection panel.
Mainframe Connector Internal List Data for a representative example of the type of information that is available from the internal list display.

Mainframe Connector List Selection Panel

  ---------------------------  Mainframe Connector  -----------------------------
 -------------------------------------------------------------------------------
 --------------------------------  P  I  C  S  ---------------------------------
 -------------------------------------------------------------------------------
 ----------------  Parallel Information Communication Service  -----------------
 ----------------------------------  7.0.3  ------------------------------------
 -------------------------------------------------------------------------------
 ------------------------------  Internal Tables  ------------------------------
 ------------------------------------------------------------------------------- 
  Command ===> 
 Select list type(s) (enter any nonblank character beside desired selection(s)): 
 ===>   INCLUDEUSER list    ===>   INCLUDEGROUP list 
 ===>   EXCLUDEUSER list    ===>   EXCLUDEGROUP list 
 ===>   ADMINIDS list

Mainframe Connector Internal List Data

 VIEW       Mainframe_Connector_Internal_Tables             Columns 00001 00022
 Command ===>                                                  Scroll ===> HALF
 ****** ***************************** Top of Data ******************************
 000001 INCLUDEUSER : No data
 000002 INCLUDEGROUP: No data
 000003 EXCLUDEUSER : TEST1
 000004 EXCLUDEUSER : MVS001
 000005 EXCLUDEUSER : IBMUSER
 000006 EXCLUDEUSER : MVSJDL-
 000007 EXCLUDEUSER : MVSSKG-
 000008 EXCLUDEUSER : DBAJGR-
 000009 EXCLUDEGROUP: MYGROUP
 000010 ADMINID     : ADMMVS-
 000011 ADMINID     : ADM77
 ****** **************************** Bottom of Data ****************************

The Mainframe Connector ISPF/PDF Activity Log Panel

If you select Option 2 from the Mainframe Connector primary selection panel , an activity log data selection panel will be displayed. This panel can be used to select which Mainframe Connector log information is to be displayed. Three types of log information can be requested – log information that has been written to the AUDIT DD , log information that has been written to the SYNCHLOG DD , and Mainframe Connector SMF record images. The collection of log information can be influenced after Mainframe Connector has been started. See Modifying the DATASPACE logging options for the operator commands that can be used to activate and deactivate log data collection.

See:

Mainframe Connector Log Selection Panel for a sample display of the log data selection panel.
Mainframe Connector Log Data provides a representative example of the type of information that is available from the log data display. Remember, right scrolling will be necessary to examine all data available in this display.

Mainframe Connector Log Selection Panel

 ---------------------------  Mainframe Connector  -----------------------------
 -------------------------------------------------------------------------------
 --------------------------------  P  I  C  S  ---------------------------------
 -------------------------------------------------------------------------------
 ----------------  Parallel Information Communication Service  -----------------
 ----------------------------------  7.0.3  ------------------------------------
 -------------------------------------------------------------------------------
 ------------------------------  Dataspace Logs  -------------------------------
 -------------------------------------------------------------------------------

  Command ===>
   

 Select log type(s) (enter any nonblank character beside desired selection(s)): 
 ===>   SMF    ===>   AUDIT    ===>   SYNCHLOG

Mainframe Connector Log Data

 VIEW       Mainframe_Connector_Dataspace_Logs              Columns 00001 00072
 Command ===>                                                  Scroll ===> HALF
 ****** ***************************** Top of Data ******************************
 000001 Rectype = Synchlog   Date-time = 2002.317-11:42:41.74   Msg = Attempting
 000002 Rectype = Synchlog   Date-time = 2002.317-11:42:41.87   Msg = Password f
 000003 Rectype = SMF        Date-time = 2002.317-11:42:41:87   UID = MTECH1
 000004 Rectype = Audit      is not present in the dataspace
 ****** **************************** Bottom of Data ****************************

Removing a previous PICS version

After successfully installing and activating PICS 7.0.3, you may wish to reclaim resources by removing the components associated with a previous PICS version, if one had been installed.

Note

This only applies if the prior PICS version was from a PSYNCH/390 1.x.x release.

To accomplish this, delete the following:

ISPF panel members PICSLOGH, PICSLOGP, PICSTBLH, PICSTBLP, PICS001H, and PICS001P
ISPF message member PICS00
Load modules PICSLOG, PICSMAC, PICSTBL, and PICSTBLA
The PICSTBLA program name entry in the AUTHTSF section of the active IKJTSOxx PARMLIB member

In this section:

Would you like to provide feedback? Just click here to suggest edits.