$Web Restore Recset or $Web Rest Recset - Revision history

JAL: /* Syntax */

2013-06-05T21:38:47Z

Syntax

← Older revision		Revision as of 21:38, 5 June 2013
Line 10:		Line 10:

	==Syntax==		==Syntax==
	<p class="syntax"><span class="term">%rc</span> = <span class="literal">$Web_Restore_Recset</span>(<span class="term"> name, id, opts )		<p class="syntax"><span class="term">%rc</span> = <span class="literal">$Web_Restore_Recset</span>(<span class="term"> name, id, opts</span> )
	</p>		</p>

JALWiccan: Automatically generated page update

2013-06-05T21:09:47Z

Automatically generated page update

← Older revision		Revision as of 21:09, 5 June 2013
Line 64:		Line 64:

	%ID = $Web_Form_Parm('FINDID')		%ID = $Web_Form_Parm('FINDID')
	IF %ID NE '' THEN		IF %ID NE <nowiki>''</nowiki> THEN
	%RC = $Web_Restore_Recset('F1', %ID)		%RC = $Web_Restore_Recset('F1', %ID)
	IF NOT %RC THEN		IF NOT %RC THEN

JALWiccan: Automatically generated page update

2013-04-12T19:56:46Z

Automatically generated page update

← Older revision		Revision as of 19:56, 12 April 2013
Line 10:		Line 10:

	==Syntax==		==Syntax==
	<p class="syntax"><span class="term">%rc</span> = $Web_Restore_Recset( name, id, opts )		<p class="syntax"><span class="term">%rc</span> = <span class="literal">$Web_Restore_Recset</span>(<span class="term"> name, id, opts )
	</p>		</p>

JALWiccan: Automatically generated page update

2013-04-10T18:18:24Z

Automatically generated page update

← Older revision		Revision as of 18:18, 10 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:<var>$Web_Restore_Recset</var> or $Web_Rest_Recset}}		{{DISPLAYTITLE:<var>$Web_Restore_Recset</var> or $Web_Rest_Recset}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Restore saved set of records~~<section end="desc" />~~</span>		<span class="pageSubtitle">Restore saved set of records</span>


Line 10:		Line 10:

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~><span class="term">%rc</span> = $Web_Restore_Recset( name, id, opts )		<p class="syntax"><span class="term">%rc</span> = $Web_Restore_Recset( name, id, opts )
	~~<section end="syntax" />~~</p>		</p>

	===Syntax terms===		===Syntax terms===

JAL at 21:12, 26 October 2012

2012-10-26T21:12:16Z

← Older revision		Revision as of 21:12, 26 October 2012
Line 27:		Line 27:
	<td>Does a ''copy''-style save, that is, the contents of the source record set or $list are copied to the restored version, so the source saved record set or $list is still accessible after the call. This is less efficient than a MOVE style save, but it does avoid a potentially problematic side-effect.		<td>Does a ''copy''-style save, that is, the contents of the source record set or $list are copied to the restored version, so the source saved record set or $list is still accessible after the call. This is less efficient than a MOVE style save, but it does avoid a potentially problematic side-effect.
	</td></tr></table>		</td></tr></table>
	The default behavior of <var>$~~WEB_REST_RECSET~~</var> is as if MOVE were specified. This default behavior can be changed on a thread basis, however, by setting the <var>[[SRSPARM parameter\|SRSPARM]]</var> parameter.		The default behavior of <var>$Web_Rest_Recset</var> is as if MOVE were specified. This default behavior can be changed on a thread basis, however, by setting the <var>[[SRSPARM parameter\|SRSPARM]]</var> parameter.
	</td></tr></table>		</td></tr></table>

Line 52:		Line 52:
	The target list or foundset inherits the record locking characteristics of the saved record set which inherited its characteristics from the saved list or foundset. This means that <var>$Web_Restore_Recset</var> makes it possible to restore a record set with different locking characteristics than what the name or label would automatically have. For example, if a saved record set was originally built with an FDR (FIND AND RESERVE) but restored to a label for an FDWOL, the found set associated with the label would still be enqueued in exclusive mode. Similarly, if a saved record set was originally built with a PLACE RECORDS but restored to a label for a FIND, the foundset for the label would be unenqueued. Again, because <var class="product">Model 204</var> LIST manipulation statements assume that LIST is unlocked, <var>$Web_Restore_Recset</var> will not allow an enqueued found set to be restored to a LIST. </p>		The target list or foundset inherits the record locking characteristics of the saved record set which inherited its characteristics from the saved list or foundset. This means that <var>$Web_Restore_Recset</var> makes it possible to restore a record set with different locking characteristics than what the name or label would automatically have. For example, if a saved record set was originally built with an FDR (FIND AND RESERVE) but restored to a label for an FDWOL, the found set associated with the label would still be enqueued in exclusive mode. Similarly, if a saved record set was originally built with a PLACE RECORDS but restored to a label for a FIND, the foundset for the label would be unenqueued. Again, because <var class="product">Model 204</var> LIST manipulation statements assume that LIST is unlocked, <var>$Web_Restore_Recset</var> will not allow an enqueued found set to be restored to a LIST. </p>

	<li><var>$Web_Restore_Recset</var> can be used on non-<var class="product">[[Janus Web Server]]</var> threads by <var class="product">[[Janus Web Server]]</var> customers. In fact, a record set can be saved on one type of thread (say a <var class="product">[[Janus Web Server]]</var> thread) and restored on another (say a VTAM 3270 thread).		<li><var>$Web_Restore_Recset</var> can be used on non-<var class="product">[[Janus Web Server]]</var> threads by <var class="product">Janus Web Server</var> customers. In fact, a record set can be saved on one type of thread (say a <var class="product">Janus Web Server</var> thread) and restored on another (say a VTAM 3270 thread).

	<li>A <var>$Web_Restore_Recset</var> must be issued under the same userid under which the <var>$Web_Save_Recset</var> was issued. This userid ''can'' be the WEBUSER userid.		<li>A <var>$Web_Restore_Recset</var> must be issued under the same userid under which the <var>$Web_Save_Recset</var> was issued. This userid ''can'' be the WEBUSER userid.
Line 81:		Line 81:
	</p>		</p>
	<p>		<p>
	In the above example, the ID for a previous range find is retrieved from an invisible form field. If the ID exists and the record set is restored, the expensive FIND statement is skipped. Otherwise, the parameters for the FIND are retrieved from (possibly invisible) form fields and the FIND is redone. Later in the code, the record set associated with label F1 could be saved with [[$Web_Save_Recset]], whether it had been restored with <var>$Web_Restore_Recset</var> or built with the FIND. </p>		In the above example, the ID for a previous range find is retrieved from an invisible form field. If the ID exists and the record set is restored, the expensive FIND statement is skipped. Otherwise, the parameters for the FIND are retrieved from (possibly invisible) form fields and the FIND is redone. Later in the code, the record set associated with label F1 could be saved with <var>[[$Web_Save_Recset]]</var>, whether it had been restored with <var>$Web_Restore_Recset</var> or built with the FIND. </p>

	==See also==		==See also==

JALWiccan: 1 revision

2012-10-26T20:26:24Z

1 revision

← Older revision	Revision as of 20:26, 26 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-26T20:26:21Z

1 revision

← Older revision		Revision as of 20:26, 26 October 2012
Line 27:		Line 27:
	<td>Does a ''copy''-style save, that is, the contents of the source record set or $list are copied to the restored version, so the source saved record set or $list is still accessible after the call. This is less efficient than a MOVE style save, but it does avoid a potentially problematic side-effect.		<td>Does a ''copy''-style save, that is, the contents of the source record set or $list are copied to the restored version, so the source saved record set or $list is still accessible after the call. This is less efficient than a MOVE style save, but it does avoid a potentially problematic side-effect.
	</td></tr></table>		</td></tr></table>
	The default behavior of $WEB_REST_RECSET is as if MOVE were specified. This default behavior can be changed on a thread basis, however, by setting the <var>[[SRSPARM parameter\|SRSPARM]]</var> parameter.		The default behavior of <var>$WEB_REST_RECSET</var> is as if MOVE were specified. This default behavior can be changed on a thread basis, however, by setting the <var>[[SRSPARM parameter\|SRSPARM]]</var> parameter.
	</td></tr></table>		</td></tr></table>

JALWiccan: 1 revision

2012-10-17T21:45:51Z

1 revision

← Older revision	Revision as of 21:45, 17 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-17T21:45:47Z

1 revision

← Older revision		Revision as of 21:45, 17 October 2012
Line 10:		Line 10:

	==Syntax==		==Syntax==
	<p class="syntax"><section begin="syntax" />%rc = $Web_Restore_Recset( name, id, opts )		<p class="syntax"><section begin="syntax" /><span class="term">%rc</span> = $Web_Restore_Recset( name, id, opts )
	<section end="syntax" /></p>		<section end="syntax" /></p>

JALWiccan: 1 revision

2012-10-16T23:37:46Z

1 revision

← Older revision	Revision as of 23:37, 16 October 2012
(No difference)