Summary of Configuration Tasks

Use this summary to plan your configuration for testing and production. Detailed steps for each phase are provided in the sections that follow.

Phase I. Set up initial configuration.

First, set up an initial configuration on the MSS Administrative Server and import the Automated Sign-On for Mainframe Add-On.

Then, configure the z/OS mainframe to enable support for PassTickets. You may need to consult your IBM host administrator about configuring DCAS and RACF.

Phase II. Configure a simple test session.

Create an IBM 3270 mainframe session and configure it for automated sign-on.

Record and edit a macro, assign user access for testing, and then run a test of Automated Sign-On for Mainframe.

Phase III. Set up and store mainframe username mappings.

Based on your environment, choose a data store option and store the mainframe usernames in a directory so that they are associated with particular users. (This step is not necessary if the mainframe usernames are stored on each user’s smartcard.)

Then, create mappings between users and groups in the directory, and map the mainframe usernames for users and groups.

Phase IV. Configure settings for production.

Create and configure the terminal emulation client sessions, and then use Assign Access in the MSS Administrative Server to give users and/or groups access to the sessions.

Then, specify the source for the mainframe username to be used for automated sign-on when a user or member of a group runs an assigned session.