DOCUMENTATION UPDATES

Transcription

1 CORVU DOCUMENTATION UPDATES Date Description Where Changed 3/25/99 Added a section to explain how to download the Knowledge Library from the Internet. Installation Chapter in the Downloading the CorVu/P21 Knowledge Library and Sample Queries section (page 20)

2 CORVU,QVWDOODWLRQ,QVWUXFWLRQV 8SGDWLQJ&RU9X &RPPRQ3URFHGXUHV.QRZOHGJH/LEUDU\,QIRUPDWLRQ 7URXEOHVKRRWLQJ ii

3 The documentation in this publication is provided pursuant to a Sales and Licensing Contract for the Prophet 21 System entered into by and between Prophet 21 and the Purchaser to whom this documentation is provided ( License Agreement ). In addition, the licensed software to which this documentation refers may be supported in accordance with a customer support agreement by and between the same parties ( Support Agreement ). All warranties, conditions of use, transfer restrictions, and other provisions in the License Agreement or Support Agreement which are applicable to Licensed Software, are applicable to this publication. In addition, this publication may include inadvertent technical inaccuracies or typographical errors for which Prophet 21 is not responsible. Changes may be periodically made to this publication; these changes will be incorporated in new editions of the publication. Any questions about the material contained in the publication should be addressed to the Prophet 21 Customer Support Department at ITS-PR21. Improvements and/or changes to the Licensed Software described in this publication may be made by Prophet 21 at any time without notice. DOCUMENTATION CONVENTIONS The eyeglass symbol ($) indicates a field on which you can browse. The star ( ) indicates the default for a field. To allow for the widest possible parameters when printing a report or performing a function, accept the defaults for all of the parameter fields. To accept the defaults, either escape through all the fields, or press [Enter] without specifying any values. Generally, samples in the documentation are shown using the default values. Start and End parameters define the limits to a range of information you will print on a report. If information does not appear on a report, it may be because the information was excluded from the Start, End range. For a detailed explanation on how maintenance screens function, refer to the Tour Guide manual. Use the Documentation Index to find which manual describes a specific module, job, or function. 5/25/99 Prophet 21 Acclaim Version 10 The Prophet 21 System and Prophet 21 Acclaim are registered trademarks, and Prophet 21 and ScratchPad are trademarks of Prophet 21. All other trademarks and registered trademarks are the property of their respective companies. iii

4 Table of Contents 1 INTRODUCTION 6 2 INSTALLATION 7 Installation Summary 7 Minimum PC Requirements 8 Installing the Client Software 8 Installing the CorVu Server 12 Configuring the CorVu Client to Access the Server 12 Obtain Your RS/6000 s Hostname 12 Obtain Your RS/6000 s IP Address 13 Obtain Your CorVu Server Port Number 13 Configure the CorVu Software to Access the RS/ Configuring CorVu to Access Prophet Setting up the Secure Server User ID 17 Downloading the CorVu / P21 Knowledge Library and Sample Queries 20 Updating the Knowledge Library 22 Building the Link to Item Status Table 22 Verifying Space Requirements 23 Running the Hidden Option 23 Logging Into CorVu 24 3 UPDATING CORVU 25 4 SUPPORT 28 5 COMMON PROCEDURES 29 Building the Link to Item Status Table 29 Terminating a Query Locked during Processing 29 iv

5 Saving CorVu Queries to Disk 30 Performing Updates using Patch Disks 30 Checking Version Level 31 6 KNOWLEDGE LIBRARY 32 Why Columns May Not Produce Output 32 Viewing Column Information 33 The FRECNO Column 33 Column Descriptions using Description and Disp 34 Tables By Code vs. Tables By Key 35 Why Fields Do or Do Not Link 36 Custom Tables 36 Using the Link to Item Status Table 37 Hiding Specific Columns 39 7 TROUBLESHOOTING 41 8 MISCELLANEOUS 45 Files and Maintenance (PC Side) 45 Distributing CorVu Data Files 46 Server Configuration File 47 Bases 47 Limits 47 Messages 48 User Preferences 49 CorVu User Manuals 51 SUPPORT FORM 52 v

6 1 INTRODUCTION The CorVu report writer is used to view information from all Prophet 21 databases with a simple, graphical interface. CorVu automates report structure and layout, and it allows you to include calculated fields and graphics. Designed to augment the user manual provided by CorVu, this manual contains information and tips on using Prophet 21 and CorVu, not covered in the CorVu User Manual. To best use this manual, you should first have a good understanding of the information supplied in the CorVu User Manual. Information specific to the Prophet 21 Acclaim system databases is found in this supplemental manual. The following sections describe installation and update instructions, support procedures, and different topics that will help you use and understand the knowledge library. Prophet 21 has also written several CorVu queries. To access these predefined queries and to get more information on executing them, visit our web site at For more information on this procedure, refer to page 20. 6

7 2 INSTALLATION INSTALLATION SUMMARY Several components need to be installed to run CorVu. The following is a summary of the tasks that must be performed to fully install CorVu. 1. You must have Acclaim version C or higher installed on your system. The CorVu server is automatically installed with these Acclaim installations. 2. The PC that will run CorVu must have a working network connection to the RS/ Install the PC/client software by following the instructions starting on page 8. This will guide you through installing and configuring the CorVu software on a PC and installing the CorVu patch disks, if you received them. For more information on patch disks, refer to page Configure the CorVu PC/client software to access the RS/6000. For CorVu to access the Prophet 21 database, it must be able to connect to the RS/6000 via a network connection. The section on page 12 will show you how to configure the PC/client software to connect to the RS/6000 via network. 5. Configure the PC/client CorVu software to access the Prophet 21 database by following the instructions on page Download the Prophet 21 knowledge library and sample queries. For more information on this procedure, refer to page 20. Before installing CorVu, verify that you received the following materials from Prophet 21 and CorVu: Materials from Prophet 21 Materials from CorVu North America This CorVu manual A CD-ROM that contains the CorVu software user manuals and other programs. Refer to the section CorVu User Manuals in the chapter Miscellaneous for instructions on viewing and printing the manuals. Note: You may have also received one of more patch disks from CorVu. As corrections and enhancements are made to CorVu, patch disks are sent. Patch disks may come on diskette or CD-ROM. Insert them and run Setup for installation. For further information on patch disks, refer to page 30 or contact CorVu Support at

8 ,167$//$7,21 In addition, if you need to upgrade to Acclaim C or higher, you will have also received an Acclaim update tape. MINIMUM PC REQUIREMENTS Pentium 133MHz 16 MB RAM 30 MB of free hard disk space CD-ROM drive Network (Ethernet) connection to RS/6000. You must have a network (TCPIP) connection installed and tested between the PC that will be running CorVu and the RS/6000. CorVu will not work without this connection. Microsoft Windows 95 or Microsoft Windows NT 3.51 or later INSTALLING THE CLIENT SOFTWARE 1. Close all applications except Windows itself. Make sure no applications are minimized to the task bar. 2. Insert the CorVu CD-ROM into the CD-ROM drive. The setup program should start automatically on Windows 95 or Windows NT. 3. Click the Setup CorVu button. Click the Setup CorVu button. 8

9 ,167$//$7,21 4. The setup program will prompt you for the components of CorVu you want to install. If you are installing CorVu on a network disk, you should include the Network Installation Files. This will allow you to set up additional workstations without needing the CorVu CD-ROM. To save disk space, select and/or clear the relevant checkboxes. 9

10 ,167$//$7,21 Tip! Approximate Disk Space Requirements are: Windows 95/NT Version Windows 3.1 Version 8.25 MB 7.20 MB Network Installation Files 1.20 MB Database Connectivity Help Files Mandatory Files Menu Buttons Full Installation 6.00 MB 2.20 MB 1.20 MB 0.50 MB MB 5. Click Continue. The system will begin the installation process. 6. When the installation process is complete, the system displays the Choose Program Manager Group screen. Click OK to accept the default program manager group name, CorVu. 10

11 ,167$//$7,21 7. When the application has been installed, the setup program displays the CorVu Administrator screen: 8. Select the Enterprise Licenses tab. Enter the licensee and the licensing information for the components that you purchased. The fields of the components you have not purchased should be left blank. For example, if you only purchased Graphical Analysis and Report Writer, enter the licensing information in these fields, and leave the rest of the component fields on the CorVu Administrator screen blank. Note: In the Licensee field, enter the name on the CorVu License Certificate to which your version of CorVu is issued. 11

12 ,167$//$7,21 9. Click OK. If the installation process was successful, the Installation Status screen appears. Click Yes to exit this screen. Note: If the Installation Status screen does not appear after you install CorVu, contact CorVu technical support at If the installation completed successfully, a program group will be created for CorVu. 11. Close the previous window. On the CorVu CD-ROM screen, click Exit. 12. If you have patch disks, install them now. For further instructions on this installation process, see page 30. INSTALLING THE CORVU SERVER The CorVu server is automatically installed as part of the install and/or update procedure of Acclaim version C or higher. No instructions or further processing is needed to install the CorVu server. CONFIGURING THE CORVU CLIENT TO ACCESS THE SERVER Before you can configure the CorVu client to access the server, you must identify your RS/6000 s hostname, IP address, and the CorVu server port number. This information will be needed in a later step. OBTAIN YOUR RS/6000 S HOSTNAME 1. Log into the system as root and get to a pound (#) sign prompt. 12

13 ,167$//$7,21 2. To see what the hostname is, type: hostname [Enter]. The system will report your hostname. If your system does not report a hostname, contact the Prophet 21 Technical Support Department. In the following section, be sure that the hostname is entered exactly as it is displayed on your screen. OBTAIN YOUR RS/6000 S IP ADDRESS 1. Log into the system as root and get to a pound (#) sign. 2. Type: ping <hostname> [Enter]. Replace <hostname> with the hostname of your RS/6000. For example, if the hostname of the RS/6000 is abcelec, type: ping abcelec [Enter]. The output from this command would look like: PING abcelec: ( ): 56 data bytes 64 bytes from : icmp_seq=0 ttl=255 time=16 ms 64 bytes from : icmp_seq=1 ttl=255 time=1 ms 64 bytes from : icmp_seq=2 ttl=255 time=1 ms 64 bytes from : icmp_seq=3 ttl=255 time=1 ms Your IP address will be listed in the output of this command. In the previous example, the IP address of the RS/6000 is To exit this screen, press [Ctrl][C]. OBTAIN YOUR CORVU SERVER PORT NUMBER 1. Log into the system as root to access the pound (#) sign. 2. At the root prompt, type the following: tail [Space Bar] / etc / services [Enter]. 3. The port number for each unit appears on the line with the CorVu server number and server ID, which is represented by cv-yy. The number following yy is the number of your unit. The port number appears before /tcp on this line. 13

14 ,167$//$7,21 The server number and ID appear. The port numbers appear next to the server number and ID. For example, on the previous screen, the port number for unit 0 is 7000, and the port number for unit 1 is Note: In the previous example, the user had two units unit 0 and unit 1. If you have multiple units, they will be listed accordingly. If you have only one unit, only one line with cv-yy with the unit number will display. CONFIGURE THE CORVU SOFTWARE TO ACCESS THE RS/6000 To connect to the Prophet 21 database, you need to have a working network (TCPIP) connection established and tested. If you do not, CorVu will not run. For assistance in setting up a network connection between the PC using CorVu and the RS/6000, contact your network provider. The following steps will configure the CorVu software to access the RS/ Start the CorVu Administrator by selecting Start/Programs/CorVu. Then choose CorVu Administrator or select the icon from the CorVu program group. You can choose CorVu Administrator by selecting Start/Programs/C orvu/corvu Administrator. 14

15 ,167$//$7,21 You can also select the icon from the CorVu program group. 2. On the CorVu Administrator screen, verify that the CorVu Setup Server tab is selected. Click New to define a connection to a database. 3. On the New Server screen, select TCP Connected Server in the Available Server Type box. Click OK. 15

16 ,167$//$7,21 4. From the drop-down list of the Network Type field on the TCP Host Parameters screen, select Windows Sockets 1.1 (32Bit). Note: If you are using any Windows Sockets compliant network, you should select Windows Sockets. For assistance with your network software or connection, contact your network provider. 5. On the TCP Host Parameters screen, complete the parameters. For more information on the fields on this screen, refer to the page numbers indicated below. Field Page Number Server Name Enter your RS/6000 s host name page 12 Network Type Page 16 Host IP Address Page 13 Port Number Page After you specify the correct values for your RS/6000, click OK to continue. 16

17 ,167$//$7,21 7. The system will prompt you to create the knowledge library directory: C:\CORVU\DICT. Select Yes to accept this prompt. 8. On the CorVu Administrator screen, the server name appears. Click OK. CONFIGURING CORVU TO ACCESS PROPHET 21 CorVu supports two methods of accessing a database: secure servers and open servers. The version of the CorVu Server customized for Prophet 21 supports only secure servers. This means that you must have a user called * with a password of * in the CorVu user base. This will allow your users to log into CorVu and into the Prophet 21 database using their own AIX user ID and password. To access the database, you must use a valid AIX user ID and password. SETTING UP THE SECURE SERVER USER ID To set up the secure server user ID and password in the CorVu client, use the following instructions. 1. Start the CorVu client application by choosing Start\Programs\CorVu\CorVu. Or, select the CorVu icon from within the CorVu program group. 17

18 ,167$//$7,21 2. Enter the user name admin and password -corvu-. Note: The dashes are part of the password and must be entered. 3. Verify that the Connect to Server box is cleared, or not checked. Click OK. 4. The main CorVu menu appears. From the Users menu, select Modify User Base. Select Modify User Base. 18

19 ,167$//$7,21 5. On the following screen, select New User. Select New User. 6. In the Name for New User box, type * (an asterisk). 7. Click OK. 8. In Access List, click 1. 19

20 ,167$//$7,21 9. Click Change Password. 10. On the Changing Password screen, enter * (an asterisk) as the password. You must enter the * in Password 1 and Password Click OK. 12. At the Modify Users screen, click All Done. From the CorVu main menu, click File then Exit. DOWNLOADING THE CORVU / P21 KNOWLEDGE LIBRARY AND SAMPLE QUERIES Periodically, you can download CorVu/P21 knowledge library updates or sample queries. The knowledge library updates keep your CorVu application current with the most up-to-date features. You can run the predefined queries to access information on your system, or you can use them as samples to create other CorVu queries. Caution! We recommend that you backup your current knowledge library before you perform the update. If you have customized your knowledge library or any of its parameters, this update will overwrite those changes. If you perform the update, you will need to reenter your work to customize your knowledge library. If you have any questions on the CorVu/P21 knowledge library or sample queries, call Prophet 21 Software Support for assistance. To download the knowledge library or sample queries, use the following steps: 1. Using any Internet browser, access Prophet 21 s web site at 2. Click the Customer Entrance tab at the top of the home page. 3. Click the Customers May Enter Here link located underneath Customer Support. 4. If the Enter Network Password screen appears, enter your user name and password. Note: If the previous screen does not appear, the Customer Support screen should appear. If the Customer Support screen does not appear, notify Prophet 21 by sending an to the following address: Webmaster@p21.com, or call Internet Services at On the Customer Support screen, click the Acclaim/XL link. 6. On the Acclaim/XL Support screen, click the File Downloads button on the left side of the page. 7. In the File Downloads section, click the CorVu Downloads link. 20

21 ,167$//$7,21 8. The CorVu Downloads screen appears. If you want to download the CorVu /P21 Knowledge Library, select the Corvudic.exe file. If you want to download the sample queries, select the Corvusam.exe file. 9. You have the option to either open the file immediately or save it to a disk. When you choose to open the file, security screens appear. Click the option to continue and to install the files on your system. If you choose to save the file to a disk, select the directory in which you want to save it. Using My Computer or Windows Explorer, access the directory where you saved the file, and double-click it. 10. The WinZip Self-Extractor screen appears, similar to the following sample: Note: The directory that appears in the Unzip to Folder box defaults to your temp directory. This varies from PC to PC. 11. Change the directory in the Unzip to Folder box to wherever your knowledge library or queries are stored. In most cases, the knowledge library is stored in C:\Corvu\Dict, and the CorVu queries are stored in C:\Corvu\Data. Your screen should look similar to the following: Change this field to the directory where your knowledge library or CorVu queries exist. Tip! When you access the WinZip Self Extractor screen, the Overwrite Files Without Prompting box is selected. When this option is enabled, the system automatically overwrites all files, without prompting you beforehand. When this option is disabled, the system prompts you to overwrite each file individually. To disable this option, clear the check box. 12. On the WinZip Self-Extractor screen, click Unzip. 21

22 ,167$//$7, A message indicating that the files are unzipped successfully appears, similar to the following: 14. Click OK. Note: If this message does not appear, notify Prophet 21 by sending an to the following address: Webmaster@p21.com, or call Internet Services at On the WinZip Self-Extractor screen, click Close. 16. If you chose to save the file, exit My Computer or Windows Explorer. If you chose to open the file, proceed to the next step. 17. Execute CorVu and immediately test the knowledge library or the sample queries. A common way to test the knowledge library is to run a query using the new tables or fields. UPDATING THE KNOWLEDGE LIBRARY Several times a year, an updated knowledge library version will be available. You can download it from the Prophet 21 web site at or you can fax a request to for the knowledge library on diskette from the Software Distribution Group in the Programming Department. &DXWLRQ If you have customized your knowledge library or any of its parameters, the updates will overwrite those changes. When you perform the update, you will need to re-enter the work you have already done to customize the knowledge library. For further information on the CorVu/P21 knowledge library, call Software Support at Prophet 21 for assistance. BUILDING THE LINK TO ITEM STATUS TABLE When you install CorVu for the first time, you need to run a hidden option that builds the Link to Item Status table in the Accounting database. This table links your items to their item status information at each location, which includes data on free stock quantity and sold quantities for the month and year. You also need to run this hidden option periodically, since the Link to Item Status table itself will not track any changes to your item database. Over time, as your item database changes, the table will become outdated. Running this hidden option on a regular basis ensures that CorVu will display valid item status information. The addition or deletion of a location will not automatically be reflected in the Link to Item Status table. The hidden option must be run in this situation, so that the table is rebuilt to include the current location information. 22

23 ,167$//$7,21 VERIFYING SPACE REQUIREMENTS The Link to Item Status table can take up a significant amount of space on your hard drive, since it contains an entry for every item at every stocking location. Before running the hidden option, you need to verify that you have enough space in your system to hold the table. If the creation or rebuilding of the Link to Item Status table fills the db filesystem on your hard disk, you will not only have problems with the CorVu link to item status information, but also be unable to perform transactions in the accounting modules. In this instance, you must expand the db file system. Use the following steps to verify space requirements: 1. At the AIX prompt, type: Note: If your system consists of multiple units, you need to specify which p21pro directory to access, such as p21pro or p21pro1. For example, running the above command for a Unit #1 system would be entered as: 2. The following screen appears: View the %Used column. If this value is under 80%, you will be able to run the hidden option to create or rebuild the table. If the value is 80% or higher, your file system may need to be expanded. If you have any questions on expanding the file system, call Prophet 21 Technical Support for assistance. The file system can be expanded while your system is up and running. RUNNING THE HIDDEN OPTION The hidden option is (( [two forward parentheses] and can be run from the Hidden Option menu located under Utilities on the System Administration menu. If you are not familiar with running hidden options, call the System Administration Team in Software Support. When the hidden option is performed, the following screen appears: Enter Yes to build the Link to Item Status table. An asterisk moves across the following screen, indicating that the table is being built: When the build is complete, the following screen appears: 23

24 ,167$//$7,21 For more information on using the Link to Item Status table, refer to the section, Using the Link to Item Status Table on page 37. LOGGING INTO CORVU To successfully log into the Prophet 21 database through CorVu, you must have a working network connection to the RS/6000, and have a valid AIX user ID and password. 1. Start the CorVu client on the PC by selecting Start/Programs/CorVu. Then click CorVu. You should see the CorVu Login screen: 2. In the User Name field, enter a valid AIX user ID. This must be entered exactly as it would be typed to log into AIX. 3. In the Password field, specify the AIX password for this AIX user ID. This also must be entered exactly as it would be to log into AIX. 4. Highlight the RS/6000 s hostname in the Server box. Make sure Connect to Server is checked. 5. Click OK. 6. After a brief pause, you should be placed into the main screen of CorVu. If you receive any errors, recheck all your settings. If you still have problems, contact CorVu directly at

25 3 UPDATING CORVU &DXWLRQ Before updating your current version of CorVu to version 4.0, make sure you have a backup copy of all of your current files (e.g., queries and the knowledge library). After you have created a backup copy of all of your files, complete the following steps to update to CorVu 4.0: 1. Close all applications except Windows itself. Make sure no applications are minimized to the task bar. 2. Insert CorVu CD-ROM into the CD-ROM drive. The setup program will start automatically. 3. Click the Setup CorVu button. Click the Setup CorVu button. 4. The setup program will prompt you for the components of CorVu 4.0 you want to install. 25

26 83'$7,1*&2598 If you are updating CorVu on a network disk, you should include the Network Installation Files. This will allow you to set up additional workstations without needing the CorVu CD-ROM. To save disk space, select and/or clear the relevant checkboxes. Tip! Approximate Disk Space Requirements are: Windows 95/NT Version Windows 3.1 Version 8.25 MB 7.20 MB Network Installation Files 1.20 MB Database Connectivity Help Files Mandatory Files Menu Buttons Full Installation 6.00 MB 2.20 MB 1.20 MB 0.50 MB MB 5. Click Continue. The system will begin the update process. 26

27 83'$7,1*& When the update process is complete, the system displays the Choose Program Manager Group screen. Click OK to accept the default program manager group name. Note: If you named the program manager group a name other than CorVu, select that name on the previous screen and click OK. 7. The CorVu Administrator screen appears. Verify that your server list is accurate, and click OK. 8. If the update process was successful, the Installation Status screen appears. Click Yes to exit this screen. Note: If the Installation Status screen does not appear after you install CorVu, contact CorVu Technical Support at If the CorVu update completed successfully, a program group will be created for CorVu. A program group is created for CorVu. 10. Close the previous window and the CorVu CD-ROM installation screens. 27

28 4 SUPPORT Support for CorVu is provided by CorVu directly. If you have any problems or questions when installing, configuring, or using CorVu, please call CorVu at Their hours are 8:00am - 5:00pm, Central time, Monday through Friday. The knowledge library, which holds Prophet 21 database information, is supported by Prophet 21 s Software Support Department. If you have any problems or questions on the output of a query, such as wrong data or no data appearing, call Prophet 21 for assistance. Before you call for support, keep the following in mind: Ensure that you have read the relevant sections of the installation chapter, on page 7, in their entirety. Many questions can be answered by reading forward to the next step in the installation manual, or by carefully re-reading the current or previous steps. Many common problems are listed in Chapter 7, Troubleshooting. Some problems listed there have similar symptoms. Always have this manual and the CorVu User Manual with you. CorVu s support staff will direct you to the relevant parts of the manuals, as needed. 28

29 5 COMMON PROCEDURES The following general procedures are described in this chapter: Building the Link to Item Status Table Terminating a Query Locked During Processing Saving CorVu Queries to Disk Performing Updated Using Patch Disks BUILDING THE LINK TO ITEM STATUS TABLE When you installed CorVu for the first time, you ran a hidden option that built the Link to Item Status table in the Accounting database. This table links your items to their item status information at each location, which includes data on free stock quantity and sold quantities for the month and year. Because the Link to Item Status table itself will not track any changes to your item database, you also need to run this hidden option periodically. As your item database changes, the table will become outdated. Running this hidden option on a regular basis ensures that CorVu will be displaying valid item status information. The addition or deletion of a location will not automatically be reflected in the Link to Item Status Table. Therefore, the hidden option must be run so that the table is rebuilt to include the current location information. For more information on running this hidden option, refer to page 22. TERMINATING A QUERY LOCKED DURING PROCESSING There may be times when a query becomes locked during processing. This can happen when a selected field cannot produce output. Closing the window that is running the query is not recommended, since the process is left running. As the number of abandoned processes grows, the CorVu server responds more and more slowly. The proper way to terminate a locked query is by stopping the CorVu server. To do this, perform the following steps: 1. Click Start. 2. Select Programs and select CorVu. 29

30 & &('85(6 3. There are three choices under the CorVu option. Select the option for Stop CorVu Server (32 Bit). These actions stop the CorVu server and erase all abandoned processes running on your IBM RS/6000 system. If there were many abandoned processes on your system, they are now removed and the speed of the server returns to normal. To reenter CorVu, start the program in the normal way. SAVING CORVU QUERIES TO DISK Having the ability to save CorVu queries to disk provides many benefits, including: Giving the query to a CorVu user who is not on your network. The query could then be imported into the stand-alone version of CorVu, and the same report could be generated. Having a good backup of your CorVu queries, which alleviates the stress of recreating them if future problems arise. Freeing up hard drive space. To save the queries to a disk, perform the following steps. 1. Insert a disk into your drive. 2. With all active windows minimized, double-click the My Computer icon located on the PC s desktop. 3. Select the icon that represents your hard drive, usually identified as the C: drive. 4. Find the CorVu folder (directory) and double-click. 5. Find the Data folder and double-click. This folder will include a list of the CorVu queries that you saved. 6. To save multiple files to the disk, highlight the first query to be saved by clicking its name. Hold the [Ctrl] key down while using the down arrow key to highlight all the files you wish to save to disk. 7. While the files are selected and the cursor is positioned on one of these files, press the right mouse button to display the context menu. Select the Send to choice. Several options are displayed; choose the correct option, depending on your system setup. Note: Informational reports generated by the queries, known as result sets, are held in the Tables folder. PERFORMING UPDATES USING PATCH DISKS Patch disks are sent to update CorVu for revisions and to provide additional programming features. In most cases, a set of two disks needs to be installed. You may receive this information on a CD-ROM. The update instructions are similar to the installation instructions and screens found in the section entitled, Installing the Client Software on page 8. Perform the following steps to upgrade your system: 1. Close all applications except for Windows itself. There should be no applications that are open and minimized. 2. Insert CorVu Patch Disk 1 into the disk drive of the PC. 30

31 & &('85(6 3. Select Start on the task bar of Windows 95 or Windows NT. Select Run from the menu, then type A:\SETUP in the Open field. (If your 3 ½ floppy drive is the B: drive, type B:\SETUP.) 4. Click OK to continue. 5. The Select Installation Options window appears. The setup program determines the version of Windows that you are using, and automatically selects the correct options. Click OK to continue. 6. The Select Locations for CorVu Files window appears. The default values shown in the fields are correct; no modification is necessary. Click Install to start processing the information on the disk. 7. The setup program prompts you for the second patch disk after the first one s information is updated to the system. CHECKING VERSION LEVEL You can check that the update was successful by checking CorVu s version level. To do this, follow these steps: 1. Go to the CorVu main menu and select Help on the task bar. 2. Select About CorVu. The version level appears in the second line of information. 31

32 6 KNOWLEDGE LIBRARY The following sections describe information about the Prophet 21 knowledge library. Definitions of tables and flags, as well as information on custom software and optional package fields are included. Details on why certain fields do or do not link, and the linking to item status from the accounting database are discussed. WHY COLUMNS MAY NOT PRODUCE OUTPUT The knowledge library is not tailored for any one user. It is shared by all Prophet 21 users. Field names created for a specific customer by custom software are displayed in the column information for every user. For these reasons, you may notice column (field) names in the knowledge library that may seem unusual or unique. If you do not use the custom software or optional package, selecting these special fields for a CorVu query will display a zero value in the result set, or final report. If you notice that a column is displaying zero values, review the column description to see if it may be linked to custom or optional software packages. The following list includes some column descriptions that will create zero output if you do not have their applicable software enabled: Data Entry database under Item by Code and Item by Key tables: UPC Check Digit Item Disposal Number Duty Factor D-length for Hose Fittings Labor Hours for Service Parts MSDS Sheet Number Inventory database under PO Header 1 Information table: EDI Customer Code* EDI PO Flag EDI Alternate Ship-To Exchange Factor for Currency Exchange Rate Foreign Currency ID *The EDI database is accessible when the Electronic Data Interchange optional package is installed. Note: The previous column descriptions are just some of the examples of the optional package or custom software fields that exist in the knowledge library. 32

33 .12:/('*(/,%5$5< VIEWING COLUMN INFORMATION To make using CorVu more user-friendly, the column descriptions have been revised to better define exactly what the column will display. Column descriptions represent the internal field names within your database records. They are displayed in alphabetical order of the field names found in the CorVu/P21 knowledge library. You may notice, when creating or editing a query, that the column descriptions will not appear in alphabetical order on the Generate Query screen. This is because the internal field name starts with a letter different from the column description. In the following example, the Order Line-Item Information Table displays a section of its column descriptions. The Line-Item Entry Date description is placed among descriptions starting with E and F, and appears out of alphabetical order. This is because the description s internal field name is Entry Date; the column description was edited to Line-Item Entry Date so it would be more descriptive. The Line- Item Entry Date column looks out of order due to its internal field name, Entry Date. Note: Only the system administrator is typically allowed to access the library. So, you may not be able to see the internal field name of the column. THE FRECNO COLUMN Many tables will have a column entitled Frecno. It is an internal field that is used to identify the record number of the record being accessed. The Frecno column is used with many of the Prophet 21 databases to display the internal record number of each record shown in the result set. Although present in most tables throughout the knowledge library, it is not a column typically used in a query. There are no business applications within the Prophet 21 system that require you to know this value. Therefore, you can ignore any Frecno entries. 33

34 .12:/('*(/,%5$5< You can ignore the Frecno column. There are no P21 business applications that use this column COLUMN DESCRIPTIONS USING DESCRIPTION AND DISP Some tables show one field name represented by three column names. For example, in the Order Line-Item Information table, the column Disposition is represented as Disposition, Disposition Description, and Disposition Disp. Different values are generated from each field. Column Description Disposition Disposition Description Disposition Disp Displayed Output The disposition code of the line-item generates a numerical value such as 0, 1, 2, etc. The descriptive text is used to describe the line-item s disposition, such as complete, backordered, allocated, cancelled, etc. The disposition code of the line-item generates letter values, such as A, L, C, etc. 34

35 .12:/('*(/,%5$5< For our example, the Disposition field can have one of several values. The following defined values are shown in order of the Disposition field, the Disposition Description field, and the Disposition Disp field. Disposition Disposition Description Disposition Disp 0 Completed COMP 1 Allocated or Picked AP 2 Back Ordered B 3 Cancelled C 4 On Hold H 5 Direct Ship D 6 Local Pick-Up L 7 Pick-Up/Deliver P Many tables will contain three column descriptions representing one field name. The previous example will help you determine which column to use in your query. Generally, the column with description in its name will be most helpful to you. TABLES BY CODE VS. TABLES BY KEY The Prophet 21 Acclaim System consists of XL and Progress files. Because each type has a unique file structure, different CorVu databases were created to address each one. Several databases, such as item, vendor, and customer, have two tables. The tables by code, such as Customer by Code, address the XL files in the system. They use actual values, such as customer codes, item codes, vendor codes, and vendor numbers, to link the XL files together. The tables by key, such as Item by Key, address the Progress files in the system. They use the internal record number of a Progress database record to link to another Progress database record. The following list illustrates which tables should be used for XL files, and which ones should be used for Progress files: Data Entry Database Tables Tables for XL Files Branch by Number Vendor by Code Vendor by Number Item by Code Customer by Code Tables for Progress Files Branch by Key Company by Key Vendor by Key Item by Key Customer by Key 35

36 .12:/('*(/,%5$5< WHY FIELDS DO OR DO NOT LINK Any two tables that have a logical link can normally be linked together to create a CorVu query based on multiple databases. For example, creating a query with the following columns, although from different tables and databases, produces a listing of ordered and invoiced sales values. Any open amounts that can be invoiced are shown by order number. Column Table Database Customer Code Order Header 1 Information Order Processing Bill-To Name Customer by Code Data Entry Order Number Order Header 1 Information Order Processing Order Date Order Header 1 Information Order Processing Ordered Sales Value Order Header 2 Information Order Processing Invoiced Sales Value Order Header 2 Information Order Processing If an error in linking message appears, the columns chosen for the query do not logically link together. This may be caused by using columns that are found in both a database by code and a database by key. Or two columns selected just are not logically related. For example, running a query that consists of the Customer Code column, from the Customer by Code table, and a Cost column from the Vendor Sales History table, produces the error: If an error should happen, review the query to make sure the selected columns are logically related so that a valid report will result. Errors are displayed only when you choose to either save, run, or modify the query. Errors are not displayed while the columns are being selected. Note: You should be able to link as many tables together as necessary. For example, links can be made between customers, orders, and receivables. CUSTOM TABLES You may notice certain tables marked with an asterisk (*) in some of the databases. These are custom tables that have been created by request. Only the customer who requested the table has access to it. If you are not this customer, creating a query based on any column within this table will not generate a valid result set. 36

37 .12:/('*(/,%5$5< USING THE LINK TO ITEM STATUS TABLE Because different types of files exist in the system, a unique table had to be created to link item information to item status information. For example, a specific type of file holds item information, such as description and pricing, and a different type of file holds item status information, such as free stock quantity and PTD times sold. The table that was created to handle this is the Link to Item Status (Data Entry) table found in the Accounting database. The following steps illustrate creating a sample query reporting on item code, item location ID, and the current quantities in free stock, allocated stock, and backordered stock. 1. Choose an Item Code column from any table. For this example, the Data Entry database and Item by Code table have been chosen. Choose any other fields from this table on which you wish to report. 2. To link to the type of file that holds stock quantities, select the Link to Item Status table found in the Accounting database. Choose any of the columns found in this table. This column provides the link to item status information. Note: It does not matter which column is chosen in the Link to Item Status table. Any of them provide the necessary link between the different types of files. The Item Key and Item Location Key columns show internal record numbers that are not useful to any business application. The Location Slot column also displays a number that has no bearing on the type of information displayed. The Location Number column displays exactly that, so that column may be the most comprehensive to use. 37

38 .12:/('*(/,%5$5< 3. To access stock status fields, choose the appropriate columns found in the Item Stock Status table found in the Data Entry database. 4. When the query is run, the result set will look similar to this: 38

39 .12:/('*(/,%5$5< HIDING SPECIFIC COLUMNS Some of the Link to Item Status columns provide the link from item information to item status, but are not useful for any other application. You may want to mask this column, or any column, from view. To prevent a column from displaying on the result set, use either the Don t Fetch or Hide Column option. To use the Don t Fetch option: 1. Modify the query and enter the field name of a column you wish to mask. This value is entered in the Column field. Choose the Column that you do not want displayed in the result set. The system will not display any column marked Don t Fetch. 2. Highlight the Don t Fetch option and this column will not show up in the result set. 3. Run the query and the Location ID column is no longer displayed: Note: Saving the query with the Don t Fetch option activated prevents the selected column from being displayed no matter how often the query is run. To use the Hide Column option: 1. Viewing the result set, position the mouse over the column heading you wish to hide. 2. Click the right mouse button and choose the Hide Column option. The column will disappear from view. 39

40 .12:/('*(/,%5$5< Note: The Hide Column option is temporary and is effective only while you view the result set. Saving the query with the Hide Column option activated has no effect on future runs of the query. The hidden column is displayed the next time the query is run. 40

41 7 TROUBLESHOOTING The following table describes causes and solutions to problems you may experience. Problem Probable Causes Remedy 1. When retrieving a query, or going into the knowledge library, the message "Cannot open... COLLECT.TMP" appears. 2. The CorVu menus are frequently corrupted. 3. CorVu gives an Unrecoverable Application Error or hangs when it starts up. 1. The Temporary directory specified in CORVU.INI does not exist or the user cannot write to it. 2. You are set up on a network and you have placed the temporary directory on a network disk other than a user s private directory and two users are using CorVu at the same time. In this situation, if one user starts up CorVu while another is using it, CorVu's temporary files will be lost. 3. You are set up on a network with the temporary directory on the user's private drive and the user has logged in and run CorVu twice. The Data directory specified in CORVU.INI is on a network disk and not in the user's private directory and more than one person has tried to modify the menu at once. The user's menu has become corrupted or there is no menu in the user's data directory. Create the directory or change it to a local disk or to the user's private directory, if on a network. If the temporary directory is on the user's private network directory, that user should not attempt to log in and run CorVu twice. Make sure the data directory is on a local drive or is in the user's private directory. Copy the file DEFAULT.MNU from the backup (DEFAULT.BAK) or from the CorVu programs directory to the user's data directory. 41

42 7528%/(6+227,1* Problem Probable Causes Remedy 4. When I start CorVu and log in, I sometimes get a message "Cannot execute <program>: Error n." 5. When I start CorVu and log in, I get CORVU caused a General Protection fault in module LOADMSG. 6. When I start CorVu and log in, I always get the message "Cannot execute <program>: Error n." 1. Your system is out of memory, or the program named is corrupted (Error 8). 2. The program named does not exist (Error 2). Check that the entry in the Servers section is correct and that the program exists. 3. A copy of the CorVu communications server is still running. CorVu has previously exited unexpectedly and the communications component is still running. 1. The [Servers] section of CORVU.INI has not been correctly set up. 2. The program may be corrupted. 1. Free up memory or delete the program and reinstall it. 2. Correct the Servers section entry or reinstall CorVu. 3. Double click on the Stop CorVu Server icon. Double click the Stop CorVu Server icon in the program manager. Ensure that the servers section of CORVU.INI is correctly set up. If the program is corrupted, erase it and reinstall it from the CorVu installation disks. 7. When I add users to the CorVu user base, they do not get saved properly. 8. When I start up CorVu, it gives a message saying my license has expired and exits. If it doesn't exit, trying to execute a query hangs. 9. When I start up CorVu, I get a message, "Cannot find xxxxx.dll." 10. When I start CorVu, I get the message "General Protection Fault in xxxxxxx.dll called from XXXX.EXE," where XXXX.EXE is a CorVu communications driver. 1. You are using a network and do not have access to the CorVu password file. 2. The password file has become corrupted. Your CorVu server license has not been activated or expired. 1. Windows has become corrupted. 2. Your networking software is not listed in your DOS PATH. 3. You have chosen to use networking software that is not installed. 1. You have not started your network software. 2. You have not installed the Windows virtual device driver for your network. 3. You have attempted to use a host name in a TCP parameter file with a network for which using host names is not supported. Ensure that you have access to the CorVu password file. If the file has become corrupted you will need to restore it from backups. If you are on a trial license, contact your distributor to discuss purchasing CorVu. If you have purchased CorVu, contact CorVu to arrange for new license numbers. Reinstall Windows. See if the DLL is in your networking software. If it is, make sure the directory it is in is listed in your PATH. Install any required files from the Windows Sockets Drivers disk. Start your network software. Check your network software's installation instructions for information on setting up Microsoft Windows for your network. Use an Internet numeric address instead of a host name. 42

43 7528%/(6+227,1* Problem Probable Causes Remedy 11. When I start CorVu using my TCP networking software, I get the message "Cannot connect to <Internet number>" almost immediately on pressing the "OK" button at the login screen. 12. When I start CorVu using my TCP networking software, I get the message "Cannot connect to <Internet number>" after a long delay after pressing the "OK" button at the login screen. 13. When I start CorVu using my TCP networking software, all apparently goes well, but when I try to execute a query or go into the knowledge library, CorVu hangs. 14. When I start CorVu using a serial line connection, I get an "Unable to connect to server" message. There is no CorVu server running on the host for the port specified in the CorVu Administrator. 1. The host system is not running. 2. The host system s network interface has been marked as down. 3. Part of the network is down. 4. The host parameter in the CorVu Administrator is incorrect. 1. Inetd is having trouble running the CorVu server. 2. mini_inetd.conf has an incorrect path name for a CorVu server program. Your serial line login script is timing out. Ensure that the host number and port number specified in the CorVu Administrator file are correct. If you are using inetd, ensure that it has been reinitialized by sending it signal 1 (on a UNIX host, kill -1 process_number). If you are using mini_inetd, ensure that mini_inetd is running. Ensure that you have set up the CorVu server to run on the port you expected by checking mini_inetd.conf if you are using mini_inetd, or by checking inetd.conf and services if you are using inetd. Use the telnet test to confirm that the port has been configured correctly. Ensure that the host system is running. Ensure that the host system s network interface is marked as up. Ensure that the network is functioning normally. Correct the host parameter in the CorVu Administrator. Check the system logs and system console on your host system for hints as to what problems inetd is having. Correct the CorVu server path name in mini_inetd.conf. If these are both correct, problem 17 may apply. Add the line "Debug=C" to the [Config] section of CORVU.INI. When you run CorVu with this line, SERCHK.EXE will create a diagnostic window that will list all data sent and received over the serial line. You can use this log to adjust your serial line login script. When you have corrected the problem, be sure to remove the line. You may need to modify the TIMEOUT parameter in your parameter file. 43