Another thing to check is the LOCK or UNLOCK status by issuing the PROFILE command with no parameters on the ISPF command line while in edit on one of the affected members: =PROF> ....JCL (FIXED - 80)....RECOVERY ON....NUMBER OFF.......................... =PROF> ....CAPS ON....HEX OFF....NULLS ON STD....TABS ON `........................ =PROF> ....AUTOSAVE ON....AUTONUM OFF....AUTOLIST OFF....STATS ON................. =PROF> ....PROFILE UNLOCK....IMACRO NONE....PACK OFF....NOTE ON................... =PROF> ....HILITE OFF CURSOR FIND................................................. =TABS> - * * * =COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+
If you set the profile the way you want it, and then issue PROFILE LOCK. Changes you make during an individual edit session will then not affect the saved version of the profile and should always start an edit session with the saved profile settings. If you have UNLOCK then a change made during one session may affect your later sessions. --Roger On Mon, Jan 31, 2011 at 1:44 PM, John Walker <jwalker...@yahoo.com> wrote: > Say, I have been noticing over the last year or so that i FREQUENTLY end up > with my edit setting set to NULLS ON. This is an annoying and aberrant > setting for any non-PC or non-unix use, which is to say ALL mainframe > applications and work. However, when I set it to off, it ends up being > reset somehow by ISPF. It seems that sometimes I am not even in browse or > edit and it still does it. How can I reset this obvious over-riding default > which I dislike? > > > >
