Skip to main content

Checklist for SMP/E install

  • Download the compressed software archive (in zip format).

  • Extract files from the archive.

  • Binary FTP the SMPMCS , the MFCXMIT1 , and the MFCXMIT2 files to z/OS.

  • Run TSO RECEIVE for MFCXMIT1 and MFCXMIT2 . This will create MFC7030.F1 and INSTLIB .

  • If Mainframe Connector will be running on a system using ACF2, binary FTP the MFCXMIT3 file to z/OS and run TSO RECEIVE for MFCXMIT3 . This will create MFCA703.F1 .

  • SMP/E RECEIVE the Mainframe Connector base function MFC7030. If the target system is using ACF2, SMP/E RECEIVE the Mainframe Connector ACF2 dependent function MFCA703.

  • Determine if z/OS will be used as a Bravura Pass transparent synchronization trigger system. If it will not be, skip to the next item. If it will be, determine if a security product "new password" exit is already in use. If it is and the security product is RACF or ACF2, consider using the Mainframe Connector exit driver macros to build a single "new password" exit. If the security product is TopSecret, contact Bravura Security to discuss options on how to merge the exit requirements.

  • Create an authorized library entry for the Mainframe Connector load library in SYS1.PARMLIB (either IEAAPFxx or PROGxx).

  • Choose a unique subsystem name to be used by Mainframe Connector . Create a subsystem name entry for the Mainframe Connector subsystem name in SYS1.PARMLIB (IEFSSNxx).

  • SMP/E APPLY the Mainframe Connector base function MFC7030 and, if appropriate, the Mainframe Connector ACF2 dependent function MFCA703.

  • If an SMPPTFIN maintenance file was provided with the distribution package, RECEIVE and APPLY all appropriate maintenance.

  • SMP/E APPLY the usermod for the appropriate security product "new password" exit (if z/OS will be used as a transparent synchronization trigger system).

  • If Mainframe Connector will be making use of a TCPaccess TCP/IP stack, create a second load module dataset. Run the LNKSNS job from the INSTLIB dataset and use the second load module dataset as the target SYSLMOD dataset.

  • IPL with CLPA (for RACF or ACF2 environments) if the new password or pass phrase exit (ICHPWX01 or ICHPWX11 for RACF; NEWPXIT for ACF2) are to be activated.

  • Add the Mainframe Connector start procedure to SYS1.PROCLIB .

  • Define a started task userid for Mainframe Connector . The started task userid must have an OMVS segment and default group.

  • Customize the Mainframe Connector initialization parameters:

    • DNS:

    • TCPPORT#:

    • KEY:

    • SUBSYSNAME:

    • HOSTID:

    • LISTENPORT#:

    • LISTENMAX:

    • ADMINID:

    • SMFREC:

    • TIMEOUT:

    • PASSIVESTART:

    • LISTENONLY:

    • LISTCHECK:

    • DEBUGLEVEL:

    • RESETAUTH:

    • REPORTSYSID:

    • DATASPACE:

    • DEBUGMAX:

    • KEYDISPLAY:

    • KEYENCRYPT:

    • ENCRYPTION:

    • ENTROPYFALLBACK:

    • SOCKETCLOSEWAIT:

    • OUTBOUNDPWCASE:

    • USERIDFASTDEL:

    • TSSTARGET:

    Verify the values specified in the Mainframe Connector PARMLIB dataset for the above parameters.

  • If multiple Mainframe Connector started tasks will be active concurrently and the z/OS system will be used for transparent password synchronization, be sure that a PSNCUIDT table has been created. See Multiple Mainframe Connector Started Tasks and New Password Exits for details.

  • Determine if an include or exclude list will be used and if so, add an INLIST or EXLIST DD statement to the Mainframe Connector JCL.

  • Determine if an ADMINIDS list will be used and if so, add an ADMINIDS DD statement to the Mainframe Connector JCL.

  • Ensure TCP/IP on z/OS is active.

  • Ensure that user exits PSNCUX01 , PSNCUX02 , PSNCUX03 , and PSNCUX04 are set up to return the expected return codes.

  • Ensure that user exits ISNCUX01 , ISNCUX02 , ISNCUX03 , and ISNCUX04 have incorporated necessary post userid create, post userid delete, post RACF group userid add or group userid delete, and post userid attribute update functionality.

  • Start the Mainframe Connector subsystem.

  • Test various password changes to validate proper Mainframe Connector installation.

In this section: