CICS Client Timeout

[stephenwales]

Been bringing up a new system, under CICS 5.0, on HPUX 11.11, Oracle 9.2.0.5 for Ellipse 5.2.1.4.

The users are reporting that they walk away from the keyboard for 30 minutes and come back and hit enter and they get a message about the session being disconnected.

I know I've seen this before. I've got a feeling that there's a setting in the Ellipse Control Panel, or perhaps the CTG that defines this timeout, but I've not been able to find it.

I'm pretty sure that our other instances don't drop after 30 minutes like this.

Anyone seen this before and maybe familiar enough to point me to a control settings to extend or eliminate this seemingly default setting?

Thanks
Steve

 

[Calator]

In MIMS 4.1 with Mincom TP, the setting is in tpnames.tbl. Eg: Set t4 and t5 below to 10800 seconds to achieve 3 hours:
/*************************************************************************
/*** The directive to set the system timing parameters.
/*** Usage:
/*** %TIMING <t1>,<t2>,<t3>,<t4>,<t5>,<t6>,<t7>,<t8>,<t9>,<10>
/***
/*** where
/*** <t1> The alarm clock interval
/*** <t2> The max. time a user must wait for an application serv.
/*** <t3> Minimum time between the start of applic. serv.s
/*** <t4> Timeout period for servers which have never been used
/*** <t5> Timeout for inactive terminal servers
/*** <t6> Timeout for inactive application servers
/*** <t7> Time between check for failed application servers
/*** <t8> Timeout for resolving deadlocks
/*** <t9> Logging checkpoint interval
/*** <t10> Resource test interval

%TIMING 10,14,10,90,10800,10800,15,20,180,180

 

[Calator]

In MIMS 4.1 with Mincom TP, the setting is in tpnames.tbl. Eg: Set t5 and t6below to 10800 seconds to achieve 3 hours:
/*************************************************************************
/*** The directive to set the system timing parameters.
/*** Usage:
/*** %TIMING <t1>,<t2>,<t3>,<t4>,<t5>,<t6>,<t7>,<t8>,<t9>,<10>
/***
/*** where
/*** <t1> The alarm clock interval
/*** <t2> The max. time a user must wait for an application serv.
/*** <t3> Minimum time between the start of applic. serv.s
/*** <t4> Timeout period for servers which have never been used
/*** <t5> Timeout for inactive terminal servers
/*** <t6> Timeout for inactive application servers
/*** <t7> Time between check for failed application servers
/*** <t8> Timeout for resolving deadlocks
/*** <t9> Logging checkpoint interval
/*** <t10> Resource test interval

%TIMING 10,14,10,90,10800,10800,15,20,180,180

 

[stephenwales]

Yes, but that's the TP, unfortunately, I don't believe that CICS has a similar setting, or at least we haven't found one yet.

Steve

 

[SPV]

Do you have the EAC (Ellipse Admin Console)? If so, it can be configured in there.

In the tree view (left pane), open Instance -> ellipse -> (your CICS region).
In the right pane choose Configure -> Definitions...
Go to the TP tab.
You should find the "Timeout of Inactive Clients" setting in the Connection Management area.

You will need the password for the instance owner (not runtime) user to make the change. Can't remember if the CICS region needs to bounce to pick up the change.

Sorry, but I don't know where these changes are made at file level if the EAC isn't an option.

 

[SPV]

Forgot to mention that, certainly through the EAC, an effective "no timeout" is apparently achieved by setting a timeout of 999. How this works in practice I don't know. That is, it might actually time a connection out after 999 minutes, or it might really leave it alone for ever.

A bit vague, but I hope it helps.