SRSPARM parameter - Revision history

JAL: minor formatting

2017-09-11T16:46:31Z

minor formatting

← Older revision		Revision as of 16:46, 11 September 2017
Line 23:		Line 23:
	The default behavior of all of these functions can, however, be changed on		The default behavior of all of these functions can, however, be changed on
	a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset		a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset
	with <var>[[~~$Resetn\|~~$Resetn]]</var>).		with <var>[[$Resetn]]</var>).

	<var>SRSPARM</var> is a bitmask user parameter where the bits mean:		<var>SRSPARM</var> is a bitmask user parameter where the bits mean:

DCameron: /* Description */

2017-09-11T11:55:23Z

Description

← Older revision		Revision as of 11:55, 11 September 2017
Line 23:		Line 23:
	The default behavior of all of these functions can, however, be changed on		The default behavior of all of these functions can, however, be changed on
	a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset		a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset
	with <var>$Resetn</var>).		with <var>[[$Resetn\|$Resetn]]</var>).

	<var>SRSPARM</var> is a bitmask user parameter where the bits mean:		<var>SRSPARM</var> is a bitmask user parameter where the bits mean:

DmeWiccan: Automatically generated page update

2013-08-27T16:44:06Z

Automatically generated page update

← Older revision		Revision as of 16:44, 27 August 2013
Line 1:		Line 1:
			{{Template:SRSPARM parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

JAL2 at 16:58, 13 March 2012

2012-03-13T16:58:47Z

← Older revision		Revision as of 16:58, 13 March 2012
Line 6:		Line 6:
	<dd>User		<dd>User
	<dt>Where set		<dt>Where set
	<dd>User and <var>$Resetn</var> resettable		<dd>User and <var>[[$Resetn]]</var> resettable
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All
Line 22:		Line 22:
	The default behavior of all of these functions can, however, be changed on		The default behavior of all of these functions can, however, be changed on
	a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset		a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset
	with <var>[[$Resetn]]</var>).		with <var>$Resetn</var>).

	<var>SRSPARM</var> is a bitmask user parameter where the bits mean:		<var>SRSPARM</var> is a bitmask user parameter where the bits mean:

JAL2 at 16:56, 13 March 2012

2012-03-13T16:56:47Z

← Older revision		Revision as of 16:56, 13 March 2012
Line 6:		Line 6:
	<dd>User		<dd>User
	<dt>Where set		<dt>Where set
	<dd>User and $~~RESETN~~ resettable		<dd>User and <var>$Resetn</var> resettable
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd>Before [[Sirius Mods]] 6.7		<dd>Before <var class=product">Sirius Mods</var> 6.7
	</dl>		</dl>

	==Description==		==Description==
	This bitmask parameter makes it possible to change the default behavior		This bitmask parameter makes it possible to change the default behavior of the
	of the [[$Web_Restore_Recset]] and [[$Web_Restore_List]] functions.		<var>[[$Web_Save_Recset]]</var> and <var>[[$Web_Save_List]]</var> functions as well as
	By default, ~~they~~ act as if MOVE were specified.		the <var>[[$Web_Restore_Recset]]</var> and <var>[[$Web_Restore_List]]</var> functions.

			By default, these $Web_Save functions act as if the <code>STEAL</code>, <code>USTEAL</code> and <code>MOVE</code> options were specified;
			these $Web_Restore functions act as if <code>MOVE</code> were specified.
	The default behavior of all of these functions can, however, be changed on		The default behavior of all of these functions can, however, be changed on
	a thread basis by setting the SRSPARM parameter (which can be reset		a thread basis by setting the <var>SRSPARM</var> parameter (which can be reset
	with $~~RESETN~~).		with <var>[[$Resetn]]</var>).

	SRSPARM is a bitmask user parameter where the bits mean:		<var>SRSPARM</var> is a bitmask user parameter where the bits mean:
	<dl>		<table>
	<dt>X'01'		<tr><th>X'01'
	<dd>Make ~~“~~ERROR~~”~~ the default for $~~WEB_SAVE_RECSET~~ and $~~WEB_SAVE_LIST~~.		</th><td>Make <code>ERROR</code> the default for <var>$Web_Save_Recset</var> and <var>$Web_Save_List</var>.
	<dt>X'02'		</td></tr>
	<dd>Make ~~“~~CANCEL~~”~~ the default for $~~WEB_SAVE_RECSET~~ and $~~WEB_SAVE_LIST~~.		<tr><th>X'02'
	If this bit is set, the X'01' bit is irrelevant.		</th><td>Make <code>CANCEL</code> the default for <var>$Web_Save_Recset</var> and <var>$Web_Save_List</var>. If this bit is set, the X'01' bit is irrelevant.
	<dt>X'04'		</td></tr>
	<dd>Make ~~“~~UERROR~~”~~ the default for $~~WEB_SAVE_RECSET~~ and $~~WEB_SAVE_LIST~~.		<tr><th>X'04'
	<dt>X'08'		</th><td>Make <code>UERROR</code> the default for <var>$Web_Save_Recset</var> and <var>$Web_Save_List</var>.
	<dd>Make ~~“~~UCANCEL~~”~~ the default for $~~WEB_SAVE_RECSET~~ and $~~WEB_SAVE_LIST~~.		</td></tr>
	If this bit is set, the X'04' bit is irrelevant.		<tr><th>X'08'
	<dt>X'10'		</th><td>Make <code>UCANCEL</code> the default for <var>$Web_Save_Recset</var> and <var>$Web_Save_List</var>. If this bit is set, the X'04' bit is irrelevant.
	<dd>Make ~~“~~COPY~~”~~ the default for $~~WEB_SAVE_RECSET~~ and $~~WEB_SAVE_LIST~~.		</td></tr>
	<dt>X'20'		<tr><th>X'10'
	<dd>CANCEL request on a COPY style $~~WEB_SAVE_RECSET~~ for an exclusively locked record set.		</th><td>Make <code>COPY</code> the default for <var>$Web_Save_Recset</var> and <var>$Web_Save_List</var>.
	If this bit is not set, this error would simply be reflected with an error code of 7.		</td></tr>
	This operation is not allowed, because there cannot be two threads that		<tr><th>X'20'
	have the same records locked in exclusive mode, which is what would be		</th><td><var>CANCEL</var> request on a <var>COPY</var> style <var>$Web_Save_Recset</var> for an exclusively locked record set. If this bit is not set, this error would simply be reflected with an error code of 7.
	the case after a COPY type save of an exclusively locked record set.		This operation is not allowed, because there cannot be two threads that have the same records locked in exclusive mode, which is what would be the case after a <var>COPY</var> type save of an exclusively locked record set.
	<dt>X'40'		</td></tr>
	<dd>Make ~~“~~COPY~~”~~ the default for $~~WEB_REST_RECSET~~ and $~~WEB_REST_LIST~~.		<tr><th>X'40'
	<dt>X'80'		</th><td>Make <code>COPY</code> the default for <var>$Web_Rest_Recset</var> and <var>$Web_Rest_List</var>.
	<dd>CANCEL request on a COPY style $~~WEB_REST_RECSET~~ for an exclusively locked record set.		</td></tr>
	If this bit is not set, this error would simply be reflected with an error code of 7.		<tr><th>X'80'
	This operation is not allowed, because there cannot be two threads that		</th><td><var>CANCEL</var> request on a <var>COPY</var> style <var>$Web_Rest_Recset</var> for an exclusively locked record set. If this bit is not set, this error would simply be reflected with an error code of 7.
	have the same records locked in exclusive mode, which is what would be		This operation is not allowed, because there cannot be two threads that have the same records locked in exclusive mode, which is what would be the case after a <var>COPY</var> type restore of an exclusively locked record set.
	the case after a COPY type restore of an exclusively locked record set.		</td></tr></table>
	</dl>
	In general, table full problems with saved record sets are best handled		In general, table full problems with saved record sets are best handled
	(as are most system-wide resource shortages) with request cancellation,		(as are most system-wide resource shortages) with request cancellation,
	because it does not make sense to code applications in a way that		because it does not make sense to code applications in a way that
	would be able to detect and correct for these shortages.		would be able to detect and correct for these shortages.

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

JAL2: /* Description */

2012-03-13T15:45:43Z

Description

← Older revision		Revision as of 15:45, 13 March 2012
Line 23:		Line 23:
	<dl>		<dl>
	<dt>X'01'		<dt>X'01'
	<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST ~~“ERROR”~~.		<dd>Make “ERROR” the default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST.
	<dt>X'02'		<dt>X'02'
	<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST ~~“CANCEL”~~.		<dd>Make “CANCEL” the default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST.
	If this bit is set, the X'01' bit is irrelevant.		If this bit is set, the X'01' bit is irrelevant.
	<dt>X'04'		<dt>X'04'
	<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST ~~“UERROR”~~.		<dd>Make “UERROR” the default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST.
	<dt>X'08'		<dt>X'08'
	<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST ~~“UCANCEL”~~.		<dd>Make “UCANCEL” the default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST.
	If this bit is set, the X'04' bit is irrelevant.		If this bit is set, the X'04' bit is irrelevant.
	<dt>X'10'		<dt>X'10'
	<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST ~~“COPY”~~.		<dd>Make “COPY” the default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST.
	<dt>X'20'		<dt>X'20'
	<dd>CANCEL request on a COPY style $WEB_SAVE_RECSET for an exclusively locked		<dd>CANCEL request on a COPY style $WEB_SAVE_RECSET for an exclusively locked record set.
	record set.		If this bit is not set, this error would simply be reflected with an error code of 7.
	If this bit is not set, this error would simply be reflected with an error
	code of 7.
	This operation is not allowed, because there cannot be two threads that		This operation is not allowed, because there cannot be two threads that
	have the same records locked in exclusive mode, which is what would be		have the same records locked in exclusive mode, which is what would be
	the case after a COPY type save of an exclusively locked record set.		the case after a COPY type save of an exclusively locked record set.
	<dt>X'40'		<dt>X'40'
	<dd>Make default for $WEB_REST_RECSET and $WEB_REST_LIST ~~“COPY”~~.		<dd>Make “COPY” the default for $WEB_REST_RECSET and $WEB_REST_LIST.
	<dt>X'80'		<dt>X'80'
	<dd>CANCEL request on a COPY style $WEB_REST_RECSET for an exclusively locked		<dd>CANCEL request on a COPY style $WEB_REST_RECSET for an exclusively locked record set.
	record set.		If this bit is not set, this error would simply be reflected with an error code of 7.
	If this bit is not set, this error would simply be reflected with an error
	code of 7.
	This operation is not allowed, because there cannot be two threads that		This operation is not allowed, because there cannot be two threads that
	have the same records locked in exclusive mode, which is what would be		have the same records locked in exclusive mode, which is what would be

JAL2 at 14:46, 26 May 2011

2011-05-26T14:46:29Z

New page

==Summary==
<dl>
<dt>Default value
<dd>X'00'
<dt>Parameter type
<dd>User
<dt>Where set
<dd>User and $RESETN resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
==Description==
This bitmask parameter makes it possible to change the default behavior
of the [[$Web_Restore_Recset]] and [[$Web_Restore_List]] functions.
By default, they act as if MOVE were specified.
The default behavior of all of these functions can, however, be changed on
a thread basis by setting the SRSPARM parameter (which can be reset
with $RESETN).

SRSPARM is a bitmask user parameter where the bits mean:
<dl>
<dt>X'01'
<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST “ERROR”.
<dt>X'02'
<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST “CANCEL”.
If this bit is set, the X'01' bit is irrelevant.
<dt>X'04'
<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST “UERROR”.
<dt>X'08'
<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST “UCANCEL”.
If this bit is set, the X'04' bit is irrelevant.
<dt>X'10'
<dd>Make default for $WEB_SAVE_RECSET and $WEB_SAVE_LIST “COPY”.
<dt>X'20'
<dd>CANCEL request on a COPY style $WEB_SAVE_RECSET for an exclusively locked
record set.
If this bit is not set, this error would simply be reflected with an error
code of 7.
This operation is not allowed, because there cannot be two threads that
have the same records locked in exclusive mode, which is what would be
the case after a COPY type save of an exclusively locked record set.
<dt>X'40'
<dd>Make default for $WEB_REST_RECSET and $WEB_REST_LIST “COPY”.
<dt>X'80'
<dd>CANCEL request on a COPY style $WEB_REST_RECSET for an exclusively locked
record set.
If this bit is not set, this error would simply be reflected with an error
code of 7.
This operation is not allowed, because there cannot be two threads that
have the same records locked in exclusive mode, which is what would be
the case after a COPY type restore of an exclusively locked record set.
</dl>
In general, table full problems with saved record sets are best handled
(as are most system-wide resource shortages) with request cancellation,
because it does not make sense to code applications in a way that
would be able to detect and correct for these shortages.

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