× Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…

Maintenace file T24.SESSION, OS.TOKEN,OS.TOKEN.USE

  • kda
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
9 years 5 months ago #16464 by kda
Dear all

Please tell us how these process & their maintenace T24.SESSION, OS.TOKEN,OS.TOKEN.USE

Thanks

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • TAFj-R20 - 'unix'
More
9 years 5 months ago #16481 by jpb
From TCSP - FAQ

T24.SESSION
From R10, when any connection is made to T24, system would generate a unique session number and will update in T24.SESSION file. This unique session number will be used for the life of that process/session. Sample of the below update to this file. Field AGENT.NUMBER will hold the id of the corresponding TSA.STATUS record.
LIST F.T24.SESSION
@ID............ 9038
@ID............ 9038
T24.SESSION.NO. 9038
AGENT.NUMBER... OLTP9038
DATE........... 20100130
TIME........... 18:42:50
Please note that whenever a request is posted from T24 browser, a connection is established between web application server and the jbase Agent. At this point, system will get a session number by randomly generating a number from 1 to 9999.After getting the session number system will check whether the T24.SESSION number generated already exists or not. If it does not exists, system will assign this session number and update the T24.SESSION record and TSA.STATUS record.
If a particular session number exists, system also cross checks if that is being currently used or not, if not system would reuse the same session number.
This is a very sensitive file and should never be cleared as the unique part in ID generation will now contain this session number instead of port number of that session.

OS.TOKEN & OS.TOKEN.USE
When will OS.TOKEN get deleted?
Whenever a user login to T24, a unique token id will be created in the F.OS.TOKEN and F.OS.TOKEN.USE. When the user log-off, system will remove the id from the F.OS.TOKEN.
The record is removed from the F.OS.TOKEN only in the following scenario
1. When the user sign off by using “sign-off” button
2. When the user sign off by using “LO” command from command line
3. When the system is in idle, the record from F.OS.TOKEN gets removed only when the time in TIME.OUT.MINUTES field in USER record is reached. If the TIME.OUT.MINUTES field in USER record is empty, then time specified in AUTOLOG.TIME.MINS field of SPF record is referred.
The record from F.OS.TOKEN will not be removed in the following scenario but the record will be overwrite when the same T24 user logins next time:
1. If user shut TCServer/jboss down abruptly
2. If the user closes the Browser window using X button in the top right corner of the window without signing off.

--> so you can clear them when no users are signed on.
The following user(s) said Thank You: tomsawyer

Please Log in or Create an account to join the conversation.

Time to create page: 0.095 seconds