Previous Topic: &SNAMS REGISTER

Next Topic: &SOCKET ACCEPT


&SNAMS SEND

The &SNAMS SEND verb sends a formatted MDS-MU request, reply, or error to a nominated target application or focal point. In addition to the application data GDS variable, the following MDS-MU Routing Information GDS variable (X'1311') contents must be present:

If the MDS-MU is destined for a focal point, destination values in the MDS-MU header are set to those destinations of the active focal point for the supplied category.

If the MDS_MU is flagged as the FIRST message, the Agent Unit of Work Correlator GDS variable (X'1549') is not required (SNAMS generates one for it). Otherwise, Agent Unit of Work Correlator is mandatory (that is, for MDS replies).

This verb has the following format:

&SNAMS SEND MU=mdo [ CATEGORY=fpcategory ]

Operands:

MU=mdo

Specifies the name of the MDO that contains a formatted MDS-MU to send. The value is a stem name or a compound MDO name.

CATEGORY=fpcategory

(Optional) If specified, must be one through eight characters long-it is a hexadecimal quoted string. The MDS-MU is sent to the active focal point application for this category, with respect to the original application.

The active focal point is determined as follows:

Return Codes:

&RETCODE

&ZFDBK

Meaning

0

0

Send request accepted

4

0

Focal point is unavailable

8

0

MDS-MU header format exception

 

1

MDS routing exception

 

2

Request rejected by internal application

 

3

Invalid origin node

For &RETCODE 0, if it is an MDS-MU request that expects one or more MDS-MU replies (that is, it is not flagged as the LAST message), the &ZSNAMID variable contains a non-zero request identifier, which is used on subsequent &SNAMS RECEIVE verbs for correlating replies.

For &RETCODE 8, the &SYSMSG variable contains an error message. A sense code is also returned for &ZFDBK 0 and 1.

Notes:

Although SNAMS can accept the SEND request, it does not guarantee delivery of the MDS-MU to a remote destination. If delivery failed for one reason or another, an MDS error message is returned.

MDS replies, if any, are delivered to the initiator of the request and not the registered receiver of the destination application. Thus, the origin application of MDS requests need not be registered with SNAMS. MDS errors however, are delivered to the registered receiver if it does not correlate to an outstanding request. Thus, if the origin application is not registered, errors are lost.