FSEDIT Procedure Windows

Creating Application-Specific Key Definitions

The FSEDIT procedure enables you to specify a customized set of function key assignments. This gives you control over which commands the function keys issue in your application.

By default, the FSEDIT procedure uses the function key assignments that are defined in the FSEDIT.KEYS entry in the SASHELP.FSP catalog. This is one of the standard catalogs that are defined automatically when a SAS session is initiated. The SASHELP.FSP catalog is shared by all SAS users at your site, so when you use the KEYS command in the FSEDIT window, the procedure creates a copy of the FSEDIT.KEYS entry in your personal PROFILE catalog (SASUSER.PROFILE, or WORK.PROFILE if the SASUSER library is not allocated). This copy is then used in subsequent FSEDIT sessions.

You can use the KEYS= option with the PROC FSEDIT statement to select a different KEYS entry for your FSEDIT session. When you use the KEYS= option, the procedure searches the following catalogs in the order shown for the specified KEYS entry:

the SAS catalog that is identified in the SCREEN= option, if that option was also used with the PROC FSEDIT statement
SASUSER.PROFILE (or WORK.PROFILE if the SASUSER library is not allocated)
SASHELP.FSP

If the specified KEYS entry is not found, a blank KEYS entry that has the specified name is created in the catalog that is identified in the SCREEN= option, or in your personal PROFILE catalog if the SCREEN= option was not used with the PROC FSEDIT statement.

When you use the MODIFY command to create a new SCREEN entry, the KEYS entry that is used when the SCREEN entry is created is recorded in the Keys name field in the FSEDIT Parms window. (See Modifying General Parameters for details about the FSEDIT Parms window.) If you do not use the KEYS= option in the PROC FSEDIT statement that initiates the FSEDIT session, the KEYS entry name is FSEDIT.

Once a SCREEN entry is created, the KEYS entry name that is specified in the SCREEN entry parameter takes precedence over one that is specified in a KEYS= option. For example, assume that you have previously created a SCREEN entry named DISPLAY.SCREEN in the MASTER.CUSTOM catalog, and that the Keys name parameter that is specified in the SCREEN entry is MYKEYS. If you then submit the following statements, the procedure uses the KEYS entry MYKEYS.KEYS (specified in the SCREEN entry) rather than the EDKEYS.KEYS entry (specified in the KEYS= option).

proc fsedit data=master.subscrib
     screen=master.custom.display.screen
     keys=edkeys;
run;

The procedure looks for the KEYS entry MYKEYS.KEYS in the MASTER.CUSTOM catalog, then in SASUSER.PROFILE (or WORK.PROFILE), then in SASHELP.FSP. If the entry is not found, a blank KEYS entry is created.

Note: The FSEDIT NEW window always uses the KEYS entry that was specified in the KEYS= option or in the default entry FSEDIT.KEYS, not the entry that was specified in the SCREEN entry. [cautionend]

You can change the associated KEYS entry during an FSEDIT session by using option 5 in the FSEDIT Menu window. Use the MODIFY command to open the FSEDIT Menu window; then select option 5 to open the FSEDIT Parms window. Enter the name of the desired KEYS entry in the Keys name field. The new value takes effect immediately. If the specified entry is not found in the current screen catalog (or in your PROFILE catalog or SASHELP.FSP), then a new blank KEYS entry is created in the screen catalog if one has been identified; otherwise, the entry is created in your personal PROFILE catalog.

Top of Page