RE: moving libraries from user asp to system asp

Yo, Bob, et al (et Al? <g>),

I just found my notes from when I was doing this in 1993 (!).  I used both
CRTDUPOBJ and SAV/RST at different times under particular circumstances,
depending on the relevance of the issues that each had.  Here they are:

CRTDUPOBJ method:
        CRTLIB newlib ASP(*whatever) etc.
        CRTDUPOBJ *ALL FROMLIB(oldlib) OBJTYPE(*ALL) TOLIB(newlib) DATA(*YES)
        DLTLIB or RNMOBJ oldlib
        RNMOBJ newlib *LIB oldlib
   Issues -
        1) All duplicated objects are owned by the user running the process.
        2) Owner's authority to objects reset to *ALL.
        3) Private authorities lost, RSTAUT would not restore.
        4) All access paths rebuilt, no way to save and restore them.
   Note -
        DSPOBJAUT could be used to write the authority stuff to a file, which
could be read by a reasonably simple program which would plug the authorities
back in using CHGOBJOWN, GRTOBJAUT, and RVKOBJAUT.

SAV/RST method:
        SAVSECDTA
        SAVLIB oldlib DEV(*whatever) ACCPTH(*YES) etc.
        DLTLIB or RNMOBJ oldlib
        RSTUSRPRF
        RSTLIB oldlib DEV(*whatever) RSTASP(*whatever) etc.
        RSTAUT
   Issues -
        1) Usually takes a LOT longer, depending on time saved on access paths
versus time lost in all the extra steps.
        2) RSTUSRPRF and RSTAUT need a dedicated system (ENDSYS or ENDSBS *ALL).

Dave Shaw
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---