Application programming on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


Conducting a debugging session

Application programming on z/OS

See the latest information on:

The application programmer conducts a "unit test" to test the functionality of a particular module being developed. The programmer uses job monitoring and viewing software such as SDSF to track the running compile jobs, view the compiler output, and verify the results of the unit tests. If necessary, the programmer makes the appropriate corrections to source code or other objects.

Sometimes, a program will create a "dump" of memory when a failure occurs. When this happens, a z/OS® application programmer might use tools such as IBM® Debug Tool and IBM Fault Analyzer to interrogate the dump output and to trace through executing code to find the failure or misbehaving code.

A typical development session follows these steps:
  1. Log on to z/OS.
  2. Enter ISPF and open/check out source code from the SCLM repository (or PDS).
  3. Edit the source code to make necessary modifications.
  4. Submit JCL to build the application and do a test run.
  5. Switch to SDSF to view the running job status.
  6. View the job output in SDSF to check for errors.
  7. View the dump output to find bugs.1
  8. Re-run the compile/link/go job and view the status.
  9. Check the validity of the job output.
  10. Save the source code in SCLM (or PDS).

Some mainframe application programmers have now switched to the use of Interactive Development Environment (IDE) tools to accelerate the edit/compile/test process. IDE tools such as the WebSphere® Studio Enterprise Developer are used to edit source code on a workstation instead of directly on the host system, to run compiles "off-platform," and to perform remote debugging.

The use of the IDE is particularly useful if hybrid applications are being built that employ host-based programs in COBOL or transaction systems such as CICS® and IMS™, but also contain a Web browser-like user interface. The IDE provides a unified development environment to build both the online transaction processing (OLTP) components in a high-level language and the HTML front-end user interface components. Once the components are developed and tested, they are packaged into the appropriate deployment format and passed to the team that coordinates production code deployments.

Besides new application code, the application programmer is responsible for the maintenance and enhancement of existing mainframe applications. In fact, this is the primary job for many high-level language programmers on the mainframe today. And, while most z/OS customers are still creating new programs with COBOL or PL/I, languages such as Java™ have become popular for building new applications on the mainframe, just as on distributed platforms.

However, for those of us interested in the traditional languages, there is still widespread development of programs on the mainframe in high-level languages such as COBOL and PL/I. There are many thousands of programs in production on mainframe systems around the world, and these programs are critical to the day-to-day business of the corporations that use them. COBOL and other high-level language programmers are needed to maintain existing code and make updates and modifications to those programs.

Also, many corporations continue to build new application logic in COBOL and other traditional languages, and IBM continues to enhance the high-level language compilers to include new functions and features that allow these languages to continue to exploit newer technologies and data formats.

1 The origin of the term "programming bug" is often attributed to US Navy Lieutenant Grace Murray Hopper in 1945. As the story goes, Lt. Hopper was testing the Mark II Aiken Relay Calculator at Harvard University. One day, a program that worked previously mysteriously failed. Upon inspection, the operator found that a moth was trapped between the circuit relay points and had created a short circuit (early calculators occupied many square feet, and consisted of tens of thousands of vacuum tubes). The September 9, 1945 log included both the moth and the entry: "First actual

Go to the previous page   |   Go to the next page




Copyright IBM Corporation 1990, 2010