Blog
i can

Dawn May

Dawn May




Bookmark and Share

October 2014

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

« Lesser-Known Features of Work With System Activity | Main | Move My i »

April 18, 2012

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83545a5d153ef0163045805a6970d

Listed below are links to weblogs that reference IBM Improves the Handling of the Inactivity Timeout :

Comments

This is a fantastic improvement that will make the inactive timeout more precise.

Now is there any chance we can get the work management team to disconnect an inactive job if it is on a device name that starts with QPADEV? At least give us an option to do it? I've had it explained to me about 5 times in 10 years but it makes no sense why the inactivity timer can end a job but not disconnect it just because the device name starts with QPADEV.

Thanks for the consideration.

There has been some discussion about allowing DSCJOB for QPADEVxxxx devices.

For the case where DSCJOB is being done in response to a device error, the restriction would probably still be there. The session is gone and it is very unlikely for the same user to get that device when the device is next used.

For inactivity, the session is still intact and connected to the same user's workstation. Similarly, if a user wants to DSCJOB rather than SIGNOFF, this is probably a good thing to allow.

I don't know if this sort of change will ever get done (it is not currently "in plan"), but there is a chance.

The comments to this entry are closed.