Re: New Mainframe Blog Site -- mainframeblogger.com



On Apr 26, 7:31 pm, "William M. Klein" <wmkl...@xxxxxxxxxxxxxxxxx>
wrote:
Only because Pete made humorous comments about ISPF, I thought he (and maybe
others) might want to look at:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ispzu261/2...
or
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ispzug61/2...

(for example)

Notice that is supports both GUI and non-GUI and is intended for "network" (and
workstation) work via ISPF.

I haven't used this personally, but did want to make certain that others know
that the (IBM) mainframe development environment isn't what it was several
decades ago.

--
Bill Klein
wmklein <at> ix.netcom.com

Wow. Blast from the past. The ISPF GUI interface was introduced in
the mid 1990s. Most people hated it then, and I know of very few
people who use it today. IMO it failed because the GUI was poorly
designed and offered no productivity benefit over the traditional
interface. IBM "functionally stabilized" the GUI interface several
years ago.

Along with the GUI however, IBM provided several ISPF services that
are extremely useful, if little known. Among other things, the
services allow you to transfer files between your workstation and the
mainframe at FTP-like speeds. You can also set it up to transparently
edit mainframe files using a workstation editor, or vice versa.
Pretty cool stuff...but one of ISPF's best-kept secrets.

Don Leahy
.



Relevant Pages

  • Re: Java is becoming the new Cobol
    ... THE biggest problem with the mainframe is that IBM never embraced a GUI ... People don't want 3270 screens and ...
    (comp.lang.cobol)
  • Re: Java is becoming the new Cobol
    ... THE biggest problem with the mainframe is that IBM never embraced a GUI ... People don't want 3270 screens and ...
    (comp.lang.cobol)
  • Re: Java is becoming the new Cobol
    ... THE biggest problem with the mainframe is that IBM never embraced a GUI ... People don't want 3270 screens and ...
    (comp.lang.cobol)
  • Re: Java is becoming the new Cobol
    ... you can't do that on the mainframe. ... People don't want 3270 screens and ... If IBM had embraced GUI screen application ... In fact, when PC's first became generally available - IBM, remember - there ...
    (comp.lang.cobol)
  • Re: Java is becoming the new Cobol
    ... THE biggest problem with the mainframe is that IBM never embraced a GUI ... People don't want 3270 screens and ...
    (comp.lang.cobol)