MVSFORUMS.com

Dip · Beginner Joined: 24 Mar 2006 Posts: 27 Topics: 14

Hi,

Is there any way we can control the timeout of a CICS screen?

Let say I want a application screen to be set to timeout after XX sec? Can we control this?

Thanks!
Dip.

kolusu · Posted: Thu Feb 24, 2011 1:15 am Post subject:

Dip,

Read Timeout section in here

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dfht5a09/1.2.5.2
_________________
Kolusu
www.linkedin.com/in/kolusu

warp5 · Posted: Thu Feb 24, 2011 2:12 am Post subject:

Why would you want to do that?

Dip · Beginner Joined: 24 Mar 2006 Posts: 27 Topics: 14

Hi Kolsu,

Thanks for your reply. Seems like this TIMEOUT option is set for the terminal timeout. Any idea if we can set something like this at a Tran ID level?

Hello Warp5,

I am working on a CICS update screen where only one user can update some data at one point of time after browsing the screen. But I dont want the users to stay in the screen for more than X mins.

I think there is a default time-out set up by CICS, so that if one user browse the screen but does not do anything it will be automatically timed out after certain time. But if that default time-out setting is too much (let say 10-15 mins) then i want to reduce it to X mins so that other users can update the data after X mins.

I was looking for an option to handle this situation programtically or some other way using the tran ID.

Tahnks!
Dip.

kolusu · Posted: Sat Feb 26, 2011 9:46 pm Post subject:

dbzTHEdinosauer · Posted: Mon Feb 28, 2011 2:12 am Post subject:

save the 'file/database' before image in your dfhcom.

When you receive 'change to' data from the user,
insure the file/database contains the same data as the before image
(i.e. read or select the data and compare.)
if not, return error to user telling him/her that the data was updated prior to his/her attempt.

you don't want to waste resources nagging a user about how slow he/she is.
what you want to do is prevent updates to files/databases based on faulty data -
i.e. before image displayed to user is not the same as the actual file.
_________________
Dick Brenholtz
American living in Varel, Germany

warp5 · Posted: Mon Feb 28, 2011 3:42 am Post subject:

It sounds like you want to have a conversational transaction, which can not be recommended, a CICS transaction should send out data and end. The transaction starts again after the user has pressed enter. There are usually no controls at all between those two actions. So, with the information you have given so far it sounds like you have a bad solution.

Dip · Beginner Joined: 24 Mar 2006 Posts: 27 Topics: 14

In our system the TYPETERM SIGNOFF is set to YES and the TIMEOUT value is 1 Hr. So if a terminal has an hour of inactivity, the user will automatically be logged out of CICS.

dbzTHEdinosauer,

My design assumption is 'Only One user can update the data at one point of time'. Our requirement is NOT to 'block' a particualr screen/ system access for standard cutoff 1 Hr time. As TYEPTERM is a system parameters and applies to all the users / screens I really dont want to change that in our system. Even I dont think the CICS admin will agree to change the TYPETERM SIGNOFF defination.

Kolsu,

I like your idea. Can you please give me some technical details on 'setting the wait time' for a screen and 'trigger another transaction like going back to the main screen' so that I can discuss this option with the tech team here?

Thanks!
-DIp

kolusu · Posted: Wed Mar 09, 2011 3:48 pm Post subject:

Dip · Beginner Joined: 24 Mar 2006 Posts: 27 Topics: 14

Kolusu,

First of all, extremely sorry for misspelling your name but just believe me from the very first post in mvsforum where you replied against my query I am addressing you wrongly as 'Kolsu' instead of 'Kolusu'. I was looking at all my posts in 'mvsforums' help board and saw that 99% times I spelled your name wrongly as 'Kolsu'. A BIG Sorry for that too...

Also I am not a experienced person in CICS and before posting this query to mvsforums my thought was, someone already faced similar problem and can help me with a

warp5 · Posted: Thu Mar 10, 2011 2:18 am Post subject:

I still say that you have a bad design and solution. This is not transaction oriented programming. Either you have a low CICS volume or few users. We have some 600,000 transactions a day which means there is a high probability that more than one person will try to use the same transaction near the same time. Like I have already said, it sounds like you are using conversational transactions, which is a very bad idea for CICS.

papadi · Supermod Joined: 20 Oct 2009 Posts: 594 Topics: 1

Dip · Beginner Joined: 24 Mar 2006 Posts: 27 Topics: 14

warp5,

Transaction volume is very very low ..

No of users: 20-30
Transaction rate: 400-500 Updates / day

Thanks!
-Dip.

warp5 · Posted: Fri Mar 11, 2011 2:59 am Post subject:

Ok, it may work, but you are learning and implementing a solution that can not be transferred to a real working environment. In other words, you are learning and implementing a bad habit.