Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Technical solutions are described for facilitating a first computer program product to communicate with a second computer program product. The first computer program product invokes an application programming interface (API) function from an API of the second computer program product, where the first computer program product and the second computer program product use distinct programming languages. The solutions described herein initiate a record corresponding to the API function and invoke an interpreter that calls the API function in the second programming language. Upon receiving, from the interpreter, an indication that the API function has completed execution, result of the execution are obtained from the record and returned to the first computer program product.

Abstract: Embodiments relate to wrapping of a common cryptographic architecture (CCA) key token. An aspect includes wrapping, by an exporting computer, the CCA key token using a key wrapping export function, the CCA key token comprising a CCA key data section and an unencrypted control vector. Another aspect includes splitting the control vector into a first control vector portion and a second control vector portion. Another aspect includes encrypting the CCA key data section and the first control vector portion using an key encrypting key (KEK) to generate a wrapped key block. Another aspect includes binding the second control vector portion to the wrapped key block to form an associated data section, wherein the associated data section is not encrypted, and wherein the wrapped key block and the associated data section comprise a wrapped key token.

Abstract: Embodiments relate to wrapping of a common cryptographic architecture (CCA) key token. An aspect includes wrapping, by an exporting computer, the CCA key token using a key wrapping export function, the CCA key token comprising a CCA key data section and an unencrypted control vector. Another aspect includes splitting the control vector into a first control vector portion and a second control vector portion. Another aspect includes encrypting the CCA key data section and the first control vector portion using an key encrypting key (KEK) to generate a wrapped key block. Another aspect includes binding the second control vector portion to the wrapped key block to form an associated data section, wherein the associated data section is not encrypted, and wherein the wrapped key block and the associated data section comprise a wrapped key token.