Unless those include files have identically named macros (and nothing else) with different behavior I would suggest you are spending a lot of time for not much reward. And if you do have the same named macro in each that is generally not a good idea. If they do different things they should have a different name. Since compiling macros takes relatively few processes, include all of the macro source code at the start of the job, or investigate AUTOCALL macro libraries. Are you getting errors? What value(s) of UPD that is causing the problem? Have you run this with OPTIONS MPRINT SOURCE2; ... View more