|
Hi Rob, If you're using RUNQRY to run the query, you can use *LIBL there -- RUNQRY QRY(myquery) QRYFILE((*libl/myfile))I figured that out for a customer that kept cloning one query for 5 hospitals, and then having to modify 5 queries everytime they made a change. Using RUNQRY, they all use one query.
*Peter Dow* / Dow Software Services, Inc. 909 793-9050 pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> / rob@xxxxxxxxx wrote:
Query/400 is nice, I like it and still use it a lot. Grinds me, though, that it has to hardcode the library name in there. Even takes *LIBL, figures out which library currently works and puts that library name in there, replacing *LIBL. Hate that. I know IBM is sunsetting it, but you suppose a DCR has any chance on stopping that behavior?One workaround that is often suggested is to use Query Management instead. Granted, if you don't have STRSQL you don't get the prompter of STRQM. But you can still build QM Queries and "compile" them without it by using CRTQMQRY. Here, you can use *LIBL.Rob Berendt
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.
midrange.com
