View source for New and updated messages in Model 204 version 7.5

[[Release_notes_for_Model_204_version_7.5|Back to 7.5 Release Notes]]

[[M204wiki main page|Back to wiki main page]]

<div class="noautonum">__TOC__</div>

==M204 messages==
===Mixed case messages by default===
As of version 7.5, all Model 204 messages are issued with mixed case text by default unless [[UPCASMSG parameter|UPCASMSG]] is set.
===M204.0141: Bug .. duplicate file name in cp record===
<p><b>Explanation:</b> A duplicate file name was encountered while attempting to add a deferred update dataset to the file directory during recovery. This indicates a potential problem in the Model 204 software.</p>

<p><b>System manager response:</b> Contact Technical Support with the following documentation:</p>
<ul>
<li>Audit trail from the previous run</li>
<li>Journal from the previous run</li>
</ul>
<p><b>Return codes:</b> E 0 4 AD OPR</p>

----
===M204.0163: SERVSIZE increased to 65536===
<p><var class="term">In version 7.5, with zap maintenance applied, this message is now available.</var></p> 
If the calculated SERVSIZE or the SERVSIZE specified in CCAIN is less than 64K, it is forced to its minimum value of 64K.

<b>Response:</b> No response is needed. This message is for information only.

<b>Return codes:</b> I 0 0 AUDITMS
----

===M204.0204: Parameter <var class="term">parmName</var> obsolete and not reset===
'''Explanation:''' Writing records to the SMF data set no longer requires the installation of an SVC. The
SMFSVC parameter is therefore obsolete and cannot be reset.
<br>'''System manager response:''' No response required.
<br>'''Return codes:''' I 0 0 AUDITMS

----
===M204.0223: Statement label multiply defined===
'''Explanation:''' A statement label is found that is not unique in a User Language request. This error does not prevent the request from executing. 
<ul>
<li>A jump or call to a statement label defined multiple times goes forward to the nearest occurrence of the statement label. It goes backward to the nearest occurrence if there is no forward occurrence.</li> 
<li>A FOR or COUNT statement referring back to a previous found set label defined 
multiple times goes backward to the nearest occurrence.</li>
<li>Other statement label references go to the first occurrence in the request.</li>
</ul>
'''Response:''' Change  the statement label(s) and retry. You can ignore this message if you are satisfied that the request executes correctly.<br>
'''Return codes:''' I 0 0 ECHO

----

===M204.0316: Recursive ON units exceed MAXOND: Evaluation stopped===
'''Explanation:''' During evaluation, one or more ON units was entered recursively. When the number of recursions exceeded MAXOND, the evaluation was terminated.
<br>'''System manager response:''' This message might indicate a logic error in the program. Inform the program author.  
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.0332 and M204.0336===
These messages indicate problems with the CRAM interface. 
The visibility of these messages has been improved by:
<ul>
<li>writing the message to the operator and the JESLOG
<li>writing the message as an ER line in CCAAUDIT
<li>setting the return code to 80
</ul>

====M204.0332: RC ''nn'' from CRFS ''operation''====
'''Explanation:''' The run has failed to initialize due to problems with the CRAM interface.
The possible formats of this message are:

Format 1: RC nn from CRFS OPEN/PUT/GET

Format 2: ECB postcode from CRFS PUT/GET
<ul>
<li>
Format 1 indicates that Model 204 module CRFS attempted to open channel, send a message down the channel, or receive a message from a channel. CRAM was unable to satisfy the request. The message states the return code and the
operation attempted.</li>
<li>
Format 2 indicates that Model 204 module CRFS received an unexpected post code from CRAM while attempting an I/O operation on a channel. The message states the post code and the operation attempted.
</li>
</ul>
<p>Possible return codes include the following values:</p>
<table>
<tr class="head"><th>Value</th> <th>Description</th>
<tr><td>4</td> <td>INVALID FUNCTION</td></tr>
<tr><td>8</td> <td>CB FORMAT ERROR</td></tr>
<tr><td>16</td> <td>(OPEN MAST) CHANNEL ALREADY OPEN</td></tr>
<tr><td>20</td> <td>(OPEN USER) NO USER LINES FREE</td></tr>
<tr><td>24</td> <td>(OPEN) SUBTASKS NOT PROPERLY OPENED</td></tr>
<tr><td>12</td> <td>(READ/WRITE) ICB NOT OPEN</td></tr>
<tr><td>16</td> <td>(READ/WRITE) OTHER TASK HAS DIED</td></tr>
<tr><td>20</td> <td>(READ/WRITE) UNEXPECTED COMMAND</td></tr>
<tr><td>28</td> <td>NOT ENOUGH STORAGE</td></tr>
<tr><td>99</td> <td>There is no SVC defined in the IGCLM244 module and the XMEMOPT ’80’ bit must be set for an SVC-less installation</td></tr>
<tr><td>110</td> <td>(VMCF WRITE) MESSAGE LIMIT EXCEEDED</td></tr>
</table>
'''System manager response:''' Contact Technical Support and have the audit trail available.
<br>'''Return codes:''' C 80 80 AUDITER NOTERM OPR

====M204.0336: RC ''nn'' from CRIO OPEN====
'''Explanation:''' The run has failed to initialize due to problems with the CRAM interface.
The possible formats of this message are:

Format 1: RC nn from CRIO OPEN/PUT/GET

Format 2: ECB postcode from CRFS PUT/GET
<ul>
<li>
Format 1 indicates that Model 204 module CRIO attempted to open a channel,
send a message down a channel, or receive a message from a channel. CRAM
was unable to satisfy the request. The message states the return code and the
operation attempted. For example, the return code 16 indicates that the CRAM
channel is already open.</li>
<li>
Format 2 indicates that a Model 204 CRAM interface module, such as CRFS or CRIO, received an unexpected post
code from CRAM while attempting an I/O operation on a channel. The message
shows the post code and the operation attempted.</li>
</ul>
<p>Possible return codes include the following values:</p>
<table>
<tr class="head"><th>Value</th> <th>Description</th>
<tr><td>4</td> <td>INVALID FUNCTION</td></tr>
<tr><td>8</td> <td>CB FORMAT ERROR</td></tr>
<tr><td>16</td> <td>(OPEN MAST) CHANNEL ALREADY OPEN</td></tr>
<tr><td>20</td> <td>(OPEN USER) NO USER LINES FREE</td></tr>
<tr><td>24</td> <td>(OPEN) SUBTASKS NOT PROPERLY OPENED</td></tr>
<tr><td>12</td> <td>(READ/WRITE) ICB NOT OPEN</td></tr>
<tr><td>16</td> <td>(READ/WRITE) OTHER TASK HAS DIED</td></tr>
<tr><td>20</td> <td>(READ/WRITE) UNEXPECTED COMMAND</td></tr>
<tr><td>28</td> <td>NOT ENOUGH STORAGE</td></tr>
<tr><td>99</td> <td>There is no SVC defined in the IGCLM244 module and the XMEMOPT ’80’ bit must be set for an SVC-less installation</td></tr>
<tr><td>110</td> <td>(VMCF WRITE) MESSAGE LIMIT EXCEEDED</td></tr>
</table>
'''System manager response:''' Contact Technical Support and have the audit trail available.
<br>
'''Return codes:''' C 80 80 AUDITER NOTERM OPR

----

===M204.0349: Login failed <br /> (<var class="term">alternative text</var>) Enter logoff===
'''Explanation:''' Either you entered an invalid userid, or the password for the userid is incorrect. If an external authorizer is active, you may not be authorized to use Model 204, or you may have entered an invalid account code if account validation is active. 
<p><b>Available with zap 75Z279:</b> The "Enter logoff" text is displayed for this message if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter is set to 19.</p>

<b>Response:</b> Retry the login with a valid user ID and the correct password. If you are still unable to log in, contact your system manager to verify your userid and password. 

<b>System manager response:</b> Issue the LOGLST command to determine if the user has a user ID and, if so, find out his or her password from your hardcopy file record and give the correct password to the user. If you do not have any record of the password or if the user ID does not exist, change the entry or add a new entry to the password table for the user with the LOGCTL command. 

If an external authorizer is active (ACF2, Security Server (formerly RACF), Top Secret), use the appropriate commands for that system to verify that the user is a valid system user. 
If Model 204 is validating the authority of the user to enter the system, verify that the user has the appropriate authorization. In addition, if the default user ID has been set to blanks, or, if the default user ID cannot log in, no CCASTAT defined users may log in. 

Finally, if account validation is active, ensure that the userid has the authority to use the account code that was entered. 

<b>Return codes:</b> C 0 4 AUDITER 

----

===M204.0434: NJBUFF set to %C===

'''Explanation:''' The NJBUFF parameter was set to an invalid value. NJBUFF must be equal to:
<ul>
<li>One (1), or </li>
<li>Value of the NSERVS parameter, plus NSUBTKS parameter, plus 1.</li>
</ul> 
<p>NJBUFF specifies the number of journal buffers allocated by Model 204 during initialization.</p>
<p><b>Response:</b> Notify the system manager. </p>
<p><b>System manager response:</b> Reset the NJBUFF parameter to a valid value and rerun Model 204.</p> 
<p><b>Return codes:</b> I 0 0 AUDITAD</p> 

----

===M204.0761: ATRPG*ASTRPPG exceeds <var class="term">maxentries</var>===

'''Explanation:''' You attempted to initialize a file that was created with invalid parameters. The number of dictionary entries is determined by the product of the parameters <var>ATRPG</var> and <var>ASTRPPG</var>. The maximum allowed product is 4000 (attribute dictionary entries), or 32000 for a <var>FILEORG</var> X'100' file. The <var>INITIALIZE</var> command is rejected.

'''Response:''' The file must be recreated. Retry the <var>CREATE</var> command specifying <var>ATRPG</var> and <var>ASTRPPG</var> parameter values such that the product of the two is less than <var class="term">maxentries</var>.

'''Return codes:''' C 0 4 AUDITER
----

===M204.0790: File too big===

'''Explanation:''' The total number of records possible in Table B exceeds 342 segments for files that do not have the FILEORG X'200' bit set and 1024 segments for files that have the FILEORG X'200' bit set.                           
The number of potential record numbers per segment is 49,152.             
The number of possible segments in Table B is calculated by the following formula:
<p class="code">((BSIZE * BRECPPG) / 49,152)) + (1 if remainder not 0)
</p>
If the result exceeds 342 or 1024 respectively too many segments result and MODEL 204 rejects the CREATE command. 
<br>'''File manager response:''' Make the file smaller (by specifying a smaller BSIZE or smaller BRECPPG), or divide the file into smaller pieces and use the file group feature to process them as a single logical file.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.0797: BSIZE*BRECPPG exceeds maximum value===

'''Explanation:''' The product of BSIZE and BRECPPG must not exceed 16,777,216 for regular Model 204 files (which do not have the FILEORG X'200' bit set) and 50,331,648 for files that have the FILEORG X'200' bit set. These numbers specify the maximum number of records allowed in a single Model 204 file. 

The CREATE or INCREASE command is rejected.        
<br>'''File manager response:''' Retry the command, specifying values for BSIZE and BRECPPG so that BSIZE*BRECPPG does not exceed the limit. See [[Managing file and table sizes]] for more information.                                                                      
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.1050: CCATEMP full: <var class="term">operation</var> or <var class="term">pooltype</var>===
<p><b>Explanation:</b> The operation being performed required an extra page from CCATEMP, but there were no free pages available. CCATEMP is defined by the system manager and provides a set of work pages that are assigned on request to various users. If a request gets this message, it might be because some other user is holding a large number of CCATEMP pages.</p>

The message specifies either the operation being performed, or the section ("pool") of CCATEMP that was full.

<var class="term">operation</var> can be one of:
<ul>
<li>$BLDPROC</li>
<li>"USE PROCEDURE" COMMAND</li>
<li>WHILE INITIALIZING SORT</li>
<li>FOR FRV KEYS</li>
<li>WHILE GENERATING RECORDS TO BE SORTED</li>
<li>WHILE GENERATING ORDERED INDEX SORTED RECORDS</li>
<li>WHILE PERFORMING SORT</li>
</ul>

<var class="term">pooltype</var> can be one of:
<ul>
<li>SMALL MODEL PAGE POOL</li>
<li>SMALL MODEL PAGE POOL AND EXPANSION PAGE POOL</li>
</ul>
The current request is cancelled.

If the operation was $BLDPROC or USE PROCEDURE COMMAND, then the temporary procedure that was being written is deleted, except for its very last CCATEMP page, which is retained for information purposes.

In some cases the user is restarted and, if the user was in the process of updating any files, MODEL 204 marks them physically inconsistent.

CCATEMP pages below 64K are allocated from the small model pool.
CCATEMP pages above 64K are allocated from the expansion area pool.

The <var class="term">pooltype</var> specified in the message indicates whether you exceeded the capacity of the small model pool or both the small model and expansion area pools.

<p><b>Response:</b> Notify your system manager.</p>
<p><b>System manager response:</b> Recover the physically inconsistent files using one of the following procedures:
<ul>
<li>Roll back/roll forward</li>
<li>File reorganization procedure described in [[File reorganization and table compaction]]</li>
<li>The RESTORE command for restoring previously dumped copies</li>
</ul></p>
This message is informational, but it indicates a need to increase the space allocation for CCATEMP. As the size of CCATEMP is fixed at initialization, it is necessary to bring down MODEL 204 to increase it.

<b>Return codes:</b> E 60 60 AUDITAD CANCEL NOTERM OPR

----

===M204.1052: LOUTPB %C TO %C===
'''Explanation:'''
LOUTPB has been increased or decreased, to the value given in the message.
With a full-screen terminal the value is 1.5 times the minimum for that model number, rounded
up to a multiple of 8.
A model 2 terminal results in a LOUTPB of 3200.
A model 5 terminal results in a LOUTPB of 5664.
<p>If NBKPG is greater than 0, the largest allowable value for LOUTPB is PAGESZ
minus 40, so the value can be decreased for this reason.</p>
'''User response:''' No response is needed. This message is for information only.
<br>'''Return codes:''' I 0 0 AUDITAD
----

===M204.1060: %C not allowed with non swappable servers===
<p>'''Explanation:''' The service requested is not compatible with non-swappable servers.</p>
<p>'''System manager response:''' Remove any non-swappable server settings and restart Model 204 to repeat the service.</p>
<p>'''Return codes:''' E 0 4 AUDITMS</p>
----

===M204.1131: Can't <var class="term">action</var>===

'''Explanation:''' The procedure action cannot be taken for one of the following reasons:
<ul>
<li>The procedure is in use by another user.</li>
<li>The procedure is not in the file.</li>
<li>The user does not have the correct privileges to change the procedure.</li>
<li>If a RENAME or ASSIGN has been attempted, the alias might already exist.</li>
</ul>
'''Response:''' Make sure that the procedure name is spelled correctly.
If the named procedure is in use, retry the command when the procedure is no longer in use.  Otherwise, arrange to place the
procedure in the file or to obtain the privileges to change the procedure.
<br>'''Return codes:''' C 0 4 SUFFIX AUDITER

----
The return codes for message M204.1149 have changed.

===M204.1149: <var class="term">parameter_name</var> has been set to its minimum|maximum value: <var class="term">value</var>===

'''Explanation:''' You have attempted to reset a parameter either below the minimum or above the maximum allowed for it. Model 204 has reset the parameter to the correct minimum or maximum. 
<br>
'''Response:''' Retry the command with a value within the correct range, or leave the value as is, since Model 204 has already reset the parameter to the correct minimum or maximum. 
<p>For PARAMETER=ESIZE, if you specify:</p>
<ul>
<li>A zero value, which is the equivalent of Not Applicable, no pages are allocated for Table E.</li>
<li>A non-zero value, then the minimum of 20 pages allocated for Table E is enforced.</li>
</ul>
'''Return codes:''' I 0 0 AUDITMS 

----

===M204.1167: ITBL full -- argument string ignored===

<p><b>Explanation:</b> Model 204 stores the arguments passed by the <var>INCLUDE</var> command ($READ and dummy string (??) responses) in the ITBL server table. If the storage allocated to ITBL is too small to accommodate the number and size of the arguments being passed, the argument string is ignored. </p>

<p>For example: 
In your include command <code>INCLUDE HOTEL,GRAND,BUDAPEST</code>, the procedure named HOTEL is being passed the arguments GRAND and BUDAPEST. However, the M204.1167 message indicates that the storage allocated to ITBL is too small to accommodate those arguments. Consequently, the argument string <code>GRAND,BUDAPEST</code> is ignored. You will be prompted to provide those arguments, one at a time, as required for the number of $READ statements and dummy string substitutions encountered in the procedure.</p>
<p><b>Response:</b> Use the <var>[[VIEW command|VIEW]] LITBL</var> command to determine the current size of ITBL; then use the <var>[[UTABLE command|UTABLE]] LITBL</var> command to increase its size.  A 10-20% increase should be sufficient in most cases.</p>
<p><b>Return codes:</b> C 0 4 AUDITER</p>

----

===M204.1260: {Field|Fieldgroup} was previously defined with different attributes, new {field|fieldgroup} options ignored===

<p><b>Explanation:</b> A <b>DEFINE FIELD</b> or a <b>DEFINE FIELDGROUP</b> command has attempted to define an existing field or field group with different attributes.</p>
<p><b>Response:</b> To redefine the attributes of the field or field group, you must issue the <b>REDEFINE FIELD</b> or the <b>REDEFINE FIELDGROUP</b> command. Notify your file manager.</p>
<p><b>Return codes:</b> C 0 4 AUDITER</p>
----

===M204.1307: %C logon rejected - <var class="term">reason text</var> (reason code: %X)===

<p><b>Explanation:</b> The MODEL 204 3270 terminal handler has rejected a logon request from a 3270 terminal for the reason stated. The following reason codes are defined:</p>
<ol>
<li>There are no control blocks available for new logons. Increase the number of IODEV 7 terminal definitions. The reason text is: NOT ENOUGH 3270 TERMINALS.</li>
<li>The terminal has been defined with a non-3270 transmission services profile. The LU type must be 2.  The reason text is: LU TYPE NOT = 2.</li>
<li>The terminal has been defined to require definite responses to messages it sends inbound to the host. The transmission services profile must be 3. <br>
The reason text is: TS PROFILE NOT = 3.</li>
<li>There has been an error on this terminal. This is a retryable error. The reason text is: LOSTERM SET FOR THIS TERMINAL.</li>
<li>The terminal definition is in use. This error should not occur. The reason text is: TERMINAL ALREADY IN USE.</li>
</ol>
<p><b>System manager response:</b> Contact your VTAM systems programmer to correct the VTAM definition.</p>
<p><b>Return codes:</b> E 0 4 AD SAVE NOTERM OPR</p>
----
===M204.1346: Server area greater than cylinder capacity for this device. Cylinder size = <var class="term">nnn</var> BYTES.===                                               
<p><b>Explanation:</b>                                                                    
The number of bytes specified for the largest server area (SERVSIZE)      
is greater than <var class="term">nnn</var>, the number of bytes contained in a cylinder for    
the type of disk device on which your CCASERVR (CCASRVR for DOS) data set resides.</p>  
<b>System manager response:</b> Do one of the following:                                                  
<ul>
<li>ensure that the largest SERVSIZE value does not exceed <var class="term">nnn</var></li>           
<li>place your server data sets on a type of disk device that has a         
larger cylinder capacity</li>                                                  
<li>place [[Creating server data sets (CCASERVR)#CCASERVR in Storage feature|CCASERVR in storage]]</li>
</ul>
'''Return codes:''' C 96 96 AUDITER      
----

===M204.1381: (new informational message for REGENERATE)===
M204.1381 is a new informational  message issued during REGENERATE to help verify that the journal data provided in CCAGEN is from the correct CCAJRNL.  

The 58 bytes printed are the journal header of each journal block. (Journal headers are described in the [[Using system statistics#Header entries (Type 0)|Header entry formats]] table.)  

The message has four variations, which always appear:
<ol>
<li>
<b>M204.1381: CCAGEN: FIRST 5 CCAJRNL BLOCKS + LAST BLOCK IN HEX</b>
<p><b>Explanation:</b> The first 58 bytes, in hex, of the first five CCAJRNL blocks and the last CCAJRNL block read from CCAGEN follow in CCAAUDIT.</p>   
</li>
<li><b>M204.1381: PASS1:</b> <var class="term">hex representation of data</var></li>
<li><b>M204.1381: LASTB:</b> <var class="term">hex representation of data</var></li>
<li>
<b>M204.1381: CCAGEN BLOCK COUNT: <var class="term">nnnn</var></b>
<p><b>Explanation:</b> The count of CCAJRNL blocks read from CCAGEN.</p>
</li>
</ol>  
<b>Example</b>

This example shows the first 5 CCAJRNL blocks and the last block read from CCAGEN during pass 1 of REGENERATE.
<p class="code">M204.1381: CCAGEN: FIRST 5 CCAJRNL BLOCKS + LAST BLOCK IN HEX
M204.1381: PASS1: 006000020113214F155421910000000000CB...            
M204.1381: PASS1: 0AD000020113214F155421910000000100CB...            
M204.1381: PASS1: 07BF008A0113214F155421920000000200CB...            
M204.1381: PASS1: 0B5E00020113214F155422000000000300CB...            
M204.1381: PASS1: 0AAF00120113214F155422030000000400CB...            
M204.1381: LASTB: 00C900020113214F155930280000337100CB...   
M204.1381: CCAGEN BLOCK COUNT: <var class="term">....</var></p>                                                  
<p><b>Response:</b> This message is informational only; no response is required.</p>
<p><b>Return codes:</b> I 0 0 AUDITAD</p>
----

===M204.1382: Chunk size <var class="term">nn</var> used: flags=X"<var class="term">nn</var>", low=<var class="term">nn</var>, high=<var class="term">nn</var>===
<b>Explanation: </b>This is a debugging error message. 
<br>
<b>Response: </b>No response is required.
<br>
<b>Return codes:</b> I 0 0 AUDITMS
----

===M204.1387: Allocate failed; DDNAME=<var class="term">ddname</var>,DSNAME=<var class="term">dsname</var> could not be located===    
<p><b>Explanation:</b> An attempt to allocate an existing data set, data set name=<var class="term">dsname</var>, failed because the specified dsname was not found in the catalog or the catalog could not be accessed.</p>  
M204.1387 replaces <p class="code">M204.1070: ALLOCATE FAILED - <var class="term">reason</var></p> with additional information regarding the failure of the ALLOCATE command. However, M204.1070 remains in use by Janus/TCPIP for a different purpose. 
<p><b>Response:</b> Correct the data set name or ensure that the data set exists and is cataloged.</p>
<p><b>Return codes:</b> C 0 4 AUDITER</p>
----

===M204.1388: CHUNK size exceeds maximum of <var class="term">nnn</var>===
<p>On a DEFINE field command, the chunk size specified is too large.</p>
<p><b>User response: </b>Specify a chunk size less than or equal to the maximum.</p>
<p><b>Return codes: </b>C 0 4</p>
----

===M204.1393: CHUNK clause not of format "CHUNK <var class="term">chunkSize</var> FOR <var class="term">chunkTarget</var>"===

'''Explanation:''' On a DEFINE FIELD, the syntax of the CHUNK clause was not in the format shown in this message.                                                   
<br>'''File manager response:''' Correct the DEFINE FIELD command that has the incorrect CHUNK clause syntax.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.1394: CHUNK <var class="term">chunkSize</var> value invalid: <var class="term">reason</var>===

'''Explanation:''' On a DEFINE FIELD, the value specified for the size of a CHUNK is invalid;  
"reason" indicates why. 
<br>'''File manager response:''' Correct the DEFINE FIELD command that has the invalid CHUNK size.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.1395: CHUNK target field invalid type: <var class="term">reason</var>===

'''Explanation:''' On a DEFINE FIELD, the field specified as a CHUNK target is not a field type that can be used as a chunk target, for the reason specified. 
<br>'''File manager response:''' Correct the DEFINE FIELD command containing the invalid CHUNK target type.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.1396: CHUNK fields must be INVISIBLE ORDERED NUMERIC===

'''Explanation:''' On a DEFINE FIELD, an attempt was made to create a CHUNK field that was not INVISIBLE ORDERED NUMERIC, which is a requirement of chunk fields. 
<br>'''File manager response:''' Correct the DEFINE FIELD command that has the invalid CHUNK target type.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.1397: A CHUNK field was defined, %F may no longer be opened with M204 releases prior to V7R5===
'''Response:''' This is an informational message. No action is required.
<br>'''Return codes:''' I 0 0 AUDITMS
 
----

===M204.1399: Same server area defined for server above the bar and non swappable server===
<b>Explanation: </b>The same server table has been defined in SERVNSA and SERVGA.
<br>'''Response:''' Correct the SERVNSA and/or SERVGA settings. 
<br>'''Return codes:''' E 0 4 AUDITMS

----

===M204.1400: Server areas ATB require server swapping in memory===
<b>Explanation: </b>Parameters indicated that server areas ATB were used in the run where CCASERVR data set was defined.  
<br>'''System manager response:'''  Either remove the server areas ATB parameters or use server swapping in memory.    
<br>'''Return codes:''' E 0 4 AUDITMS

----

===M204.1402: Invalid value for chunk target: <var class="term">fname</var>='<var class="term">val</var>'; values must be -999999999999999 -> 999999999999999===
<p><b>Explanation: </b>If a chunk target is any field type besides DATETIME, any value stored in it must be within the range shown in the error message.
<br><b>Response: </b>Correct the value being stored.
<br><b>System manager response: </b>Correct the value being stored.
<br><b>Return codes: </b>C 0 4 CANCEL
</p>

----

===M204.1403: Increase SERVGSZ to at least %C for required ATB server areas===
<b>Explanation: </b>The total size of ATB server areas is larger than the ATB server size defined in SERVGSZ.
<br>'''User response:''' If the message is issued in response to a UTABLE command, decrease the size of the ATB server areas.       
<br>'''System manager response:''' If the message is issued during initialization, either increase SERVGSZ or decrease the ATB server area size.    
<br>'''Return codes:''' E 80 80 AUDITAD OPR 

----

===M204.1412: <var class="term">service</var> not allowed with ATB servers===
<b>Explanation: </b>The requested service is not compatible with ATB (above the bar) servers.
<br><b>System manager response: </b>Remove the ATB server parameters and restart Model 204.
<br><b>Return codes: </b>E 0 4 AUDITMS

----
===M204.1414: ERROR: SORT RECORD > 16MEG===
<b>Explanation: </b>The user attempted to sort a record greater than 16M.<br>
<b>Response: </b>Reduce the record size and retry. (See [[Sorting#Usage guidelines for the SORT RECORDS statement|sorting guidelines for SORT RECORDS]].)
<br><b>Return codes: </b>C 0 4 CANCEL AUDITER

----

===M204.1433: CCAGEN: IS EMPTY ¦ CCAGEN: PERMANENT I/O ERROR===
<b>Explanation:</b> There were no valid records found in the journal(s) pointed to by CCAGEN, or a permanent I/O error was encountered.
<br><b>System manager response: </b>Verify that you have the correct journal(s) for the run. If I/O errors were detected while reading in CCAGEN, the appropriate error messages will have been issued before this message. Correct the error and rerun media recovery. If the problem remains unclear, contact Technical Support and have the following documentation available:
<ul><li>Audit trail</li>
<li>Snap dump</li>
<li>UTILJ output for CCAGEN dataset</li></ul>
<b>Return codes: </b>C 0 4 AUDITER

----

===M204.1489: Not enough file space to continue procedure definition - %F===
<p><b>Explanation:</b> There is no room in the file to store the procedure being entered with the PROCEDURE command.</p>

<table>
<tr><td><b>If…</b></td><td><b>Then Model 204…</b></td></tr>
<tr><td>Error occurs after the first line of procedure text has been stored</td><td>Keeps the partial procedure</td></tr>
<tr><td>You are entering the text at your terminal</td><td>Ends procedure definition immediately</td></tr>
<tr><td>Procedure text is supplied by another procedure</td><td>Flushes the remainder of the input</td></tr>
<tr><td>Procedure text is supplied in a batch input stream (CCAIN)</td><td>Flushes the remainder of the procedure text and resumes processing after the END PROCEDURE command</td></tr>
</table>

<p><b>Response:</b> Create space in the file by deleting unwanted procedures or increasing Table D with the INCREASE command. Replace the partial procedure using the PROCEDURE command, or use the EDIT command to supply the missing text.</p>

<p><b>Return codes:</b> C 0 4 CANCEL AUDITER</p>

----
===M204.1508: %<C userid> is not authorized to use Model 204=== 
Message M204.1508 has been updated to include the actual user ID of the unauthorized user.
<p><b>Explanation:</b> This user ID does not have the authority to use Model 204.  Login authorization to Model 204 is defined by your installation security officer or system manager.</p>

<p><b>Response:</b> Ask your installation security officer or system manager to authorize you for logging into Model 204.</p> 
<p><b>System manager response:</b> Contact the installation security officer or issue the appropriate external security system commands to give the user’s logon ID the authority to use Model 204. Refer to the [[Security_interfaces_overview|Security interfaces pages]] for instructions.</p>
 
<p><b>Return codes:</b> C 0 4 AUDITER</p>

----

===M204.1587: FSCB full, IMAGE too large: LFSCB required = <var class="term">num</var>, bytes available in FSCB = <var class="term">num</var>===

<p><b>Explanation:</b> The value specified in an <var>Identify</var> statement with
the <var>Len</var> or <var>Occurs</var> option causes the size of the associated <var>Image</var> to overflow the full screen buffer (FSCB). The FSCB is a server work area that is used to hold a compiled Image definition.</p>

<p>'''Response:''' Use the <var>VIEW LFSCB</var> command to determine the current
size of the FSCB. Use the <var>UTABLE</var> command to increase the value of the
<var>LFSCB</var> parameter. Check the <var class="product">SOUL</var> request for programming errors that might cause the value specified in the <var>Identify</var> statement to be too large. Retry the request.</p>

<p>'''Return codes: '''C 0 4 CANCEL AUDITER </p>
 
----

===M204.1589: Maximum IMAGE length is 32767: LFSCB required = <var class="term">num</var>===
<p><b>Explanation:</b> An attempt has been made to define an image greater than 32K.</p>
<p>'''Response:''' Redefine the image so that it is not greater than the maximum length of 32767.</p>
<p>'''Return codes:''' C 0 4 CANCEL AUDITER</p>
 
----
===M204.2126: User's pushdown list overflowed===
<p>
'''Explanation:''' The user's pushdown list is an internal stack for maintaining state information for user threads across internal Model 204 subroutines. The user pushdown list lives in each user's server.  Its size requirement depends on the complexity of the command or User Language request.</p>

This message is issued whenever Model 204 detects that pushdown list data has spilled into adjacent control structures.  Because of potential corruption the user is restarted.
<br>'''Response:''' Increase the size of the user pushdown list by using the LPDLST parameter of the UTABLE command.  Notify your system manager.
<br>'''System manager response:''' If this becomes a frequent occurrence, consider more permanent changes to LPDLST and SERVSIZE, since the pushdown list is a server component.
<br>'''Return codes:''' C 0 4 CANCEL
----
===M204.2316: TCPIP ERROR: <I>category</I>, PROCESS=<I>process_name</I>, REMOTEID=<I>remote_id</I>, SEITUH=<I>data_header</I>===
<I>In version 7.5, with zap maintenance applied, this message no longer issues a snap.</I> 

Unexpected data has been received on this connection requiring the connection to be closed. <var class="term">process_name</var> identifies the name of the process opened at the time of error. <var class="term">remote_id</var> identifies the remote Internet address. SEITUH is the data header (for Rocket Software internal use).

<b>Response:</b> Contact the System Manager.

<b>System manager response:</b> Obtain the CCAAUDIT file and contact Technical Support.

<b>Return codes:</b> C 0 20 AUDITER NOTERM
----
===M204.2329: <var class="term">subsystem_name</var> at <var class="term">location_name</var> unavailable===
<p><b>Explanation:</b> The indicated subsystem at the specified node is not available for use due to one or more errors occurring at the specified node during start or login processing.</p>
<p><b>Response:</b> Notify the system manager or try again later.</p>
<p><b>System manager response:</b> If the subsystem is started, stop the subsystem and resolve communications errors or other errors which occurred at the specified node. After resolving error, use the START SUBSYSTEM command to make the subsystem available for general use. Check to make sure that the LOCATION parameter was set properly in the CCAIN input stream for the Online.</p>
<p><b>Return codes:</b> C 0 4</p>
----

===M204.2551: {FPL|FCT PG1} is invalid for file: <var class="term">filename</var>===

'''Explanation:''' If the message says FPL, then the FPL (file parameter list) for the associated file is invalid. This could be the result of an incorrect DD, FILEDEF or DLBL statement.                                              

If the message says FCT PG1, then the existence page array page is invalid.

'''File manager response:''' If the DD, FILEDEF or DLBL statement is correct and points to the correct data set, then the file must be restored from a backup.         
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.2651: Not all threads processed for IODEV %C===
<p><b>Explanation:</b> The run is terminated because either:
<ul>
<li>The number of threads specified by NUSERS has been initialized, but there are fewer users of the specified IODEV type than expected.</li>
<li>The DUPTERM number specified by the IODEV card could not be initialized because it exceeded the number of NUSERS.</li>
</ul></p>
<p><b>Response:</b> Check that NUSERS matches the total of the listed IODEVs, plus one extra for USER 0. Check also the NOTERM/DUPTERM parameter for the specified IODEV card.</p>
<p><b>Return codes:</b> E 80 80 ER</p>
----
===M204.2719: Open %C failed. Update statements already compiled, read only privileges insufficient===
<p><b>Explanation:</b> The OPEN or OPENC User Language statement was issued from a request to reopen a file with read-only privileges. However, that request had already been compiled with update statements against the file.</p>
<p><b>Response:</b> In a User Language request, you cannot use the User Language OPEN or OPENC statement to reopen a file with read-only privileges, if that request contains updates statements against the same file.</p>
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----
===M204.2739: Parameter <var class="term">parm</var> cannot be reset on user 0’s parameter line: value ignored===
<p><b>Explanation:</b> You reset parameter <var class="term">parm</var> on the User 0 parameter line, but the parameter cannot be set there. The value is ignored, the default value for this parameter remains in effect.</p>
<p><b>Response:</b> Remove <var class="term">parm</var> from the User 0 parameters, since it will not change the value of the parameter.</p>
<p><b>Return codes:</b> E 0 4 AD</p>
----
===M204.2746: XSIZE*XRECPPG may not be 1 nor exceed 536870911===
<p><b>Explanation:</b> The product of XSIZE and XRECPPG must not exceed 16777216 times 32 minus one, or 536870911. This specifies the maximum number of extension records allowed in a single Model 204 file when using Table X. Also, setting both XRECPPG and XSIZE to 1 is invalid.</p>
The CREATE command is rejected.
<p><b>Response:</b> Retry the command specifying values for XSIZE and XRECPPG whose product does not exceed the 526870911 limit. Refer to the <var class="book">Rocket Model 204 File Manager’s Guide </var>for more information on file sizes.</p>
<p><b>Return codes:</b> C 0 4</p>
----

===M204.2774: Another <i>command</i> command is in progress===

<b>Explanation:</b> An INCREASE or DECREASE command or auto increase is taking place while another INCREASE, DECREASE, or auto increase has not finished yet.
<br><b>File manager response:</b> Repeat the command after the completion of the auto increase or previous INCREASE or DECREASE command. 
<br><b>Return codes:</b> C 0 4

----

===M204.2826: %F %C compaction not allowed===

'''Explanation:''' An attempt was made to compact a file created prior to Model 204 version 6.3.
<br>'''File manager response:''' Reorganize the file using Model 204 version 6.3.
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2831: Updates to DTS files not supported in this environment===
<p><b>Explanation:</b> DTS files cannot be updated in IFAM, SQL, or PQO environments.</p>
<p><b>Response:</b> Do not attempt to update DTS file.</p>
<p><b>Return codes:</b> C 0 4</p>
----							
===M204.2833: Fields cannot be defined in a file with ATRPG*ASTRPPG&gt;4000===
<p><b>Return codes:</b> C 0 4</p>
----

===M204.2836: Value of parameter %C invalid—reset to %C===

'''Explanation:''' This is an informational message only.

A parameter was specified with an incorrect value. It has been reset to an internally calculated value that will accommodate other parameter settings. See the description of the parameter named to see what that calculation involves.
<br>'''System manager response:''' The parameter has been reset. No response is required.
<br>'''Return codes:''' I 0 0 AUDITMS
----

===M204.2838: %C only valid in FILEORG X’100’ files===
<p><b>Return codes:</b> C 0 4</p>
----
===M204.2839: %C is a %C, not a %C===
<p><b>Return codes:</b> C 0 4 ECHO</p>
----							
===M204.2841: Remote fieldgroups not supported=== 
<p><b>Return codes:</b> C 0 4 ECHO</p>
----							
===M204.2842: Invalid context for fieldgroup===
<p><b>Return codes:</b> C 0 4 ECHO</p>
----									
===M204.2843: Maximum fieldgroup id exceeded in record %R in %F===
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----								
===M204.2844: Mix of fields and fieldgroups, name <nowiki>=</nowiki>===
<p><b>Return codes:</b> C 0 4 SUFFIX ECHO</p>
----

===M204.2845: Invalid fieldgroup context for %C===
<p><b>Explanation:</b> The $function was used outside of field group context.</p>
<p><b>Return codes:</b>C 0 4 SUFFIX ECHO</p>
----
===M204.2846: Invalid fieldgroup context for %C===
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----
===M204.2847: Fieldgroup context lost in record %R in %F===
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----
===M204.2848: Invalid fieldgroup id: %C===
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----

===M204.2849: Required keyword %C missing===
<p><b>Return codes: </b>X 0 4 ECHO</p>
----

===M204.2850: %C value missing===
<p><b>Return codes:</b> C 0 4</p>
----
===M204.2851: %C value &quot;%C&quot; too big, must be &lt;%C bytes===
<p><b>Return codes:</b> C 0 4</p>
----
										
===M204.2852: Update to missing fieldgroup occurrence in record %R in %F===
<p><b>Return codes:</b> C 0 4 CANCEL</p>
----

===M204.2853: %C not allowed for EXACTLY-ONE field===
<b>Return codes:</b> C 0 4
----
										
===M204.2854: Attempt to do %C for EXACTLY-ONE field: %C===
<b>Return codes:</b> C 0 4 CANCEL
----
										
===M204.2855: Field depth+length unrepresentable in record %R in %F===
<b>Return codes:</b> C 0 4 CANCEL
----
										
===M204.2856: Fieldname variable %C: expected %C, got %C===
<b>Return codes:</b> C 0 4 CANCEL
----
										
===M204.2857: %C field not allowed for %C field===
<b>Return codes:</b> C 0 4
----
										
===M204.2858: Fieldgroup context mismatch between COUNT-OCCURRENCES-OF field and counted field===
<b>Return codes: </b>C 0 4
----
										
===M204.2859: New automatic field not allowed for non-empty file===
<b>Return codes:</b> C 0 4
----
										
===M204.2860: Field %C already has a COUNT-OCCURRENCES-OF field===
<b>Return codes:</b> C 0 4
----
										
===M204.2861: Occurrence counter %C overflowed===
<b>Return codes:</b> C 0 4 CANCEL
----
										
===M204.2862: Attempt to update automatic field %C===
<b>Return codes:</b> C 0 4 SUFFIX ECHO
----
										
===M204.2863: Attempt to do %C for automatic field: %C===
<b>Return codes: </b>C 0 4 CANCEL
----
										
===M204.2865: Attempt to %C invalid datetime value: %C = %C===
<b>Return codes: </b>C 0 4 CANCEL
----
											
===M204.2866: File already has %C field===
<p><b>Return codes:</b> C 0 4</p>
----
								
===M204.2867: Fieldgroup %C already has %C field===
<b>Explanation:</b> If you try to define a second update tracker field of the same type for the same field group, you will invoke message 2867, where %C represents:
<ul>
<li>A CREATE-TIME</li>
<li>A CREATE-TIMEUTC</li>
<li>A CREATE-USER</li>
<li>AN UPDATE-TIME</li>
<li>AN UPDATE-TIMEUTC</li>
<li>AN UPDATE-USER</li>
</ul>
<p><b>Return codes:</b> C O 4</p>
----
								
===M204.2868: MINLOBE must be between 0 and %C===
<p><b>Return codes:</b> C 0 4</p>
----

===M204.2869: Change refused: MINLOBE > 0 for File <var class="term">filename</var> field <var class="term">fieldname</var>===
'''Return codes:''' C 0 4 AUDITER
----

===M204.2870: Change refused: MINLOBE > 0 for File <var class="term">filename</var> field <var class="term">fieldname</var>===
'''Return codes:''' C 0 4 CANCEL AUDITER
----

===M204.2871: Fieldgroup context mismatch between CONCATENATION-OF field and COMPONENT field===
<b>Return codes:</b> C 0 4
----

===M204.2872: Concatenation value too long for field %C===
<b>Return codes: </b>C 0 4 CANCEL
----

===M204.2873: Concatenation field %C component field %C contains separator character===
<b>Return codes: </b>C 0 4 CANCEL
----
										
===M204.2874: Attempt to %C a value that&#39;s %C: %C===
<b>Return codes: </b>C 0 4 CANCEL
----
										
===M204.2875: Concatenation list invalid: %C===
<b>Return codes:</b> C 0 4
----
										
===M204.2876: Invalid %C value: %C===
<b>Return codes:</b> C 0 4
----
										
===M204.2877: WITH clause invalid: %C===
<b>Return codes: C 0 4 ECHO</b>

----
										
===M204.2878: WITH clause invalid: field %C in %F %C===
<b>Return codes:</b> C 0 4 CANCEL
----
										
===M204.2879: Remote id %C mode %C===
<b>Return codes: I 0 0 SAVE NOTERM OPR</b>

----
										
===M204.2880: Memory datasets cannot be part of multi-dataset file===
<b>Return codes: C 0 4</b>

----
										
===M204.2881: Data conversion error===
<p><b>Return codes:</b> C 0 4 CANCEL</p>

----

===M204.2882: Recovery journal (CCARF) version %C is not supported===
<b>Explanation: </b>A CCARF data set was provided as input to a recovery step, but that CCARF data set was produced by a different version of Model 204 than the version that is running recovery.
<br><b>System manager response: </b>Correct the data set name referenced in CCARF and ensure that it was produced by the version of Model 204 that you are using to run recovery.
<br><b>Return codes: </b>E 52 52 OPR

----

===M204.2883: Mix of journal versions in recovery CCARF===
<b>Return codes: </b>E 52 52 SNAP OPR    

----
								
===M204.2884: {Field|Fieldgroup} was previously defined as a {fieldgroup|field}, new definition ignored===
<b>Return codes:</b> C 0 4

----

===M204.2885: Invalid fieldgroup id: <var class="term">fieldgroup</var>===
<b>Return codes:</b> C 0 4 CANCEL

----
								
===M204.2886: Fieldgroup id %C already exists in record %R in %F===
<b>Return codes:</b> C 0 4

----

===M204.2903: FILEORG=X&#39;100&#39; is not supported during FLOD/FILELOAD===
<b>Return codes:</b> E 0 8
----

===M204.2916: %C requires at least one area to be set in %C===
'''Explanation:''' When the size of a non-swappable server area is indicated (SERVNSSZ), at least one non-swappable server area must be indicated in SERVNSA.              
<br>'''Operator response:''' Correct the SERVNSA parameter setting.
<br>'''Return codes:''' E 0 4 AUDITMS
----

===M204.2921: Server areas above the bar are not supported in VSE===
'''Explanation:''' Non-swappable server areas ATB are not supported in VSE.                 
<br>'''Operator response:''' Remove the parameters for non-swappable server areas.
<br>'''Return codes:''' E 0 4 AUDITMS

----

===M204.2922: %C bit setting is not valid===
'''Explanation:''' The bit setting in [[SERVNSA parameter|SERVNSA]] is not valid. 
<br>For release 7.4, valid bits are: X'02000000'  
<br>For release 7.5, valid bits are: X'02000000', X'00800000', X'00004000', and X'00002000'                    
<br>'''Operator response:''' Correct the SERVNSA setting.  
<br>'''Return codes:''' E 0 4 AUDITMS
----
===M204.2923: Increase SERVNSSZ to at least %C for required non swappable server areas===
'''Explanation:''' The total amount of non-swappable server areas is larger than the non-swappable area size defined by the SERVNSSZ parameter. The total amount equals a sum of nonswappable area sizes plus 8 bytes per area. M204.2923 is issued when the problem occurs during initialization.
<br>'''System manager response:''' Increase the value of SERVNSSZ as noted (or decrease the non-swappable table size).  
<br>'''Return codes:''' E 80 80 AUDITAD OPR
----

===M204.2933: Module version mismatch, KOMM=%C, %C=% C===
'''Return codes:''' E 0 4 SNAP

----
===M204.2934: FILEORG X<nowiki>'200'</nowiki> not supported for hashed or sorted file organizations===
'''Explanation:''' Hashed or sorted files must be 16M files. The CREATE FILE command   
is rejected. 
<br>'''File manager response:''' Remove the conflicting FILEORG parameter and reissue CREATE FILE.
<br>'''Return codes:''' E 0 4 AUDITMS

----

===M204.2935: {CHUNK|CHUNK target} fields may not be RENAMED or DELETED===
'''File manager response:''' Do not attempt to RENAME or DELETE chunks or chunk targets.
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2936: A CHUNK field of size <var class="term">nnn</var> already exists for this field===
'''Explanation:''' For a given CHUNK target field, duplicate chunk sizes are not permitted. 
<br>'''File manager response:''' Correct the DEFINE FIELD that caused the message.
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2937: CHUNK SIZE: <var class="term">nnn</var> is not an integral multiple/divisor of the existing CHUNK size: <var class="term">nnn</var>===
'''Explanation:''' A CHUNK field's chunk size must be an integral multiple/divisor of all other chunk's sizes for a given chunk target.  
<br>This message identifies the existing chunk size that conflicts with the new one.  
<br>'''File manager response:''' Correct the DEFINE FIELD that caused the message.
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2938: You may not define more than %C chunks for a field===
'''Explanation:''' A given chunk target can have at most 20 chunks defined. 
<br>'''File manager response:''' Do not try to define more than 20 CHUNK fields for any given CHUNK target field.
<br>'''Return codes:''' C 0 4 AUDITER
----

===M204.2939: %C has been set to its %C value: %C===

<br>'''Return codes:''' I 0 0 AUDITMS

----

===M204.2940: Use of filename after INITIALIZE keyword discouraged because it gave different results prior to version 7.5===
'''Explanation:''' This message indicates that the format of the INITIALIZE command as entered does not conform to the syntax of:  
   <p class="code">INITIALIZE [KEEPDEF[S]]</p>
Prior to version 7.5, it was possible to place any text on the INITIALIZE command, and if it was anything other than KEEPDEF[S], it  was ignored.  In version 7.5, the syntax of INITIALIZE command is checked for strict correctness. 
<br>
If you have entered the name of the file being initialized AFTER the INITIALIZE command keyword, you can either correct the command (that is, remove the filename after the INITIALIZE command keyword) or use the MSGCTL M204.2940 command as described below so that the command can continue to work.
<br>'''File manager response:''' The most direct response is to correct the command to conform to the proper syntax, that is, remove extraneous strings after the INITIALIZE command keyword.
<br>'''System manager response:''' If the file manager has chosen to keep the filename after the INITIALIZE command keyword, and the filename is the same as the name of the file being initialized, you can have the following command executed at any time before the INITIALIZE command is executed:
    <p class="code">MSGCTL M204.2940 NOCOUNT</p>
This action represents a very special case for the NOCOUNT option of MSGCTL.
<br>
Normally, the NOCOUNT option only changes a message such that it does not increment the count of counting errors, but does not directly affect the operation which issued the error message.
<br>
For this message, however, setting the NOCOUNT operation indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.
<br>
Issuing the above MSGCTL command with version 7.5 of Model 204 will not present any risk of an incorrect operation of INITIALIZE. 
A word of caution, however: In prior versions of Model 204, a filename after the INITIALIZE command keyword is NOT checked against the name of the file being initialized. Therefore the use of the filename after the INITIALIZE command keyword could be a risky practice if such a command might be used in a prior version of Model 204. 
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2941: File being initialized does not match name given after INITIALIZE command: %C===
'''Explanation:''' 
This message indicates that the format of the INITIALIZE command as entered does not conform to the syntax of:  
<p class="syntax">INITIALIZE [KEEPDEF[S]]</p>     
Prior to version 7.5, it was possible to place any text on the INITIALIZE command, and if it was anything other than KEEPDEF[S], it was ignored.  In version 7.5, the syntax of INITIALIZE command is checked for strict correctness. 
<br>
In some cases, users have entered the name of the file being initialized AFTER the INITIALIZE command keyword, but this message indicates that whatever string you entered after the INITIALIZE command keyword is not the name of the file being initialized. 
<br>'''File manager response: '''
Correct the command. The most direct response is to correct the command to conform to the proper syntax: that is, remove extraneous strings after the INITIALIZE command keyword. 
<br>
However, if the system manager has performed a MSGCTL M204.2940 NOCOUNT command, and you want to enter the correct filename on the INITIALIZE command, that will allow the INITIALIZE operation to  proceed. 
<br>
'''System manager response: '''
<br>If the file manager is unable to correct the INITIALIZE command, you can have the following commands executed at any time before the INITIALIZE command is executed:                                                                         
   <p class="code">MSGCTL M204.2940 NOCOUNT
MSGCTL M204.2941 NOCOUNT</p>
These actions represent a very special case for the NOCOUNT option of MSGCTL. 
<br>Normally, the NOCOUNT option only changes a message such that it does not increment the count of counting errors, but it does not directly affect the operation which issued the error message.   
<br>For this message, however, setting the NOCOUNT operation indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.
<br>Issuing MSGCTL M204.2941 NOCOUNT is not recommended, because this results in what might appear to be checking of the filename when in fact it is not checked.                                             
<br>Issuing MSGCTL M204.2940 NOCOUNT does not present any risk with version 7.5 of Model 204, but, as discussed in the System Manager response section of message 2940, this practice should be done with caution. 
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2942: Extraneous string after field attribute list: %C===
'''Explanation:''' This message indicates that the format of the INITIALIZE command as entered for a hashed, sorted, or record security file does not conform to the syntax of: 
<p class="code">INITIALIZE
[SORT fldName (attributes)]
[HASH fldName (attributes)]
[RECSCTY fldName (attributes)]</p>
In particular, it indicates that some string followed the right parenthesis (')') of the attribute list.
Prior to version 7.5, nothing after the closing parenthesis was checked.
<br>'''File manager response:''' Correct the command. There should be no string after the right parenthesis.
<br>'''System manager response:''' If the file manager is unable to correct the INITIALIZE command, you can have the following command executed at any time before the INITIALIZE command is executed:  
   <p class="code">MSGCTL M204.2942 NOCOUNT </p>                                           
This action represents a very special case for the NOCOUNT option of MSGCTL. Normally, the NOCOUNT option only changes a message such that it does not increment the count of counting errors, but does not directly affect the operation which issued the error message. 
<br>For this message, however, setting the NOCOUNT operation indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.
<br>Issuing MSGCTL M204.2942 NOCOUNT is not recommended, because if you issue this command the string after the right parenthesis will not be analyzed.
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2943: Error using filename phrase for file %C: <var class="term">restriction</var>===
'''Explanation:''' This message indicates that the format of the INITIALIZE command as entered does not conform to the syntax of:
    <p class="code">INITIALIZE [KEEPDEF[S]]</p> 
Prior to version 7.5, it was possible to place any text on the INITIALIZE command, and if it was anything other than KEEPDEF[S], it was ignored.  In version 7.5, the syntax of INITIALIZE command is checked for strict correctness. 
<br>
In some cases, users have entered the name of the file being initialized AFTER the INITIALIZE command keyword, but this message indicates that the syntax requires some modification for the particular file being initialized. 
<br>'''File manager response:''' The command should be corrected; the most direct response is to correct the command to conform to the proper syntax, that is remove extraneous strings after the INITIALIZE command keyword. 
However, if the system manager has performed a MSGCTL M204.2940 NOCOUNT command, you can modify the command as indicated by the <var class="term">restriction</var> shown in the M204.2943 text.
<br>'''System manager response:''' If the file manager is unable to correct the INITIALIZE command, you can have the following commands executed at any time before the INITIALIZE command is executed:
<p class="code">MSGCTL M204.2940 NOCOUNT
MSGCTL M204.2943 NOCOUNT</p>
This action represents a very special case for the NOCOUNT option of MSGCTL. Normally, the NOCOUNT option only changes a message such that it does not increment the count of counting errors, but does not directly affect the operation which issued the error message.
<br>
For this message, however, setting the NOCOUNT operation indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.
<br>
Issuing MSGCTL M204.2943 NOCOUNT is not recommended, because this bypasses the checking that is intended by the <var class="term">restriction</var> shown in the M204.2943 text.
<br>
Issuing MSGCTL M204.2940 NOCOUNT does not present any risk with version 7.5 of Model 204, but, as discussed in the system manager response for M204.2940, this practice should be done with caution. 
<br>'''Return codes:''' C 0 4 AUDITER

----

===M204.2944: Should have end of <var class="term">cmd</var> command but instead found: <var class="term">string</var>===
'''Explanation:''' This message indicates that the format of the command indicated by cmd as entered does not conform to command syntax. 
<br>'''User response:''' Correct the command, either by simply removing string and any following strings or else by correcting the command to conform to the proper syntax.       
<br>'''File manager response:''' If the cmd in the M204.2944 text is INITIALIZE, this message indicates that the format of the INITIALIZE command as entered does not conform to the syntax of:  
   <p class="code">INITIALIZE [KEEPDEF[S]]</p>
Prior to version 7.5, it was possible to place any text on the INITIALIZE command, and if the text was anything other than KEEPDEF[S], it was ignored.  In version 7.5, the syntax of INITIALIZE command is checked for strict correctness. 
The command should be corrected as described in the user response above.
<br>'''System manager response:''' If the file manager is unable to correct the INITIALIZE command, you can have the following command executed at any time before the INITIALIZE command is executed:  
   <p class="code">MSGCTL M204.2944 NOCOUNT</p>
This action represents a very special case for the NOCOUNT option of MSGCTL. Normally, the NOCOUNT option only changes a message such that it does not increment the count of counting errors, but does not directly affect the operation which issued the error message.   
                                                                   
For this message, however, setting the NOCOUNT operation indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.  

Issuing MSGCTL M204.2944 NOCOUNT is not recommended, because whatever string was indicated on the INITIALIZE command is not checked.
<br>'''Return codes:''' C 0 4 AUDITER

----
 
===M204.2945: Error encountered, <var class="term">cmd</var> command not performed===
'''Explanation:''' This counting error message indicates that the processing of the <var class="term">cmd</var> command was not performed. This message should be preceded by one or more messages. (If the preceding messages were not counting error messages, they might not have been displayed on the user's terminal, depending on the MSGCTL parameter setting.) 
<br>'''User response:'''  Correct any conditions indicated by the preceding messages.   
<br>'''Return codes:''' C 0 4 AUDITER

----
 
===M204.2946: Error encountered, <var class="term">cmd</var> command not performed ===
'''Explanation:''' This informational message indicates that the processing of the <var class="term">cmd</var> command was not performed. This message should be preceded by one or more messages. (If the preceding messages were not counting error messages, they might not have been displayed on the user's terminal, depending on the MSGCTL parameter setting.) 
<br>'''User response:'''  Correct any conditions indicated by the preceding messages.   
<br>'''Return codes:''' I 0 0 AUDITMS

----

===M204.2947: Module address <var class="term">address</var> length <var class="term">length</var> protected===
<b>Explanation:</b> This informational message is displayed during startup to show the ranges of load module protection. To see which Rocket CSECTs are being referenced, look at the module map in a snap. For more information on the load module protection facility, see the [[MODPROT parameter]] description.
<br><b>Response:</b> No response is required. 
<br><b>Return codes:</b> I 0 0 AUDITMS

===M204.2955: Buffer allocation failed.===
<p><var class="term">Available in version 7.5 with zap maintenance applied. This message results in a cancel instead of a bug when storage is not available for universal buffer allocation.</var></p> 
 
There is not enough storage to allocate the universal buffer. The request has been cancelled. 

<b>System manager response:</b> Correct and retry.

<b>Return codes:</b> C 0 4 CANCEL
----

===M204.3026  TPN: <I>transaction program name</I>  Requesting User: <I>user id</I>===
<p><var class="term">Available in version 7.5 with zap maintenance applied.</var></p> 
Message 3026 accompanies this message: 
<br /><code>M204.2027 REJECTING ATTACH - SENSE DATA = <var class="term">xx</var></code> <br /> 
and displays the transaction program requested by the attach and the User ID associated with that request.

<b>System manager response:</b> Use the information in this message to identify the issuer of the rejected attach request.

<b>Return codes:</b> E 0 4 AUDITMS
----
===M204.3027 Source was <I>remote id</I>===  
<p><var class="term">Available in version 7.5 with zap maintenance applied.</var></p>
Message 3027 accompanies this message: <br />
<code>M204.2027 REJECTING ATTACH - SENSE DATA = <var class="term">xx</var></code> <br />
and displays the remote id from which the attach request was made.

<b>System manager response:</b> Use the information in this message to identify the issuer of the rejected attach request.

<b>Return codes:</b> E 0 4 AUDITMS

==DDGEN messages==

===DDG017: UNABLE TO PROCESS NON-TBO FILE WITH SYSOPT=4, CHANGE FILE TO TBO OR RESET SYSOPT.===
<p>&nbsp;</p>

===DDG018: FICREATE UNRECOGNIZABLE. DDGEN RUN CANCELLED.===

<p style="margin-left: 25%">[[#toc|Up to Contents]]</p>