My technique for debugging this kind of problem is to start with the just the epilogue and prologue, then add half the code back in, then half the remaining code, etc., until i get the error again (ignoring all the other errors), then stripping out code until I get rid of the error. Ever since I got away from once a day turnaround on batch assemblies in the early 80's this has proved pretty efficient.
On 2019-11-18 10:35 a.m., Tom Marchant wrote: > On Mon, 18 Nov 2019 08:17:37 -0500, Peter Relson wrote: > >> Due diligence before posting such questions includes trying to eliminate >> the possibility that you made some simple mistake. > Such as assembling the prolog and epilog macros with no intervening code. > Gary Weinhold Senior Application Architect DATAKINETICS | Data Performance & Optimization Phone:+1.613.523.5500 x216 Email: [email protected] Visit us online at www.DKL.com E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
