(When specifying the message to be passed to the application program to be activated and activating the application program)

DATA DIVISION (communication description entry) specification

CD  communication-description-name
    FOR  OUTPUT  PROGRAM
    [STATUS  KEY  IS  data-name-1]
    SYMBOLIC  TERMINAL  IS  data-name-2
    [ACTIVE {INTERVAL|TIME}  IS  data-name-9].
 
01 unique-name-1.
   02 data-name-10  PIC  9(4) COMP.
   02 data-name-11  PIC  X(2).
   02 data-name-12  PIC  X(n).
01 unique-name-2.
   02 data-name-13  PIC  X(1).

PROCEDURE DIVISION specification

SEND  communication-description-name  FROM  unique-name-1
     [WITH {ESI|EMI|unique-name-2}] .

(When reporting termination of message transfer after a request to transfer a segment other than the last segment is sent)

DATA DIVISION (communication description entry) specification

CD  communication-description-name
    FOR  OUTPUT  PROGRAM
    [STATUS  KEY  IS  data-name-1]
    SYMBOLIC  TERMINAL  IS  data-name-2.

PROCEDURE DIVISION specification

SEND  communication-description-name  WITH  EMI.

SEND enables the following CALL interface facility:

• CBLDCMCF('EXECAP ') Activate an application program.

The maximum length of a single message segment that can be sent is 32 kilobytes. Note that the actual maximum length might be smaller than this value depending on the protocol. For details, see the relevant description in the applicable OpenTP1 Protocol manual.

FOR clause

Specify OUTPUT indicating a send-only message.

STATUS KEY clause

Specify this clause to receive a status code. If this clause is omitted, a status code cannot be received.

SYMBOLIC TERMINAL clause

Specify the data item for which the logical terminal name was specified.

ACTIVE clause

This clause is specified to timer-start the application program.

INTERVAL: Interval timer start

TIME: Time point timer start

data-name-9

Interval timer start

Specify a period of time in hours, minutes, and seconds. The MHP or SPP will start the specified period of time after the application program start statement is issued. The period of time is specified in the format of HHMMSS00 where HH indicates hours, MM indicates minutes, SS indicates seconds, and 00 is fixed. The range of specifiable times is from 00000100 (start after one second) to 99595900 (start after 99 hours 59 minutes 59 seconds).

Time point timer start

Specify the time at which the MHP or SPP is to start. The time is specified in the format of HHMMSS00 where HH indicates hours, MM indicates minutes, SS indicates seconds, and 00 is fixed. The range of specifiable times is from 00000000 (start at 00:00:00) to 23595900 (start at 23:59:59) in local time.

If nothing is specified, immediate start is assumed.

Since OpenTP1 monitors timeout at fixed intervals, an error arises between the time specified for timer (for COBOL, data-name-D) of the function dc_mcf_timer_set() [CBLDCMCF('TIMERSET')] and the time that elapses before actual detection of timeout. The accuracy of time monitoring depends on the value for the time monitoring interval specified for the btim operand in the -t option of the MCF communication configuration definition mcfttim.

unique-name-1

Specify the data item indicating the send area of the message segment which is to be passed to the application program to be activated. The following figure shows the format of the segment which is passed to MHP to be activated.

WITH clause

Specify whether the segment to be passed to the application program to be activated is the last segment of a logical message.

ESI: Specify ESI for the first segment or an intermediate segment.

EMI: Specify EMI for the last segment. EMI must also be specified if the message to be passed consists of a single segment.

unique-name-2: Data item for which either of the following values was specified

'1': ESI (first or intermediate segment)

'2': EMI (last or single segment)

If this clause is omitted, EMI (last or single segment) is assumed.

1. The activation order of application programs varies depending on the mcfmuap -c order specification in the UAP common definition of the MCF manager definition.
2. If you use a single service function to update a TAM or DAM file and call the SEND statement to start an application that will reference the updated file, make sure that the application will lock the file. If the application references the file without locking the file, the data existing before the file was updated might be referenced.