NatQuery integrates to a remote Natural / ADABAS platform through the use of automated FTP against all platforms (OS/390, VSE, UNIX or Windows) with the additional ability to achieve integration against ADABAS on Windows through automated File Copy operations. Integration to the remote server platform is achieved in a manner that completely shields the End-user from the need to have any knowledge of, or even be aware of, the connectivity method being used.
In all cases, a NatQuery request to the remote Natural / ADABAS server platform results in the generation of a dynamically customized JCL or Scripts (depending on target platform) that are designed to execute in the server batch environment. JCL / Script are built based on administratively provided templates (that are built upon NatQuery provided default templates).
Through the use of the server batch environment, and in addition to the default templates that NatQuery provides, an administrator can easily create additional customized JCL / Scripts that can perform further site specific operations upon NatQuery provided extract data. For example: Custom templates can be easily built to automatically FTP / copy extracted data to another platform, handle the automatic e-mailing of extract data, issue Remote Execution commands (such as REXEC or RSH), among other operations.
The JCL / Scripts that NatQuery generates after being moved to the server platform through FTP or File Copy operations, can then be executed in one of several ways:
To accomplish FTP connectivity, NatQuery utilizes a Microsoft-provided DLL called “wininet.dll”. This DLL is typically present on a Windows workstation as a result of being a core component of Microsoft’s Internet Explorer product. In the rare case that this DLL is not already available on a Windows workstation, this DLL can be obtained free of charge by downloading and installing Microsoft Internet Explorer.
To accomplish FTP connectivity, it is assumed that the server platform is running an FTP Service.
United We Stand