Understanding the ISPF editor screen layout is essential for effective editing. The editor display is organized into specific areas that serve different purposes: margins define editable boundaries, line numbers help identify and reference lines, column display aids in positioning text, and the status line provides important information. This tutorial covers all aspects of the editor screen layout, helping you understand and navigate the editor interface effectively.
The editor layout is designed specifically for mainframe editing, with features that support fixed-format languages like COBOL, handle different record formats, and provide clear visual organization. Understanding the layout helps you edit more efficiently and avoid errors related to column positioning or record boundaries.
Overview of Editor Screen Layout
The ISPF editor screen is divided into several distinct areas, each serving a specific purpose.
Screen Areas
The editor screen typically includes:
Status Line: Information line showing editor state and file information
Line Number Area: Column showing line numbers for reference and line commands
Data Area: Main area where file contents are displayed and edited
Command Line: Area for entering primary commands
Function Key Labels: Labels showing available function keys
Layout Organization
The layout is organized to support efficient editing:
Top Area: Status line and command line
Main Area: Line numbers and data area side-by-side
Bottom Area: Function key labels and additional information
Line Numbers
Line numbers are displayed in a column to the left of the data area, providing reference numbers for each line in the file.
Line Number Display
Line numbers typically appear:
In a column to the left of the data area
Showing sequential numbers (1, 2, 3, 4, etc.)
Aligned to help identify specific lines
Used for placing line commands
Line Number Format
Line numbers are typically displayed as:
text
1
2
3
000001 This is line 1
000002 This is line 2
000003 This is line 3
The numbers help you identify lines and are essential for line command operations.
Uses of Line Numbers
Line numbers are used for:
Line Identification: Identifying specific lines in the file
Line Commands: Placing line commands in the line number area
Reference: Referencing line positions in commands or documentation
Navigation: Understanding your position in the file
Error Location: Locating errors reported by line number
Line Number Area
The line number area is where you place line commands:
Place single-character commands (I, D, R, M, C, etc.) in this area
Commands are placed next to the line they operate on
The area is to the left of the line numbers
This is the primary interface for line-level operations
Data Area
The data area is the main working area where file contents are displayed and edited.
Data Area Characteristics
The data area:
Displays file contents line by line
Allows you to type and edit text
Shows the actual data from the dataset
Is the primary editing workspace
Respects margins and column boundaries
Data Area Display
The data area shows:
File contents as they appear in the dataset
Text you type or edit
Changes you make (before saving)
Column positions (if column markers are enabled)
Record boundaries and formatting
Margins
Margins define the left and right boundaries of the editable area in the editor.
Left Margin
The left margin determines where text starts when you type:
Defines the left boundary of the editable area
Typically starts at column 1, but can be configured
Text you type starts at the left margin
Important for fixed-format languages where column 1 has meaning
Right Margin
The right margin indicates the end of the editable area:
Defines the right boundary of the editable area
Typically corresponds to the record length (LRECL)
Helps you stay within record length limits
Important for fixed-format languages where specific columns mark the end of data
Margin Importance
Margins are particularly important for:
Fixed-Format Languages: Like COBOL where column 72 typically marks the end of a line
Record Length Limits: Staying within dataset record length (LRECL)
Data Integrity: Ensuring data fits within record boundaries
Format Compliance: Maintaining proper formatting for structured data
Margin Configuration
Margins can be configured through:
ISPF Settings (Option 0) for default margins
Editor commands like BOUNDS to set column boundaries
Editor profile settings
Panel-specific configurations
Column Display
Column display shows column numbers or markers to help you understand column positions, which is essential for fixed-format languages.
Column Markers
Column markers may be displayed as:
Column numbers at the top or bottom of the data area
Vertical lines marking specific column positions
Highlighted columns for important positions (like column 72 for COBOL)
Column rulers showing column positions
Important Column Positions
For COBOL and other fixed-format languages, important columns include:
Column 1-6: Sequence number area (optional)
Column 7: Indicator area (continuation, comment, etc.)
Column 8-11: Area A (division, section, paragraph names, level numbers)
Column 12-72: Area B (procedure statements, data descriptions)
Column 73-80: Identification area (optional, for sequence numbers)
Column Display Benefits
Column display helps you:
Position text correctly in fixed-format languages
Stay within column boundaries
Understand where different areas begin and end
Avoid column-related errors
Maintain proper formatting
Editor Status Line
The editor status line provides important information about the current editor state and file.
Status Line Location
The status line is typically displayed:
At the top of the editor screen (above the data area)
Or at the bottom of the editor screen (below the data area)
The exact location depends on your ISPF version and configuration
Status Line Information
The status line typically displays:
Dataset Name: The name of the dataset being edited
Member Name: The member name (if editing a PDS member)
Current Line: The line number where your cursor is positioned
Column Position: The column number where your cursor is positioned
Editor Mode: Whether you're in Edit, Browse, or View mode
File Status: Whether the file has been modified, saved, etc.
Record Information: Record format, length, or other dataset attributes
Other State Information: Additional editor state information
Function key labels at the bottom of the screen show what each function key does in the editor.
Function Key Label Display
Function key labels typically show:
PF1=Help, PF3=End, PF7=Up, PF8=Down, etc.
Editor-specific function key assignments
Available operations and shortcuts
Understanding Column Positions
Understanding column positions is crucial for fixed-format languages like COBOL.
COBOL Column Areas
For COBOL, the editor layout corresponds to specific column areas:
text
1
2
3
4
5
Columns 1-6: Sequence Number Area (optional)
Column 7: Indicator Area (continuation, comment, etc.)
Columns 8-11: Area A (division, section, paragraph names, level numbers)
Columns 12-72: Area B (procedure statements, data descriptions)
Columns 73-80: Identification Area (optional, for sequence numbers)
Column Positioning
When editing COBOL:
Division, section, and paragraph names start in Area A (columns 8-11)
Procedure statements and data descriptions start in Area B (columns 12-72)
Continuation indicators go in column 7
Comments are indicated in column 7 with an asterisk (*) or hyphen (-)
Lines should not extend beyond column 72
Customizing Editor Layout
You can customize some aspects of the editor layout through ISPF Settings.
Customizable Elements
You can typically customize:
Line Number Display: Whether line numbers are shown and their format
Column Markers: Whether column markers are displayed
Status Line: What information appears in the status line
Margins: Default margin settings
Display Options: Various display preferences
Customization Through Settings
To customize the layout:
Go to Option 0 (Settings) from the Primary Option Menu
Select editor settings or display options
Modify layout preferences
Save changes to your ISPF profile
Changes persist across sessions
Best Practices for Understanding Layout
Following best practices helps you use the editor layout effectively:
Check Status Line: Regularly check the status line to know your position and file state
Use Line Numbers: Use line numbers to identify lines and place line commands
Respect Margins: Stay within margin boundaries to avoid record length issues
Use Column Display: Enable column markers when editing fixed-format languages
Monitor Position: Pay attention to your line and column position
Customize Thoughtfully: Customize layout to match your work style and needs
Learn Column Areas: For COBOL, learn the column areas and their meanings
Check Before Saving: Review your position and changes before saving
Explain Like I'm 5: Editor Screen Layout
Think of the ISPF editor like a special notebook with helpful guides:
Line Numbers are like page numbers in a book. They tell you "this is line 5" or "this is line 10" so you know exactly where you are in the file, like knowing which page you're on in a book.
Margins are like the edges of your paper. The left margin is like the left edge where you start writing, and the right margin is like the right edge where you stop. They keep your writing in the right place!
Column Display is like having a ruler with numbers on it. It shows you "you're at number 10" or "you're at number 50" so you know exactly where you are, like using a ruler to measure where to put things.
Status Line is like a little sign that tells you important things: "You're editing file ABC, you're on line 5, you're at column 12, and you've made changes." It's like a helper that always tells you what's going on!
Data Area is like the main writing space on your paper. It's where you actually write and see what you've written, like the big blank space on a piece of paper where you do your work.
So the editor layout is like a smart notebook that shows you line numbers (like page numbers), margins (like paper edges), column markers (like a ruler), and a status sign (like a helper) to make editing easier!
Practice Exercises
Complete these exercises to reinforce your understanding of editor screen layout:
Exercise 1: Layout Component Identification
As you use the ISPF editor, identify each component of the screen layout: locate the status line, line numbers, data area, command line, and function key labels. Document where each component appears and what information it provides. Build familiarity with the layout structure.
Exercise 2: Status Line Observation
Observe the status line as you edit files. Note what information it displays, how it changes as you move through files, and what it shows when you make changes. Practice reading the status line to understand your editor state and position.
Exercise 3: Column Position Practice
Practice understanding column positions: enable column markers if available, practice positioning text at specific columns, and work with fixed-format files (like COBOL) to understand column areas. Practice until you can position text accurately by column.
Exercise 4: Margin Awareness
Practice working within margins: observe left and right margins, practice staying within boundaries, and understand how margins relate to record length. Work with files of different record lengths to see how margins adapt.
Exercise 5: Layout Customization
Explore layout customization options: go to ISPF Settings and examine editor display options. Try customizing line number display, column markers, and status line information. Document what customizations are available and how they affect the editor display.
Test Your Knowledge
1. Where are line numbers displayed in the ISPF editor?
At the top of the screen
To the left of the data area
At the bottom of the screen
In the status line
2. What does the editor status line show?
Only the dataset name
Current line, column, dataset name, and editor state
Only function keys
Only error messages
3. What are margins used for in the ISPF editor?
Only for display
Defining editable area boundaries and staying within record limits
Only for printing
Only for COBOL
4. Why is column display important in the ISPF editor?
Only for aesthetics
For positioning text correctly in fixed-format languages like COBOL