M204.2943 Error using filename phrase for file string: FILE keyword required
This message indicates that a string within an INITIALIZE command needs to be qualified, to ensure that the command is not ambiguous.
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.
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, without qualification by the FILE keyword, any file name after the INITIALIZE keyword, you can issue (usually in CCAIN) the following command:
MSGCTL M204.2943 NOCOUNT
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 that 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.
MSGCTL M204.2943 NOCOUNT is not recommended, however, because of possible misunderstandings that could result from ambiguity.
|RETCODEO=0||Sets online return code|
|RETCODEB=4||Sets batch (single user) return code|
|CLASS=E||Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter|
|AUDITER||Writes the message with line type ER to the audit trail|
|COUNT||Increments the error count (ERCNT) parameter|