﻿<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://owl.unipharm.com/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Information_Systems%3AOrder_Allocation_Problems</id>
	<title>Information Systems:Order Allocation Problems - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://owl.unipharm.com/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Information_Systems%3AOrder_Allocation_Problems"/>
	<link rel="alternate" type="text/html" href="https://owl.unipharm.com/mediawiki/index.php?title=Information_Systems:Order_Allocation_Problems&amp;action=history"/>
	<updated>2026-09-01T13:15:33Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.4</generator>
	<entry>
		<id>https://owl.unipharm.com/mediawiki/index.php?title=Information_Systems:Order_Allocation_Problems&amp;diff=1502&amp;oldid=prev</id>
		<title>Sheilav: Created page with &quot;Occasion this error message appears during the order allocation monitor -                            Additional Message Information...&quot;</title>
		<link rel="alternate" type="text/html" href="https://owl.unipharm.com/mediawiki/index.php?title=Information_Systems:Order_Allocation_Problems&amp;diff=1502&amp;oldid=prev"/>
		<updated>2015-12-17T23:21:09Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Occasion this error message appears during the order allocation monitor -                            Additional Message Information...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Occasion this error message appears during the order allocation monitor - &lt;br /&gt;
&lt;br /&gt;
                         Additional Message Information                         &lt;br /&gt;
                                                                                &lt;br /&gt;
 Message ID . . . . . . :   RNQ1218       Severity . . . . . . . :   99         &lt;br /&gt;
 Message type . . . . . :   Inquiry                                             &lt;br /&gt;
 Date sent  . . . . . . :   12/16/15      Time sent  . . . . . . :   20:31:06   &lt;br /&gt;
                                                                                &lt;br /&gt;
 Message . . . . :   Unable to allocate a record in file SRBSOH (R C G D F).    &lt;br /&gt;
 Cause . . . . . :   RPG procedure DMR764 in program XX2480BP/DMR764 at         &lt;br /&gt;
   statement 3978 is unable to allocate a record in file SRBSOH.  The record    &lt;br /&gt;
   may be allocated to another process with the file under commitment control.  &lt;br /&gt;
   The actual file is UP1480BFVA/SRBSOH(SRBSOH).                                &lt;br /&gt;
 Recovery  . . . :   Check the job log for more information on the cause of the &lt;br /&gt;
   error and contact the person responsible for program maintenance.            &lt;br /&gt;
 Possible choices for replying to message . . . . . . . . . . . . . . . :       &lt;br /&gt;
   R -- Retry the input operation.                                              &lt;br /&gt;
   D -- Obtain RPG formatted dump.                                              &lt;br /&gt;
   S -- Obtain system dump.                                                     &lt;br /&gt;
   G -- Continue processing at *GETIN.                                          &lt;br /&gt;
   C -- Cancel.                                                                 &lt;br /&gt;
   F -- Obtain full formatted dump.                                             &lt;br /&gt;
 Technical description . . . . . . . . :   Unexpected results may occur if      &lt;br /&gt;
   response 'R' is selected and the program has an INFSR in which the cursor    &lt;br /&gt;
   position for the file SRBSOH is changed and the operation at statement 3978  &lt;br /&gt;
   is a sequential input operation or in which an input operation that locks a  &lt;br /&gt;
   record is performed to a file.                                               &lt;br /&gt;
&lt;br /&gt;
It's not possible to tell what other process has looked the record unless we can catch this in the status LOCK WAIT.  By the time we get this message, and Retry, the lock is over.&lt;/div&gt;</summary>
		<author><name>Sheilav</name></author>
	</entry>
</feed>