VPT_REQUEST_EXT3
Syntax
typedef struct _VPT_REQUEST_EXT3 { unsigned long struct_size; unsigned char *pucTransactionId; unsigned long ulLockCodeSelectorArr[MAX_REDUNDANT_SERVERS_IN_PT]; unsigned char *pucLockInfoArr[MAX_REDUNDANT_SERVERS_IN_PT]; unsigned long ulTimeStamp; unsigned char *pucCustomDefined; unsigned long ulCustomDefinedLength; unsigned long ulRequestArraySize; PVPT_REQUEST_LINE_EXT2 pvRequestArrayExt; } VPT_REQUEST_EXT3, *PVPT_REQUEST_EXT3;
Member | Description |
struct_size | The size of the structure. |
pucTransactionId |
The transaction ID to uniquely identify a permission ticket to be generated. |
ulLockCodeSelectorArr |
The locking criteria as an array. Each index of the ulLockCodeSelectorArr field specifies the lock selector for each of the License Manager in a redundant pool. Corresponding to the lock selector, each index of the pucLockInfoArr field specifies the locking code for each of the License Manager. The value of the macro (MAX_REDUNDANT_SERVERS_IN_PT) is 11. This corresponds to the maximum number of License Managers allowed in a redundant pool. In the case of non-redundant licenses, fill only the 0th index of both the ulLockCodeSelectorArr and pucLockInfoArr fields. |
pucLockInfoArr |
The locking code corresponding to the locking criteria. To allow revocation of redundant licenses, each index can contain the locking code of each of the License Manager. The maximum array size can be 11 as explained earlier. |
ulTimeStamp | The time stamp of the permission ticket to be generated. |
pucCustomDefined |
The vendor defined custom data contained in the permission ticket. Can contain up to 384 alpha-numeric characters. This mandatory field does not accept NULL value. |
ulCustomDefinedLength | The length of the vendor defined custom data. |
ulRequestArraySize | The number of requests.* |
pvRequestArrayExt |
A pointer to an array of structure for the requested operations and licenses. |
* Note the following recommendation when the structure is embedded in the VLSgeneratePermissionTicketExt2 API:
The number of license lines that can be embedded in the VPT_REQUEST_EXT3 structure varies—depending upon the number of License Managers targeted for PT execution:
Number of License Managers | Maximum Number of License Lines in a Single PT |
1 | 6 |
2-4 |
5 |
5-8 |
4 |
9-11 |
3 |