Lock Monitor - Revision history

Anw: Merged from training document

2024-05-10T15:15:00Z

Merged from training document

← Older revision		Revision as of 17:15, 10 May 2024
Line 6:		Line 6:

	Lock Monitor form can be accessed from the Administration Menu.		Lock Monitor form can be accessed from the Administration Menu.

			== Record Lock ==
			The system can legitimately notify where a user is attempting to view or change data where another user is currently in the process of editing the same record related to a specific order or trip.
			The user is advised to use the Lock Monitor form in order to enquire why the data is locked.

			[[Image:record_lock.png]]

			In this instance the form should be used for enquiry in order to ascertain whether it is genuine user activity or if it is a data lock from a redundant session – in the majority of cases the user should be advised to Save their data which will release the lock.

			{{Note}} C-TMS server automatic administration routines run to check where a redundant session lock may have been left and will automatically remove this.

			== The Lock Monitor Form ==

			The lock Monitor is a high level super user screen which allows you to see any data tables for which there may be one or more locked records. You can also see all current user sessions and any user sessions that may be blocked by another user.

	There are multiple tabs.		There are multiple tabs.

	== Locks ==		=== Locks ===
			This tab indicates any current data tables that have one or more records locked by a user. This will show ALL transactions and so the majority of which will be perfectly normal transactions updating data.
	~~The data shown in this~~ tab ~~will show~~ any ~~user~~ that ~~is currently within~~ a ~~form making changes~~. ~~When they save their changes~~ the ~~lock~~ will ~~release~~. ~~This is to stop other people making changes to the same record~~

	Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.		Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.
Line 24:		Line 37:


	== Blocks ==		=== Blocks ===
			This tab highlights any users that may currently be blocked by another user process and indicates which data table the blocked user is trying to update. This is predominately caused when two or more users are attempting to update the same data record.

	Blocking happens when one connection from an application holds a lock and a second connection requires a conflicting lock type. This forces the second connection to wait, blocked on the first. One connection can block another connection, regardless of whether they emanate from the same application or separate applications on different client computers.		Blocking happens when one connection from an application holds a lock and a second connection requires a conflicting lock type. This forces the second connection to wait, blocked on the first. One connection can block another connection, regardless of whether they emanate from the same application or separate applications on different client computers.

Line 32:		Line 47:


	== Sessions ==		=== Sessions ===
			This tab highlights any current users sessions that are connected to the C-TMS application.

	This tab shows all sessions that a User currently has open. Note that C-TMS is a Modal database, which means the user can open up multiple forms at the same time. Each time the user opens up a form on top of another one another session will be created.		This tab shows all sessions that a User currently has open. Note that C-TMS is a Modal database, which means the user can open up multiple forms at the same time. Each time the user opens up a form on top of another one another session will be created.

	Please note that you will also see sessions in here if a developer or Administrator is accessing the system via the SQL server.		Please note that you will also see sessions in here if a developer or Administrator is accessing the system via the SQL server.

			An indication of the initial logon time and when the last activity was conducted is also shown. Most of these will be genuine sessions and are perfectly normal.

	<center>[[Image:lock_sessions.png\|800px]]</center>		<center>[[Image:lock_sessions.png\|800px]]</center>


	== Multiple Sessions ==		=== Multiple Sessions ===
	This tab shows all users with multiple sessions open.		This tab shows all users with multiple sessions open.

Line 46:		Line 65:


	== Jobs Running ==		=== Jobs Running ===
	This tab shows all running jobs in the system.		This tab shows all running jobs in the system.

Line 52:		Line 71:


	== Print Queues ==		=== Print Queues ===
	This tab shows all print queues.		This tab shows all print queues.

Anw: Categorisation

2024-05-09T12:55:15Z

Categorisation

← Older revision		Revision as of 14:55, 9 May 2024
Line 62:		Line 62:
	You can restart the queue, cancel the running job or cancel all jobs with the provided buttons.		You can restart the queue, cancel the running job or cancel all jobs with the provided buttons.

			<noinclude>
	[[Category:C-TMS Admin\|190]]		[[Category:C-TMS Admin\|190]]
	[[Category:C-TMS User Guide\|C-190]]		[[Category:C-TMS User Guide\|C-190]]
			</noinclude>

Anw: Merged from training document

2024-05-09T12:38:58Z

Merged from training document

← Older revision		Revision as of 14:38, 9 May 2024
Line 1:		Line 1:
	~~The~~ Lock Monitor ~~screen~~ is a ~~utility to show potential blocking issues preventing~~ the ~~application running as smoothly as it should,~~ and ~~to provide limited tools to clear those issues~~.		Lock Monitor functionality in C-TMS allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.

			One simple example where the system could lock a transaction is that when in midst of changing the details of a Order/Trip the users closes the session with C-TMS by using the ‘x’ button of the windows explorer and not properly ‘Exiting’ the C-TMS system.

			[[Image:lock_1.png]]

			Lock Monitor form can be accessed from the Administration Menu.

	There are multiple tabs.		There are multiple tabs.

	== Locks ==		== Locks ==

			The data shown in this tab will show any user that is currently within a form making changes. When they save their changes the lock will release. This is to stop other people making changes to the same record

	Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.		Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.

			By using the '''Kill Session''' button, you will be able to close the session of a particular user. All unsaved information will be lost and the user will show an error message and will have to log into C-TMS again.

			As this is powerful functionality, the access to this form will be restricted to a select few users.

	<center>[[Image:lock_locks.png\|800px]]</center>		<center>[[Image:lock_locks.png\|800px]]</center>
Line 13:		Line 25:

	== Blocks ==		== Blocks ==
	Blocking ~~locks will prevent anyone else using~~ the ~~system~~. ~~This screen shows them~~.		Blocking happens when one connection from an application holds a lock and a second connection requires a conflicting lock type. This forces the second connection to wait, blocked on the first. One connection can block another connection, regardless of whether they emanate from the same application or separate applications on different client computers.

			When data is seen within this tab the user can kill the session(s) by clicking on the '''Kill Session''' button from within the Locks Tab.

	<center>[[Image:lock_blocks.png\|800px]]</center>		<center>[[Image:lock_blocks.png\|800px]]</center>
Line 19:		Line 33:

	== Sessions ==		== Sessions ==
	~~Sessions~~ shows all ~~users~~ or ~~processes connected to~~ the system.		This tab shows all sessions that a User currently has open. Note that C-TMS is a Modal database, which means the user can open up multiple forms at the same time. Each time the user opens up a form on top of another one another session will be created.

			Please note that you will also see sessions in here if a developer or Administrator is accessing the system via the SQL server.

	<center>[[Image:lock_sessions.png\|800px]]</center>		<center>[[Image:lock_sessions.png\|800px]]</center>
Line 31:		Line 47:

	== Jobs Running ==		== Jobs Running ==
	This tab ~~shos~~ all running jobs in the system.		This tab shows all running jobs in the system.

	<center>[[Image:lock_jobs.png\|800px]]</center>		<center>[[Image:lock_jobs.png\|800px]]</center>

Anw: Minor correction

2024-05-08T15:34:46Z

Minor correction

← Older revision		Revision as of 17:34, 8 May 2024
Line 3:		Line 3:
	There are multiple tabs.		There are multiple tabs.

	== Locks ===		== Locks ==

	Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.		Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.

Anw: Updated to latest screen version

2024-05-08T15:34:13Z

Updated to latest screen version

@@ Line 1: / Line 1: @@
 Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.
-To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[C-TMS]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''
+<center>[[Image:lock_locks.png|800px]]</center>
 [[Category:C-TMS Admin|190]]
 [[Category:C-TMS User Guide|C-190]]

Admin at 13:20, 11 May 2011

2011-05-11T13:20:34Z

← Older revision		Revision as of 15:20, 11 May 2011
Line 3:		Line 3:
	To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[C-TMS]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''		To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[C-TMS]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''

	<center>[[Image:lock_1.jpg]]</center>		<center>[[Image:lock_1.jpg\|600px]]</center>

	[[Category:C-TMS Admin\|190]]		[[Category:C-TMS Admin\|190]]
	[[Category:C-TMS User Guide\|C-190]]		[[Category:C-TMS User Guide\|C-190]]

Anw at 13:09, 11 May 2011

2011-05-11T13:09:36Z

← Older revision		Revision as of 15:09, 11 May 2011
Line 4:		Line 4:

	<center>[[Image:lock_1.jpg]]</center>		<center>[[Image:lock_1.jpg]]</center>

			[[Category:C-TMS Admin\|190]]
			[[Category:C-TMS User Guide\|C-190]]

Admin at 14:12, 12 November 2010

2010-11-12T14:12:29Z

← Older revision		Revision as of 16:12, 12 November 2010
Line 1:		Line 1:
	Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.		Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.

	To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[~~MTS~~]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''		To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[C-TMS]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''

	<center>[[Image:lock_1.jpg]]</center>		<center>[[Image:lock_1.jpg]]</center>

Admin: New page: Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked. ...

2008-12-31T12:13:55Z

New page: Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked. ...

New page

Lock Monitor allows users with appropriate authority to view and monitor user sessions that are locking a particular transaction. It is possible to close sessions that have been locked.

To test this on a test system Edit a Trip in the [[Trip Manipulation]] screen then Open Lock Monitor, you will see that you have particular tables locked relating to the trip you are editing. Now open two [[MTS]] sessions with different user ID’s and use both to access the same trip in [[Trip Manipulation]]. One user will be informed that the other user has the trip locked. '''(Do not try this in a production environment! Make sure you are logged into a test system first.)'''

<center>[[Image:lock_1.jpg]]</center>