1) Kirk Wolf • Our development for z/OS is in C/C++, Assembler, and Java.

Our development desktops are generally Ubuntu Linux (but Windoze and Mac would work fine with the same tools)

We use the Eclipse IDE framework with:
- CVS or Subversion source code repositories
- Java(JDT) and C++(CDT) plugins
- Ant scripts that incrementally upload changed C/C++ and asm source files to z/OS Unix directories and remotely build via an incremental Makefile on z/OS (launching make via Ant script SSH task).
- Java code is built incrementally via Eclipse, and scripts automatically deploy jars and wars to z/OS as needed.

We also use TSO/ISPF a bit (x3270 w/ 133x60 dynamic logmodes), but also use ssh connections for interactive z/OS Unix shells.

2) I use PL/1 as mainframe-language. The company develop UI's in MS .Net using C# and a homemade webservice-interface doing a CICS-call to the mainframe. Data are stored in DB2. This way our new z196 takes care of data and business-logic. Of course the batch is in PL/1 as well.
We do some green-screen in different ways. Common is SDF-II for designing the screen. Some do normal CICSBMS calls (SEND/RECIEVE/and so on) others use a smart homemade interface making it very easy to do a nice CUA-based dialog.
Application are normal split into UI, Data, Communication and Logic - as IBM's SAA described back in 1987. Funny to think about - it is still going strong making us able to locate problems easy and do component-based test. We can also share components so we don't have to rewrite code. All that is true for any well designed system. These days many consider this four-break coding kind of service arcitecture (hmmmm).

3)In my case -where most development is Mainframe Assembler- I use PC based "Dignus Systems/ASM"; Also I love UltraEdit (including its FTP feature, although -eventually- I also use Filezilla.
A 3270 emulator is always required to access TSO, CICS, etc., but ISPF is only used for file administration (rarely for editing, unless the PDS is a z/OS System PDS). The SMB (provided via DFS) is very useful to store object code for later linkedit. And I also developed a neat JOB submit using C# (this one I use from UltraEdit as a "tool"). So 98% of my JCL resides on the PC.
As you can see it is pretty much "PC based(?)" development.

4) I developed RIPPLE-TRAC for my mainframe development.

RIPPLE-TRAC is a conduit into Legacy Systems.

• RT works as a query tool against your source. In other words, it is like Crystal Reports or MS Query, except that it works against the source library rather than against a relational repository and is transparent of language.

5) We use Dignus' Systems/C, Systems/C++ and Systems/ASM on UNIX-based platforms.

Editors are UNIX-based, up to the developer (I happen to use 'vi'). On the mainframe
side, it's all "green screen." We have used ASMIDF in the past, that works well.