Search results

Jump to navigation Jump to search

Google site results

Loading...

Wiki results

  • <span class="pageSubtitle">FORMREDIRWAIT seconds &mdash; seconds to wait for browser to process redirect</span> Indicates the default number of seconds to wait for the client on a <var>[[JANUS DEFINE#type|WEBSERV]]</var> port (presumab ...
    1 KB (228 words) - 17:55, 8 June 2016
  • ...code>), not the percentage of, that might contain users in a non-swappable wait for CFR in EXCL mode.</p> ...o 75 percent of <var>NSERVS</var> to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p> ...
    2 KB (263 words) - 20:30, 20 May 2015
  • ...the number of milliseconds waited for each automatic record locking retry wait. ...with a non-zero value for <var>[[ENQRETRY parameter|ENQRETRY]]</var> will wait at least 3 seconds before the conflict is dealt with. This can degrade over ...
    2 KB (233 words) - 15:13, 18 April 2018
  • ...d.]]   This is not needed if you only use [[TN3270 DEBUG WAIT|TN3270 DEBUG WAIT]].</span> ...#TN3270 DEBUG ON|TN3270 DEBUG ON]] or the [[TN3270 DEBUG WAIT|TN3270 DEBUG WAIT]] command. Your session lasts until you log off </span><var>Model 204</var> ...
    3 KB (463 words) - 23:11, 17 November 2022
  • ...QUIESCE processing is delayed with <var class="term">nnnn</var> user(s) in wait type <var class="term">waitType</var></p> ...n for <var class="term">waitType</var> 48, if the number of users in those wait types, respectively, is non-zero. ...
    1 KB (187 words) - 21:02, 30 March 2018
  • ...he pseudo subtask performing the offload of the ring stream are put into a wait state until the offload process finishes draining the ring member. </P> ...
    1 KB (174 words) - 20:31, 26 March 2018
  • <p>Between each retry attempt, the request is put into a wait state until either: </p> The record locking wait interval time has elapsed. In version 7.8 (or version 7.7 with maintenance) ...
    1 KB (175 words) - 20:25, 11 April 2018
  • ...e</var> statement specified a negative number for the number of seconds to wait. </P> ...
    308 bytes (49 words) - 23:46, 21 February 2018
  • .../var> exception is thrown. Since <var>ContinueIndependently</var> does not wait for the <var>daemon</var> thread to do anything, a <var>DaemonLost</var> ex ...nueIndependently</var> against a daemon not in a <var>ReturnToMaster</var> wait results in an <var>[[IncorrectDaemonState class|IncorrectDaemonState]]</var ...
    3 KB (391 words) - 16:02, 5 August 2014
  • <p><b>Response:</b> Wait for recovery to complete, and retry the command. </p> ...
    347 bytes (56 words) - 14:12, 25 February 2018
  • ...statement specified a number greater than 600 for the number of seconds to wait. </P> ...
    325 bytes (52 words) - 23:47, 21 February 2018
  • <b>Response:</b> Wait for recovery to complete. Then retry the command. ...
    448 bytes (65 words) - 20:48, 15 March 2018
  • <b>Response:</b> Wait for recovery to complete, and retry the command. ...
    363 bytes (58 words) - 20:39, 15 March 2018
  • ...e cannot be enqueued in exclusive mode by ''[[Fast/Unload]]''.load. Either wait until the updating job is completed or use the NOENQ ''[[Fast/Unload]]'' pa ...
    431 bytes (75 words) - 13:41, 19 April 2013
  • ...nts and associated string do not change. Any other thread waiting (<var>[[$Wait]]</var>) on the specified ECB becomes eligible to resume processing.</p> Use the <var>$Post</var>, <var>[[$UnPost]]</var>, and <var>$Wait</var> functions to coordinate processing between threads. </p> ...
    4 KB (748 words) - 17:21, 2 January 2018
  • ...abase file is enqueued in share mode by the maximum number of jobs. Either wait until one or more of the other enqueued jobs is completed or use the ''[[Fa ...
    375 bytes (67 words) - 13:41, 19 April 2013
  • <b>Response:</b> Wait until a subsystem completes the start process, and enter the <var>STOP SUBS ...
    441 bytes (70 words) - 21:32, 16 March 2018
  • <p><b>File manager response:</b> Wait for recovery to complete. Then retry the RESTOREG command. </p> ...
    449 bytes (71 words) - 21:02, 14 February 2018
  • <p>The real-time interval in milliseconds a user must wait before being promoted by the aging feature</p> ...faster than <var>[[AGESCAN_parameter|AGESCAN]]</var>, a user might have to wait a multiple of AGEINTVL milliseconds before being noticed by the scheduler. ...
    2 KB (246 words) - 12:42, 9 October 2014
  • <b>Response:</b> Wait a few minutes for recovery to complete, and retry. ...
    440 bytes (72 words) - 21:29, 27 February 2018
View ( | ) (20 | 50 | 100 | 250 | 500)