HPlogo LU 6.2 API Application Programmer's Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 5  Intrinsic Descriptions

MCSendData

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

Sends one data record to the remote TP.

Syntax

			              I16V      CA    I16V            I16
										MCSendData(ResourceID, Data, Length, RequestToSendReceived,
 
 					             I32
 				           Status);

Parameters

ResourceID

Required; 16-bit signed integer by value; input. This is the unique resource ID number assigned to this conversation when it was allocated. See MCAllocate or MCGetAllocate, in this chapter, for more information.

Data

Required; character array; input; EBCDIC. This byte array holds the data that is to be sent to the remote TP. Data that is to be sent to an EBCDIC application must be translated from ASCII to EBCDIC. The MPE CTRANSLATE intrinsic, or the NLTRANSLATE intrinsic on MPE XL, may be used.

Length

Required; 16-bit signed integer by value; input. This is an integer from 0 through 32763 that specifies the length, in bytes, of the data record to be sent. If Length = 0, a null record is sent.

RequestToSendReceived

Required; 16-bit signed integer; output. Indicates whether the remote TP has issued a RequestToSend. Possible values are as follows:

1 = YES

Indicates a RequestToSend has been received from the remote TP. The remote TP has issued the equivalent of the MCReqToSend intrinsic, requesting that the local TP enter Receive state and place the remote TP in Send state.

0 = NO

No RequestToSend has been received.

Status

Required; 32-bit signed integer; output. Indicates the result of intrinsic execution. See the "Status Parameter" section, earlier in this chapter, for more information.

Description

The MCSendData intrinsic sends data to the remote TP. When it is called, the data in the Data parameter is moved to the send buffer. When the send buffer is full, or when an intrinsic is called that flushes the send buffer, all the data in the send buffer is transmitted to the remote TP.

On MPE V, the send buffer is 2044 bytes for every conversation. On MPE XL, the send buffer is the same size as the maximum RU size for the session. The maximum RU size is a configured value from 256 through 2048 associated with the session type. For more information on configuring RU sizes, see the APPC Subsystem on MPE XL Node Manager's Guide.

If you call MCSendData with a Data parameter smaller than the send buffer, the data might not be transmitted immediately to the remote TP. To empty the send buffer and transmit all data immediately to the remote TP, call the MCFlush intrinsic. See the description of MCFlush, earlier in this chapter. See Chapter 6 “Buffer Management” for more information on the send and receive buffers.

Status Info Values

0    Successful Completion.
-1    Intrinsic called with parameter out of bounds.
-2    Invalid 'ResourceID' parameter specified in intrinsic call.
-11   Out of range 'Length' parameter specified in intrinsic call.
-13   Data buffer specified in intrinsic call is out of bounds.
-20   Not enough stack space for intrinsic to run.
-40   Intrinsic called in invalid state.
-50   Allocation Error.
-51   Resource Failure:  Retry possible.
-52   Resource Failure:  No retry possible.
-60   Program Error:  Data may have been purged.
-90   An internal error in Presentation Services has occurred.
-91   An internal error in the APPC subsystem has occurred.
-1002 An internal error at the mapped conversation level has occurred.
-1003 Required parameter missing.
-1020 Deallocate Abend.
-1105 Internal Error: Conversation deallocated.
Feedback to webmaster