M204.1787: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 1: Line 1:
{{Template:M204.1787 skeleton}}
{{Template:M204.1787 skeleton}}
<P>
<P>
The DATALEN parameter, in the DEFINE PROCESS command, is too large. If CICS TRANSFER (MODE=XCTL), DATALEN must be less than or equal to the CRAM buffer size, minus 12 bytes. </P>
The <var>DATALEN</var> parameter, in the <var>DEFINE PROCESS</var> command, is too large. If CICS TRANSFER (MODE=XCTL), <var>DATALEN</var> must be less than or equal to the [[Cross-memory facilities CRAM and M204XSVC|CRAM]] buffer size, minus 12 bytes. </P>
<P>
<P>
If SNA Communications Server (also known as VTAM) TRANSFER (MODE=PASS), DATALEN must be less than or equal to 255 bytes. </P>
If SNA Communications Server (also known as VTAM) TRANSFER (MODE=PASS), <var>DATALEN</var> must be less than or equal to 255 bytes. </P>
<p>
<p>
<b>Response:</b> Contact your system manager. </p>
<b>Response:</b> Contact your system manager. </p>
<p>
<p>
<b>System manager response:</b> The CRAM buffer size for full-screen type threads (IODEVs 11 and 41) is determined by the value of the output page buffer. The DATALEN parameter in the DEFINE PROCESS command must specify a value that is less than or
<b>System manager response:</b> The CRAM buffer size for full-screen type threads (<var>IODEV</var>s 11 and 41) is determined by the value of the output page buffer. The <var>DATALEN</var> parameter in the <var>DEFINE PROCESS</var> command must specify a value that is less than or
equal to the CRAM buffer size, minus 12 bytes. </p>
equal to the CRAM buffer size, minus 12 bytes. </p>
<P>
<P>
See [[DEFINE PROCESS command: Transfer Control partner]] for detailed information about setting DATALEN when using SNA Communications Server TRANSFER. </P>
See [[DEFINE PROCESS command: Transfer Control partner]] for detailed information about setting <var>DATALEN</var> when using SNA Communications Server TRANSFER.  
</P>
{{Template:M204.1787 footer}}
{{Template:M204.1787 footer}}
<!-- skeleton as it was in pdf/THE DEFINED PROCESS-TO-PROCESS BUFFER SIZE IS TOO LARGE /-->
<!-- skeleton as it was in pdf/THE DEFINED PROCESS-TO-PROCESS BUFFER SIZE IS TOO LARGE /-->

Latest revision as of 19:16, 12 March 2018

M204.1787  The defined process-to-process buffer size is too large

The DATALEN parameter, in the DEFINE PROCESS command, is too large. If CICS TRANSFER (MODE=XCTL), DATALEN must be less than or equal to the CRAM buffer size, minus 12 bytes.

If SNA Communications Server (also known as VTAM) TRANSFER (MODE=PASS), DATALEN must be less than or equal to 255 bytes.

Response: Contact your system manager.

System manager response: The CRAM buffer size for full-screen type threads (IODEVs 11 and 41) is determined by the value of the output page buffer. The DATALEN parameter in the DEFINE PROCESS command must specify a value that is less than or equal to the CRAM buffer size, minus 12 bytes.

See DEFINE PROCESS command: Transfer Control partner for detailed information about setting DATALEN when using SNA Communications Server TRANSFER.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter
SAVESaves the message in the VIEW ERRORS table

Back to list of messages