RE: Retrieve list of *ALLUSR libraries

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Tom and others,

Thank you for your reply. In this case I have read the rules and they
are difficult to implement. In part because they change from release to
release and also due to some of the wildcard specifications like
QUSRVxRxMx. In this case, I have a list of all libraries along with some
associated data. When I refresh *ALLUSR libraries, I want to delete all
but the data associated with system libraries. Ideally, I would just
piggyback off of whatever logic IBM uses to support *ALLUSR.

David Morris

>>> qsrvbas@xxxxxxxxxxxx 5/18/2004 8:45:21 PM >>>
Though rules are documented, they may change from release to release
(see V5R3, e.g.) It may be better to use a command such as DSPOBJD
*ALLUSR to an outfile or use the QUSLOBJ API which will return the same
list in a user space if input parms are set appropriately. I'd be very
disappointed if the command and the API didn't adjust automatically
after an upgrade.

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>  10. Re: Retrieve list of *ALLUSR libraries (Al Barsa)
>
>The rules are well documented in both the Backup and Recovery Guide
and the
>help text for SAVLIB.
>                                                                      
    
>             "David Morris"                                           
   >
>Does anyone know of a way to retrieve the libraries returned by
*ALLUSR?
>Alternatively, is there a way to determine a library is a system
library
>by looking at its description (via API or otherwise)?

-- 
Tom Liotta