From m204wiki
Jump to navigation Jump to search

M204.2940  Attempt to use filename (string) after INITIALIZE keyword disallowed because it is misleading

This message indicates that an INITIALIZE command was entered that does not strictly conform to the syntax: an extraneous string was entered which appeared to be a filename, but INITIALIZE operates on the file specified by the IN clause, not by a filename following INITIALIZE.

Prior to version 7.5, it was possible to place extraneous text on the INITIALIZE command, and that text would be ignored. In version 7.5 and higher, the syntax of the INITIALIZE command is checked for strict correctness.

If you have entered the name of the file being initialized after the INITIALIZE keyword, you should correct the command. That is, remove the file name (and preceding FILE keyword, if present) that is after the INITIALIZE keyword.

The system manager can also use the MSGCTL workaround as described below so that all invalid INITIALIZE commands formatted in this way can continue to work.

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 keyword.

System manager response: If you choose to always allow a file name after the INITIALIZE keyword (when that name is the same as the name of the file being initialized), you can issue (usually in CCAIN) the following command:


This action represents a very special case for the NOCOUNT option of MSGCTL. Normally, NOCOUNT only changes a message so that it does not increment the error count, and it does not directly affect the operation which issued the error message. For this message, however, NOCOUNT indicates that this condition is to be allowed, and normal processing of the INITIALIZE command will continue.

Issuing the above MSGCTL command does not introduce any risk, relative to behavior with Model 204 prior to version 7.5, of an incorrect operation of INITIALIZE. The only caution to be observed is that in pre-7.5 versions of Model 204, a file name after the INITIALIZE keyword is not checked against the name of the file being initialized. So the use of the file name after the INITIALIZE keyword might be a risky practice, if it is possible such a command might be used in a pre-7.5 version of Model 204.

See also

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages