The PROFILE command displays the current profile. It can also lock the profile from further changes (PROFILE LOCK). The profile is displayed as a series of =>PROF lines, which can be removed using the D/DD line commands or the RESET primary command.
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
=PROF> ….RES (FIXED – 80)….RECOVERY OFF WARN….NUMBER DISPLAY STD………
=PROF> ….CAPS ON….HEX OFF….NULLS ON STD….TABS OFF………………….
=PROF> ….AUTOSAVE ON….AUTONUM OFF….AUTOLIST OFF….STATS ON…………..
=PROF> ….PROFILE UNLOCK….IMACRO NONE….PACK OFF….NOTE ON…………….
=PROF> ….HILITE REXX LOGIC CURSOR FIND…………………………………
=BNDS> < >
The sample profile contains:
- The first profile line (=PROF>) shows the profile name (EXEC), the data set record format and length (FIXED – 80), and the settings for edit recovery mode (RECOVERY ON) and number mode (NUMBER ON STD).
- The second profile line shows the settings for caps mode (CAPS ON), hexadecimal mode (HEX OFF), nulls mode (NULLS OFF), tabs mode (TABS OFF), and UNDO mode (SETUNDO STG).
- The third profile line shows the settings for the auto modes: autosave (AUTOSAVE ON), autonum (AUTONUM OFF), and autolist (AUTOLIST OFF). It also shows the setting for stats mode (STATS ON).
- The fourth profile line shows the lock status of the EXEC profile (PROFILE UNLOCK), the name, if any, of the initial macro called at the beginning of the edit session (IMACRO NONE), and the settings for pack mode (PACK OFF) and note mode (NOTE ON).
- The fifth profile line shows the current hilite status (HILITE OFF).
- The last four lines of the edit profile show the tabs settings (=TABS>), edit mask (=MASK>), bounds settings (=BNDS>), and the column position line (=COLS>).
BOUNDS and MASK settings are also stored in the profile. MASKs can be used to preset data on inserted lines. BOUNDS defines limits for the following primary commands: FIND, CHANGE, EXCLUDE and SORT. Bounds also affect the operation of the text line, data shifting, and scrolling commands.
The default lines for MASK and TAB lines are all blanks. The default bounds are the first and last bytes of the dataset record length, minus numbers if it applies. For example, a DATA LRECL of 80 sets the right bound to 80; a JCL member with numbers sets the right bound to 72.
MASK: when turned on, causes a mask to be presented on every inserted line. For example, setting the MASK in a CNTL PDS as “//” begins each line with the slashes. If you don’t want the mask on a line, it can be overtyped.
BOUNDS: the BOUNDS primary or line command sets limits for scrolling, text, and many other commands. The primary command BOUNDS with no arguments resets them to the default.
RECOVERY: when turned on, ISPF keeps track of your edit session. You can then recover your changes if your edit session crashes. Recovery is automatic, but you have a choice of deferring or skipping the recovery.
RECOVERY also allows use of the UNDO edit command. UNDO works the same way as the undo you find in Microsoft products such as Word or Excel. It backs out all changes made since the previous ENTER or edit command.
To turn on edit recovery, type RECOVERY ON. This is recommended.
SETUNDO: when turned on, the edit session can use the UNDO command without turning RECOVERY on. The command is either SETUNDO STG (do the undo on the in-storage copy) or SETUNDO REC (do the undo in the recovery copy). There are two advantages to SETUNDO STG:
- It’s faster;
- It does not turn recovery on.
NULLS: by default, blanks on the end of a line are considered valid characters (spaces). With NULLS OFF, if you try to insert characters on a line, the insertion is not allowed. You must delete characters or erase to end-of-line before inserting any characters. I set NULLS ON so I don’t have to constantly delete or erase characters.
TABS: With TABS ON, the editor can determine where to put the cursor. You can let the editor decide where to put the cursor, or use the TAB keys on your keyboard to position the cursor. Because the tab line is used for all tabs, it may contain asterisks, dashes, or underscores. All tabs are set using the TABS line command.
- Software tabs are set by typing dashes or underscores on the TABS line over the areas you want to tab to. For example, this sets three tab areas:
TABS ———- ——- ——–
Software tabbing does not provide tab locations, therefore the TAB key does not work with these tabs. The editor uses these tabs to position the cursor in the general area it needs to be in.
- Hardware tabs are accessed using the keyboard’s TAB key. The edit screen has two hardware tabs set: one at the line labels and one at the first byte of the data line. You can set more hardware tabs by placing an asterisk on the tab line just before you want your field to start. The editor will not let you type on top of a hardware tab. For example, this sets three tabs at positions 10, 16, and 36:
TABS * * *
To turn off hardware (or logical) tabs, type TABS OFF (clears all tabs) or space out the asterisk(s) on the TABS line.
- Logical tabs are represented by a character, e. g. “TAB ¬“. To set data areas as 1-9, 10-15, 16-35, and 36-72, set up your TABS line as:
=TABS> – * * *
When you enter lines like this:
000100 ¬la¬0,0¬clear counter register
000200 *¬¬¬to initial value
the result is:
000100 LA 0,0 CLEAR COUNTER REGISTER
000200 * TO INITIAL VALUE