7B. Record and edit a macro in a Reflection for the Web session

The logon macro is initiated when an authenticated user launches the session to connect or reconnect to the host. Keep these notes in mind when creating the macro.

NOTE: The automated sign-on macro must:

  • Send a host application ID to the MSS Administrative Server so that the Administrative Server can request a PassTicket from DCAS.

  • Insert the user's RACF credentials (PassTicket and mainframe user ID) that are returned from the MSS Administrative Server (to the client) into the data that is transmitted to the host. This action logs the user on to the mainframe application.

These instructions are guidelines to enable Automated Sign-On for Mainframe. Although error- checking is omitted for brevity and clarity, the macro author should check for errors as required by the application. These settings are needed for testing, and can also be used in production.

  1. In the open IBM 3270 session you created, start the macro recorder (Macro > Start recording).

  2. Connect to the host and log on to the appropriate host application using a valid user name and password.

    You will edit the macro to replace specific user information with values that support logon by any authenticated user.

  3. Click Macro > Stop Recording...

  4. Enter the macro name, such as TSO Logon.

  5. Save the macro and click OK to acknowledge the alert message, which tells you that the macro will be saved to the MSS Administrative Server only after you save and exit the session.

  6. Click Macro > Macros... Select the macro you just created and click Edit.The macro opens for editing in a Macro Editor window.

  7. Below the variable definitions at the top of the recorded macro, add the following line:

    var credentials = eclcredentials.getDASOPassTicket( "APPID" );

    where "APPID" is replaced with the appropriate host application ID.

  8. In the macro’s “performAction” function, edit the statement that sends your user name.

    Remove your user name and replace it with the mainframe username that was retrieved by the getDASOPassTicket method. The edited line should look like this:

    ps.SendDASOUserID( credentials );

  9. In the macro’s “performAction” function, comment out or delete the lines that use the SendCredential method to transmit the mainframe password. Replace it with a new line that transmits the passticket retrieved from the MSS Administrative Server.

    The modified line should look like this:

    ps.SendDASOPassTicket( credentials );

  10. Save the macro and close the Macro Editor window.

  11. To configure the macro to run on session startup, or to run on each connection, click Macros > Macros…

  12. In the Macros dialog box, select “Run at startup” if you want the automated sign-on macro to run after the session launches.

    Click the Events button, then assign the macro as the “On connect macro” if you want the automated sign-on macro to run every time the session connects.

  13. Close the Macros dialog box, and then Save and Exit the session to send the settings to the MSS Administrative Server.

  14. Continue with 8. Assign access to one user for testing.

 8. Assign access to one user for testing

 Configuration Workflow

 Task List for Administrators