ISPF

In computing, Interactive System Productivity Facility (ISPF)^[1] is a software product for many historic IBM mainframe operating systems and currently the z/OS and z/VM operating systems that run on IBM mainframes. It includes a screen editor, the user interface of which was emulated by some microcomputer editors sold commercially starting in the late 1980s, including SPF/PC.^[2]

ISPF primarily provides an IBM 3270 terminal interface with a set of panels. Each panel may include menus and dialogs to run tools on the underlying environment, e.g., Time Sharing Option (TSO). Generally, these panels just provide a convenient interface to do tasks—most of them execute modules of IBM mainframe utility programs to do the actual work. ISPF is frequently used to manipulate z/OS data sets via its Program Development Facility (ISPF/PDF).^[3]

ISPF is user-extensible and it is often used as an application programming interface. Many vendors have created products for z/OS that use the ISPF interface. ISPF can be run from a z/OS batch job.

An early version was called Structured Programming Facility (SPF) and introduced in SVS and MVS systems in 1974.^[4] IBM chose the name because SPF was introduced about the same time as structured programming concepts. In 1979 IBM introduced a new version and a compatible product for CMS^[5] under Virtual Machine Facility/370 Release 5.

In 1980, IBM changed its name to System Productivity Facility^[6] and offered a version^[7] for CMS under VM/SP.^[8] In 1982 IBM changed the name to Interactive System Productivity Facility,^[9] split off some facilities into Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) and offered a version for VSE/AF.

IBM released ISPF Version 2 and ISPF/PDF Version 2 in 1984; the VM versions^[10] allowed the user to select either the PDF editor or XEDIT. IBM eventually merged PDF back into the base product.

When a foreground (interactive) TSO user invokes ISPF, it provides a menuing system, normally with an initial display of a Primary Option Menu^[11] this provides them access to many useful tools for application development and for administering the z/OS operating system.

Such tools include:

• Browse – for viewing data sets, partitioned data set (PDS) members, and Unix System Services files.
• Edit – for editing data sets, PDS members, and Unix System Services files.
• Utilities – for performing data manipulation operations, such as:
  • Data Set List – which allows the user to list and manipulate (copy, move, rename, print, catalog, delete, etc.) files (termed "data sets" in the z/OS environment).
  • Member List – for similar manipulations of members of PDSs.
  • Search facilities for finding modules or text within members or data sets.
  • Compare facilities for comparing members or data sets.
• Library Management, including promoting and demoting program modules.^[12]

Underlying ISPF/PDF is an extensive set of tools that allow application developers to create panel-driven applications, and a set of guidelines to promote consistent use of ISPF functions. A "panel" is a character-based "window" which can encompass all or part of a 3270 session's screen real estate. See Text-based user interfaces.

Most mainframe software vendors used ISPF functions to create their applications, so their tools are similar in appearance and operation to ISPF. Similarly, many installations write their own informal tools that use ISPF services.

ISPF services are generally available to any programmer using the system, and can be used to write panels for either personal or system-wide use, writing in either compiled languages such as HLASM, C, COBOL, PL/I, or interpreted languages such as CLIST, REXX and ooRexx.^{[citation needed]}

ISPF applications can use file tailoring to create customized members from skeletons; one use of file tailoring is to create JCL that the user can then submit as a batch job.

The editor screen is formatted with 2 lines (info & command line) at the top or bottom (user choice), a six-character line number column in the left margin, and the remainder of the screen width being filled with the records of the dataset being edited. Primary commands (which apply to the whole dataset) such as Find, Print, Sort, etc. are typed in the command line. Line commands (which apply only to specific line(s)) such as copy, move, repeat, insert, exclude, delete, text flow, text split are entered by over-typing the line number fields with a one or two character code representing the command to be applied at that line followed by an optional number which further modifies the supplied command.

The editor has several key features:

• Context sensitive color highlighting for several languages and file types
• Code folding via the X or XX...XX(hide) line(s) command & indentation-selective reveals
• editor macro commands in REXX or compiled languages
• comparison with another dataset
• models of ISPF service calls
• context-sensitive Help available
• recovery from lost sessions

The editor can also be invoked in a 'view' mode. It behaves like the editor, but does not allow saving the data. Edited files can also be saved under a different name, creating or replacing another file.

ISPF provides the 'editor interface' which lets an application program display arbitrary data in the familiar editor panel. Thus many vendor packages use this familiar interface.

ISPF is designed to be customized for each user (a fairly new concept in 1974, when it was introduced). Some of the customization is global and some is specific to an ISPF application.

It supports a set of 24 function keys which, when pressed, execute commands.^[8] These are customizable: Each user can replace the default commands assigned to any key with his own preferred command (or series of commands). User settings are stored centrally, so that the user can logon from any terminal and that session will remember their previously-chosen commands for each key. Most personal computers (PCs) copied this, and have a set of 12 or 24 function keys. Even some defaults have endured: the F1 key triggers a "help" function on a large number of mainframe and PC programs.

ISPF remembers each user's choices for such things as screen colors and layout, the location of the command line and scrolling preferences. It also remembers the last-used data set names on each panel, so the next time the panel is used the names are already filled in. This is very convenient for mainframe programmers because they frequently work with the same files repeatedly.

Many of the early users of PCs were mainframe programmers or users, who were accustomed to and liked the ISPF panel system. This led several companies to create partial clones of ISPF that run on DOS, OS/2, Windows or Unix PC systems. In 1984 IBM introduced the EZ-VU dialog manager for DOS PCs,^[13][14] and later OS/2. In 1991 Tritus, Inc introduced Tritus SPF (TSPF), a program to allow use of mainframe ISPF applications and edit macros written in REXX on DOS, OS/2 and Windows; the last release was 1.2.8 in 1994. Freeware ISPF-style editors for Windows include SPF/SE and SPFlite.

In 1994 IBM introduced a built-in downloadable client program called the ISPF Workstation Agent (WSA)^[a] that can install and run on OS/2, Windows and selected Unix workstations; the z/OS version of ISPF only includes WSA for Windows and selected Unix workstations. WSA communicates directly with ISPF on z/OS and provides a point-and-click graphical user interface automatically.

The ISPF Workstation Agent can be used to edit PC based files from the ISPF editor to take advantage of the editor's strengths.

• SMIT, the built-in menu/panels program for AIX

• ISPF for z/OS at IBM
• IBM: ISPF documentation Deprecated link archived 2012-12-09 at archive.today