Hi RonBOL,
Before you start moving things from Librarian to Endevor, you have some initial set up work to do.
- Review what Types you have in Librarian and determine if you need to create new Types in Endevor
- Review the current inventory structures, life cycles and mapping you have in Endevor now. Are you going to be using existing ones or do you need to create new Environments / Systems / Subsystems and mapping for the Librarian members?
- If needed, create any new Base/Delta, MCF, Source output libraries, Listing libraries
- Update anything else like Processors, security and backups
As you can see there is a lot to think about and prepare in Endevor.
After you have everything defined and prepared on the Endevor side, the actual conversion is a multi step process -- some Librarian utility steps and some REXX routines.
The conversion process I currently have moves up to 10 levels for each Librarian member over to Endevor. If necessary, the job and REXX routines can be changed to do more levels.
//* THIS JOB CONVERTS CONTENTS OF ONE LIBRARIAN MASTER FILE TO
//* ENDEVOR - UP TO 10 ARCHIVE LEVELS FOR EACH MEMBER.
//*
//* INPUTS: LIBRARIAN MASTER FILE
//*
//* OUTPUTS: 1 INDEX(M) LISTING OF THE LIBRARIAN MASTER FILE MBRS.
//*
//* 10 PDS SOURCE LIBRARIES - ONE FOR EACH ARCHIVE LEVEL.
//*
//* 10 SCL LIBRARIES TO USE FOR ADDING INTO ENDEVOR.
//* NEED TO MODIFY THE SCL STATEMENTS APPROPRIATELY
//* BEFORE USE.
After we extract everything from the Librarian Master file to the PDS libraries and generate the SCL statements for each member, we then Add everything to Endevor one PDS at a time in oldest to newest order which builds the Change history in Endevor along with loading the actual source of the previous versions.
It takes some planning and work but can be done.
When you get ready to start working on the conversion, open a Support case and we can work on this with you.
June