SESDEBUG parameter - Revision history

DCameron: /* Description */

2017-05-30T14:05:01Z

Description

← Older revision		Revision as of 14:05, 30 May 2017
Line 23:		Line 23:
	<dd>Issue message [[MSIR.1050\|MSIR.1050]] whenever a session is closed with exclusive record locks in session objects.		<dd>Issue message [[MSIR.1050\|MSIR.1050]] whenever a session is closed with exclusive record locks in session objects.
	<dt>X'02'		<dt>X'02'
	<dd>Issue message [[MSIR.1051\|MSIR.1051]] whenever a session is closed with exclusive record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a SirFact dump to be collected for the problem without actually causing the request to be canceled.		<dd>Issue message [[MSIR.1051\|MSIR.1051]] whenever a session is closed with exclusive record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a [[SirFact\|SirFact dump]] to be collected for the problem without actually causing the request to be canceled.
	<dt>X'04'		<dt>X'04'
	<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.		<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.

DCameron: /* Description */

2017-05-30T14:02:08Z

Description

← Older revision		Revision as of 14:02, 30 May 2017
Line 21:		Line 21:
	<dl>		<dl>
	<dt>X'01'		<dt>X'01'
	<dd>Issue message MSIR.1050 whenever a session is closed with exclusive record locks in session objects.		<dd>Issue message [[MSIR.1050\|MSIR.1050]] whenever a session is closed with exclusive record locks in session objects.
	<dt>X'02'		<dt>X'02'
	<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a SirFact dump to be collected for the problem without actually causing the request to be canceled.		<dd>Issue message [[MSIR.1051\|MSIR.1051]] whenever a session is closed with exclusive record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a SirFact dump to be collected for the problem without actually causing the request to be canceled.
	<dt>X'04'		<dt>X'04'
	<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.		<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.
Line 33:		Line 33:
	<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.		<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.
	</dl>		</dl>

	==Notes==		==Notes==

DmeWiccan: Automatically generated page update

2013-08-27T16:43:49Z

Automatically generated page update

← Older revision		Revision as of 16:43, 27 August 2013
Line 1:		Line 1:
			{{Template:SESDEBUG parameter subtitle}}

	==Summary==		==Summary==

JALWiccan: Automatically generated page update

2013-04-19T20:07:05Z

Automatically generated page update

← Older revision		Revision as of 20:07, 19 April 2013
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Sirius Mods</var> 8.0		<dd><var class="product">[[Sirius Mods]]</var> 8.0
	</dl>		</dl>
	==Description==		==Description==

Alex: /* Notes */

2012-04-06T12:54:15Z

Notes

← Older revision		Revision as of 12:54, 6 April 2012
Line 34:		Line 34:
	==Notes==		==Notes==

	MSIR.1050 indicates the session object name that can be used to get to the object with the record lock and the strength of the lock. If multiple session objects can be used to get to multiple objects with record locks, only one is indicated by the message and the greatest lock strength s indicated.		MSIR.1050 indicates the session object name that can be used to get to the object with the record lock and the strength of the lock. If multiple session objects can be used to get to multiple objects with record locks, only one is indicated by the message and the greatest lock strength is indicated.

	Specifying lower bits is redundant. That is, there is no difference between SESDEBUG X'04', and X'05', and X'06', and X'07', the X'04' bit causes request cancellation on a detected exclusive record lock. Similarly, SESDEBUG X'22' and X'20' have identical meaning, they will both issue MSIR.1051 without cancelling the request for any record locks in session objects. SESDEBUG X'14' is different from X'10', however, because X'14' will cause request cancellation for an exclusive lock in a session object and a only a message for a share lock, while X'10' will only result in a message, regardless of the lock strength.		Specifying lower bits is generally redundant. That is, there is no difference between SESDEBUG X'04', and X'05', and X'06', and X'07', the X'04' bit causes request cancellation on a detected exclusive record lock. Similarly, SESDEBUG X'22' and X'20' have identical meaning, they will both issue MSIR.1051 without cancelling the request for any record locks in session objects. SESDEBUG X'14' is different from X'10', however, because X'14' will cause request cancellation for an exclusive lock in a session object and a only a message for a share lock, while X'10' will only result in a message, regardless of the lock strength.


	[[Category:User parameters]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: /* Description */

2012-04-06T12:53:21Z

Description

← Older revision		Revision as of 12:53, 6 April 2012
Line 32:		Line 32:
	<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.		<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.
	</dl>		</dl>
			==Notes==

	MSIR.1050 indicates the session object name that can be used to get to the object with the record lock and the strength of the lock. If multiple session objects can be used to get to multiple objects with record locks, only one is indicated by the message and the greatest lock strength s indicated.		MSIR.1050 indicates the session object name that can be used to get to the object with the record lock and the strength of the lock. If multiple session objects can be used to get to multiple objects with record locks, only one is indicated by the message and the greatest lock strength s indicated.

Alex: Created page with " ==Summary==

Default value
0
Parameter type
User
Where set
User and `$Resetn` resettable (in subsystem only)
Related products
Al..."

2012-04-06T12:52:15Z

Created page with " ==Summary== <dl> <dt>Default value <dd>0 <dt>Parameter type <dd>User <dt>Where set <dd>User and <var>$Resetn</var> resettable (in subsystem only) <dt>Related products <dd>Al..."

New page

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>User
<dt>Where set
<dd>User and <var>[[$Resetn]]</var> resettable (in subsystem only)
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Sirius Mods</var> 8.0
</dl>
==Description==
This is a bitmask parameter that helps collect diagnostics for problems caused by record locks in session objects. Since session objects can persist over extended periods, it is generally not a good idea to hold record locks in session objects.

The meaning of the <var>SESDEBUG</var> bits are:
<dl>
<dl>
<dt>X'01'
<dd>Issue message MSIR.1050 whenever a session is closed with exclusive record locks in session objects.
<dt>X'02'
<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a SirFact dump to be collected for the problem without actually causing the request to be canceled.
<dt>X'04'
<dd>Issue message MSIR.1051 whenever a session is closed with exclusive record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.
<dt>X'10'
<dd>Issue message MSIR.1050 whenever a session is closed with any (share or exclusive) record locks in session objects.
<dt>X'20'
<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects, but undo the request cancellation normally caused by MSIR.1051. This allows a SirFact dump to be collected for the problem without actually causing the request to be canceled.
<dt>X'40'
<dd>Issue message MSIR.1051 whenever a session is closed with any (share or exclusive) record locks in session objects. This allows a SirFact dump to be collected for the problem and then terminates the request and deletes the session, preventing the record locks from causing any lock conflicts.
</dl>
MSIR.1050 indicates the session object name that can be used to get to the object with the record lock and the strength of the lock. If multiple session objects can be used to get to multiple objects with record locks, only one is indicated by the message and the greatest lock strength s indicated.

Specifying lower bits is redundant. That is, there is no difference between SESDEBUG X'04', and X'05', and X'06', and X'07', the X'04' bit causes request cancellation on a detected exclusive record lock. Similarly, SESDEBUG X'22' and X'20' have identical meaning, they will both issue MSIR.1051 without cancelling the request for any record locks in session objects. SESDEBUG X'14' is different from X'10', however, because X'14' will cause request cancellation for an exclusive lock in a session object and a only a message for a share lock, while X'10' will only result in a message, regardless of the lock strength.

[[Category:User parameters]]
[[Category:Parameters]]

SESDEBUG parameter - Revision history

DCameron: /* Description */

DCameron: /* Description */

DmeWiccan: Automatically generated page update

JALWiccan: Automatically generated page update

Alex: /* Notes */

Alex: /* Description */

Alex: Created page with " ==Summary== Default value 0 Parameter type User Where set User and $Resetn resettable (in subsystem only) Related products Al..."

Alex: Created page with " ==Summary==

Default value
0
Parameter type
User
Where set
User and `$Resetn` resettable (in subsystem only)
Related products
Al..."