New and updated messages in Model 204 version 7.6

Back to 7.6 release notes

Back to wiki main page

M204 messages

M204.0066: MINIMUM SERVSIZE|SERVNSSZ|SERVGSZ REQUIRED FOR THIS USER IS nnnnnn

This message displays the minimum server size required for this user. The minimum server size is determined by the user tables whose sizes are fixed at Model 204 initialization, along with the sizes of all variable length tables set in the user parameters, such as STBL and VTBL. These tables, and the formula for determining server size, are described in Defining the runtime environment (CCAIN).

Return codes: I 0 0 AUDITAD

As of version 7.6, this message can now display SERVSIZE, SERVNSSZ, or SERVGSZ.

M204.0067: FIXED SERVSIZE|SERVNSSZ FOR THIS USER IS nnnnnn

This message displays the size of the fixed portion of the server for this user. The fixed portion of the server is determined by the user tables whose sizes are set during initialization. These tables, and the formula for determining server size, are described in Defining the runtime environment (CCAIN).

Return codes: I 0 0 AUDITAD

As of version 7.6, this message can now display either SERVSIZE or SERVNSSZ.

M204.0098: MINIMUM SERVSIZE FOR THESE TABLES: BTB=nnnnnnnn; ATB =nnnnnnnn; NSA=nnnnnnnn

This message informs the user of the minimum server size, in bytes, required to contain the user’s server tables below the bar, above the bar, and in the non-swappable area.

Return codes: I 0 0 AUDITMS

As of version 7.6, this message displays the server requirements for the above-the-bar and non-swappable areas as well as the below-the-bar area.

---

M204.0099: MINIMUM SERVSIZE FOR THESE TABLES: BTB=nnnnnnnn; ATB =nnnnnnnn; NSA=nnnnnnnn

This message informs the user of the minimum server size, in bytes, required to contain the server tables below the bar, above the bar, and in the non-swappable area.

Return codes: I 0 0 NOTERM

As of version 7.6, this message displays the server requirements for the above-the-bar and non-swappable areas as well as the below-the-bar area.

---

M204.0131: MSGCTL command

In previous Model 204 versions, 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 to CCAAUDIT 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.0524: Maximum number (256) of screens|images exceeded

Model 204 allows a maximum of 256 screens and/or images per request.

Response: Reduce the number of screens and images to 256 or fewer, and retry the request.

C 0 4 ECHO AUDITER

---

M204.0569: Find: filename Table B records to be searched = number

In version 7.6, with zap maintenance applied, this message now displays the name of the file containing the Table B records to be searched.

A Find statement requiring a direct search of the file filename has identified the number of records to be retrieved. This number exceeds the value of the MBSCAN parameter.

Response: Reply to the prompt that follows this message to indicate whether or not you want the direct search to proceed. Use the VIEW MBSCAN command to determine the maximum number of records to be retrieved without a prompt. Use the RESET MBSCAN command to change the number of records. A value of -1 indicates no limit.

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

---

M204.2950: IODEV 25 line not allowed with FUNTSKN > 0

System manager response: Correct the command and retry.

C 0 4

---

M204.2953: File filename dataset_name zHPF capabilities hex_values Supported: indicator

This informational message displays zHPF capabilities for each data set in a currently open file. The Supported: indicator shows whether zHPF type I/O, called "transport mode I/O," can be used for the data sets.

hex_values, 3-bytes represent the existing zHPF capabilities as shown in the following tables:

Byte 1: ZHPF_FLAG1: zHPF Channel Program Information Area, Capabilities flag 1

Value	Meaning
X'80'	all of the online paths for the device support bidirectional data for zHPF I/O requests.
X'40'	zHPF is supported for EXCPVR requests
X'20'	The incorrect length facility is supported by the processor
X'10'	zHPF is supported for EXCP virtual requests

Byte 2: ZHPFD_FLAG1: zHPF DASD Feature Information Area, Capabilities flag 1

Value	Meaning
X'80'	Phase 0 zHPF features are supported
X'20'	Multi-track operations are supported
X'08'	Transfer TCA Extension (TTE) DCW supported
X'04'	Phase 1 zHPF features are supported
X'02'	Imbedded Locate Records are supported
X'01'	Format and Update writes in same chnl pgm

Byte 3: ZHPFD_FLAG2: zHPF DASD Feature Information Area, Capabilities flag 2

Value	Meaning
X'80'	zHPF Format Write supported
X'40'	zHPF TCAX Pad fix

indicator has one of the following values:

Value	Meaning
YES	zHPF is supported for dataset_name in filename
NO	hardware or z/OS support for zHPF functionality is insufficient (for example when z/OS runs under VM)
N/A	zHPF support is not available at all at the z/OS or hardware level

1 0 0 AUDITMS

---

M204.2954: Feature name not supported

This informational message indicates that the named feature is not supported for zHPF.

I 0 0 AUDITMS

---

M204.2955: Buffer allocation failed.

There is not enough storage to allocate the universal buffer. The request has been cancelled.

System manager response: Correct and retry.

C 0 4 CANCEL

---

M204.2958: APSYPAGE obsolete as of 7.6

The APSYPAGE parameter is disabled as of version 7.6. This message is informational: if APSYPAGE is set, the Online will still come up. However, APSYPAGE will have no effect. See APSYPAGE parameter for information about an alternative to APSYPAGE.

I 0 0 AUDITMS

---

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