z/OS ISPF Planning and Customizing
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Site-wide edit profile initialization

z/OS ISPF Planning and Customizing
GC19-3623-00

When no ZDEFAULT profile exists in the ISPTLIB concatenation and the user has no edit profile member in the ISPPROF concatenation, new edit profiles are created based on the settings in the ISPF configuration table. Using the configuration table, you can change any of the defaults for new edit profiles and you may override (force) settings for PACK, RECOVERY, WARN, SETUNDO, STATS, and IMACRO in existing profiles. When a setting is forced the editor WILL CHANGE the users' profiles, so be very careful if you override the IMACRO setting. IBM® recommends that you use the site-wide initial macro instead of forcing the initial macro in each user's profile.

It is helpful to understand when the ZDEFAULT profile is used and where it exists in a user's concatenations. The ZDEFAULT profile exists as a row of the edit profile table named xxxEDIT where xxx is the application profile.

If ZDEFAULT exists in the edit profile table in the ISPTLIB concatenation, and the user has NO edit profile table in the ISPPROF allocation, the ZDEFAULT profile is copied from ISPTLIB into the user's edit profile when the user's edit profile is created. Therefore, many of your existing users may already have a ZDEFAULT profile in their edit profile. Individual users may delete their ZDEFAULT profiles using the PROFILE RESET command from within an edit session. Doing so will allow them to use the site-wide configuration for new profiles. You may also use a site-wide edit initial macro to issue a PROFILE RESET for all users. ISPF does not ship any edit profiles.

Note: If you use the force settings such as PACK OFF, edit macro commands which attempt to change forced settings will not get a failing return code, but the settings will not change.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014