New and updated messages in Model 204 version 7.6

From m204wiki
Jump to navigation Jump to search

Back to 7.6 release notes

M204 messages

M204.0131: MSGCTL command

In previous Model 204 releases, M204.0131 was used for two purposes:

  • to echo the preceding MSGCTL command just issued by any user (when the CUSTOM parameter was set to 39)
  • to indicate a successful checkpoint completion (in this case, M204.0131 was redundant with M204.0843)

As of release 7.6, M024.0131 is used only with CUSTOM=(39) to echo the preceding MSGCTL command just issued by any user.

The checkpoint status is returned (as in previous releases) by M204.0843.

M204.0349: Login failed
(alternative text) 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.

Note: The CUSTOM parameter setting of 19, available in version 7.6 (or version 7.5 with zap 75Z279 applied), causes "Enter logoff" to be displayed instead of "Login failed."

Response: 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.

System manager response: 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.

Return codes: C 0 4 AUDITER


M204.0468: Compilation not saved - reason filename

The compilation for a precompileable subsystem procedure could not be saved for the indicated reason. The procedure is marked as a non-precompiled procedure for the duration of the subsystem session.

As of release 7.6, if reason indicates a problem with a file, filename is displayed.

Response: Notify the system manager.

System manager response: Look at the audit trail to determine the name of the procedure in error. Correct the procedure so that it follows all the conventions required for subsystem precompiled procedures.

I 0 0 AUDITMS

M204.1158 CAN’T action (reason) PROCEDURE: procname

M204.1158 is now issued only once, if an attempt is made to copy or display multiple procedures and the first attempt fails. This avoids issuing the same message numerous times for all remaining procedures and possibly exceeding ERMX, which could result in a user restart. No attempt will be made to copy or display the remaining procedures.

action is a copy or display of the procedure identified by procname

reason (such as "proc not found") indicates why procname cannot be copied or displayed:

  • The specified procedure does not exist.
  • The specified procedure is being modified.
  • You do not have proper authority to copy or display this procedure.
  • You do not have proper authority to copy into this procedure.

Response: Check for misspelling, wait until the procedure is not in use by someone else, or have the file manager grant you access to this procedure.

File manager response: Consider giving the user access to copy or display this procedure. If the user has access to the procedure and it is a SECURED procedure, check that the user has access to the same PCLASS in the output file.

C 0 4 AUDITER

M204.1173: Can't edit (reason) procedure procname

Message 1173 now displays (in parentheses) the reason that the edit failed.

reason (such as "proc not found") indicates why procname cannot be edited:

  • The specified procedure does not exist.
  • The specified procedure is being modified.
  • You do not have proper authority to edit this procedure.

Response: Check for misspelling, wait until the procedure is not in use by someone else, or have the file manager grant you access to this procedure.

File manager response: Consider giving the user access to edit this procedure. If the user has access to the procedure and it is a SECURED procedure, check that the user has access to the same PCLASS in the output file.

C 0 4 AUDITER

M204.2949: Expecting item on command_name command, found: "baditem"

This message indicates that the command_name command was incorrectly entered. A required term (item) was missing at a certain point of the command, and instead the command contained badItem at that point.

System manager response: Correct the command and retry.

C 0 4 AUDITER

MSIR messages

MSIR.1075: Not all ciphers supported on this hardware; SSLCIPH reset to X'nnnn(new SSLCIPH)'

The SSLCIPH parameter, used with a JANUS DEFINE command for an SSL connection, specifies one or more ciphers that are not supported on this hardware.

The parameter has been reset to the value indicated.

System Manager response: Check with the system programmers to determine what level of the IBM MSA (Message-Security Assist) feature is installed and if an upgrade is required.

Return Codes: E 0 4 AUDITMS

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=New_and_updated_messages_in_Model_204_version_7.6&oldid=77243"