JAL: add comma

2018-03-06T20:52:44Z

add comma

← Older revision		Revision as of 20:52, 6 March 2018
Line 4:		Line 4:
	There are three forms of this message: </P>		There are three forms of this message: </P>
	<ul>		<ul>
	<li>The first form is for the critical file resources RECENQ, DIRECT, INDEX and EXISTS. Its format is:		<li>The first form is for the critical file resources RECENQ, DIRECT, INDEX, and EXISTS. Its format is:
	<P class="code">M204.1223 ENQ ... WAITING FOR <i>resource enqtype filename</i> </P>		<P class="code">M204.1223 ENQ ... WAITING FOR <i>resource enqtype filename</i> </P>
	<P>		<P>
Line 14:		Line 14:

	<li>The second form is also for critical file resources RECENQ, DIRECT, INDEX, and EXISTS. Its format is:		<li>The second form is also for critical file resources RECENQ, DIRECT, INDEX, and EXISTS. Its format is:
	<P class="code">M204.1223 ENQ ... WAITING FOR <i>resource</i> (SHARE/EXCLUSIVE) (BEHIND <i>userid userno</i> RUNNING <i>procname</i>) </P>		<P class="code">M204.1223 ENQ...WAITING FOR <i>resource</i> (SHARE/EXCLUSIVE) (BEHIND <i>userid userno</i> RUNNING <i>procname</i>)</P>
	<p>		<p>
	The second form prints only if one user is blocking another by holding the critical file resource exclusively. If procedure <var class="term">procname</var> is not available, the literal <code>BEHIND</code> and the procedure name are not printed. </P></li>		The second form prints only if one user is blocking another by holding the critical file resource exclusively. If procedure <var class="term">procname</var> is not available, the literal <code>BEHIND</code> and the procedure name are not printed. </P></li>

DmeWiccan: Automatically generated page update

2018-03-01T04:26:37Z

Automatically generated page update

New page

{{Template:M204.1223 skeleton}}

This message is output to the audit trail to indicate that the user is waiting to enqueue on a specific resource (usually the named file). If initialization parameter <var>[[CFRLOOK parameter|CFRLOOK]]</var> is 0, not all of the information is available.
There are three forms of this message: 
<ul>
<li>The first form is for the critical file resources RECENQ, DIRECT, INDEX and EXISTS. Its format is:
M204.1223 ENQ ... WAITING FOR resource enqtype filename 

Where: 

<var class="term">resource</var> is RECENQ, DIRECT, INDEX, or EXISTS. 

<var class="term">enqtype</var> is SHR or EXC. 

<li>The second form is also for critical file resources RECENQ, DIRECT, INDEX, and EXISTS. Its format is:
M204.1223 ENQ ... WAITING FOR resource (SHARE/EXCLUSIVE) (BEHIND userid userno RUNNING procname) 

The second form prints only if one user is blocking another by holding the critical file resource exclusively. If procedure <var class="term">procname</var> is not available, the literal <code>BEHIND</code> and the procedure name are not printed. </li>

<li>The third form is:
M204.1223 ENQ ... WAITING FOR resource filename 
Where: 
<TABLE>
<TR class="head"><TH>Resource</TH>
<TH>Is... </TH></TR>

<TR><TD>ACTEXP </TD>
<TD>Change size of access control table </TD></TR>

<TR><TD>CHUNK </TD>
<TD>Change size of procedure dictionary </TD></TR>

<TR><TD>CTTCCMND </TD>
<TD>Access the password table in CCASTAT </TD></TR>

<TR><TD>INSV </TD>
<TD>Save precompiled CCASYS proc (APSY) </TD></TR>

<TR><TD>MRKFCT </TD>
<TD>Update current file status - FISTAT </TD></TR>

<TR><TD>PRSV </TD>
<TD>Save precompiled proc (APSY) </TD></TR>

<TR><TD>SGDTxxxx </TD>
<TD>Group Definition Table in CCATEMP </TD></TR>

<TR><TD>SGFTxx </TD>
<TD>Group Field Table in CCATEMP when BLDGFT = yes for group </TD></TR>

<TR><TD>UPDATE </TD>
<TD>Update a file </TD></TR>

<TR><TD>UPDTPGDT </TD>
<TD>Update CCAGRP </TD></TR>

<TR><TD>UPDTSGDT </TD>
<TD>Update Group Definition Table in CCATEMP </TD></TR>

<TR><TD>File </TD>
<TD>Open a file - READ or UPDATE </TD></TR>

<TR><TD>(group) </TD>
<TD>Name of one file group </TD></TR>

<TR><TD>(subsys) </TD>
<TD>Name of one subsystem </TD></TR>

<TR><TD>(usr) </TD>
<TD>User defined resource via IFENQ </TD></TR>

<TR><TD>PRxxxx </TD>
<TD>Access a permanent procedure </TD></TR>
</TABLE>

For more information, see [[Defining the runtime environment (CCAIN)#Resource locking|Resource Locking]]. 

System manager response: Contact the file manager and application users if this message occurs often for the same resource. Changes to data division in Model 204 files or changes to applications may reduce enqueueing conflicts and improve performance. 

{{Template:M204.1223 footer}}

M204.1223 - Revision history

JAL: add comma

DmeWiccan: Automatically generated page update