JAL: add word

2018-06-19T21:54:45Z

add word

← Older revision		Revision as of 21:54, 19 June 2018
Line 1:		Line 1:
	This page lists messages that have an <code>M204IFIF.</code>, <code>M204CMIF.</code>, <code>M204ULIF.</code>, or <code>M204XDM.</code> prefix.		This page lists Model 204 messages that have an <code>M204IFIF.</code>, <code>M204CMIF.</code>, <code>M204ULIF.</code>, or <code>M204XDM.</code> prefix.

	__TOC__		__TOC__

JAL: add M204ULIF.0009

2018-06-19T21:33:37Z

add M204ULIF.0009

← Older revision		Revision as of 21:33, 19 June 2018
Line 174:		Line 174:

	<b>Response:</b> Look for error messages in the CCAOUT data set. Check the target Model 204 Online audit trail for problems that occurred at the point of the BATCH2 failure.		<b>Response:</b> Look for error messages in the CCAOUT data set. Check the target Model 204 Online audit trail for problems that occurred at the point of the BATCH2 failure.

			<hr style="height:2px; margin-top:2em">

			===M204ULIF.0009: PREVIOUS CCAOUT LINE LONGER THAN DCBLRECL-4; LINE TRUNCATED===
			This situation is described in [[Program Communication facilities#Managing DCBLRECL to avoid an ABEND\|Managing DCBLRECL to avoid an ABEND]].

			<b>Response:</b> To avoid the error, specify <code>RESET OUTCCC</code> to a value less than <code>DCBLRECL-4</code>, or increase DCBLRECL for CCAOUT.

JAL: Created page with "This page lists messages that have an `M204IFIF.`, `M204CMIF.`, `M204ULIF.`, or `M204XDM.` prefix. TOC ==M204xxIF. mes..."

2018-06-19T20:56:59Z

Created page with "This page lists messages that have an <code>M204IFIF.</code>, <code>M204CMIF.</code>, <code>M204ULIF.</code>, or <code>M204XDM.</code> prefix. __TOC__ ==M204xxIF. mes..."

New page

This page lists messages that have an <code>M204IFIF.</code>, <code>M204CMIF.</code>, <code>M204ULIF.</code>, or <code>M204XDM.</code> prefix.

__TOC__

==M204xxIF. messages==
These messages have an <code>M204IFIF.</code>, <code>M204CMIF.</code>, or <code>M204ULIF.</code> prefix.

The <code>M204IFIF</code> messages can be issued in IFAM2
and [[Program Communication facilities#BATCH2 facility|BATCH2]] applications. The same messages might be issued in IFAM1 or IFAM4 applications, but without the <code>M204IFIF</code> prefix.

The <code>M204CMIF</code> and <code>M204ULIF</code> messages can be issued in BATCH2.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0001 IFAM xxxxxxxx NOT UP===

Response: Start the Model 204 Online that is handling the desired channel.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0002 IFAM xxxxxxxx DIED===
The Model 204 Online that is handling the desired channel has terminated.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0003 IFAM xxxxxxxx NO THREADS AVAILABLE===
The Model 204 Online is not available for connection.

Response: Restart the Online with additional IODEVs.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0004 INSUFFICIENT STORAGE FOR ICB xxxxxxxx===
Response: Allocate additional private storage.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0005 INVALID ARGUMENT - UNABLE TO SET ERROR CODE===
Response: Correct the invalid user parameter list.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0006 INVALID FUNCTION NUMBER PASSED TO IFCALL===
Response: Correct the invalid user function parameter.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0007 NO CURRENT IFAM THREAD OR MODEL 204 CONNECTION===
A valid function was attempted; however, no connection is currently open.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0008 INVALID PARAMETER LIST===
Response: Correct the invalid user parameter list.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0009 INVALID LANGUAGE TYPE CODE FOR CURRENT THREAD===
Response: Correct the invalid Type parameter.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0010 SERIOUS CRAM ERROR, MACRO RETURN CODE = nnnn SAVE DUMP===
CRAM has returned an error.

Response: Save dumps and [[Contacting Rocket Software Technical Support|contact Technical Support]].

<hr style="height:2px; margin-top:2em">

===M204IFIF.0011 INSUFFICIENT SQA SPACE===
Response: Allocate additional SQA storage.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0012 ARGUMENTS TOO LARGE FOR IQB. CHECK IFFNSH STATISTIC ON AUDIT TRAIL===
Too much data was passed.

Response: Increase IFAM buffer size.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0013 TOO MANY DIAL CONNECTIONS CURRENTLY ACTIVE===
M204IFIF.0014 CALL TO IFSTHRD RESULTED IN NO SWITCH
Internal error.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0015 INVALID THREAD ID SPECIFIED FOR NEXT THREAD===
Internal error.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0016 IFDTHRD CALLED WITH NEXT THREAD ID EQUAL CURRENT M204IFIF.0017 WRONG CALL, SHOULD HAVE BEEN OTHER ONE===
Internal error.

<hr style="height:2px; margin-top:2em">

===M204IFIF.0018 LARGEST INPUT STRING: xxxxx BYTES, LARGEST IQB REQUIRED: xxxxx===

<hr style="height:2px; margin-top:2em">

===M204IFIF.0019 SUBSYSTEM NAME=%C===
This message is generated if the application cannot connect. The message contains a [[Cross-memory facilities CRAM and M204XSVC#The XDM load modules|secondary subsystem]] name.

Response: Check the CCAAUDIT output from the Model 204 Online job, and determine if the subsystem name matches the one that is displayed right after the CCAIN parameters are echoed, for example:
/// M204.2157: XMEMSVC VERSION = 4.1.1B 02/25/98
/// IGCLM244 4.1.1B 02/25/98
/// SUBSYSTEM NAME = QA04


<hr style="height:2px; margin-top:2em">

===M204CMIF.0001 CMSIUCV CONNECT FAILURE: RC = NN 3 1nnn===
An attempt to connect to Model 204 failed. Two-digit return code values are internal errors. A return code of <code>1nnn</code> indicates an IUCV error, where <var class="term">nnn</var> is the IUCV return code.

Response: Check that the correct channel name for the target Model 204 Online was specified. Make certain that the Online has a sufficient number of <var>IODEV</var>s for this type of connection. Verify that the target Model 204 Online is up.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0001 INVALID CHANNEL NAME VALUE===
The channel name was incorrectly specified to a BATCH2 job, and the job terminated with a return code of 300.

Response: Read [[Program Communication facilities#BATCH2 facility|BATCH2 facility]] for the correct parameter format.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0002 INVALID OMC PARAMETER VALUE===
The OMC value was incorrectly specified to a BATCH2 job, or the execution
parameters were specified out of order. The job terminated with a return code of 300.

Response: Read [[Program Communication facilities#BATCH2 facility|BATCH2 facility]] for the correct parameter format.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0003 INVALID URCTYPE PARAMETER VALUE===
The URCTYPE parameter was incorrectly specified to a BATCH2 job, or the execution parameters were specified out of order. The job terminated with a return code of 300.

Response: Read [[Program Communication facilities#BATCH2 facility|BATCH2 facility]] for the correct parameter format.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0004 BUFFER STORAGE NOT AVAILABLE===
A BATCH2 job failed to initialize because it was unable to obtain sufficient storage. The job terminated with a return code of 300.

Response: Increase the storage available to the BATCH2 job.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0005 CCAIN DATASTREAM COULD NOT BE OPENED===
A BATCH2 job could not open the CCAIN file and terminated with a return code of 300.

Response: Make sure the file has been correctly defined to the BATCH2 job.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0006 M204 CONNECTION NOT ESTABLISHED. ERROR CODE = nnn===
BATCH2 was unable to connect to the target Model 204 Online and terminated with a return code of 300.

Response: Look up the [[IFDIALN (HLI function)#Completion return code (RETCODE)|error code for IFDIALN]]. Make sure the Model 204 Online was started when the error occurred. Check the CCAOUT data set for additional errors.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0007 M204 CONNECTION LOST. ERROR CODE = nnnn===
After a BATCH2 job was started, it lost the connection to Model 204. The job terminated with a return code of 300.

Response: Look up the error code for <var>[[IFREAD (HLI function)|IFREAD]]</var> and <var>[[IFWRITE (HLI function)|IFWRITE]]</var>. Check for additional error messages in the CCAOUT data set.

<hr style="height:2px; margin-top:2em">

===M204ULIF.0008 RUN TERMINATED DUE TO USER RESTART===
A Model 204 error occurred that caused the BATCH2 User ID to be restarted. The BATCH2 job ends with a return code of 300.

Response: Look for error messages in the CCAOUT data set. Check the target Model 204 Online audit trail for problems that occurred at the point of the BATCH2 failure.

==M204XDM. messages==
This section lists status and report messages that can be issued by [[Defining the user environment (CCAIN)#Two CRAM options|M204XDM]] or [[M204XMON]].

<hr style="height:2px; margin-top:2em">

===M204XDM.001 GETMAIN identifier FAILED - TERMINATING===
A request to dynamically allocate storage (GETMAIN) failed.

<hr style="height:2px; margin-top:2em">

===M204XDM.002 NOT APF AUTHORIZED - TERMINATING===
This message is issued by the XDM master (M204XDM) when it is starting. M204XDM must be APF authorized, but it is not. This is an installation error.

<hr style="height:2px; margin-top:2em">

===M204XDM.003 SWAPPABLE - TERMINATING===
This message is issued by the XDM master (M204XDM) when it is starting. M204XDM must be [[Defining the user environment (CCAIN)#The importance of non-swappability|defined as non-swappable]], but it is not. This is an installation error.

<hr style="height:2px; margin-top:2em">

===M204XDM.004 module NOT LOADED - TERMINATING===

A request to dynamically LOAD a module failed. The most likely cause is that the module does not exist in the <code>//JOBLIB</code> or <code>//STEPLIB</code> for the job.

Response: Check the JCL and/or XDM installation. If the problems persist, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<hr style="height:2px; margin-top:2em">

===M204XDM.005 ERROR ON M204XSVC INITIALIZATION===
Internal error.

<hr style="height:2px; margin-top:2em">

===M204XDM.006 ATTACH 1 FAILED===
The operator issued a <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command (in response to [[#M204XDM.100 AWAITING COMMAND|message 100]]) to monitor the XDM master (M204XDM). M204XDM calls M204XMON, but some internal error
means this could not be done.

Response: Retry the command.

Possible cause: The most likely cause is that the M204XMON module does not exist in the <code>//JOBLIB</code> or <code>//STEPLIB</code> for the XDM master job.

<hr style="height:2px; margin-top:2em">

===M204XDM.007 XMEMORY ERROR OR XDM ALREADY ACTIVE===
Many reasons may elicit this message: for example, the subsystem name passed to the XDM started task did not match that defined in IEFSSN. Any failure to set up the [[Defining the user environment (CCAIN)#Using CRAM on a z/OS operating system|cross memory environment]] correctly causes this error message: for example, assignment of an LX, assignment of AX, memory shortage, authorization failure, and so on. Also, XDM may already be active.

<hr style="height:2px; margin-top:2em">

===M204XDM.008 ATTACH 2 FAILED - EOJ NOT AVAILABLE===
XDM attempted to attach the monitor facility to check for active tasks, but the attach failed. XDM does not allow an <var>EOJ</var> if there is a possibility of any active tasks.

<hr style="height:2px; margin-top:2em">

===M204XDM.009 M204XMON CHECK FAILED - EOJ NOT AVAILABLE===
The operator issued an <var>EOJ</var> command (in response to [[#M204XDM.100 AWAITING COMMAND|message 100]]) to shut down the XDM master (M204XDM). M204XDM calls M204XMON to see if there are any Onlines
still active, but some internal error occurred that means this check could not be done.

Response: Retry the command. If it still fails, manually check that no Onlines are using this XDM master, and then issue an <var>[[Defining the user environment (CCAIN)#Shutdown commands|EOJ,CANCEL]]</var> command.

Note: The <var>EOJ,CANCEL</var> command should be used with extreme caution. Abnormal termination of the XDM master may require an IPL in order for Model  204 Online jobs to use cross-memory services. 

Possible cause: The most likely cause is that the M204XMON module does not exist in the <code>//JOBLIB</code> or <code>//STEPLIB</code> for the XDM master job. 

<hr style="height:2px; margin-top:2em">

===M204XDM.010 ONLINES ACTIVE, CANNOT TERMINATE===
The operator issued an <var>EOJ</var> command (in response to [[#M204XDM.100 AWAITING COMMAND|message 100]]) to shut down the XDM master, but the XDM master cannot shut down because Onlines that use it are still active.

Response: Issue a <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR,ONLINES]]</var> command to see what they are.

<hr style="height:2px; margin-top:2em">

===M204XDM.100 AWAITING COMMAND===
Whenever the XDM master is active (it should always be), <code>100</code> is displayed on the console. XDM master commands are issued by replying to this message.

<hr style="height:2px; margin-top:2em">

===M204XDM.101 INVALID COMMAND===
An invalid or unrecognized command was entered.

<hr style="height:2px; margin-top:2em">

===M204XDM.250 ERROR TRAPPED (NO SDWA) TERMINATING===
Internal error.

<hr style="height:2px; margin-top:2em">

===M204XDM.300 M204XMON not APF-authorized - terminating===
This message is issued by the monitor ([[M204XMON]]) when it is starting. M204XMON
must be APF authorized, but it is not. This is an installation error.

<hr style="height:2px; margin-top:2em">

===M204XDM.301 Parameter missing - terminating===
A parameter error occurred when the Monitor, M204XMON, was run. Parameters are
specified on the <code>PARM=</code> part of the EXEC card.

<hr style="height:2px; margin-top:2em">

===M204XDM.302 Parameter too long - terminating===
A parameter error occurred when the Monitor, M204XMON, was run. Parameters are specified on the <code>PARM=</code> part of the EXEC card.

<hr style="height:2px; margin-top:2em">

===M204XDM.303 Parameter SSNAME missing===
A parameter error occurred when the Monitor, M204XMON, was run. Parameters are
specified on the <code>PARM=</code> part of the EXEC card.

<hr style="height:2px; margin-top:2em">

===M204XDM.304 Parameter invalid===
A parameter error occurred when the Monitor, M204XMON, was run. Parameters are
specified on the <code>PARM=</code> part of the EXEC card.

<hr style="height:2px; margin-top:2em">

===M204XDM.305 CCAPRINT open failed - terminating===
You are probably missing a <code>//CCAPRINT</code> DD card in the JCL for the M204XMON or M204XDM job.

<hr style="height:2px; margin-top:2em">

===M204XDM.306 GETMAIN failed - terminating===
Internal error.

<hr style="height:2px; margin-top:2em">

===M204XDM.307 Subsystem error===
The XDM monitor, [[M204XMON]], was invoked with a parameter of <code>SSNAME=name</code>, but an error was encountered when processing the specified subsystem name. The error is either <code>NOT DEFINED</code> or <code>occurs more than once - ERROR</code>.

Response: Check whether the subsystem name you specified is correct. It should be the same value as the parameter for the XDM master, <var>M204XDM</var>.

<hr style="height:2px; margin-top:2em">

===M204XDM.310 XDM Monitor V4.1.1x - Starting yyyy/mm/dd hh:mm:ss===
The XDM monitor, [[M204XMON]], is starting.

Response: No action is required.

<hr style="height:2px; margin-top:2em">

===M204XDM.311 Listing all subsystems===
Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.312 Subsystems listed, Count=nnn===
Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.313 XDM MASTER status===
The XDM monitor, [[M204XMON]], was invoked with a parameter of <code>SSNAME=name</code> to monitor the XDM master using the specified subsystem.

This message reports the status of the XDM master as one of the following:
<ul>
<li>Subsystem=ssss </li>
<li>Jobname=jjjjjjjj ACTIVE (Subsystem=ssss) </li>
<li>INACTIVE (Subsystem=ssss) </li>
<li>IN ERROR with multiple active SSACBs (Subsystem=ssss) </li>
</ul>

Response: None, except for <code>IN ERROR</code> status. For that status, rerun M204XMON, and if the error persists, report it to [[Contacting Rocket Software Technical Support|Technical Support]].

<hr style="height:2px; margin-top:2em">

===M204XDM.314 Online Jobname=jjjjjjjj Users=nnn===
The <code>Users</code> in this message represent XDM threads, also called connected CRAM threads.

Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.315 Total Users=nnn===
The <code>Users</code> in this message represent the total XDM threads, also called connected CRAM threads.

Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.317 User Jobname=jjjjjjjj (Channel=cccccccc)===
Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.318 Totals) Onlines=nnn Users=nnn===
The Users in this message represent XDM threads, also called connected CRAM
threads.

Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.319 Online Jobname=jjjjjjjj===
Information message; no response required.

<hr style="height:2px; margin-top:2em">

===M204XDM.390 0C4 trapped - terminating===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a
control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

<hr style="height:2px; margin-top:2em">

===M204XDM.391 0C4 trapped processing SSCTs - recovering===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a
control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

<hr style="height:2px; margin-top:2em">

===M204XDM.392 0C4 trapped processing IICBs/SSACBs - recovering===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a
control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

<hr style="height:2px; margin-top:2em">

===M204XDM.393 0C4 trapped processing SSCBs - recovering===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a
control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

<hr style="height:2px; margin-top:2em">

===M204XDM.394 0C4 trapped processing IICBs - recovering===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

<hr style="height:2px; margin-top:2em">

===M204XDM.395 0C4 trapped processing UICBs - recovering===
While [[M204XMON]] was processing the XDM control blocks to produce a report, a
control block was changed by another XDM user.

Response: Rerun the <var>[[Defining the user environment (CCAIN)#Monitoring XDM|MONITOR]]</var> command job, or reissue the operator <var>MONITOR</var> command.

M204xxIF. and M204XDM. messages - Revision history

JAL: add word

JAL: add M204ULIF.0009

JAL: Created page with "This page lists messages that have an M204IFIF., M204CMIF., M204ULIF., or M204XDM. prefix. __TOC__ ==M204xxIF. mes..."

JAL: Created page with "This page lists messages that have an `M204IFIF.`, `M204CMIF.`, `M204ULIF.`, or `M204XDM.` prefix. TOC ==M204xxIF. mes..."