Browse Prior Art Database

Dynamically define Input/Output API parameters

IP.com Disclosure Number: IPCOM000013565D
Original Publication Date: 2001-Feb-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

Disclosed is a method by which a user can dynamically define their own application programming interface transactions and the input/output parameters used by those transactions. This method consists of 2 functions called TAPIDATA and SETAPIDATA. Tivoli Service Desk for OS/390 (TSD390) has a predefined set of transactions that enable client applications to use an application programming interface (API) to access the TSD390 database on OS/390. Examples of these transactions include Create, Update, Delete, Retrieve and Inquiry. Suppose a user wants to have a new transaction called "Close" which closes a problem record and requires user-defined input and output parameters. The user can write a REXX program that leverages TSD390 functionality to implement this transaction and use self-defining dynamic input data to the transaction. The REXX program will use GETAPIDATA to receive input parameters from a client application, and will use SETAPIDATA to send output parameters to the client application. These input/output parameters are defined by the implementer. The client application can run on distributed platforms such as Windows NT, OS/2 and AIX. An architected mechanism is provided to allow the API call to accept, recognize, and produce multiple types of data including simple strings, lists of strings, and multi-line field data. The processing to support the user written API function can be dynamically added to the system without having to change any base TSD390 configuration settings. 1

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 96% of the total text.

Page 1 of 1

Dynamically define Input/Output API parameters

    Disclosed is a method by which a user can dynamically define their own application programming interface transactions and the input/output parameters used by those transactions. This method consists of 2 functions called TAPIDATA and SETAPIDATA.

    Tivoli Service Desk for OS/390 (TSD390) has a predefined set of transactions that enable client applications to use an application programming interface (API) to access the TSD390 database on OS/390. Examples of these transactions include Create, Update, Delete, Retrieve and Inquiry. Suppose a user wants to have a new transaction called "Close" which closes a problem record and requires user-defined input and output parameters. The user can write a REXX program that leverages TSD390 functionality to implement this transaction and use self-defining dynamic input data to the transaction. The REXX program will use GETAPIDATA to receive input parameters from a client application, and will use SETAPIDATA to send output parameters to the client application. These input/output parameters are defined by the implementer. The client application can run on distributed platforms such as Windows NT, OS/2 and AIX. An architected mechanism is provided to allow the API call to accept, recognize, and produce multiple types of data including simple strings, lists of strings, and multi-line field data.

    The processing to support the user written API function can be dynamically added to the syste...