Site-wide Edit Profile Initialization

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.

Attention: Be very careful if you override the IMACRO setting. When a setting is forced the editor WILL CHANGE the users' profiles. For this reason it is usually better to use the site-wide initial macro than to force the initial macro in each user's profile.

Using the configuration table, you can change any of the defaults for new edit profiles and you can override (force) settings for PACK, RECOVERY, SETUNDO, STATS, and IMACRO in existing profiles.

It is helpful to understand when the ZDEFAULT profile is used and where it exists in a user's concatenations. The ZEDFAULT 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 might already have a ZDEFAULT profile in their edit profile. Individual users can delete their ZDEFAULT profiles using the PROFILE RESET command from within an edit session. Doing so allows them to use the site-wide configuration for new profiles. You can 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 that attempt to change forced settings will not receive a failing return code, but the settings will not change.