Has anyone successfully allocated VSAM Elibs with page sizes bigger than 4088? I'm finding the manual slightly confusing
Setting Up ELIB Data Sets (broadcom.com)
Ah! I think I see the problem - IDCAMS may not accept your calculation of CISIZE!
If you insert a LISTCAT ENTRY('xxx') just after your DEFINE I suspect you will see that even though you specified a CISIZE of 16392, the actual size that gets allocated is different - in my case I found that the reported CISIZE was 18432, and PHYREC-SIZE 6144. So the dataset characteristics you got did not match what Endevor needed, hence the C1LB002S.
That CIsize, just over 16k, is being rounded up it looks to a multiple of 2048. if you use 16K (16384) as the CISIZE and 8 bytes less for the record size and PAGE Size - then everything seems to work. I noticed in the IBM doc, that it says "If the override indicator in Data Class is set ON, the user specified CISIZE in DEFINE command will be overridden by the CISIZE in the DATACLAS..." so you might also need to check you ACS and/or dataclass specifications.
I think the best course of action here is to open a ticket with development and get a definitive ruling, certainly my suggestion that the PAGE size should be set to the CISIZE seems suspect, though VSAM might allow a record longer than the maxsize to be written??? Is that happening (maybe with spanned records) or the ELIB utility actually writes shorter records when the underlying file type is VSAM rather than BDAM???
Either way the doc is certainly less than clear and it should be updated with final development team findings.