Version 6.3.13 for Windows	SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT

The utility SYSEXT is used to locate and test Natural Application Programming Interfaces (APIs) contained in the current system library SYSEXT either in a local Windows environment or in a remote environment located on a Windows, a UNIX, an OpenVMS or a mainframe platform.

A Natural API is a Natural subprogram (cataloged object) that is used for accessing and possibly modifying data or performing services that are not accessible by Natural statements. Natural APIs refer to Natural, a subcomponent or a subproduct.

The SYSEXT Utility - Natural Application Programming Interfaces documentation covers the following topics:

• Prerequisite

• Introduction to SYSEXT

• Invoking and Terminating SYSEXT

• SYSEXT Tree View Items

• Performing SYSEXT Utility Functions

• Interface Versions

• Reserved Keywords

• Using a Natural API

• List of Natural APIs

Related Topics:

• Application Programming Interfaces - Natural Security documentation

• SYSAPI - APIs of Natural Add-on Products - Utilities documentation

• Natural Functions - System Functions documentation

Prerequisite

• The Enable Plug-ins option must be selected. This option is selected by default. For details, see Workspace Options in the section Setting the Options in the Using Natural Studio documentation.

Introduction to SYSEXT

For each Natural API, the utility SYSEXT provides a functional description, one example program and API-specific keywords.

The following diagram is an overview of the Natural objects and major features SYSEXT provides:

Objects Provided for Natural APIs

The types of Natural object typically provided for each Natural API are listed in the following section. Additional objects that might exist for a particular API are not covered.

All API-related objects are contained in the library SYSEXT on the system file FNAT.

In the following table, nnnn denotes the 4-digit number to identify the API as well as the corresponding example program and text object.

Caution:
Do not modify the source objects EXT-XML1 and EXT-XML2. They are required for configuring the SYSEXT utility and intended for Software AG internal use only.

Invoking and Terminating SYSEXT

This section provides instructions for invoking and terminating the SYSEXT utility.

To invoke SYSEXT

• Enter the following system command:

  SYSEXT

  Or:
  From the Tools menu, select Development Tools > Application Programming Interfaces.

  When invoking SYSEXT, the plug-in for the utility SYSEXT is activated and the SYSEXT utility window appears with the root node SYSEXT - Application Programming Interfaces as shown in the example below:

  

To restart SYSEXT

• If you want to restart SYSEXT during the current Natural session, as an alternative to the start methods mentioned above, from the toolbar, choose the following icon:

  

  This icon appears after initially invoking SYSEXT, when the plug-in for the utility SYSEXT is activated.

To terminate SYSEXT

• Choose the standard Windows close function.

SYSEXT Tree View Items

This section describes the nodes and items contained in the tree view of the SYSEXT utility window.

If you expand all tree nodes, the tree looks similar to the example below:

Each Natural API is represented by an API node that contains the example program, description and keywords that relate to this API. The API node name consists of the name of the API subprogram (USRnnnnN) and a brief description of its functional purpose. The nodes are sorted by API names.

The following items are provided in an API node:

Performing SYSEXT Utility Functions

The SYSEXT utility functions can be used to perform operations on API-specific text objects (descriptions) and example programs or find APIs relevant to a current task by specifying a keyword.

Object operations include functions such as List, Open and Execute, which correspond to the standard functions available when maintaining or executing a Natural object of the type text or program. These functions can be performed by using the context menu associated with each object. For details of these functions, refer to the relevant sections in the Using Natural Studio documentation.

The section below covers the following topics:

• Select Keyword

• List All Keywords

• Refresh

Select Keyword

This function is used to list APIs by keyword.

To list APIs by keyword

1. Select the root node SYSEXT - Application Programming Interfaces, open the context menu and choose Select Keyword or press SHIFT+K.

   The Select Keyword window appears.

2. From the drop-down list box, select a keyword as shown in the example below:

   

3. Choose the OK button.

   The root node SYSEXT - Application Programming Interfaces with Keyword appears for the selected keyword.

4. Expand the root node.

   The nodes of all APIs to which the specified keyword applies are displayed as shown in the example of keyword *LANGUAGE below:

   

5. If desired, to return to the display of all API nodes (default setting), in the Select Keyword window, select the asterisk (*).

List All Keywords

This function is used to list all keywords for the APIs available in the current system environment.

To list all API keywords

1. Select the root node SYSEXT - Application Programming Interfaces, open the context menu and choose List All Keywords or press SHIFT+A.

   The All Keyword window appears as an additional window with the root node SYSEXT - All Keywords of Application Programming Interfaces.

2. Expand the root node.

   A list of all keywords is displayed as shown in the example below:

   

Refresh

This function updates API information in the tree view using the data from the objects contained in the current library SYSEXT. The refresh is only required if an API description or a keyword was modified or if a text object was removed.

Note:
Do not modify the source objects EXT-XML1 and EXT-XML2. They are required for configuring the SYSEXT utility and intended for Software AG internal use only.

To refresh API information

1. Select the root node SYSEXT - Application Programming Interfaces, open the context menu and choose Refresh or press SHIFT+R.

   A Refresh window appears.

   If you access a remote environment on a mainframe, you must specify the parameter SORT in the map environment settings as indicated below:

   SORT=(WRKSIZE=50)

   For details on mapping a server, see Accessing a Remote Development Environment in the documentation Remote Development Using SPoD. For details on SORT, refer to the Parameter Reference of Natural for Mainframes.

2. Choose the OK button to confirm the refresh or choose Cancel to abort the operation.

Interface Versions

Interface versions can be seen as a collection of APIs with (almost) the same functionality but with differently extended parameter specifications. Thus, they cover a development cycle to be kept explicit for sake of compatibility (of later versions with earlier versions).

If an API has interface versions, they are displayed in the corresponding text object USRnnnnT. Interface versions are ordered within a list according to the version they belong to. The rightmost element belongs to the current version. This status is expressed by the reserved keyword +CURRENT-VERSION. All other elements belong to a previous version and are marked with the reserved keyword +PREVIOUS-VERSION. APIs without interface versions are called unique.

APIs with interface versions are displayed intensified on the menu.

Reserved Keywords

Reserved keywords refer to meta information on APIs, for example the Natural version in which an API has been added. Reserved keywords always start with a plus sign (+). See the table below for a description:

Using a Natural API

If you want to use a Natural API contained in the system library SYSEXT, perform one of the following steps:

• Define the system library SYSEXT in the system file FNAT as a steplib library for the user library that contains the Natural objects that use this API. Thus, no API-specific actions are required when upgrading your Natural version.

• Copy the required API to the system library SYSTEM in the system file FNAT. Thus, you only need to check a single library for APIs when upgrading your Natural version.

• Copy the required API to the system library SYSTEM in the system file FUSER (not recommended).

• Copy the required API to the user library (or one of its steplibs) in the system file FUSER which contains the Natural objects that use this API (not recommended).

An API can only be used in the Natural version with which it is delivered. It is strongly recommended to store the APIs only in the FNAT system file. This will ensure that the right version is always executed.

To make use of an interface

1. In the calling program, use the DEFINE DATA statement to specify the parameters listed in the text object USRnnnnT of that API. In the example program USRnnnnP, the parameters are defined within the DEFINE DATA LOCAL statement. Alternatively, you can specify the parameters outside the calling program in a separate LDA (Local Data Area) or PDA (Parameter Data Area), with a DEFINE DATA LOCAL USING statement referencing that data area.

2. Enter the following statement:

   CALLNAT 'USRnnnnN' parameters

   For further information, see the CALLNAT statement in the Statements documentation.

Note:
Non-standard usage is always documented in the respective text object USRnnnnT.

List of Natural APIs

The following table gives an overview of available APIs and their function.

Notes:

1. Because there can be situations where a newly added API is not yet covered by the current documentation, we recommend to rely on the list of APIs in the SYSEXT utility in cases where being up-to-date is vital.
2. For detailed information on the use of APIs that apply to Natural Remote Procedure Call (RPC), refer to section Application Programming Interfaces for Use with Natural RPC in the Natural Remote Procedure Call documentation.
3. APIs with product code PRD are listed and documented separately in the section Application Programming Interface in the administration part of the Predict documentation.

www.softwareag.com

Copyright © 1992-2012 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT