I have an IEBGENER running every some minutes and it does most of the time work fine, reporting:
ICE084I 0 EXCP ACCESS METHOD USED FOR SYSUT2
ICE084I 0 EXCP ACCESS METHOD USED FOR SYSUT1
ICE751I 1 F4-BASE F5-BASE E8-K48846
ICE090I 0 OUTPUT LRECL = 80, BLKSIZE = 6160, TYPE = FB
ICE084I 0 EXCP ACCESS METHOD USED FOR SYSUT1
ICE751I 1 F4-BASE F5-BASE E8-K48846
ICE090I 0 OUTPUT LRECL = 80, BLKSIZE = 6160, TYPE = FB
But it sometimes does generate a dataset with allocation VB, 255, 27998 (instead of FB, 80, 6160) and then IEBGENER reports:
ICE084I 0 BSAM ACCESS METHOD USED FOR SYSUT2
ICE084I 0 EXCP ACCESS METHOD USED FOR SYSUT1
ICE751I 1 EF-K49535 F0-K49038 E8-K48846
ICE090I 0 OUTPUT LRECL = 80, BLKSIZE = 6160, TYPE = FB
ICE084I 0 EXCP ACCESS METHOD USED FOR SYSUT1
ICE751I 1 EF-K49535 F0-K49038 E8-K48846
ICE090I 0 OUTPUT LRECL = 80, BLKSIZE = 6160, TYPE = FB
Does anyone have a guess on why IEBGENER could be choosing BSAM instead of EXCP and if that could be the reason the allocation definition is not respected in the practice? This is causing trouble at the time of the next IEBGENER as it abends with "CONFLICTING DCB PARAMETERS" (Obviously, I don't need a VB, 255, 27998, but a FB, 80, 6160 instead). Now why IEBGENER could be doing that, is a mystery to me.
Thanks a lot for your guidance.