Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Net - <b>chain send</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
CHAIN SEND

Command code
. Hex 17 - wait option
. Hex 97 - no-wait option

Fields required
. NCB_LSN
. NCB_BUFFER@
. NCB_LENGTH
. NCB_CALLNAME  The format of the second buffer is specified as follows:
                . NCB_LENGTH2  (DW)
                . NCB_BUFFER2@ (DD)
. NCB_POST@     (if no-wait option is used)
. NCB_LANA_NUM  (number of the adapter you want to chain send)

Field returned
. NCB_RETCODE
. NCB_CMD_CPLT

Immediate return codes
. Hex 00    - Command has no immediate errors
. Hex 03    - Invalid command
. Hex 21    - Interface busy
. Hex 22    - Too many commands outstanding
. Hex 23    - Invalid number in NCB_LANA_NUM field
. Hex 40/4F - Unusual network condition
. Hex 50/FE - Adapter malfunction

Final return codes
. Hex 00    - Command complete
. Hex 03    - Invalid command
. Hex 05    - Command time-out
. Hex 08    - Invalid local session number
. Hex 0A    - Session closed
. Hex 0B    - Command canceled
. Hex 18    - Session ended abnormally
. Hex 21    - Interface busy
. Hex 22    - Too many commands outstanding
. Hex 23    - Invalid number in NCB_LANA_NUM field
. Hex 40/4F - Unusual network condition
. Hex 50/FE - Adapter malfunction

Function
This command sends data by the session number indicated in NCB_LSN. The data
is taken from the buffers for the indicated number of bytes. Two buffers can
be chained together with this command.

The data in the second buffer is chained to the data in the first buffer and
sent as a single message. The NCB_CALLNAME is used to specify the length and
address of the second buffer. The length is specified in the first 2 bytes;
the buffer address is the next 4 bytes.

When a session is closed by the remote computer, all Chain Send commands
pending on the closed session will be returned with a session closed status.
If a local Hang Up command is issued with any pending Chain Send commands, the
Hang Up execution is delayed until the Send commands are complete.

If a session ends abnormally, a "session ended abnormally" status is returned.
If the CHAIN SEND time-out expires, the session immediately ends and a
"command timed out" status is returned. Time-out values for the Send command
are associated with the session when CALL or LISTEN is issued.

Message lengths can be from 0 to 65,535 bytes in length for each of the two
buffers. The maximum number of bytes that can be sent with one Chain Send
command is 131,070.

If more than one Chain Send command is pending, the data is transmitted in a
first-in-first-out (FIFO) order.

See Also: Session support commands

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson