The IEFJFCBN and CVT macros have had PRINT OFF at least as far back as MVS 3.8, so for these macros the PRINT OFF was not gained over any very recent years. In both macros, specifying LIST=YES avoids the PRINT OFF, as you no doubt would have found if you had followed your inclination, which you mentioned, to modify the macros.
Bill On Tue, 23 Feb 2010 06:01:21 -0800, Charles Mills wrote: >Thank you to everyone who replied. I suspected there was some sort of >parameter or statement that would effectively defeat PRINT OFF, but I came >up with using SYSTERM before I got around to researching any of those. I >freely admit that I am not familiar with *every* HLASM feature; just those >that I use from day to day. > >A valid question I think might be "why should I HAVE to learn how to defeat >PRINT OFF?" Except in the rarest of circumstances, why shouldn't a macro >writer assume that the user knows whether he wants a listing or not? Isn't >that what PRINT NOGEN is for? > >Peter, I know the specific macro that caused (or rather, obscured) my >problem was IEFJFCBN, but there were at least two or three others with the >same "feature" -- perhaps one was CVT. And no, I won't make any jokes about >Freudian slips. > >On 2/22/2010 9:15 PM, Charles Mills wrote: >> <rant> >> Many of the IBM-supplied storage definition macros and copy members have >> gained PRINT OFF statements over the years. As a result I had the > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
