• Aucun résultat trouvé

GET ALLOCATE

Dans le document Programming Guide (Page 115-123)

Requests APPCjPC to dequeue the next queued incoming ALLOCATE if you have specified synchronous

management of incoming ALLOCATEs.

Alternatively, the application subsystem can test for queued ALLOCATEs, without dequeuing one.

In both cases, APPCjPC supplies a return code of OK if the queue holds an incoming ALLOCATE, and a return code of UNSUCCESSFUL if the queue does not hold an incoming ALLOCATE.

The application subsystem should issue the

GET_ALLOCATE verb only if it specified synchronous management of incoming ALLOCATEs

(QUEUE_ALLOCATES=YES in the ATTACH_LU verb).

SUQQlied Parameters:

GET_ALLOCATE LU -ID (variable) TYPE (DEQUEUE)

(TEST)

Returned Parameters:

RETURN_CODE (variable) CREATE_TP_PTR (variable)

i

Supplied Parameters:

LU_ID specifies the identifier for the local LU that the application subsystem wants to access. APPCjPC returns this value when the application subsystem identifies and initializes the LU by issuing the ATTACH_LU verb. For more information, see "ATTACH_LU" on page 5-7.

Returned Parameters:

RETURN_CODE indicates the result of verb execution.

See Appendix C, "Verb Return Codes," for more information on return codes. The GET_ALLOCATE return codes are as follows:

• BAD_LU_ID: APPCjPC does not recognize the specified LU_ID.

• GET_ALLOC_BAD_TYPE: APPCjPC does not recognize the parameter specified in the TYPE field.

• UNSUCCESSFUL: The LU is not currently holding any incoming ALLOCATEs in its queue.

For detailed information on the following return codes, see "Understanding Control Verb Return Codes" on page 5-3 and Appendix C, "Verb Return Codes."

• APPC_ABENDED

• APPC_BUSY

• APPC_DISABLED

• OK.

CREATE_TP _PTR specifies a pointer to a CREATE_TP record identical in format to the record APPCjPC passes to the user exit for incoming ALLOCATEs when you use asynchronous management of incoming allocates. This record contains the TP _ID and CONV _ID of the new transaction program and the new conversation.

CREATE_TP _PTR is set only if TYPE = DEQUEUE and RETURN_CODE=OK. For more information see

"CREATE_TP" on page 5-66.

TP ENDED

Notifies APPCjPC of the end of the identified transaction program. APPC JPC responds by performing a

DEALLOCATE (TYPE=ABEND_PROG) to free only conversations associated with that program. For more information, see "DEALLOCATE" on page 7-32.

Supplied Parameters:

TP -ENDED TP - ID (variable) Returned Parameters:

RETURN -CODE (variable)

;

Supplied Parameters:

TP _ID specifies the identifier for the transaction program that you want to terminate. APPCjPC returns this value when the application subsystem initiates the program with the TP _STARTED verb (see "TP _STARTED" on

page 5-58) or with the CREATE_TP verb (see

"CREATE_TP" on page 5-66).

Returned Parameters:

RETURN_CODE indicates whether APPCjPC accepts the TP _ENDED request. See Appendix C, "Verb Return Codes," for more information on return codes. The

TP _ENDED return codes are as follows:

• BAD_TP_ID: APPCjPC does not recognize the supplied TP _ID as an assigned transaction program ID.

For detailed information on the following return codes, see "Understanding Control Verb Return Codes" on

• INCOMPLETE (possible only if all conversations are not deallocated)

• OK.

Note:

After the application subsystem issues TP _ENDED, the TP _ID is no longer a legal value for any basic or mapped conversation verb.

TP STARTED

Notifies APPCjPC that the application subsystem has requested resources for a transaction program initiated as a result of a local command, rather than initiated from an incoming ALLOCATE. APPCjPC responds by generating a transaction program identifier (TP _ID) and returning it to the application subsystem. The initiated transaction program must use this TP _ID with all later conversation verbs.

SUQQlied Parameters:

TP -STARTED LU - 1D (variable) Returned Parameters:

TP - 1D (variable)

RETURN_CODE (variable)

i

Supplied Parameters:

L U _ID specifies the identifier for the local L U under which the application subsystem wants to initiate this transaction program. APPCjPC returns this value when the application subsystem identifies and initializes the LU by issuing the ATTACH_LU verb; see "ATTACH_LU" on page 5-7.

Returned Parameters:

TP _ID specifies the identifier for this transaction

program. Similarly, APPCjPC also provides a TP _ID for a transaction program started by an incoming

ALLOCATE.

RETURN_CODE indicates whether APPCjPC accepts the TP _STARTED request. See Appendix C, "Verb

• TOO_MANY_TPS: APPC/PC is already running the maximum number of transaction programs that can be run concurrently on this LU (as defined with the MAX_TPS parameter in the ATTACH_LU verb).

For detailed information on the following return codes, see "Understanding Control Verb Return Codes" on page 5-3 and Appendix C, "Verb Return Codes."

• APPC_ABENDED

• APPC_BUSY

• APPC_DISABLED

• OK.

Note:

If an incoming ALLOCATE is in the process of being rejected, it counts against the MAX_TPS parameter until rej ection is complete. Therefore, for the

TOO_MANY_TPS return code, you may wish to retry the TP_STARTED verb.

TP VALID

Notifies APPCjPC of the status of an incoming

ALLOCATE that the application subsystem has dequeued with the GET_ALLOCATE verb. A valid status indicates that the application subsystem has validated and loaded the new transaction program. The application subsystem must issue a TP _ V ALID verb before issuing any

conversation verbs for the new transaction program.

Supplied Parameters:

TP_VALID TP - ID (variable)

CREATE -TP -PTR (variable) Returned Parameters:

RETURN_CODE (variable)

;

Supplied Parameters:

TP _ID specifies the identifier for this transaction program. APPC fPC returns this value in the

CREATE_TP structure when the application subsystem uses the GET_ALLOCATE verb. The transaction program must use this identifier when it issues any conversation verbs for APPCjPC to perform.

CREATE_TP_PTR specifies the pointer to the CREATE_TP structure that APPCjPC returned in response to the previous GET_ALLOCATE verb. The application subsystem should specify whether the TP name is valid or invalid in the SENSE CODE field of the CREATE_TP record.

For a list of the valid sense codes, see "CREATE_TP" on page 5-66.

Returned Parameters:

RETURN_CODE indicates whether APPCjPC accepts the TP _ V ALID request. See Appendix C, "Verb Return Codes," for more information on return codes. The TP _ V ALID return codes are as follows:

• BAD_TP _ID: APPCjPC does not recognize the TP _ID specified with the TP _ V ALID verb.

• BAD CONV _ID: APPCjPC does not recognize the CONV _ID in the CREATE_TP record.

• BAD_STATE: TP _ VALID does not follow a GET_ALLOCATE.

For detailed information on the following return codes, see "Understanding Control Verb Return Codes" on page 5-3 and Appendix C, "Verb Return Codes."

• APPC_ABENDED

• APPC_BUSY

• APPC_DISABLED

• INCOMPLETE (possible only if the incoming ALLOCATE is rejected with a non-O sense code)

• OK.

Note:

APPCjPC, not the transaction program, manages the storage for the CREATE_ TP structure; the transaction program should not allocate or free storage for this record.

APPC/PC to Application

Dans le document Programming Guide (Page 115-123)

Documents relatifs