|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Jan, Anyone running a release higher than V2R3 will have these database cross reference files. The number of records is NOT indicative of whether or not you've ran the conversion before. The number of records is strictly dependent on one thing - the number of fields/files/libraries you have. For example, if you create a new pf with 3 fields in a library, you can display the contents of the aforementioned file and those three fields are now in this file. Doing a DSPFFD to an outfile has gone the way of the Dodo bird. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Jan Rockstedt" <jan.rockstedt@datarutinmedia.se> Sent by: midrange-l-admin@midrange.com 12/17/2002 04:23 AM Please respond to midrange-l To: <midrange-l@midrange.com> cc: Fax to: Subject: Database cross-reference files and upgrade to V5R2M0 Hi ! We have a model 170 with V4R5M0 and wan't to upgrade this to V5R2M0. The install doc say's: --------- If your system has database cross-reference files from an earlier release, these files will need to be converted before you install the new release. Converting these files may add some time to your installation process. However, the conversion will enable faster access times for future database queries. Follow the procedure given below to determine how much time you will need to complete the conversion of the cross-reference files: 1. Determine if you have any cross-reference files. a. Type DSPFD QADBIFLD at the command line and press Enter. b. Record the number shown in the Current Number of Records field: ---------- Our QADBIFLD file have the Current Number of Records field: 782023 Is this a problem should we converted before ? Regards Jan Rockstedt person: Jan Rockstedt address: Datarutin Media AB address: Box 125 address: S-201 21 Malmo address: Sweden e-mail: jan.rockstedt@datarutinmedia.se nic-hdl: JR1543-RIPE source: RIPE _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.