Subsystem Startup

Mainframe Connector is started using the START command. This is an MVS system command and can be manually entered at a console after MVS initialization is complete. For successful results, the start of Mainframe Connector should be delayed until TCP/IP has become fully functional.

Enter the START command as follows:

START mfc

S mfc

where mfc specifies the name of your Mainframe Connector catalogued procedure.

If the Mainframe Connector subsystem name has been predefined using an IEFSSNxx member of the system PARMLIB concatenation as described in Defining the Subsystem Name , and the name of the Mainframe Connector started task procedure is the same as the subsystem name, then a SUB= parameter will also be required on the START command. If an attempt is made to begin a started task that uses a predefined subsystem name that matches the started task’s procedure name, z/OS will attempt to start the started task under the master subsystem. Mainframe Connector requires the use of JES SYSOUT and as a result, it cannot successfully run under the master subsystem. If you want to use a predefined subsystem name that matches your Mainframe Connector started task procedure name, use the following START command:

START mfc ,SUB=JES2

If your site uses JES3, modify the above command appropriately.

When Mainframe Connector is initialized, the following message will appear on the console.

PSYNC001I - Mainframe Connector SUBSYSTEM INTERFACE ENABLED

At this point, Mainframe Connector has enabled its subsystem functions and is prepared to communicate with the Bravura Security Fabric server.

If Mainframe Connector fails initialization, an appropriate message is displayed on the console.