This solves it in most cases, but O&D availability is more sophisticated than this. i.e. A-B <stop> B-C on one PNR can definitely show different availability than A-B + B-C on separate PNRs, which has been an issue with this fare.
And this is particularly annoying because I don't know how to simulate this via EF, so I'm not sure how to suggest people work around this problem with easily accessible tools.

This has led to some confusion about why this (and the J version) have seemed unbookable for some - in the end all we usually need is to move a segment by a couple days to make it work.