Posted: Mon May 05, 2008 1:35 pm Post subject: Recovery/Hilite/CANCEL
Three different questions in one mighty post!
I precede this with - I am a PROGRAMMER/Analyst, and know very little about the system workings of TSO/ISPF, thus the post. I did search, but could not find exactly my situation.
1. RECOVERY - used within librarian or PDS member to allow you to "undo" changes. When opening a member for the first time of the day - the warning UNDO COMMAND NOT AVAILABLE is displayed. I type REC ON, and I am good... until the next day when I get the same message.
2. HILITE - used within librarian or PDS member to allow different colors for different lines of code (i.e., comments are blue, verbs red, etc.). Same problem as with RECOVERY. I set it today, save the member, come back in tomorrow, and it is gone, and I have to reissue the command.
For the above two - in previous shops, once this was set within a member, and saved, the profile stayed with that member. Here it does not.
Other related profile settings:
PROFILE UNLOCK
3. END vs CANCEL with 'are you sure'. When editing a PDS member, you can press F3 and with your predefined keys you END the member, saving any changes. I prefer to have F3 NOT always save the changes (because when browsing, viewing, and many CICS screens, F3 is used to get out of the screen you are in WITHOUT saving). I changed my F3 to be CANCEL. On one of our LPARS (and at every other shop I have worked), when you modify a member and press CANCEL, you get a warning box - DATA SET HAS BEEN CHANGED.... are you sure?
On all our other LPARS, when you press CANCEL, it exits out of the member without saving, or without asking. So, if you press F12 by mistake, you just lost all your work!
AUTOSAVE is on, on both LPARS.
I checked with our system programmer, and he thinks there is a variable to set to make the warning box appear, but is not sure what it is. When he finds out, he will remove it from the one lpar that has it.
WHAT REASONS would there be to not have RECOVER ON be the system default?
WHAT REASONS would there be to not have the warning box appear on a cancel with changes?
Can anyone help me to get it so I do not have to type in REC ON, and HI xxx each day when I enter a dataset? I know I can create a macro, and assign it to each of my datasets, but there should be a systematic way to do this.
Also, in TSO PROFILE, it has set NORECOVER, and it will NOT allow us to change this value. Could this have something to do??
Joined: 03 Jan 2003 Posts: 1014 Topics: 13 Location: Atlantis
Posted: Mon May 05, 2008 4:48 pm Post subject:
This almost sounds like the ISPF profile is getting reset or is maybe allocated to a temporary data set. You can type TSO ISRDDN ; O ISPPROF and see what is allocated to that ddname. That is where the settings are kept.
Also, be aware edit profile settings are defined separately based on a combination of the last qualifier, record length and record format (I think). Also, verify that the profile is not locked with settings you don't want.
The easiest way to get defaults you always want is with a 'session macro'. Search the docs for ZEDITMAC
Recovery defaults to off mainly because of the performance overhead. the default for it, like for everything else, can be changed by the sysprog.
I'm afraid I don't have time to do this right now, but I'll come back and reread the post later. _________________ New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.
Joined: 31 May 2004 Posts: 391 Topics: 4 Location: Richfield, MN, USA
Posted: Mon May 05, 2008 7:46 pm Post subject:
In addition to semigeezer's comments, once you set REC ON, locking your profile should make that setting (and most other settings at that time) your default for that particular type of PDS. However, opening a member that was saved with REC OFF, will turn recovery back off and tell you. I don't have access to a mainframe, but see if those hints don't help. You might also look into setting up an INITIAL MACRO. See the F1 key. _________________ ....Terry
My main reason for avoiding the initial macro I guess is I would need one for Cobol, one for JCL, and another for say Easytrieve.
I like using the HILITE feature - it looks gooey!!
I did check the ISRDDN, and found the userid.ISPF.ISPPROF, with the members in it.
With the hilite question, what we did find was that I had been entering
hilite cobol
it would change all the colors and such, and the profile would reflect the change, until you exit TSO, and log back in. Then, back to the green screen.
If I type HI, I then get an option to select the program type, and color or no color. When you end, you get the following:
Color, symbol and margin settings have been saved in the ISR application
profile. All other HILITE settings were saved in the edit profile.
This seems to save the information on that member so when returning, the hilite does not have to be reenterd.
With regards to the recovery - yes, HERE the default is off, however the other shops I have worked at, the default was ON.
IF anyone knows where I can find overhead/performance statistics on the pros/cons of having the default be ON, that would be most beneficial in presenting my case to upper management.
Joined: 01 Feb 2007 Posts: 45 Topics: 5 Location: Oostende
Posted: Thu May 22, 2008 5:01 am Post subject:
Elster wrote:
My main reason for avoiding the initial macro I guess is I would need one for Cobol, one for JCL, and another for say Easytrieve.
No, you just test whet you are editing, either by retrieving the current profile, or by looking at the last qualifier of the dataset being edited, or even by looking at the actual data, if like me you mix everything in personal libraries, in the initial macro and set up your session appropriately.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum