A Rationale for Pointer Enabled Tools

A Rationale for Pointer Enabled Tools

PETs programs provide an alternate, 3270-based interface to VM/CMS functions. The interface uses windows and is mouse-clickable, but it is not graphical. As such, PETs fit in the niche between traditional 3270 screen controls and full GUI interfaces.

Why?

Traditional 3270 VM/CMS is a terrific environment for programmers, but for end-users--maybe not so good. The 3270 CMS interface used to be good, but then along came the Macintosh, MS-Windows, OS/2, and other GUIs that were, frankly, just a whole lot easier to use than command line, text environments like traditional 3270 CMS.

In the late 1980's and early 1990's, the mainframe was dying (remember?), and much of that hype had to do with the easier-to-use interfaces on other platforms. ISPF, Full Screen CMS, CMS Windows, CUA 2000, and CMS GUI were proferred as usability enhancements, and each has special advantages.

The PETs programs likewise are intended to provide a user-interface to standard VM functions, but with a twist: these 3270-based programs are written to be manipulated with a workstation mouse.

Complaints About 3270 CMS

What complaints do people make about traditional 3270 CMS?

"CMS is too hard to learn; I don't have time."
"I can't remember all those commands...and all those options!"
"I can't type very fast."
"I make a lot of mistakes when I type...it's very frustrating."
"The PF keys are defined differently in different applications."
"I can't remember what the PF keys do in Xedit."
"I know you can customize colors and other things, but I can't figure out how."
"I can't use my mouse."
"I like windows."
"I want graphics!"

Yes, I made up all these quotes. But haven't you heard things just like that for years?

Key Design Considerations

PETs programs derive from precursor attempts to make the mainframe more "user-friendly," and they do make working on the mainframe considerably easier. Programs incorporate a number of key ideas.

Much less typing is required.
Mouse-clicking for navigation and functional selection is enabled.
CMS windows are used extensively.
Menus are a key component.
Menus and colors are easy to customize "on the fly."
Significant usability enhancements are added.
The interface is fast.
Colors and PF keys are used consistently.
Windows have a consistent (and familiar) look and feel.
Activity logs can record what you do so that you can do it again more quickly.
Many functions are generic and can be reused in new applications.
Programs are completely compatible with other VM/CMS tools; PETs menus can include non-PETs applications.
A critical mass of software is now available to enable users to do most of their CMS work from within PETs.

A Blend of Two Styles

PETs are intended to serve two kinds of users:

those who like using a mouse (or other pointing device), and
those who like using traditional 3270 keyboard functions (commands, PF keys, arrow keys, the ENTER key).

While some usability enhancements are obviously intended for use with a mouse, all functions are available as well on a dumb terminal. In a very real sense, the PETs interface blends these two styles together.

But you don't get graphics.

Who Can or Should Use PETs?

Everyone who logs onto CMS can use PETs to good advantage, but some individuals may find them of particular value:

people who prefer to use a mouse;
CMS users who don't type well or speedily;
programmers and documenters (click to SCRIPT?--yes) who discover advantages in some of the usability features;
novice users, especially those who are proficient with a workstation mouse;
casual or occasional users.

PETs allow you to say, "If you can use a mouse, you can use CMS."

Perhaps not as originally intended.

To Coin a Term...PE3270

It turns out that some other VM/CMS and OS/390 applications also can be manipulated (to a lesser or greater degree) with a workstation mouse. (IBM's ISPF and BookManager, and Richard A. Schafer's Mailbook are examples). Applications which are sensitive to the screen position of the cursor when the ENTER key is pressed--such applications can be manipulated with a mouse. But not having spoken with the authors of these products, I'm hard pressed to say whether such control was intended or is simply a happy bi-product.

In any case, such programs share with PETs the key feature of workstation pointer enablement. It may be appropriate to attach a new term to mainframe 3270 applications which implement this synergy, the term PE3270 - Pointer-Enabled 3270.

--rick ellis

Mail questions, comments, suggestions or inquiries to rge@uconnvm.uconn.edu .