Hi Don,
Hoping you didnt delete the IDCAMS backups here's what I would recommend (pulling this out of the cobwebs):
1) allocate new but do not init new elibs
2) repro the .DATA portion only
3) run bc1pnlib/bc1pnlst with option analyze members to verify endevor can read the file and it looks like your typical elib
4) run conrpt80 against it to verify all its footprints are intact
Future reference for LB003E:
1) use bc1pnlib to adjust reserve pages. The best analysis of reserve pages I learned over the years (Pete!) is to think of it as virtual storage. ELIBs are basically VSAM pdse's. when writing a member it first looks to overwrite its existing position in the file, if it doesn't fit it will fragment and write the rest of the member to the end of the file it has to expand. In order to expand it stores the member being written to the reserve pages , expands the file and writes out the new member. If the # of reserve pages is too small you get C1lB003E.
2) reserve pages is sufficient check the volume where the file resides, could be full, no room it expand, move/reallocate the file to a new pack.
I'll email an older version of the tech doc Olliver mentions that goes into a little more detail.
Good Luck!
Karen
Original Message:
Sent: 04-13-2020 10:59 AM
From: Don Becker
Subject: ELIB backup/reorg
Having an issue with an elib EDELTA getting error C1LB003E ELIB FULL OR MEMBER SIZE > RESERVE PAGES
Cannot EXPAND.
So I went down path of backing up with IDCAMS/REPRO
Then deleted the current elibs
Defined new elibs with IDCAMS and then INITialized with BC1PNLIB
Then used IDCAMS to REPRO backup into new elibs
Go into Endevor and when I try to access an element I get the following..
THE BASE, DELTA, OR CONFIG REC IS MISSING OR FOOTPRNT INFO IS MISSING.
I'm not seeing anything stand out in the manual. What am I missing here?
Thanks.
------------------------------
Don
------------------------------