Re: How to copy an SQL table with a long name into the same library

On Thu, Nov 4, 2021 at 12:09 AM Mark Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Surely a *SAVF always helps ...

You can always do:

RSTOBJ .... DEV(*SAVF) SAVF(xx/yyy) RSTLIB(QTEMP)

for example, to just have temporary access to the data, e.g. for your "comparison" purposes.

Just saying ...

So, how does having a SAVF that you use to materialize a PF *always*
help over just having... a PF?

Not saying that a SAVF is a *bad* thing, just that you seem to be saying that

1. Create a SAVF from a PF.
2. Restore the SAVF to a different PF.

is somehow *always* better than

1. Copy a PF to a different PF.

And you specifically talk about restoring to QTEMP.

So, if you do your comparison, end the job, and then later realize
"oh, wait, I need to do another comparison" then you are suggesting it
is better to restore from SAVF yet again than just having a PF
*already there*?

Sorry, that doesn't strike me as *always* helpful.

Just saying...

John Y.