Many people have responded and maybe this solution has already been given. In general the LOG dataset is created when certain functions are done all along in the ISPF session. Only twice in my career did I care. So setting the OPTION to "2" to delete it when I am done seemed wasteful. WHY CREATE IT IN THE FIRST PLACE ????
Go to Option 0, select LOG Defaults (1) and you will see a panel to complete. You can put "2" as the option but below you will see "Primary Pages" and "Secondary Pages". These somehow equate to a space allocation for the LOG File. Change these to 0 (zero) and in the future when it goes to allocate the log, ISPF sees no space is to be allocated: a. It does not allocate the file. b. It will not write to the file along the way c. There is no need to delete the file at the end of the session. d. If for any reason, you need it, change the settings to values and use it. My customer at the time (wife who was my paying customer) complained about when she got into ISPF it always seemed like it went off for 4-5 seconds first thing and then was fine as far as response. I surmised it was the dynamic allocation for the file. In the 1990s we even had STK and Memorex 3380s and it was noticeable. She made the changes and no more delays to get started. I never figured out what the constant logging was doing as I was working. But the best I/O delay is the one you never make happen. I still spread the word today only because of all the SPFLOGn files left out on DASD and then our Storage Person has routines to sweep them away after a while. jim ---------------------------------------------------------------------- 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
