Remote Edit/Compile/Debug

The applications for this scenario can be CICS, batch, TSO, or IMS/TM (running under BTS). Applications can access DB2, VSAM, DL/I, QSAM, and virtually any other form of data. Examine the distribution of the tasks between the host and workstation, the benefits of this scenario, and the costs to set it up.

Which Tasks are Done Where
"X" indicates the primary platform for the task
TaskHostWrkS
Edit programs on the workstation.
The program files are transparently retrieved from and saved to the host. This includes the source, JCL, and held job SYSOUT. The source remains on the host.
 X
Compile the programs.
Compilations to create load modules are done on the host but initiated from the workstation via MVS job submission.
You can also perform a syntax check of your source files on the workstation with the source on the host; COPY files are retrieved from the host. Neither DB2 nor CICS is required on the workstation for the syntax checking.
X 
Test and debug the compiled programs.
Execution takes place on the host. Batch execution is initiated from and controlled from the workstation (CICS transactions must be started from a 3270 emulator session). The debugger runs cooperatively with a GUI on the workstation and the engine on the host.
X 
Notes
Benefits
  • Be more productive with your editing tasks with the language-sensitive VisualAge COBOL editor. It parses the source as you enter it, giving a visual presentation. The learning curve is not as steep as you might think: the editor is customizable and can be made to look and feel like your favorite editor while retaining all the strengths of a workstation editor.
  • Save time: compile-time error messages appear right in your edit session following the line on which the error occurred.
  • Reduce the number of compile jobs you have to submit by using the VisualAge COBOL's ANALYZE option to easily perform syntax check compiles on the workstation, shaking out syntax errors before submitting compiles to the host compiler.
  • Reduce the number of batch debugging jobs and ease your debugging tasks by using a GUI on the workstation even when your program is executing on the target host - interactively.
  • Use your existing jobs for system test with the benefit of workstation organization.
  • Use this scenario no matter what kind of data your program accesses, even for your applications that include COBOL calling or being called by Assembler programs.
  • Host programmers get an easy start on becoming familiar with the workstation environment.
Costs
  • Host systems programmers need to be involved for configuration of the communications.
  • Network traffic will increase.

Continue viewing scenarios or view requirements:
  • add this scenario to a list and choose another,
  • get the requirements for any that you have selected, or
  • clear any prior selections and start a new list

to add this scenario to your list

to clear selections and start over
Turn to a different scenario
Click on a number to see another scenario (4 and 5 TBD).
After selecting a scenario or scenarios, to detail your environment and see the software requirements and configuration instructions
[ Back to main page]

©1998 IBM Corporation