How to add signon disclaimer text to IBM Session Manager for z/OS
BillBulfin 1000004JHC Visits (1122)
Does your site compliance officer require that you post an initial disclaimer (Welcome Screen) to your users when they access your IT systems? Most do. An IBM Session Manager for z/OS (ISM) systems programmer recently asked how to deploy such a disclaimer message to their users. If you have a similar requirement and want to learn how to go about deploying a welcome screen in IBM Session Manager for z/OS, read on to see one method you can use.
First, there's probably another method to do this, but I've used this one and it works and is pretty easy to configure and deploy. I did this in ISM 3.2, and another ISM 3.1 site confirmed it also worked for them, but I have not tried this in ISM V2.x.
We're going to need to create 3 new artifacts in ISM and update the default profile for users. The default profile is identified in the DEFPROFILE parameter of the SYSTEM statement.
So let's get started.
Step 1) Obtain the approved text of your site IT system login disclaimer and format it to display on the smallest 3270 screen your users might logon from, for example, a 24 row by 80 column screensize (24x80) 3278-2. In my example, the text is 24x80, so I created a panel definition member in my SISZCCNF ISM configuration PDSE as below.
The 'PANEL' definition name in row 1 is called "disclaim" in my example. The number of rows between the 'Textstart' and 'Textend' markers is 24.
Step 2) Create a user SCRIPT in your SISZCUSC PDSE. In this example, the script is named "disclaim". It contains just 5 lines:
Line 1 script disclaim (this is the standard first line of any script with its name).
Line 2 usermsg panel disclaim (this requests the disclaim panel be displayed on the terminal).
Line 3 waitterm (this waits for terminal input. The user sees the disclaimer text and hits enter).
Line 4 let t_message = 'Signon complete' (this sets the t_message variable text after enter).
Line 5 endsess (this ends the application session for the panel display).
Step 3) Issue commands:
PUPDATE CONFIG DISCLAIM (this makes the panel available).
PUPDATE USCRIPT DISCLAIM (this makes the script available).
Step 4) Create an APPL member in your SISZCAPL PDSE. In this example, the APPL is named "disclaim" and assumes you use OLA (Online Administration) to create and update ISM artifacts.
This disclaimer application only needs to display the message when a user first signs on, so they don't need to see it on their application menu after they (hopefully) read it and hit the enter key. To do that, the APPL definition needs to specify 3 options:
Step 5) Update the DEFPROFILE profile and add an unused session number. In my example, I added session 9999 for APPL DISCLAIM. I then specified the common enduser option AUTOSELECT 9999 which automatically selects session 9999 when the user signs on.
Step 6) Issue commands:
PUPDATE APPL DISCLAIM (this makes the application available).
PUPDATE PROFILE profile (this makes the updates to the default profile available).
Now when a user signs on to IBM Session Manager, it will automatically select the disclaimer application, which displays the user panel with the disclaimer text... the user reads it and presses the enter key, and then sees their expected menu or applications.