Not one software product is perfect, there will always be known issues that hopefully will get resolved in the next release of the software. However, if you ever run into such issues, and then afterward talk about it to somebody, that peer may answer with something like "oh yes, I know that issue, I've run into the exact same problem!".
If you do NOT always have unique &&LIST-DSNs to store staging outputs (like SYSPRINTs) in the compressed listing (using PGM=SERPRINT), you'll end up with a compressed listing where multiple staging outputs are mixed together within the same (hard to read) area of the compressed listing. So how can you automatically prevent this from ever happening again?
Not one software product is perfect, there will always be known issues that hopefully will get resolved in the next release of the software. However, if you ever run into such issues, and then afterward talk about it to somebody, that peer may answer with something like "oh yes, I know that issue, I've run into the exact same problem!".