On 31 August 2010 14:39, Pinnacle <pinnc...@rochester.rr.com> wrote: > ----- Original Message ----- From: "Benik, John E" <john_e_be...@uhc.com>
>> Does anybody know of a way to prevent the following from happening when >> setting numbers off? Short of going into every member of a PDS I have >> not found a way to prevent this. We have tried profile lock and a >> number of other things without success. >> >> -CAUTION- Profile changed to NUMBER ON STD (from NUMBER OFF). >> Data has valid standard numbers. This has been a long standing complaint of mine with ISPF. In most cases I want to be able to tell it *DO NOT FIDDLE WITH MY SETTINGS - I KNOW THE WAY I WANT IT*. And I can't. It always knows best. > If you want to suppress this for all time, create an IMACRO to do this: > > NUM ON > UNNUM > NUM OFF The problem I have with this is that there are various cases where that initial macro won't take effect, e.g. edit an empty member and then copy the content of a member with valid numbers in. And the macro has to be set up on system and userid you are using. Why on earth can't they provide an option to truly lock some or all settings? CAPS ON is the very worst, because it so easily destroys data. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
