$Wait - Revision history

JAL: add italics

2018-01-02T17:35:47Z

add italics

Dme: /* Example */

2017-12-27T12:41:31Z

Example

@@ Line 142: / Line 142: @@
 <p>
 If User 2 starts after 60 seconds have elapsed and the ECB number 3 has been posted, then User 2 will not wait, but will print the last post code for the ECB number 3.</p>
 [[Category:SOUL $functions]]

JALWiccan: Automatically generated page update

2014-09-08T20:13:38Z

Automatically generated page update

← Older revision		Revision as of 20:13, 8 September 2014
Line 131:		Line 131:
	END		END
	</p>		</p>
	<p>User 2 starting after the previous <var>$~~EcbDset~~</var>, but before 60 seconds have elapsed:</p>		<p>User 2 starting after the previous <var>$EcbDSet</var>, but before 60 seconds have elapsed:</p>
	<p class="code">BEGIN		<p class="code">BEGIN
	PRINT 'WAITING ON ECB 3'		PRINT 'WAITING ON ECB 3'

JAL at 20:02, 8 September 2014

2014-09-08T20:02:15Z

Show changes

Admin at 19:04, 8 September 2014

2014-09-08T19:04:24Z

← Older revision		Revision as of 19:04, 8 September 2014
Line 2:		Line 2:
	<p>Suspend a user until an Event Control Block (ECB) is posted</p>		<p>Suspend a user until an Event Control Block (ECB) is posted</p>
	<b>Syntax</b>		<b>Syntax</b>
	<p class="code">$~~WAIT~~(ECB-number [,'SWAP' \| 'NOSWAP']		<p class="code">$Wait(ECB-number [,'SWAP' \| 'NOSWAP']

	[,time-interval] \| 'CPQZ' \| 'QZSIG')		[,time-interval] \| 'CPQZ' \| 'QZSIG')
Line 15:		Line 15:
	<p>A time-interval may be from zero to 86400 and indicated as a number, %variable, or a string. A time-interval less than one is treated as no time-interval supplied with no time-out to happen.</p>		<p>A time-interval may be from zero to 86400 and indicated as a number, %variable, or a string. A time-interval less than one is treated as no time-interval supplied with no time-out to happen.</p>
	<p>If a time-interval is specified, the second argument, SWAP or NOSWAP, is activated. You can specify 'SWAP' or 'NOSWAP', or accept the default, SWAP, using the following syntax:</p>		<p>If a time-interval is specified, the second argument, SWAP or NOSWAP, is activated. You can specify 'SWAP' or 'NOSWAP', or accept the default, SWAP, using the following syntax:</p>
	<p class="code">$~~WAIT~~(ECB-number,,time-interval)		<p class="code">$Wait(ECB-number,,time-interval)
	</p>		</p>
	<p>The time-interval can be used as an argument to $~~WAIT~~ to determine when an extended quiesce event starts; at that time the backup can be submitted. When these users are placed in a wait state, the wait type is 47.</p>		<p>The time-interval can be used as an argument to <var>$Wait</var> to determine when an extended quiesce event starts; at that time the backup can be submitted. When these users are placed in a wait state, the wait type is 47.</p>
	</li>		</li>
	<li>The CPQZ and QZSIG keywords are the named ECBs for extended quiesce, which are used by the NonStop/204 facility for independently run third-party backups. See the Rocket <var class="product">Model 204</var> System Manager's Guide for an explanation of the facility. </li>		<li>The CPQZ and QZSIG keywords are the named ECBs for extended quiesce, which are used by the NonStop/204 facility for independently run third-party backups. See the Rocket <var class="product">Model 204</var> System Manager's Guide for an explanation of the facility. </li>
Line 24:		Line 24:
	<p>CPQZ is posted internally at the beginning of each extended quiesce and unposted internally at the interval end.</p>		<p>CPQZ is posted internally at the beginning of each extended quiesce and unposted internally at the interval end.</p>
	<p>QZSIG can be posted during the extended quiesce. It is unposted internally at the end of extended quiesce.</p>		<p>QZSIG can be posted during the extended quiesce. It is unposted internally at the end of extended quiesce.</p>
	<p>The $~~WAIT~~ function applied to CPQZ and QZSIG are bumpable, swappable waits of type 47 for CPQZ and 48 for QZSIG. You cannot specify the SWAP or NOSWAP keywords or time-interval with the named ECBs.</p>		<p>The <var>$Wait</var> function applied to CPQZ and QZSIG are bumpable, swappable waits of type 47 for CPQZ and 48 for QZSIG. You cannot specify the SWAP or NOSWAP keywords or time-interval with the named ECBs.</p>
	<b>Usage</b>		<b>Usage</b>
	<p>You can use the $~~WAIT~~ function to suspend a user, meaning: put that user into a wait state until the ECB is posted by another user with the $POST function. Users who have issued a $~~WAIT~~ function call are bumpable and may be swappable depending on whether SWAP or NOSWAP was used in the $~~WAIT~~ call. </p>		<p>You can use the <var>$Wait</var> function to suspend a user, meaning: put that user into a wait state until the ECB is posted by another user with the $POST function. Users who have issued a <var>$Wait</var> function call are bumpable and may be swappable depending on whether SWAP or NOSWAP was used in the <var>$Wait</var> call. </p>
	<p class="note"><b>Caution:</b> Limit the use of the $~~WAIT~~ function with the NOSWAP option to situations where only a small number of threads may use it. This will avoid having all servers occupied by users in a NOSWAP state and having no available server for a posting user to swap into.</p>		<p class="note"><b>Caution:</b> Limit the use of the <var>$Wait</var> function with the NOSWAP option to situations where only a small number of threads may use it. This will avoid having all servers occupied by users in a NOSWAP state and having no available server for a posting user to swap into.</p>
	<p>Using the $~~WAIT~~ function, you can put a User Language thread into a wait state. To perform third-party backups, the thread must wait for the extended quiesce of a checkpoint to start and then submit a backup job. </p>		<p>Using the <var>$Wait</var> function, you can put a User Language thread into a wait state. To perform third-party backups, the thread must wait for the extended quiesce of a checkpoint to start and then submit a backup job. </p>
	<ul>		<ul>
	<li>For numbered ECBs, you can use the $POST, $UNPOST, and $~~WAIT~~ functions to coordinate processing between threads.</li>		<li>For numbered ECBs, you can use the $POST, $UNPOST, and <var>$Wait</var> functions to coordinate processing between threads.</li>
	</li>		</li>
	<li>For the QZSIG ECB, you can use the $POST and $~~WAIT~~ functions to signal and recognize the end of an extended quiesce for third-party backups.</li>		<li>For the QZSIG ECB, you can use the $POST and <var>$Wait</var> functions to signal and recognize the end of an extended quiesce for third-party backups.</li>
	</li>		</li>
	<li>For the CPQZ ECB, you can use the $~~WAIT~~ function to wait on the start of an extended quiesce.</li>		<li>For the CPQZ ECB, you can use the <var>$Wait</var> function to wait on the start of an extended quiesce.</li>
	</li>		</li>
	</ul>		</ul>
	<p>The following return codes apply to the $~~WAIT~~ function:</p>		<p>The following return codes apply to the <var>$Wait</var> function:</p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 93:		Line 93:
	<tr>		<tr>
	<td align="right">16</td>		<td align="right">16</td>
	<td>$~~WAIT~~ finished due to expired time interval</td>		<td><var>$Wait</var> finished due to expired time interval</td>
	</tr>		</tr>
	<tr>		<tr>
Line 100:		Line 100:
	</tr>		</tr>
	</table>		</table>
	<p>When the ECB specified in the $~~WAIT~~ call is posted, the waiting user will resume evaluation and may capture the post code with $STATUSD. See the following $~~WAIT~~ example. </p>		<p>When the ECB specified in the <var>$Wait</var> call is posted, the waiting user will resume evaluation and may capture the post code with $STATUSD. See the following <var>$Wait</var> example. </p>
	<b>Example</b>		<b>Example</b>
	<p>The following code illustrates an interaction between User 1 and User 2. User 1 issues the following:</p>		<p>The following code illustrates an interaction between User 1 and User 2. User 1 issues the following:</p>
Line 118:		Line 118:
	END		END
	</p>		</p>
	<p>User 2 will be suspended (WT=30) when the $~~WAIT~~ call is evaluated and will resume processing when ECB number 3 is posted by User 1. $STATUSD will return the post code value = 5678. </p>		<p>User 2 will be suspended (WT=30) when the <var>$Wait</var> call is evaluated and will resume processing when ECB number 3 is posted by User 1. $STATUSD will return the post code value = 5678. </p>
	<p>If User 2 starts after 60 seconds have elapsed and the ECB number 3 has been posted, then User 2 will not wait, but will print the last post code for the ECB number 3.</p>		<p>If User 2 starts after 60 seconds have elapsed and the ECB number 3 has been posted, then User 2 will not wait, but will print the last post code for the ECB number 3.</p>
	[[Category:SOUL $functions]]		[[Category:SOUL $functions]]

Admin: Admin moved page $WAIT to $Wait without leaving a redirect: caps in title

2014-09-08T19:00:22Z

Admin moved page $WAIT to $Wait without leaving a redirect: caps in title

← Older revision	Revision as of 19:00, 8 September 2014
(No difference)

Alex: Automatically generated page update

2013-04-20T13:18:37Z

Automatically generated page update

New page

Function
Suspend a user until an Event Control Block (ECB) is posted
Syntax
$WAIT(ECB-number [,'SWAP' | 'NOSWAP']

[,time-interval] | 'CPQZ' | 'QZSIG')

Where:
<ul>
<li>ECB-number is a string with a numeric value from one to the NECBS parameter, which identifies the ECB upon which to wait. ECB-number can be expressed as a numeric, a literal, a %variable, or a field name. This is a user defined event. When these users are placed in a wait state, the wait type is 30.</li>
</li>
<li>SWAP keyword specifies a swappable wait; this is the default. The NOSWAP keyword specifies a nonswappable wait. If you enter a keyword, enclose it in single quotation marks.</li>
</li>
<li>time-interval specifies the maximum number of seconds to wait. A wait that is finished, because the time expired, is indicated by a return code 16.</li>
A time-interval may be from zero to 86400 and indicated as a number, %variable, or a string. A time-interval less than one is treated as no time-interval supplied with no time-out to happen.
If a time-interval is specified, the second argument, SWAP or NOSWAP, is activated. You can specify 'SWAP' or 'NOSWAP', or accept the default, SWAP, using the following syntax:
$WAIT(ECB-number,,time-interval)

The time-interval can be used as an argument to $WAIT to determine when an extended quiesce event starts; at that time the backup can be submitted. When these users are placed in a wait state, the wait type is 47.
</li>
<li>The CPQZ and QZSIG keywords are the named ECBs for extended quiesce, which are used by the NonStop/204 facility for independently run third-party backups. See the Rocket <var class="product">Model 204</var> System Manager's Guide for an explanation of the facility. </li>
</li>
</ul>
CPQZ is posted internally at the beginning of each extended quiesce and unposted internally at the interval end.
QZSIG can be posted during the extended quiesce. It is unposted internally at the end of extended quiesce.
The $WAIT function applied to CPQZ and QZSIG are bumpable, swappable waits of type 47 for CPQZ and 48 for QZSIG. You cannot specify the SWAP or NOSWAP keywords or time-interval with the named ECBs.
Usage
You can use the $WAIT function to suspend a user, meaning: put that user into a wait state until the ECB is posted by another user with the $POST function. Users who have issued a $WAIT function call are bumpable and may be swappable depending on whether SWAP or NOSWAP was used in the $WAIT call. 
Caution: Limit the use of the $WAIT function with the NOSWAP option to situations where only a small number of threads may use it. This will avoid having all servers occupied by users in a NOSWAP state and having no available server for a posting user to swap into.
Using the $WAIT function, you can put a User Language thread into a wait state. To perform third-party backups, the thread must wait for the extended quiesce of a checkpoint to start and then submit a backup job. 
<ul>
<li>For numbered ECBs, you can use the $POST, $UNPOST, and $WAIT functions to coordinate processing between threads.</li>
</li>
<li>For the QZSIG ECB, you can use the $POST and $WAIT functions to signal and recognize the end of an extended quiesce for third-party backups.</li>
</li>
<li>For the CPQZ ECB, you can use the $WAIT function to wait on the start of an extended quiesce.</li>
</li>
</ul>
The following return codes apply to the $WAIT function:
<table>
<tr class="head">
<th>Return code </th>
<th>Meaning</th>
</tr>
<tr>
<td align="right">0 </td>
<td>Success</td>
</tr>
<tr>
<td align="right">2 </td>
<td>Bad argument specified</td>
</tr>
<tr>
<td align="right">3 </td>
<td>NECBS parameter is not specified or is zero</td>
</tr>
<tr>
<td align="right">4 </td>
<td>The first argument is less than one or greater than the NECBS parameter</td>
</tr>
<tr>
<td align="right">5 </td>
<td>NUSERS = 1</td>
</tr>
<tr>
<td align="right">6 </td>
<td>NOSWAP and NSERVS EQ 1</td>
</tr>
<tr>
<td align="right">8 </td>
<td>No argument specified</td>
</tr>
<tr>
<td align="right">9</td>
<td>Checkpointing inactive, if using extended quiesce ECBs, CPQZ or QZSIG</td>
</tr>
<tr>
<td align="right">11 </td>
<td>The CPQZ or QZSIG ECB is already posted</td>
</tr>
<tr>
<td align="right">12</td>
<td>Invalid argument CPQZ or invalid argument following QZSIG</td>
</tr>
<tr>
<td align="right">13</td>
<td>For QZSIG, the system is not in extended quiesce or already leaving extended quiesce</td>
</tr>
<tr>
<td align="right">15</td>
<td>Time interval is not numeric or greater than 86,400</td>
</tr>
<tr>
<td align="right">16</td>
<td>$WAIT finished due to expired time interval</td>
</tr>
<tr>
<td align="right">17</td>
<td>Second argument entered is not SWAP or NOSWAP</td>
</tr>
</table>
When the ECB specified in the $WAIT call is posted, the waiting user will resume evaluation and may capture the post code with $STATUSD. See the following $WAIT example. 
Example
The following code illustrates an interaction between User 1 and User 2. User 1 issues the following:
BEGIN
%X=$ECBDSET(3,'THIS IS ECB 3')
PAUSE 60
%X=$POST(3,5678)
END

User 2 starting after the previous $ECBDSET, but before 60 seconds have elapsed:
BEGIN
PRINT 'WAITING ON ECB 3'
NP
%X=$WAIT(3)
PRINT 'ECB 3 HAS BEEN POSTED WITH POST CODE= ' WITH -
$STATUSD
END

User 2 will be suspended (WT=30) when the $WAIT call is evaluated and will resume processing when ECB number 3 is posted by User 1. $STATUSD will return the post code value = 5678. 
If User 2 starts after 60 seconds have elapsed and the ECB number 3 has been posted, then User 2 will not wait, but will print the last post code for the ECB number 3.
[[Category:SOUL $functions]]