where does the tso id and password gets saved for every user

mundul333 · New User Joined: 28 Nov 2005 Posts: 9 Location: mumbai

hi ,

where does the tso id and password gets saved for every user?
i had to design a clist screen where the id and password would be validated. so this will take the tso id and then process further .

once the user is logged in then at the ready prompt when we give the clist name then it should take the tso id and validate that

can anyone help to design the same

enrico-sorichetti · Posted: Thu Jul 19, 2007 1:01 pm

Just curious...

For what reason You want to redo what has been done during thelogon process ?

regards

e.s

expat · Posted: Thu Jul 19, 2007 2:54 pm

The security software that you use does this for you. As Encrico has asked, why reinvent the wheel when it is already round ?

mundul333 · New User Joined: 28 Nov 2005 Posts: 9 Location: mumbai

this second time validation needs to be done bcz at the ready prompt if we type the clist then it automatically gets started .
but this clist has to be restricted to some users only.
suppose i am dealing with that application then my tso id should be only able to run the clist . no other user from the ready prompt should be able to run the clist.

currently this clist appln is working for all the tso id.

expat · Posted: Thu Jul 19, 2007 5:51 pm

Isn't that a bit "dark ages", specifying a CLIST name from the ready prompt.

Surely this application should be offered to the selected users from within their ISPF logon procedure. There are many ways to achieve this without having to get back to the ready prompt and then type a fully qualified dataset/member name to access an application.

dick scherrer · Posted: Thu Jul 19, 2007 6:24 pm

Hello,

If you simply must do something like you've posted (instead of the more standard ways suggested), you could always add this "special" clist to a pds that "others" do not have access to. . . .

expat · Posted: Thu Jul 19, 2007 6:56 pm

Or if this CLIST is a logon PROC, and defined to RACF as such, then you can use RACF to protect its usage.