id stringlengths 14 14 | text stringlengths 3 7k | source stringclasses 1
value |
|---|---|---|
315458b74590-1 | CA InterTest for CICS - *DWARF* FILE ABEND DETECTED BREAKPOINTCOMMAND ===>
Program= COBDEMO Option # Stmt # Margin= 07
Search=
-------------------------------------------------------------------------------
____... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5716549f02f2-0 | InterTest™ and SymDump ® 11.0
---------+---------------------------------------------------------------------
_ 000415 IF TASKNUM = 2
_ 000416 MOVE 'DMAPSUM' TO MAPNAME. U 000417 IF TASKNUM GREATER 2
_ 000418 GO TO SEND-END-MSG. ...
Note the U to the left of the highlighted statement. It ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5716549f02f2-1 | or R to remove option(s).
Option Description Attributes
_ - COBDEMO Program monitor entry IBMCOB 5.2
_ - |-.ANY User monitoring options Active
| Waiting at breakpoint Task 00101, UBP since 06:39 a.m.
| Symbolic listing file *DWARF*_
- |-UBP... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
168c5648b388-0 | InterTest™ and SymDump ® 11.0
Resume Program Execution
Follow these steps:
1.Press PF5 to continue program execution.
InterTest for CICS resumes program execution. COBDEMO displays a screen confirming that you have successfully
corrected the ASRA.
2.Press Enter.
COBDEMO displays the following screen:
******************... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
168c5648b388-1 | View the data in the AutoKeep Display window.
Modify main storage
Overtype the value in the Keep Window or type D to the left of a variable. Place the cursor under the variable and
press Enter for a CORE Main Storage display. On the CORE screen, overtype the values and press Enter.
Set an uncondition
al "before" breakp... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
747173e757c3-0 | InterTest™ and SymDump ® 11.0
Remove a breakpoint from the Source Listing Display
On Source Listing, overtype U with X and press Enter.
Resume program execution
Use the RESUME command or PF5.
DWARF FAQ
This page contains frequently asked questions regarding DWARF and its integration into InterTest.
How long has DWARF b... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
747173e757c3-1 | selected SYMBOLIC option.
How do I report a DWARF issue?
Open a regular support ticket through https://support.broadcom.com/ and indicate that it is related to DWARF.
Does the TEST(SOURCE) compiler option cause any performance issues, such as the compile step running
longer or the load module take up more space in my ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
117bacff0691-0 | InterTest™ and SymDump ® 11.0
DWARF support was introduced only for InterTest for CICS. SymDump does not have DWARF support.
How does DWARF affect my compile listings stored in Endevor ?
There is no impact at all. The only change to your compile listing is the presence of the TEST(SOURCE) option in the list
of used com... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
117bacff0691-1 | From your IBM installation
•User ID
•z/OS host name
From InterTest
•Path to the file containing Testing Tools server settings to be imported. If the application was installed properly, you
have a set of servers that are properly configured for your site.
•InterTest for CICS PROTSYM data set names
For the CICS demo... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
42a55939623b-0 | InterTest™ and SymDump ® 11.0
•Select the version that you want the mainframe debugger to use and click Use.
•If you do not want to monitor the file, select Do Not Monitor.
•For batch applications, you can click Abend Stop to end the debugging session.
Use this feature to maintain synchronized processing at all times.
... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
42a55939623b-1 | and configuration details.
F1 Support
You can access online Help for most (but not all) window controls by placing the focus on the dialog or control and
pressing F1.
If the control is located in the InterTest main window, the Help view is activated automatically and a keyword search
targeting text in the online docume... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
35ea563d0954-0 | InterTest™ and SymDump ® 11.0
Visual Debugger
The Visual Debugger provides a visual representation of a running CICS COBOL transaction or COBOL batch program.
Using this, you can view the trace data that is represented by the graph structure to become better oriented with the
execution flow.
Demo Source Programs
InterT... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
149bd58e267b-0 | InterTest™ and SymDump ® 11.0
Usually, only one instance of a particular type of view may exist within the main window. Views can appear by themselves
or stacked with other views in a tabbed notebook. To activate one of these views, click the appropriate tab. Only one view
is active at one time, with the exception of t... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4c0dd4c42409-0 | InterTest™ and SymDump ® 11.0
NOTE
Some view toolbars include a Menu button, shown as an inverted triangle, that contain actions for the view.
Perspectives
The Eclipse UI has one perspective for InterTest and another for SymDump . You can switch from one product to the other
without closing the Eclipse UI, but you must... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4c0dd4c42409-1 | Keeps track of general register values during a debugging session for Assembler programs.
Servers
Displays the servers that have been defined for InterTest to communicate with the mainframe.
Session Data
Keeps track of session-related information during a debugging session for CICS programs.
1363 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
1ce5f3c5214c-0 | InterTest™ and SymDump ® 11.0
Statement Trace
Displays a trace of previously executed statements.
Tasks
Displays the tasks available for the currently active program.
Watch Data
Keeps track of variables and other program-related information during a debugging session.
Use views to navigate a hierarchy of information (s... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
d674e8095ad4-0 | InterTest™ and SymDump ® 11.0
Figure 1: Debug-EclipseUI
Connect to a Server
Before you begin debugging a program, you must connect to a server. You can import server setting and you can add new
server connections to the Eclipse UI.
1365 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
bf463f402792-0 | InterTest™ and SymDump ® 11.0
Import Broadcom Testing Tools Server Settings
Connect to a Testing Tools server before, start a debugging session. The GUI component runs on Windows and the
debugging session runs on z/OS. This server provides the communication between the Eclipse UI and the mainframe
platform.
You may ne... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
bf463f402792-1 | Port
Specifies the TCP/IP port number of the server. If there is a default port number displayed, verify it is correct. The
port number is updated in the Preferences dialog.
•For a CICS region -- This field must be the port number configured in the CICS region.
•For a Testing Tools server -- This field must be the port... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
703d65cbe3ea-0 | InterTest™ and SymDump ® 11.0
(Optional) Save Password
Specifies whether you want to save the password. If you save the password, the application preloads the saved
password into the Logon dialog whenever you are prompted to enter your user ID and password. Until the
password is deliberately reset or a logon fails, you... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
703d65cbe3ea-1 | 2.Specify a name for your project in the Project Name field.
TIP
Tip: Specify Basic Demo in the Project Name field for the Eclipse UI tutorial. The rest of this procedure uses
this demo value.
3.Check the Use default location box if it is not already checked.
4.Select Basic Demo from the InterTest Server drop-down ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
209c63707a4c-0 | InterTest™ and SymDump ® 11.0
Configure the Debug Settings
Before you execute a program, set the debug settings for your project. The debug settings dialog is different for CICS and
batch applications. This dialog is also displayed when you start the program execution.
Configure Debug Settings for CICS Applications
Fol... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
209c63707a4c-1 | provided by your InterTest administrator.
Dataset Type
Describes the type of data set. Select IBM PDS, or the data set type appropriate to the one provided by your
InterTest administrator.
Job Step Name
Describes the name of the job step. Type Step1 .
PROCLIB List
Leave empty.
Converted/Submit JCL Dataset(Member Name)
... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
db1fd1e6191c-0 | InterTest™ and SymDump ® 11.0
7.Click the Convert JCL button.
The converted JCL is placed in HLQ.MYJCL(BATCHDMO).
8.After the JCL conversion is complete, click the Edit JCL button to edit the converted JCL.
The Edit JCL dialog opens.
9.Make the following changes to the Edit JCL dialog:
–Change the job card to conform w... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a274abda76f9-0 | InterTest™ and SymDump ® 11.0
Select the Source Program to Monitor
After configuring your session, specify the program that you want to monitor. As part of monitoring a program, the
application automatically prevents all abends during execution.
Follow these steps:
1.Verify that the program to be debugged has been comp... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ed6044cb6667-0 | InterTest™ and SymDump ® 11.0
7.Scroll down through the table until you reach the program that you want to use. Select the program by checking the
box next to it.
8.If the Into folder box is empty, click the Browse button, and select the Basic Demo folder to import the program into.
The name Basic Demo appears in the I... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
d52840ac281b-0 | InterTest™ and SymDump ® 11.0
How to Use the Outline View
The Outline view displays an outline of the program that is currently active in the Program Listing area and lists the
structural elements. This makes it easier to display any section of your program. The contents of the Outline view are
specific to the active p... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
d52840ac281b-1 | 2.Ensure that the debug settings are defined as you want them.
3.Click Connect.
InterTest notifies InterTest for CICS that your program is ready for debugging .
4.Go to the mainframe CICS display (green screen), and type in the transaction identifier of the demo program.
5.Press Enter.
The Welcome screen appears.
6.Pre... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b7cbfbcdb95c-0 | InterTest™ and SymDump ® 11.0
1.Return to the InterTest Eclipse UI to continue with your debugging session. Notice that the InterTest Debug view now
displays the debug status as Debugging.
Analyze Abends
When a program encounters an error during execution, an abend occurs. See Abend Analysis with the Eclipse UI for mor... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
2a4ba27227e2-0 | InterTest™ and SymDump ® 11.0
3.Click the Resume Debugging button
on the InterTest Debug view toolbar.
The demo program halts at the unconditional breakpoint you set previously in this tutorial. The InterTest Debug view
window updates to reflect the reason for the stop
4.Click the Resume Debugging button again.
The pro... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
2a4ba27227e2-1 | occurs, or the application halts a program at a breakpoint that you have previously set.
1374 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
dc2faac5198b-0 | InterTest™ and SymDump ® 11.0
When an abend occurs:
•A small blue arrow appears in the ruler to the left of the line causing the error, and the line is highlighted.
•The status in the InterTest Debug view now displays a diagnostic message. This message explains that the error was
caused by improperly formatted data.
TI... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
dc2faac5198b-1 | Expression, and hex value at that offset.
Look at the contents of TASKNUM. Confirm that the value stored in TASKNUM is not a valid packed decimal value by
examining its current value in the Auto Data view; that is, its value prior to the execution of the AP statement that triggered
the ASRA. Instead, it contains low-va... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
edebd13ba49d-0 | InterTest™ and SymDump ® 11.0
Follow these steps:
1.Right-click the variable TASKNUM in the Auto Data view. Click Change Value.
The Data View Value dialog opens.
2.Select the Display value button.
3.Change the value of TASKNUM displayed in the box to a numeric zero (type a numeric zero).
NOTE
You do not have to know th... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0c670fffd953-0 | InterTest™ and SymDump ® 11.0
Breakpoints
A breakpoint is an intentional stopping or pausing place in a program, put in place for debugging purposes.
When you open or activate a program listing in the Program Listing area, the breakpoints added to that program are
marked with a blue circle icon. When the mouse hovers o... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
74fcfe4edbf6-0 | InterTest™ and SymDump ® 11.0
When to Use Breakpoints
You can set breakpoints at any time -- before you execute the program and when the program is stopped. Although where
you decide to set breakpoints depends on the specifics of your program, you might want to set breakpoints in the following
places:
•At the beginning... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
affd05c0d638-0 | InterTest™ and SymDump ® 11.0
4.Right-click the ruler to the left of the line you have selected (statement 484), and select Add Breakpoint.
1379 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b8412ce69573-0 | InterTest™ and SymDump ® 11.0
A blue circle appears to the left of the ruler, and a blue mark appears in the right-side vertical ruler. By default, the Add
Breakpoint dialog adds an unconditional breakpoint if the listing line is within the Procedure Division, and a variable
change breakpoint if the line is within the ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
edf16034d515-0 | InterTest™ and SymDump ® 11.0
5.Click Finish.
The dialog closes and the breakpoint displays in the Breakpoints view as a conditional breakpoint.
6.Repeat steps 1 through 5, and make statements 480 and 482 unconditional breakpoints.
7.Change the breakpoint at statement 484 back to an unconditional breakpoint.
Change Bre... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
c4120ca0281d-0 | InterTest™ and SymDump ® 11.0
2.Click the Conditional breakpoint option button.
3.Change the fields as follows:
Left Side - LOOP-OUT
Operator - GT - Greater Than
Right Side - x'00'
Note : Character literals do not need to be prefixed with a C. The system automatically recognizes them as characters.
Thus, 2 is treate... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0895bab5758e-0 | InterTest™ and SymDump ® 11.0
You can use the Eclipse UI delete several breakpoints at one time, follow these steps:
Click the first breakpoint on the Breakpoints view, hold down the Shift key, then click the last breakpoint you want to
delete.
The breakpoints you select are highlighted.
•Right-click and select Delete ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0895bab5758e-1 | A new bookmark is set at the selected statement. This is indicated by a small rectangle
appearing
next to the scroll bar. The Bookmarks view displays the details of the new bookmark.
In the Bookmarks view, after you add a bookmark, you can double-click the bookmark to open the program listing, if not
already opened. Th... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
313c7da19cd1-0 | InterTest™ and SymDump ® 11.0
How to Remove Bookmarks
Once you have created and used bookmarks, it is a good idea to delete them, so you do not clutter up your program or
the Bookmarks view.
Select the line of code that contains a bookmark, and perform one of the following steps:
•From the program listing left-hand rul... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
313c7da19cd1-1 | default part of InterTest perspective.
If you have hidden the Visual Debbuger view and want to show again, go to Window | Show View | Other .
To customize your visualization
1.Expand the InterTest node and choose Visual Debugger.
2.Click OK.
1384 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b4fec29c7506-0 | InterTest™ and SymDump ® 11.0
3.Adjust the size and the position of a new view according to your
preferences.
4.Enable the 'statement trace' option in order to get the data that you need for the visualization during debugging.
1385 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3ded973b8d93-0 | InterTest™ and SymDump ® 11.0
Batch project: Ensure that the Statement Trace and Notify at End of Task options are checked in the debug
settings.
CICS project:
Ensure that the corresponding checkboxes are checked in the program settings of each monitored program.
1386 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3ca212320fee-0 | InterTest™ and SymDump ® 11.0
5.Submit a job for debugging (Batch project) or connect to a CICS region and run a CICS transaction.
The graph appears once you start getting statement trace information.
The graph is dynamically updated until you hit a breakpoint or the execution finishes.
Statement Trace Visualization
Th... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
aae3837dc903-0 | InterTest™ and SymDump ® 11.0
Programs Level
On the programs level, each node represents a monitored program that was or is currently being executed. The executed
program is marked with a blue border.
The arrows represent transfers of controls between the programs. The number on an arrow shows how many times the
contro... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8e4e147ed93b-0 | InterTest™ and SymDump ® 11.0
Paragraphs Level
The paragraph level nodes represent the executed paragraphs or the paragraphs in the middle of execution of the
program. It also visualizes other monitored programs the control was transferred to or from during the execution. The
programs nodes have a darker background tha... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
88414257a28f-0 | InterTest™ and SymDump ® 11.0
Visualization of an Entry Point
The node that represents the first program executed in the debugging session is marked with a flag.
When the first executed program is visualized on the paragraphs level, the first paragraph executed in the debugging
session is also marked with the flag.
Dyn... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
47023864aced-0 | InterTest™ and SymDump ® 11.0
NOTE
The GET-DATE paragraph is shown because statement 000028 CALL 'DEMOGDAT' belongs to this specific
paragraph.
Example Image Breakpoint at 000034:
At the second breakpoint, the graph view is updated.
1391 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
610160e66a48-0 | InterTest™ and SymDump ® 11.0
NOTE
Generally the positions of the nodes are not determined and can differ every time the graph is redrawn.
Navigate Execution Flow History
Navigate through the execution flow history to analyze code behavior with ease.
The footer of the graph view displays a slider with the total number... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a78b4502ba3b-0 | InterTest™ and SymDump ® 11.0
Click and drag the slider back along the timeline to control which part of the statement trace is visualized. This
functionality allows you to play back every event that has taken place since the beginning of the debugging session. This
playback is useful if you want to see what was execut... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
98e0cd985c70-0 | InterTest™ and SymDump ® 11.0
Navigate in the Editor using Graph Elements
1.Selecting a node that represents a program positions the cursor to the beginning of that program. The corresponding
tab in the editor automatically opens and becomes active.
2.Selecting a node that represents a paragraph positions the cursor to... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
c710e997b87e-0 | InterTest™ and SymDump ® 11.0
Navigate through the Graph using the Cursor
1.Placing the cursor on any line will highlight the corresponding node (program or paragraph, depending on the current
level of the graph) and position it at the center of the Visual Debugger view.
Programs Level:
Paragraphs Level:
1395 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a9ba466c1c22-0 | InterTest™ and SymDump ® 11.0
2.Clicking on the Position at the breakpoint will have the same effect as manual placing of the cursor on the
corresponding line.
Zoom and Pan
In order to better view a graph that expands across the given user interface space, you can either click and drag desired
nodes away from overlappi... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
40ad5e215857-0 | InterTest™ and SymDump ® 11.0
Zoom In and Out
You can zoom in and out within the view to focus on a specific area of the graph by using the control in the bottom right
corner.
Pan the Graph
If you have a larger graph that expands outside of the given view, you can use panning to manipulate the image.
Node Dragging
You ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
fd41e17813bf-0 | InterTest™ and SymDump ® 11.0
Save and Load Session Data
You are able to easily store trace data from a session that you are currently debugging into a .trace file. You can load data
without the need to re-run the debugging session or connect to a mainframe.
Save a Debugging Session
To save a debugging session, follow ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ac72b374c74d-0 | InterTest™ and SymDump ® 11.0
2.Specify the name of the trace file in the field and click OK.
Your debugging session is saved.
Load a Debugging Session
To load a debugging session, follow these steps:
1.Right click to load a debugging session. Alternatively, you can press L while the View is active.
1399 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
286111eee251-0 | InterTest™ and SymDump ® 11.0
1400 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5077b38bb2eb-0 | InterTest™ and SymDump ® 11.0
2.Select the session you want to load from the Trace Resource Selection window and click
OK.
NOTE
The projects currently being debugged are not listed.
1401 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a9de299db193-0 | InterTest™ and SymDump ® 11.0
The graph is redrawn to represent the loaded debugging
session.
NOTE
Generally the positions of the nodes are not determined and can differ every time the graph is redrawn.
1402 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
522f2986e0d3-0 | InterTest™ and SymDump ® 11.0
Integrating
Integrate InterTest and SymDump with other solutions to extend the capabilities of the product and to expand the range of
use cases.
InterTest and SymDump features the following integrations:
Symbolic Support
Use source code information from application programs to enhance and ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
522f2986e0d3-1 | •Set conditional breakpoints based on variable values.
•View a trace of all previously executed source statements.
Symbolic support eliminates the need to manually locate variables in storage, compute program offsets for source
statements, or determine which statements were executing. You do not need to keep program li... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8bc3e833a6d7-0 | InterTest™ and SymDump ® 11.0
How Does Symbolic Support Work?
When your application programs are compiled or assembled, symbolic information about the program is written to various
reports in the output listing. A program that is called a postprocessor reads the output listing, collects the symbolic
information, and st... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8bc3e833a6d7-1 | paragraph might be moved to another paragraph. When this type of optimization occurs, the resulting object program and
corresponding listing may not accurately represent the relationship between the source statements and their generated
object code, or even between a paragraph label and the statements contained within ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8bc3e833a6d7-2 | •Unexpected or out of sequence highlighting of statements when single-stepping
•Incorrect identification of the statement which contains the abending object code
1404 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a06a5952523b-0 | InterTest™ and SymDump ® 11.0
Also, application abends may result from the use of the SKIP, GO stmt# or CS stmt# commands because the optimized
object code may have register requirements that do not support changes to the flow of control. These commands should
be avoided when debugging an optimized program.
For the bes... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a06a5952523b-1 | the symbolic information into the PROTSYM file.
The postprocessor also supports the integrated CICS and SQL preprocessors of PL/I for z/OS. However, programs that
contain EXEC SQL INCLUDE statements for user-defined members still require a separate precompile step. (EXEC SQL
INCLUDE statements for SQLCA and SQLDA are s... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a9bb3955c066-0 | InterTest™ and SymDump ® 11.0
NOTE
The PROTSYM file cannot reside in the LSR pool.
Sharing PROTSYM Files
Your PROTSYM files can be shared between Broadcom products and across multiple systems and environments. A
single PROTSYM file contains symbolic information for both CICS and batch programs.
Use RESERVE and DEQ mac... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a9bb3955c066-1 | documentation for that product.
Creating a PROTSYM File
CAVHPROT
Member CAVHPROT in CAI.CAVHJCL contains sample JCL for defining and initializing a PROTSYM file. The
INITIALIZE, UPDATE, DELETE, PURGE, and RELOAD functions are protected by a password or external security.
The default password is 12345678. To modify the ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
86d1016b630c-0 | InterTest™ and SymDump ® 11.0
SET MAXCC=0
DEFINE CLUSTER (NAME($PROTSYM$) -
REC($RECS$) -
CISZ(2048) /* DO NOT CHANGE */ -
VOLUME($SYMVOL$) -... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
86d1016b630c-1 | 1.Do not allocate any secondary space.
2.The space required depends on many factors including the size of your programs, the number of variables and labels,
the average length of their names, and the LISTER options used for loading symbolic information. We recommend
an initial allocation of 10,000 records. You can allo... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
9d6665ff1586-0 | InterTest™ and SymDump ® 11.0
Adding Symbolic Information
You can add symbolic information to your PROTSYM files using the following postprocessors:
IN25SYMC
Loads symbolic information for programs compiled using:
•OS/VS COBOL version 2.3 plus PTF8 or higher
•Optimizer/II
IN25COB2
Loads symbolic information for program... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
9d6665ff1586-1 | IN25SYMC JCL
The following table describes the DD statements used by IN25SYMC:
DDname Description
STEPLIB The load library containing IN25SYMC.
1408 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3c1af8dd59e5-0 | InterTest™ and SymDump ® 11.0
INPUT The listing that was written to SYSPRINT by the OS/VS COBOL
compiler, or by Optimizer/II , during compilation.
OUTPUT All or part of the original compiler listing is written to this file,
depending on your request.
MESSAGE Any messages produced by IN25SYMC during postprocessing are
w... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3c1af8dd59e5-1 | with InterTest for CICS, you must specify the name of the CICS program definition, or when using composite support,
specify the monitor name.
The following example shows an in-stream parameter statement that you can use to save symbolic information using the
name ORDEDIT:
//CARDS DD *
ORDEDIT
/*
Controlling Print... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0998e4bd0fe0-0 | InterTest™ and SymDump ® 11.0
,CUTPRINT=REF
Print the listing up to, but not including, the cross reference of data names.
The following sample parameter statement saves symbolic information for program ORDEDIT and prints only the source
code section of the compiler listing:
//CARDS DD *
ORDEDIT,CUTPRINT=MAP
/*
... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0998e4bd0fe0-1 | when executing IN25SYMC.
Setting Data as Nonpurgeable
You can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,
the data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you can
delete the data by program name. ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
1a590490ce3f-0 | InterTest™ and SymDump ® 11.0
/*
Required OS/VS COBOL Options
The following compiler options are required to load symbolic information for OS/VS COBOL programs into the PROTSYM
file:
Option Description
CLIST or PMAP Produces a condensed Procedure Division map or full Assembler
Procedure Division map.
DMAP Produces a... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
1a590490ce3f-1 | //IN25PARM EXEC PGM=IN25PARM,REGION=512K,
// PARM='&MEMBER,LISTER=&LISTER,CUTPRINT=&CUTPRINT'
//STEPLIB DD DISP=SHR,DSN=CAI.CAVHLOAD
//CARDS DD DSN=&&CARDS,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(TRK,(1,1)) ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e42b5c963514-0 | InterTest™ and SymDump ® 11.0
//MESSAGE DD SYSOUT=*
//
You can override the following procedure variables:
Variable Description
PROTSYM Specifies the name of the symbolic file being updated.
NAME Speci... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e42b5c963514-1 | compile step is written to SYSOUT.
3.Add a new IN25PARM step following your compile step to generate the parameter statement for the postprocessor.
4.Add a new IN25SYMC step to postprocess the listing from the compile step. The INPUT DD on this step refers to the
same file as the SYSPRINT DD from the compile step.
5.Ad... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e94dbb9f7279-0 | InterTest™ and SymDump ® 11.0
//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR
//CARDS DD DSN=&&CARDS,DISP=(NEW,PASS),
// UNIT=SYSDA,SPACE=(TRK,(1,1))
//*
//* POST-PROCESS THE COMPILER LISTING
//*
//SYM ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e94dbb9f7279-1 | must point to the same data set.
•If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,
delete this DD statement, and add SYM.CARDS DD to your invoking JCL member.
IN25COB2
Use program IN25COB2 to load symbolic information for programs compiled using any of the follow... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ff660819650b-0 | InterTest™ and SymDump ® 11.0
IN25COB2 JCL
The following table describes the DD statements used by IN25COB2:
DDname Description
STEPLIB The load library containing IN25COB2.
INPUT The listing that was written to SYSPRINT by the COBOL compiler,
or by Optimizer/II , during compilation.
OUTPUT All or part of the original ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ff660819650b-1 | Quality and Testing Tools products to locate the symbolic information and is displayed when listing the contents of your
PROTSYM.
In most cases, this name should be the same as the PROGRAM-ID. However, when loading symbolic information for use
with InterTest for CICS, you must specify the name of the CICS program defin... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
55a997d9e60d-0 | InterTest™ and SymDump ® 11.0
,CUTPRINT=ALL
Do not print any of the compiler listing.
,CUTPRINT=MAP
Print the listing up to, but not including, the Data Division Map report.
,CUTPRINT=REF
Print the listing up to, but not including, the cross reference of data names.
The following sample parameter statement saves symbol... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
55a997d9e60d-1 | •To reduce overhead and save space in your PROTSYM file, we recommend that you specify LISTER=MAP
when executing IN25COB2 unless compiling with Optimizer/II, which requires LISTER=MMAP.
Setting Data as Nonpurgeable
You can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as n... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b95889107395-0 | InterTest™ and SymDump ® 11.0
The following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,
saves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge
interval batch run.
//CARDS DD *
ORDEDIT,LISTER=A... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b95889107395-1 | INTERTST Required only when optimizing programs that are monitored using
InterTest for CICS.
MAP or MMAP Produces a Data Division map or merged Data Division map.
MMAP Required when optimizing programs that are monitored using
InterTest for CICS.
MOFFSET Produces a merged Procedure map.
NONUM Suppresses compiler-genera... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4281479f491f-0 | InterTest™ and SymDump ® 11.0
To use symbolic references in COBOL, you must declare at least one data item in working storage.
Executing IN25COB2 as a Standalone Program
Member CAVHCOB2 in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25COB2 as a standalone
batch job. Use this member to load symbolic i... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4281479f491f-1 | //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)
//OUTPUT DD SYSOUT=*,DCB=(LRECL=133,BLKSIZE=3990,RECFM=FBA)
//MESSAGE DD SYSOUT=*
//
You can override the following procedure... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5c8334e1781c-0 | InterTest™ and SymDump ® 11.0
Adding IN25COB2 to Your COBOL Procedure
To automatically update the symbolic information in your PROTSYM file whenever a COBOL program is compiled, you
can add a postprocessor step directly to the JCL procedure that you use to compile your programs.
NOTE
These same steps also apply to the ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5c8334e1781c-1 | //*
//* GENERATE THE PARAMETER STATEMENT FOR IN25COB2
//*
//CARDS EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT), <= 3
// PARM='&MEMBER,LISTER=ALL'
//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR
//CARDS DD DSN=&&CARDS,DISP=(NEW,PASS)... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
036f46d01c00-0 | InterTest™ and SymDump ® 11.0
•If the SYSPRINT DD on your compile step refers to a permanent data set, the INPUT DD for IN25COB2
must point to the same data set.
•If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,
delete this DD statement, and add SYM.CARDS DD to y... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
036f46d01c00-1 | The following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the
listing, and saves the listing up to, but not including, the Data Division map report to the PROTSYM file:
//CARDS DD *
ORDEDIT,CUTPRINT=ALL,LISTER=MAP
/*
NOTE
•If the LISTER parameter is omitted, no... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f4b98fa069bf-0 | InterTest™ and SymDump ® 11.0
delete the data by program name. See Maintaining a PROTSYM File for instructions on deleting data from the symbolic
file.
To mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.
The following sample parameter statement saves symbolic information... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f4b98fa069bf-1 | written to these files.
PROTSYM The file to which the symbolic information is written.
CARDS The input control statements that define the request.
NOTE
If you are adding a new step for IN25SYMP to a JCL procedure, use program IN25PARM to write your input
control statements to the CARDS file.
IN25SYMP Options
Options ar... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0bfab36fa116-0 | InterTest™ and SymDump ® 11.0
//IN25PARM EXEC PGM=IN25PARM,PARM='parameter statement'
//STEPLIB DD DISP=SHR,DSN=CAI.CAVHLOAD
//CARDS DD DISP=(,PASS),DSN=&&CARDS,UNIT=SYSDA,SPACE=(TRK,(1,1))
Parameter statements in the CARDS DD must begin in column 1.
The program name is the only required field on the parameter... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.