Trap Diagnostic Facility
(TDF)
TDF Methodology
• Traditional Debuggers use recovery
(ESTAEX or FRR) requiring the
application to modify its recovery stra...
TDF Methodoloy
• One server required per LPAR and only
one server can be active per LPAR
• The server creates
– System PC ...
TDF User Interface
In the following screen example, the TDF
server has been started and a test program,
job TDFHOOK and pr...
TDF User Interface (UI) Flow
When a suspended task is selected,
•The TDF UI PCs to server to connect to the
suspended task...
TDF User Interface (UI)
From the initial connection state screen, you
can issue such as a D command to display
application...
TDF User Interface
• Large display requests (more data than
can fit in a screen) are broken into multiple
requests.
• If a...
TDF User Interface
You can also use the T command to step
through program execution. The T display
automatically shows the...
TDF UI Methodology
The final display mode is scrolling. In this
mode, all command results are displayed in
the sequence is...
TDF UI Methodology
You can terminate a UI session as follows:
•Press PF3. The API disconnects the UI and
places the applic...
Tdf linked in
Tdf linked in
Tdf linked in
Tdf linked in
Tdf linked in
Upcoming SlideShare
Loading in...5
×

Tdf linked in

165

Published on

Demonstration of MVS skill set involving cross memory server application

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
165
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Tdf linked in

  1. 1. Trap Diagnostic Facility (TDF)
  2. 2. TDF Methodology • Traditional Debuggers use recovery (ESTAEX or FRR) requiring the application to modify its recovery strategy • TDF uses the TRAP instruction and does not require modifications to application recovery strategy
  3. 3. TDF Methodoloy • One server required per LPAR and only one server can be active per LPAR • The server creates – System PC routines callable from any address space – Shared (64 bit) memory object for communication – API to connect/disconnect from debugging session
  4. 4. TDF User Interface In the following screen example, the TDF server has been started and a test program, job TDFHOOK and program TSTTDFHK has been started with a TDFHOOK call. In this example, the test program is selected to start a UI session.
  5. 5. TDF User Interface (UI) Flow When a suspended task is selected, •The TDF UI PCs to server to connect to the suspended task •TDF API connects the task so that no other UI can connect to it and replies with the current program state •TDF UI display the state as follows:
  6. 6. TDF User Interface (UI) From the initial connection state screen, you can issue such as a D command to display application storage
  7. 7. TDF User Interface • Large display requests (more data than can fit in a screen) are broken into multiple requests. • If an abend occurs, the request is ended • If any command is entered, the request is ended • At the end of a screen, if more data is required, press enter for the next screen until the request has completed
  8. 8. TDF User Interface You can also use the T command to step through program execution. The T display automatically shows the current program state. It highlights modifications to registers and branching instructions as follows:
  9. 9. TDF UI Methodology The final display mode is scrolling. In this mode, all command results are displayed in the sequence issued. The following screens demonstrate scrolling.
  10. 10. TDF UI Methodology You can terminate a UI session as follows: •Press PF3. The API disconnects the UI and places the application back in the suspended queue. •Enter the E command to disconnect and release the application. It will continue uninterrupted execution.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×