How can I put *LIBL for the Library of the input file in a WRKQRY?

["Osman, Hassen" <osmanh@xxxxxxx>]

> Hello there,
>
> I am writing my query in development environment and then release it to 
> production using Thenon (for performance and security reasons I am not 
> allowed to run in production). Even though I input *LIBL for the Library of 
> the input file the system changes it to the top library where the file is 
> found from my library list. The fact that the query definition is not 
> retaining *LIBL is crushing the query when it is run in production 
> environment for the development environment is different to the production. 
>
>
> >  <<ole0.bmp>> 
>
> I entered here *LIBL
>
> >  <<ole1.bmp>>        
>
> System puts the library name from Development Library List.                   
>                                                     
>
> >  <<ole2.bmp>> 
>
> Can you please help me if you know of a way of making WRKQRY retain *LIBL. 
>
> I know of creating a CL program to run the query....
>
>       PGM 
>               RUNQRY qryname QRYFILE((*LIBL/file1) (*LIBL/file2)) 
>       ENDPGM 
> or 
>
> Running the query as follows..
>       
>       RUNQRY qryname QRYFILE((*LIBL/file1) (*LIBL/file2)) 
>
>
> Regards,
> Hassen Osman
> Release Analyst
> OTSS - Esanda Group Technology
> Australia and New Zealand Banking Group Limited
> ABN 11 005 357 522
> 1/85 Spring Street, Melbourne VIC 3000
>
> Tel. 61 3 9666 9693
> mailto:osmanh@xxxxxxx
>
> This e-mail and any attachments to it (the "Communication") is confidential 
> and is for the use only of the intended recipient. The Communication may 
> contain copyright material of Australia and New Zealand Banking Group Limited 
> ABN 11 005 357 522 ("ANZ"), of any of its related entities or of third 
> parties. If you are not the intended recipient of the Communication, please 
> notify the sender immediately by return e-mail, delete the Communication, and 
> do not read, copy, print, retransmit, store or act in reliance on the 
> Communication. Any views expressed in the Communication are those of the 
> individual sender only, unless expressly stated to be those of ANZ. ANZ does 
> not guarantee the integrity of the Communication, or that it is free from 
> errors, viruses or interference.