Batch link lets you debug applications from a terminal while they execute in batch.
The batch link facility offers the following advantages over standard foreground debugging:
Executing an application in foreground requires that all data sets used by the application be first allocated in foreground. While the application provides a JCL conversion and allocations facility for this purpose, the allocation and de-allocation process can complicate the debugging process. Applications debugged using batch link are executing in batch, so no foreground allocations are required.
Sometimes an application is executed as part of a multi-step job stream and one or more leading steps must be executed before the application can run. Batch link allows debugging of any job step executing in batch, and therefore permits the normal completion of leading steps prior to debugging. After debugging, any trailing steps can be completed prior to job termination.
Because batch link permits the execution of leading steps, applications can use temporary files created by a prior step. The job stream can then delete these files when they are no longer needed.
Batch link supports the debugging of multiple steps within the same job stream. When debugging of any step completes, the job continues as usual with the execution of the following step until end of job. Each batch link user controls which steps will be debugged within a job stream before the job is submitted.
At any time during a batch link debugging session, you can suspend the session and disconnect the terminal from the batch debugging session. This lets the debugging session be retrieved by another (or even the same) user at a later time. This facilitates the transfer of the debugging session from one user to another without terminating and restarting the application.
This section contains the following topics:
|
Copyright © 2013 CA.
All rights reserved.
|
|