M204.0336: Difference between revisions
(Automatically generated page update) |
No edit summary |
||
| Line 3: | Line 3: | ||
The run has failed to initialize due to problems with the [[Cross-memory facilities CRAM and M204XSVC|CRAM]] interface. The possible message formats are: </P> | The run has failed to initialize due to problems with the [[Cross-memory facilities CRAM and M204XSVC|CRAM]] interface. The possible message formats are: </P> | ||
<P> | <P> | ||
Format 1: RC nn FROM CRIO OPEN/PUT/GET </P> | Format 1: RC <var class="term">nn</var> FROM CRIO OPEN/PUT/GET </P> | ||
<P> | <P> | ||
Format 2: ECB postcode FROM CRFS PUT/GET </P> | Format 2: ECB <var class="term">postcode</var> FROM CRFS PUT/GET </P> | ||
<P> | <P> | ||
The formats are explained as follows: </P> | The formats are explained as follows: </P> | ||
| Line 63: | Line 63: | ||
99 </P></TD> | 99 </P></TD> | ||
<TD ROWSPAN="1" COLSPAN="1"><P CLASS="zcellbody"> | <TD ROWSPAN="1" COLSPAN="1"><P CLASS="zcellbody"> | ||
The IGCLM244 module was generated with no SVC number, indicating an SVC-less installation. The XMEMOPT X'80' bit is required for this XDM CRAM usage.</P></TD></TR> | The IGCLM244 module was generated with no SVC number, indicating an SVC-less installation. The <var>[[XMEMOPT parameter|XMEMOPT]]</var> X'80' bit is required for this XDM CRAM usage.</P></TD></TR> | ||
<TR><TD ROWSPAN="1" COLSPAN="1"><P CLASS="zcellbody"> | <TR><TD ROWSPAN="1" COLSPAN="1"><P CLASS="zcellbody"> | ||
| Line 71: | Line 71: | ||
</TR></TABLE> | </TR></TABLE> | ||
<p> | <p> | ||
<b>System manager response:</b> Contact Technical Support and have the audit trail available. </p> | <b>System manager response:</b> Contact [[Contacting Rocket Software Technical Support|Technical Support]] and have the audit trail available. </p> | ||
{{Template:M204.0336 footer}} | {{Template:M204.0336 footer}} | ||
<!-- skeleton as it was in pdf/rc nn FROM CRIO op /--> | <!-- skeleton as it was in pdf/rc nn FROM CRIO op /--> | ||
Latest revision as of 23:23, 22 February 2018
M204.0336 retCode value from CRIO op
The run has failed to initialize due to problems with the CRAM interface. The possible message formats are:
Format 1: RC nn FROM CRIO OPEN/PUT/GET
Format 2: ECB postcode FROM CRFS PUT/GET
The formats are explained as follows:
- Format 1 indicates that Model 204 module CRIO attempted to open a channel, send a message down a channel, or receive a message from a channel. CRAM was unable to satisfy the request. The message states the return code and the operation attempted. For example, the return code 16 indicates that the CRAM channel is already open.
- Format 2 indicates that Model 204 module CRFS received an unexpected post code from CRAM while attempting an I/O operation on a channel. The message shows the post code and the operation attempted.
Possible return codes include the following values:
Value |
Description |
|---|---|
4 |
INVALID FUNCTION |
8 |
CB FORMAT ERROR |
16 |
(OPEN MAST) CHANNEL ALREADY OPEN |
20 |
(OPEN USER) NO USER LINES FREE |
24 |
(OPEN) SUBTASKS NOT PROPERLY OPENED |
12 |
(READ/WRITE) ICB NOT OPEN |
16 | (READ/WRITE) OTHER TASK HAS DIED |
20 | (READ/WRITE) UNEXPECTED COMMAND |
28 |
NOT ENOUGH STORAGE |
99 |
The IGCLM244 module was generated with no SVC number, indicating an SVC-less installation. The XMEMOPT X'80' bit is required for this XDM CRAM usage. |
110 |
(VMCF WRITE) MESSAGE LIMIT EXCEEDED |
System manager response: Contact Technical Support and have the audit trail available.
Message attributes:
| RETCODEO=80 | Sets online return code |
|---|---|
| RETCODEB=80 | 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 |
| NOTERM | Does not display the message on the user's terminal |
| OPR | Writes the message to the (operator) console |