Automated Sign-on for Mainframe requires configuration to be done in different places, most likely by different people. Some tasks can be done in parallel.
Follow the flow of tasks and note what needs to be configured where. After the Initial Setup is configured, you can run a Simple Test to prepare for Production.
Table 2-1 Configuration tasks to set up Automated Sign-on for Mainframe
|
Workflow |
Configuration task |
Where to perform the task |
|---|---|---|
|
initial Setup |
server that meets the System Requirements |
|
|
in MSS |
|
|
on z/OS |
||
|
in MSS |
|
|
5. Establish trust between the MSS Administrative Server and the DCAS server |
in MSS |
|
Note: Steps 6 and 7 are specific to your emulator (and session type). |
in the emulator: |
|
|
7. Create an IBM 3270 session with an automated sign-on macro |
in MSS, for your emulator type |
|
Simple Test |
in MSS in MSS |
|
|
Production |
in the data store |
|
|
11. Assign access to the automated sign-on for mainframe sessions |
in MSS |
|
Use your typical deployment method. |
Configuration Tasks: