|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Paul, Actually it was in the correct physical and logical sequence due to a prior COPYF to another file for safe keeping while I continued to test! -----Original Message----- From: Paul Nelson [mailto:p_nelson-br@pop.inil.com] Sent: Tuesday, July 02, 2002 11:53 AM To: midrange-l@midrange.com Subject: Re: CLRPFM and DB2 Tables When you were doing the inserts, and the destination table is keyed, what physical order were the "input" records in? If the inbound data is sorted in the proper key order, the "output" goes much faster since the system isn't fighting to maintain the index area over the file. Paul Nelson Braxton-Reed, Inc. 630-327-8665 Cell 708-923-7354 Home pnelson@braxton-reed.com ----- Original Message ----- From: "Weatherly, Howard" <Howard.Weatherly@dlis.dla.mil> To: <midrange-l@midrange.com> Sent: Tuesday, July 02, 2002 10:19 AM Subject: RE: CLRPFM and DB2 Tables > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > -- > [ Picked text/plain from multipart/alternative ] > Bruce, > > I attempted using the DELETE but it just took too long! In the CL I have a > RUNSQLSTM that drops the indexes and another to rebuild them at the end. I > just can not figure out why the INSERTs went south after the CLRPFM, the > program was running fine but it was doing about 1 row every 3 or seconds, > ran from the 26th till Monday. What is really surprising is that ops gave me > a get outa jail free card on that! :-) > > -----Original Message----- > From: R. Bruce Hoffman, Jr. [mailto:rbruceh@attglobal.net] > Sent: Tuesday, July 02, 2002 11:08 AM > To: midrange-l@midrange.com > Subject: Re: CLRPFM and DB2 Tables > > > ----- Original Message ----- > From: "Weatherly, Howard" <Howard.Weatherly@dlis.dla.mil> > To: "Midrange Mailing List (E-mail)" <midrange-l@midrange.com> > Sent: Tuesday, July 02, 2002 10:52 AM > Subject: CLRPFM and DB2 Tables > > > > table was implemented (not a DB2 issue) I am not permitted to use DDL in > the > > job stream. My thought is to use CLRPFM to clear the table and reload it > > using CPYF however something strange happened in testing the program > (before > > I decided to use CPYF) it took forever using Exec SQL Insert.... and I > > eventually killed the job. > > > > Is there some reason that I should not use CLRPFM to clean out this table > > for a reload? > > > There is no real reason that you could not, unless there are constraints on > the file. Then the clear may fail. > > You said no DDL, so use DML... delete * from table > Again, if the constraints are honored (or non-existant) this will work. I > have seen tables with foreign key constraints that have rejected the clear, > but taken the delete *, but I have not investigated them further. > > Maybe suspending the constraints, clearing and then reloading and reapplying > the constraints would work in that situation if you can't use the delete for > some reason. > > =========================================================== > R. Bruce Hoffman, Jr. > -- IBM Certified Specialist - iSeries Administrator > -- IBM Certified Specialist - RPG IV Developer > > "There is a crack in everything, > that's how the light gets in. > - Leonard Cohen > > > _______________________________________________ > 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. > _______________________________________________ > 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. > > _______________________________________________ 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.