Is anything happening between the clearing of the file and the second
RUNSQLSTM which repopulates Table1?  Or is Table1 empty when the
constraints get put back?

** No. Table1 is empty.

If Table1 is populated when the constraints are added back, is the size
of Table2 relatively constant or has it increased significantly over

** All files are empty at the time the constraints are added back

Has anything happened over time to increase the number of indexes built
over Table1?

** No. These files are not allowed any more indexes (by design).
** In other words, I'm the only one that works in this library and I
haven't added any indexes.

Andy Nolen-Parkhouse

> We have a process that drops the constraints on tables (physical
> clears them with a CLRPFM, and then rebuilds the constraints.
> At first this process took 20 minutes. Now it takes 2 1/2 hours. My
> question is why? or how is this possible?
> Here is a small sample:
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member1) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)
> CLRPFM     FILE(Table1)
> .
> .
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member2) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:
To subscribe, unsubscribe, or change list options,
or email:
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.