Hi Joe,

In z/XDC, the "debugging TCB" and the "debugging PSATOLD" are the same as the program's. There is no distinction.

Also, in z/XDC the LIST TCBS command shows all of the aspace's TCBs in an indented display matching the subtasking structure, with the current TCB plainly marked. Example:

    XXX ===> list tcbs
       TCB#  PROGRAM NAME (ASID 0054, DBCOLE3)
    _  1     IEAVAR00
    _  2     . IEESB605
    _  3     . . IKJEFT01, JOBSTEP
    _  4     . . . IKJEFT02
    _  5     . . . . IKJEFT09
    _  6     . . . . . ISPF
    _  7     . . . . . . ISPTASK (ISPLLIB)
    _  8     . . . . . . . XXXCALL
    _  9     . . . . . . . . "Z1DCALL", CURRENT (XXXT0004) (ABEND: S0C1)
    _  10    . . . . . . . . . "PROXYTCB"
    _  11    . . . . . . . . . "PROXYTCB"
    _  12    . . . . . . . . . "PROXYTCB"
    _  13    . IEAVTSDT

To display the TCB's storage itself, just place an F on the display for TCB #9.

Or use FORMAT 21C?
Or use FORMAT .PSATOLD?
Or use FORMAT TCB#9

TCB#9 RB#1 ------------------------------------------------ - z/XDC ISPF INTERFACE -----------------------------------------------
    XDC ===> format .psatold?
_ 00000000_007BA670 0 (A.S.DBCOLE3) --- TCB#9+0, RETRYRB+88, PRIVATE+7B8670
    _        +0 @CDP
_ +0 TCB#9 007BA2D0 00000000 007B1048 007D2FD0 940C1000 55000000 7F50B100 80000000 *.#s}.....#...'.}m......."&......* _ +20 0000FFFE 007BA510 00067288 00000000 00000054 0006EBE8 00075970 00000254 *.....#v....h...........Y........* _ +40 80C8A802 125CF000 *.Hy..*0.* _ +48 0008F000 12513B70 1253A934 000A1010 000A45D0 0007D5C8 00C8C030 0006E010 *..0.......z........}..NH.H{...\.* _ +68 80C866BE 00000000 00063D88 007BA358 00000000 007FF070 00000000 007BAD90 *.H.........h.#t......"0......#[.* _ +88 007B6D90 00000000 000675EC 00000000 7FF16E44 7F50B7C0 007BA8A8 807DBCB0 *.#_............."1>."&.{.#yy.'..* _ +A8 00000000 00000000 00000000 007FC8C4 00FDDF38 00000000 00000000 00000000 *............."HD................* _ +C8 00000000 00000000 007BA7C8 00000000 7F566AC0 007BAD90 7F4E6E10 00000000 *.........#xH....".¦{.#[."+>.....* _ +E8 00000000 00000000 80000080 00000000 7F50B0D0 00000000 E3C3C240 00000000 *................"&.}....TCB ....*







At 2/2/2014 08:55 AM, Micheal Butz wrote:
Dave

Thanks I know you once explains to
Me how to find the debugged PSATOLD

Maybe XDC should have a LISTTCB
Command to display the debugged
TCB

Thanks

Sent from my iPhone

> On Feb 2, 2014, at 8:27 AM, David Cole <[email protected]> wrote:
>
> FWIW Joe, z/XDC runs in the same task that is being debugged.
> So the discrepancy with PSATOLD (between what the program sees and what the debugger displays) would not arise.
>
> Further, when z/XDC does display something that is a consequence of the debugging environment (such as extra Request Blocks on the RB queue), it will clearly label such things a "ARTIFACTS".
>
> Dave Cole

Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS:   <mailto:[email protected]>[email protected]

Home page:   www.colesoft.com
Facebook:     www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to