snalu62_receive_allocate(3) — Subroutines

Name

snalu62_receive_allocate − Waits for an allocate request from a remote transaction program. This request is for a specific transaction program on a specific local LU.

FORMAT

STATUS_RTN snalu62_receive_allocate(
     RES_ID ∗resource,
     TP_ID ∗tp_id,
     STATUS_VEC status_vec,
     char ∗local_lu_name,
     TP_NAME ∗tpn,
     ASYNC_INFO ∗wait_object,
     SRV_INFO ∗server_info
     );

Arguments

resource

A pointer to a RES_ID structure to receive an ID value assigned to the conversation by the interface. Supply this ID on all subsequent verb calls for this conversation.

tp_id

This parameter is a place holder. The functionality represented by this parameter is not implemented.

status_vec

A pointer to a STATUS_VEC array to receive the completion status information.

local_lu_name

A pointer to a null-terminated ASCII string specifying the fully-qualified network name or the locally-known alias of the local LU.

tpn

A pointer to a TP_NAME structure specifying the transaction program name. The translate field of the TP_NAME structure specifies whether the interface should translate the name.

wait_object

A pointer to an ASYNC_INFO structure specifying whether the interface should process this verb in a blocking or non-blocking manner.

server_info

A pointer to a SRV_INFO structure specifying the LU6.2 Server to utilize. Supply sufficient information to uniquely identify the LU6.2 Server. If this parameter is not specified, the interface attempts to connect to a local server with the name LU62_SRV.

Description

Use this unarchitected verb to receive inbound allocation requests for local transaction programs which have been previously defined with the snalu62_define_tp verb. After a successful return from this call, the program is in the Receive state. If the transaction program is started by the Attach Manager daemon, the program can let the Attach Manager provide defaults for the information normally specified by the server_info, local_lu_name, and tpn arguments. This allows a program to run unchanged using a variety of servers, LUs, and transaction program names. The information normally provided by the server_info argument defaults to the node name of the server that requested the Attach Manager to start the program, the transport that the server used to access the Attach Manager, and the server name of the server. The information normally provided by the local_lu_name argument defaults to the name of the LU that the server used when it queued the allocation request. The information normally provided by the tpn argument defaults to the transaction program name specified in the allocation request (stored in EBCDIC).

To use this defaulting feature, you must specify a value of null for the three arguments. Do not specify a data structure for either the server_info or tpn argument. You must use the null value for the verb argument, not for the fields within the data structure referenced by the argument.

Your transaction program cannot tell that it has been started by the Attach Manager daemon. Therefore, you must know in advance that the Attach Manager daemon will start your program. If you specify null for the three arguments and the Attach Manager daemon does not start your program, the program will fail.

Return Values

SNALU62_S_OK
normal successful completion

SNALU62_S_CONVCANC
conversation canceled

SNALU62_S_OPINCOMP
non-blocking operation not completed

SNALU62_S_OPNOTACC
non-blocking operation not accepted

SNALU62_S_PARERR
parameter error, function-name

SNALU62_S_PRGPARCHK
program parameter check