Skip to main content

Influencing Userids returned to Userlist processing - Exit PSNCUX02

One of the inbound requests supported by Mainframe Connector is a request from a Bravura Security Fabric server to provide a list of userids and corresponding user names as defined in the z/OS security product database. By default, Mainframe Connector ships installation exit PSNCUX02 that will return all userids defined in the security product database.

If this default action is not appropriate, the site can provide a customized PSNCUX02 exit. A return code of 4 from PSNCUX02 indicates that the current userid should not be returned to the Bravura Security Fabric server for the current user list request. Optionally, the userid can be modified by the exit to indicate the ’next’ userid that should be returned by the user list function.

A sample PSNCUX02 exit is provided in member UX02SAMP of the Mainframe Connector installation library.

Following are the characteristics of the PSNCUX02 user exit:

  • Its name must be PSNCUX02 and it must reside in either the STEPLIB used for the Mainframe Connector started task or the system linklist

  • It should run AMODE(31) RMODE(24)

  • The exit is entered problem state key 8 and should return in this same state otherwise results are unpredictable

  • The exit must be reentrant

  • On entry to the exit, R1 points to the following parameter list:

     UX02UID  DS    F    ADDR OF THE USERID FLD (8 BYTES) 
 UX02UNAM DS    F    ADDR OF THE USER NAME FLD (20 BYTES)

    Member PUX02PRM in the INSTLIB dataset contains the DSECT mapping macro for the above parameter list.

  • On return, R15 should contain one of the following return codes

     R15=0    the current userid and user name should be returned 

          to the Password Manager server for this user list request. 
 R15=4    the current userid should be bypassed.  PSNCUX02 
          may have provided an alternative 'next' userid in 
          the area pointed to by UX02UID.
In this section: