MVSFORUMS.com

[mottai]

Hi

I am currently in a project where we are converting from IDMS/ADSO to DB2/CICS. The problem I have is in the log on screen. Since IDMS allows record level lock, the existing code uses it and restricts the user from logging into different terminals.
Now we need to mimic this functionality.
We discussed using a column in DB2 user table or TSQ for this purpose. But time out or a program abend is a problem in both cases.
Record level lock in DB2 is terribly unpopular with the DBAs in my shop.
Please let me know if anyone has done anything similar.

Thanks

[kolusu]

Mottai,

I am confused as to how logging to the system is tied to a DB2 table. Can't use the mainframe regular logon feature to check if the user is already logged on to the system?

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[mottai]

Kolusu

My application has a log on of its own. The password for which is maintained in a DB2 table. This is the user record for us. On top of the RACF security, we are having our own application security.

Now, the issue is how not to allow the user to log on in to our application in multiple terminals.

Since this needs to be prorgammatically controlled, we are trying find ways of identifying whether the user has already logged on. We thought of using a column in the security table or a logon TSQ but the issue gets muddy when you think of scenarios when the application abends or simply times out.

Please let me know whether this gives you the details..

Thanks

[shiv_swami]

Do you want to mimic "Multiple signon not allowed " functionality ?
_________________
Regards,
Shivprakash

[mottai]

Hi

I got to know about it and we are checking with our CICS sysprogs about it.

My secondary question out of this is in reference to the CICS timeout facility. Is there a way to not timeout at all?.

[vak255]