ELowell at 01:00, 3 April 2018

2018-04-03T01:00:02Z

← Older revision		Revision as of 01:00, 3 April 2018
Line 2:		Line 2:

	<P>		<P>
	A request was made to allocate <var class="term">~~token0~~</var> pages in the file. Not enough pages (<var>ESIZE</var>) were allocated to Table E. Further requests for page allocation in Table E may continue if enough free pages exist.		A request was made to allocate <var class="term">token</var> pages in the file. Not enough pages (<var>[[ESIZE parameter\|ESIZE]]</var>) were allocated to Table E. Further requests for page allocation in Table E may continue if enough free pages exist.

	If the file is a [[Transaction back out\|transaction back out]] file, Model 204 will initiate back out for the transaction under way and cancel the current request. The file can still be used. If the file is not a transaction back out file, Model 204 logs you out and closes any files you had open. Any files that were being updated are marked physically inconsistent.</P>		If the file is a [[Transaction back out\|transaction back out]] file, Model 204 will initiate back out for the transaction under way and cancel the current request. The file can still be used. If the file is not a transaction back out file, Model 204 logs you out and closes any files you had open. Any files that were being updated are marked physically inconsistent.</P>
Line 11:		Line 11:
	<P>		<P>
	If the file is not a transaction back out file, you need to recover the file using restart recovery (roll back and roll forward), the file reorganization procedure described in [[System and media recovery#ROLL BACK facility\|ROLL BACK facility]],		If the file is not a transaction back out file, you need to recover the file using restart recovery (roll back and roll forward), the file reorganization procedure described in [[System and media recovery#ROLL BACK facility\|ROLL BACK facility]],
	or ~~using~~ the <var>[[RESTORE command\|RESTORE]]</var> command. The <var>RESTORE</var> command restores from a dumped copy of the file, and it increases the size of Table E for the file named in the message.		or the <var>[[RESTORE command\|RESTORE]]</var> command. The <var>RESTORE</var> command restores from a dumped copy of the file, and it increases the size of Table E for the file named in the message.
	</P>		</P>
	{{Template:M204.2690 footer}}		{{Template:M204.2690 footer}}
	<!-- skeleton as it was in pdf/%C PAGES WOULD FILL TABLE E IN %F/-->		<!-- skeleton as it was in pdf/%C PAGES WOULD FILL TABLE E IN %F/-->

DmeWiccan: Automatically generated page update

2018-03-13T17:45:35Z

Automatically generated page update

New page

{{Template:M204.2690 skeleton}}


A request was made to allocate <var class="term">token0</var> pages in the file. Not enough pages (<var>ESIZE</var>) were allocated to Table E. Further requests for page allocation in Table E may continue if enough free pages exist.

If the file is a [[Transaction back out|transaction back out]] file, Model 204 will initiate back out for the transaction under way and cancel the current request. The file can still be used. If the file is not a transaction back out file, Model 204 logs you out and closes any files you had open. Any files that were being updated are marked physically inconsistent.

Response: Notify your file manager.

File manager response: If the file was a transaction back out file, there will not be anything wrong with the file. You may want to expand Table E, since it is probably close to full.

If the file is not a transaction back out file, you need to recover the file using restart recovery (roll back and roll forward), the file reorganization procedure described in [[System and media recovery#ROLL BACK facility|ROLL BACK facility]],
or using the <var>[[RESTORE command|RESTORE]]</var> command. The <var>RESTORE</var> command restores from a dumped copy of the file, and it increases the size of Table E for the file named in the message.

{{Template:M204.2690 footer}}

M204.2690 - Revision history

ELowell at 01:00, 3 April 2018

DmeWiccan: Automatically generated page update