Author: steve-myers
Posted: Sat Jul 16, 2016 9:02 pm (GMT 5.5)
An "EXCP" is a low level macro used to start I/O. Both Syncsort and DFSORT use the EXCP macro directly since its proper use often provides for greater I/O through put than higher level I/O mechanisms such as "BSAM" or "QSAM."
As a user of and proponent of EXCP, I also know, from experience, that these improved I/O rates are often illusory; the improvements in "QSAM" and "BSAM" that date back to the Data Facility Product in the 1970s produced I/O improvements that are often nearly as good as aggressive use of EXCP. Most of the EXCP code in Syncsort and DFSORT predates DFP; in any event "nearly" is not equal or "better."
Actually, it seems to me that EXCP bought nothing here; "QSAM" and "BSAM" would work just as well for the small data set that was sorted here.
As Mr. Woodger says, these WER416B messages are not error messages; they are just Syncsort crowing about how good it is.
Posted: Sat Jul 16, 2016 9:02 pm (GMT 5.5)
An "EXCP" is a low level macro used to start I/O. Both Syncsort and DFSORT use the EXCP macro directly since its proper use often provides for greater I/O through put than higher level I/O mechanisms such as "BSAM" or "QSAM."
As a user of and proponent of EXCP, I also know, from experience, that these improved I/O rates are often illusory; the improvements in "QSAM" and "BSAM" that date back to the Data Facility Product in the 1970s produced I/O improvements that are often nearly as good as aggressive use of EXCP. Most of the EXCP code in Syncsort and DFSORT predates DFP; in any event "nearly" is not equal or "better."
Actually, it seems to me that EXCP bought nothing here; "QSAM" and "BSAM" would work just as well for the small data set that was sorted here.
As Mr. Woodger says, these WER416B messages are not error messages; they are just Syncsort crowing about how good it is.