1. An End-User Perspective On Using NatQuery Extraction From two Files www.natworks-inc.com T. 802 485 6112

2. Here we see the open desk top of NatQuery. In this example the user wishes to look up specific employees and see if they own specific types of vehicles. To begin a new query the user would click the New Query icon on the left side of the tool bar. This NatQuery example is being run against ADABAS on Linux in a PC network environment. The following screen shots may differ in your environment however the processing steps will be very similar.

3. The Select File window, allows the user to select the first File they wish to use to begin the extraction query. Our user has selected the File named EMPLYOEES.

4. In this window, Select Fields from FileName, the user can select the specific fields they wish to have extracted from the EMPLOYEES file.

5. We can see the user has selected three fields, the employees First Name, their last name (represented by “Name”), and the city in which they live. With the desired fields selected from the EMPLYOEES file, the user should click OK.

6. Now the user is presented with the Select File window again. Note that now there are only two Files showing, this is because NatQuery has been given “intelligence” as to file relationships. Of the three original files shown only VEHICLES has a relationship with the EMPLOYEES File. Our user will need to Select VEHICLES to complete their desired query.

7. Our user wishes to know if specific EMPLOYEES own specific VEHICLES. They would like the MAKE of the vehicles to be listed as part of the returned data, here they have double clicked on the Fieldname MAKE to add it to the group of Selected Fields to Retrieve. Clicking OK will return them to the Select File window where they will click the Continue button.

8. The Selection Logic window allows the user to apply specific query logic to the selected files. This screen shows the user selecting the Employee File to work with first.

9. Our user has applied the Selection Logic mode. The Field to apply the logic against (Where Field) and supplied an operand (is …). The user has several employees to look for so they clicked the List option (to …) and this has opened the Define List variable window. In this window the user has entered two names and is about to enter the third (Define List Variable), they will then click OK. to …

10. The first part of the users’ query has been built; In File01(the Employees file) find all employees named Anderson, Fernandez, or Evens. They will need to click the And button to supply the rest of their selection logic.

11. Here we see that And is now built in to the query and the user is about to select the Vehicles File using the Select Records From frame.

12. Our user has a list of vehicles they wish to match to the employee names. In this screen two vehicle Makes have been Listed and a third is about to be added. Note that NatQuery recognizes the second File, the VEHICLES file as File02, the Where Field as MAKE and the IS operand as EQUAL. The TO operand is about to be OK’d for the three vehicle manufacturers.

13. Our user clicked OK on the last operation and as we see here, the query includes all the information that is needed. “Do any of these specific employees own any of these specific vehicles?” The user will now click OK and proceed with the submission of the query to the server.

14. Because this is a new query the user is given the chance to use the defaults, QRY00008, or provide their own detailed name and information, “Employees with cars”. Providing detailed information now, will aid the user in quickly finding the saved query later. For more distinctive classification the user may wish to click the Favorite check box.

15. The Send to Server window allows the user to set the parameters for this query’s retrieval. On this screen the user has choosing to download their data to an Excel spreadsheet. The user may over-ride any default settings in the Send to Server window where applicable and permitted.

16. Satisfied with the Send to Server options, the user clicked OK. NatQuery now asks the user if they would like to edit the column headers for the targeted Excel spreadsheet.

17. Because this is a new session NatQuery is asking for the users FTP password. After the initial input of the Users FTP password and for as long as NatQuery remains open, this message box will not appear again. When the user ends the session, NatQuery will delete the password from its memory.

18. With the FTP password accepted NatQuery, now verifies that the user wishes to submit this query.

19. The user is being asked if they wish their generated program to be remotely executed now. Choosing No only means the remote execution is terminated, the query program is already on the server and could be executed manually. Please note that this message is unique to situations were remote execution is being used to process a users requests.

20. NatQuery informs the user what number (ID) has been given to their query as well as what Active Request “slot” number it occupies. NatQuery will use this information during the retrieval process.

21. Clicking the Check Server icon brings up the Check Server window. Note the information provided at the top of the window: User’s name, the next query submission number, and the Users statues. In the Standard Request frame we see the current status of the query process: Slot #1, QRY00008 is pending, and was submitted on 4/4/2006 at 11:34:29 am.

22. Clicking the Check Server for Update button our user is now told that query ID 978 is DONE and that there are three records available. Hovering the mouse over any part of the message will produce a more detailed report. * The Concatenate / Flatten option will effect total records written for any extract file. This option is exercised from the Send To Server window of NatQuery.

23. Our user has clicked the Retrieve Requested Data button and is now presented with a window that by default will allow them save their query in the NatQuery output directory. The user is allowed to override this default and save this query output to another directory if they desire. The default directory was set by the Administrator during the user configuration process.

24. NatQuery, about to save the text file, is now alerting the user that the query name is identical to an existing query file and do they wish to overlay it? Our user does wish to overlay it and will now click Yes. Had the user clicked No they would need to change this Queries name in order to save it.

25. This screen is telling the user that the query’s results were successfully saved as a text file.

26. The user is now being asked if they wish to continue with the loading of the data into the specified target. Our user chose MS Excel as their target to extract the data into and will click the Yes button.

27. The number of records being returned may be dependent on the user’s choice of having the data retrieved in a concatenated or flattened manner. A given query may return a different number of records to a target such as this Excel spreadsheet dependent on this choice.

28. After exiting or minimizing the Excel window the User is returned to the Check Server window where they may check on any other query submissions including any Scheduled Requests. Checking OK or Cancel here will close the Check Server Window.

29. Our user has clicked OK in the Check Server window and this has brought them back to the NatQuery desktop where their query remains open. At this point the user options include; saving and closing the query, modifying the query and saving it as a new query using “Save As” (creating a second query), modifying and then overlaying the original query, or close the query without saving it.

30. URL: www.natworks-inc.com E-Mail: info@natworks-inc.com 454 South Main Streetwww.natworks-inc.com Northfield, VT 05663 T. 802 485-6112 Simple Ideas with Enormous Potential