Re: BIG Query Question

[Loyd Goodbar <loyd@xxxxxxxxxxxxxx>]

Sorry for replying so late.
You want to force-save a query, basically going into the query,  
changing nothing, and saving it.

The easiest way I can think to do this is:
1. Get a list of queries. WRKOBJ *ALL/*ALL *QRYDFN to an outfile  
should work.
2. Read the list processed by 1.
3. Write a program using Albert York's (IIRC) TNAPI program. It will  
be basically "real-time" execution because you "sign on" to the  
system and perform the work. The key sequence is something like  
WRKQRY LIB/QRYDFN, 2 (change), F3 (exit), Y 3 (save, do not run).

If you have more than a handful of queries this should pay for itself  
pretty quickly; even faster if you do frequent upgrades and need to  
re-save all the query definitions.

HTH,
Loyd


On Jun 12, 2006, at 8:34 AM, Chuck Lewis wrote:

> Hi Folks,
>
>
>
> Our main application vendor is installing new update this weekend  
> and files
> are changing.
>
>
>
> We have a TON of queries that reference these files and if a file  
> they use
> had changed, the query will bomb of course.
>
>
>
> So is there any way to force the save of a query without going into  
> it and
> doing that ?
>
>
>
> Thanks !
>
>
>
> Chuck
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)  
> mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.

http://www.blackrobes.net