Sie sind auf Seite 1von 6

Work with windows and source Set and clear statement breakpoints

IBM ZOOM Expand the source window to the full A or AT Line command: set a breakpoint at the
or screen, or reduce an expanded window selected statement
Z
C Line command: clear the breakpoint at
Debug Tool ZOOM (with a cursor Expand the cursor selected window the selected statement
Terminal interface selected border
location)
F6 (with a cursor Function key: set a breakpoint at the
selected statement) cursor selected statement. If a
IBM’s Interactive Debugger for applications running in z/OS POS 509 Position the source window to breakpoint already exists at the
statement number 509 statement, clear it.
Basic Commands QUALIFY RESET Position the source window to the AT 452 Set a breakpoint at statement 452
or current statement
AT FROM 99 452 Set a breakpoint that will trigger
QUA RES th
starting with the 99 time that
FIND ‘text’ Find the next occurrence of text in the statement 452 is reached
For detailed descriptions of commands, command syntax, and or source window
command options, refer to the Debug Tool for z/OS Reference CLEAR AT 452 Clear the statement breakpoint at
F ‘text’
and Messages manual. A complete set of Debug Tool manuals or statement 452
can be obtained from the IBM Debug Tool website. F5 Function key: repeat the last find CL AT 452
www.ibm.com/software/awdtools/debugtool/ command
D Line command: disable the breakpoint
select the “Library” link at the selected statement (but do not
Run the program clear it)
Manuals: STEP Run one statement E Line command: enable the disabled
Summary of Commands, User’s Guide, Reference and or breakpoint at the selected statement
Messages, and Customization Guide STEP INTO
AT * Set a special breakpoint that will stop
F2 Function key: same as STEP at all statements
The following paragraph does not apply to the United Kingdom or STEP 25 Run 25 statements, starting with the CLEAR AT * Clear the special AT * breakpoint
any other country where such provisions are inconsistent with current statement, one at a time with or
step animation CL AT *
local law:
GO Run the program, starting with the
INTERNATIONAL BUSINESS MACHINES CORPORATION
current statement, until the next Set and clear change (watch) breakpoints
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY breakpoint or the end of the application
AT CHANGE var- Set a breakpoint that will trigger when
OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, F2 Function key: same as GO command name variable var-name changes
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON- or
RUNTO 630 Run the program starting with the
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A AT CHA var-name
current statement, until the next time it
PARTICULAR PURPOSE. Some states do not allow disclaimer reaches statement 630 (or reaches a CLEAR AT CHANGE Clear the change breakpoint for
of express or implied warranties in certain transactions, therefore, breakpoint or the end of the variable-name variable-name
application) or
this statement may not apply to you. CLE AT CHA variable-
R Line command: same as a RUNTO
name
command for the selected statement
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the JUMPTO 952 Jump to statement 952. Do not execute Set and clear program entry and exit breakpoints
information herein; these changes will be incorporated in new the current statement or any other
editions of the publication. IBM may make improvements and/or statements. The program will be AT ENTRY program- Set a breakpoint that will trigger when
changes in the product(s) and/or the program(s) described in this paused at statement 952. name program (compile unit) program-name
at any time without notice. is entered
GOTO 952 Same as a combination of JUMPTO
952 followed by a GO command CLEAR AT ENTRY Clear the entry breakpoint for program-
program-name name
Commands for working with breakpoints AT ENTRY * Set a special breakpoint that will trigger
at the entry of all programs
LIST AT Display a list of all breakpoints in the
For Use with Debug Tool Version 12 log CLEAR AT Clear the special AT ENTRY *
ENTRY * breakpoint
FINDBP Find the next statement breakpoint and
© Copyright International Business Machines Corporation position the source window to it AT EXIT program- Set a breakpoint that will trigger when
2012. All rights reserved. name program (compile unit) program-name
CLEAR AT Clear all breakpoints in the current
Revised June 30, 2012 is exited
enclave
CLEAR AT EXIT Clear the exit breakpoint for program-
program-name name
Make breakpoints conditional List variables in the log End program testing
To make a breakpoint conditional, code WHEN and a condition. L Line command in the source window: QUIT Ends debugging. Prompts with a “Are
Examples: display all variables referenced by the you sure…?” message. If accepted,
AT 502 WHEN Set a breakpoint that will trigger at selected line in the log terminates the program.
CUSTID = ‘77409’ statement 502 if the condition is true
Ln (such as L1, Line command in the source window: QQ Same as QUIT but without a prompt
when the statement is reached
L2, …) display the nth variable referenced by
QUIT DEBUG Ends debugging but the program
AT CHANGE Set a breakpoint that will trigger when the selected line in the log
continues to run from the current
CUSTID WHEN variable CUST-ID changes if the
F4 (with a cursor- Function key: display the cursor- statement
CUSTID = ‘77409’ condition is true when it changes
selected variable in the selected variable in the log
AT CHANGE Set a breakpoint that will trigger when source window)
CUSTID WHEN BAL > variable CUST-ID changes if the
LIST variable-name Display variable-name in the log QUIT DEBUG TASK Used in CICS only. Ends debugging
999 condition is true when it changes
but the program continues to run. The
LIST TITLED WSS Display all variables in the log from
DTCN or CADP profile remains active.
Monitor variables or COBOL working-storage, file, or
LIST TITLED FS linkage section, or all variables QUIT ABEND Ends debugging and terminates the
SET AUTO ON Turn on the automonitor. Variables or program with a forced abend.
referenced by the current statement LIST TITLED LS
display in the monitor window or
automatically.
Playback (step backward in a program)
LIST TITLED *
PLAYBACK ENABLE Turn on the playback recorder.
SET AUTO ON BOTH Turn on the automonitor. Variables
Consider the PLAYBACK ENABLE
referenced by both the current Change values of variables near the beginning of a program.
statement and previously displayed
Overtype the value of
statements display in the monitor PLAYBACK START Enter playback mode. The PLAYBACK
a variable in the
window automatically. This shows ENABLE command must have been
monitor window to
results automatically while stepping. entered previously. STEP commands
change the value
will step backward.
SET AUTO ON LOG Turn on the automonitor. In addition to
MOVE 987 TO varx Change the value of variables in
or displaying variables in the monitor PLAYBACK Set the direction of STEP and RUNTO
MOVE ‘ZYX’ TO var COBOL programs
SET AUTO ON BOTH window, they are also displayed in the FORWARD commands to forward
LOG log. This automatically traces variable varx = 987 Change the value of variables in PLI,
PLAYBACK Set the direction of STEP and RUNTO
values referenced by every statement. var = ‘ZYX’ C/C++, and assembler programs
BACKWARD commands to backward
M Line command in the source window: PLAYBACK STOP Exit playback mode, and return to
add all variables referenced by the Work with subprograms
normal debugging mode.
selected line to the monitor STEP When the current statement calls or The playback recorder remains on.
Mn (such as M1, Line command in the source window: or runs a sub-program, procedure, or
STEP INTO function, step into it. (The sub must be PLAYBACK DISABLE Turn the playback recorder off
M2, …) add the nth variable referenced by the
selected line to the monitor compiled for debugging)
STEP OVER When the current statement calls or
Work with program source
MONITOR LIST var- Add variable-name to the monitor
name runs a sub-program, procedure, or SET DEFAULT Search library lib-name for a debug
or function, run it but do not show it in the LISTINGS lib-name source file, if it has not already been
MON LIST var-name debugger. found for the current program.
Automatically search this library when
MON LIST TITLED Add all variables to the monitor from STEP RETURN Run to the next program return. This is
new programs are encountered.
WSS COBOL working-storage a quick way to run to the end of a sub-
program. SET DEF LIST ( lib1, Search library lib-name for a debug
lib2, … , libn ) source file, if it has not already been
C Line command in the monitor window: LOAD progname Load program progname. Display it in
found for the current program.
clear (remove) the selected item the source window if it is available.
Automatically search these libraries
H Line command in the monitor window: QUALIFY PROGRAM Display the source of progname in the when new programs are encountered.
display the value of the selected item in progname source window
Code an EQADEBUG An EQADEBUG DD can be used to
hexadecimal format QUALIFY RESET Position the source window to the DD in JCL specify a library concatenation for
D Line command in the monitor window: or current program and current statement debug source files. It is an alternative
display the selected value in default QU RES to the “SET DEF LIST …” setting.
format LDD csect-name Load the LANGX file for the specified
CLEAR MONITOR Clear all items from the monitor LDD program-name csect or program. Libraries specified by
window “SET DEF LIST …” or an EQADEBUG
DD are searched.
If an abend occurs, you are notified with a message in the log. If debugging sessions. The default
IBM the program is stopped at an abend, and you STEP or GO, the
application will abend. To continue without abending:
naming convention is user-
id.DBGTOOL.SAVEBPS, but may be
GO BYPASS This command bypasses the statement customized on each system.
Debug Tool where the abend occurred, passes
control to the next logical statement,
File attributes: PDS or PDSE (Library),
RECFM=VB, LRECL=3204 or more,
Terminal interface and stops there. BLKSIZE=any
SET SAVE SETTINGS Automatically save current settings to
IBM’s Interactive Debugger for applications running in z/OS How to call Fault Analyzer to capture a fault entry AUTO the save settings data set when the
CALL %FA Invoke IBM Fault Analyzer for z/OS to debugger ends
“How To” quick reference capture a fault entry based on the SET SAVE BPS Automatically save current breakpoints
current state of the application. Control AUTO to the save breakpoints and monitors
and Notes is returned to the debugger after the data set when the debugger ends
fault entry has been captured, and
debugging can continue. SET SAVE Automatically save current monitors to
For detailed descriptions of commands, command syntax, and MONITORS AUTO the save breakpoints and monitors
command options, refer to the Debug Tool for z/OS Reference data set when the debugger ends
Files that can be used by the debugger, and
and Messages manual. A complete set of Debug Tool manuals SET RESTORE Automatically restore settings from the
can be obtained from the IBM Debug Tool website.
commands to use them
SETTINGS AUTO save settings data set when the
www.ibm.com/software/awdtools/debugtool/ Preferences File A file that contains a series of Debug debugger starts
select the “Library” link (DD name INSPPREF) Tool commands (a script) that runs
automatically when the debugger SET RESTORE BPS Automatically restore breakpoints from
Manuals: starts. It is typically used to customize AUTO the save breakpoints and monitors
Summary of Commands, User’s Guide, Reference and debugging settings and the data set when the debugger starts
Messages, and Customization Guide environment for the developer. SET RESTORE Automatically restore monitors from the
Command File A file that contains a series of Debug MONITORS AUTO save breakpoints and monitors data set
(DD name Tool commands (a script) that runs when the debugger starts
The following paragraph does not apply to the United Kingdom or INSPCMDS) automatically when the debugger
any other country where such provisions are inconsistent with starts. It runs after the preferences file How to invoke the debugger:
completes, if there is one. It is typically Batch LE program, connecting to GUI debugger
local law:
used to run a series of commands to
INTERNATIONAL BUSINESS MACHINES CORPORATION control execution of the test session Insert a CEEOPTS DD statement with TEST run-time option in
and programs. the JCL in the step or steps to be debugged. Syntax:
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY
//CEEOPTS DD *
OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, Log File A file where Debug Tool writes TEST(,,,TCPIP&address%port:)
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON- (DD name INSPLOG) messages that are written to the log address = the IP address of your workstation, and
window., such as results of various port = the listening port number configured in the GUI
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A Debug Tool Commands. TCPIP directs the debugger to use a GUI
PARTICULAR PURPOSE. Some states do not allow disclaimer Example:
of express or implied warranties in certain transactions, therefore, //CEEOPTS DD *
this statement may not apply to you. TEST(,,,TCPIP&123.45.67.89%8001:)
SET LOG ON FILE Command that opens file-name of the How to invoke the debugger:
This information could include technical inaccuracies or file-name OLD log file. All log messages occurring Batch LE program, connecting to a Terminal
after this command is issued are
typographical errors. Changes are periodically made to the
written to the file.
Interface Mgr (TIM) terminal
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or Insert a CEEOPTS DD statement with TEST run-time option in
USE file-name Command to run Debug Tool the JCL in the step or steps to be debugged. Syntax:
changes in the product(s) and/or the program(s) described in this commands (a script) contained in the
at any time without notice. //CEEOPTS DD *
specified file.
TEST(,,,VTAM%userid:)
LANGX file Debugging information for OS/VS userid = your user ID
COBOL, VS COBOL II, or Assembler VTAM%user-id: directs the debugger to use the terminal
interface manager. It will connect to the TIM terminal
Save settings file Allows saving/restoring of SETTINGS
where userid is logged on.
between debugging executions. The
For Use with Debug Tool Version 12 Example:
default naming convention is user-
//CEEOPTS DD *
id.DBGTOOL.SAVESETS, but may be
TEST(,,,VTAM%USRX001:)
customized on each system.
© Copyright International Business Machines Corporation File attributes: sequential, RECFM=VB,
2012. All rights reserved. LRECL=3204 or more, BLKSIZE=any
Revised December 14, 2010 How to invoke the debugger:
Save breakpoints and Allows saving/restoring of breakpoints
How to bypass an Abend condition monitors file and MONITOR values between
Batch non-LE program, connecting to a GUI The LE TEST option is used to invoke the debugger. QUERY PFKEYS Display a list of the current function key
debugger settings in the log
It has five sub-options, separated by commas and a colon:
Change the program name on the EXEC statement to SET KEYS ON Displays the function key settings on
TEST( test-level , command-file , prompt , connection :
EQANMDBG, and code an EQANMDBG DD statement with the the bottom two lines of the screen
preferences-file )
program name and a TEST option.
SET KEYS OFF Turns off the function key display
test-level is not typically coded. It is used to control when the SET KEYS 12 With “SET KEYS ON”, displays
For example, if the EXEC statement in the run JCL looks like:
debugger will automatically stop as a program runs. (default = all function keys 1 - 12
//STEP10 EXEC PGM=MYPROG,PARM=’ABC,123’
conditions and abends)
SET KEYS 24 With “SET KEYS ON”, displays
Replace the EXEC statement with: function keys 13 - 24
command-file can be used to specify the DDname or file name
//STEP10 EXEC PGM=EQANMDBG,PARM=’ABC,123’
of a script file containing debugger commands that will run SET PF16 “Monitor” = Set the F16 key to the command
//EQANMDBG DD *
automatically. MONITOR LIST %CU “MONITOR LOCAL %CU LIST”. The
MYPROG, TEST(,,,TCPIP&address%port:)
/* LOCAL function key display will show PF16 as
prompt is not typically coded. (default = display the debugger “Monitor”.
when triggered)
How to invoke the debugger:
Batch non-LE program, connecting to a Terminal connection controls where the debugger displays: Default function key settings
Interface Mgr (TIM) terminal VTAM%user-id: = Connect to the TIM terminal where user-id F1 / 13 HELP
logged on
Change the program name on the EXEC statement to MFI%terminal-id: = Connect to the non-TIM terminal named F2 / 14 STEP
EQANMDBG, and code an EQANMDBG DD statement with the terminal-id F3 / 15 END
program name and a TEST option. TCPIP%workstation_tcpip_address%port_id = Connect to GUI
debugging software such as the Debug Tool Eclipse plug-in F4 / 16 LIST
For example, if the EXEC statement in the run JCL looks like:
F5 / 17 FIND
//STEP10 EXEC PGM=MYPROG,PARM=’ABC,123’ preferences-file can be used to specify the DDname or file name
of a script file containing debugger commands that will run F6 / 18 AT/CLEAR
Replace the EXEC statement with: automatically. The preferences file (if specified) runs before the F7 / 19 UP
//STEP10 EXEC PGM=EQANMDBG,PARM=’ABC,123’ command file (if specified).
//EQANMDBG DD * F8 / 20 DOWN
MYPROG,TEST(,,,VTAM%userid :) Example: TEST(,,,VTAM%USER123:) F9 / 21 GO
/*
F10 / 22 ZOOM
How to invoke the debugger: F11 / 23 ZOOM LOG
Debugging batch programs under TSO Notes:
F12 / 24 RETRIEVE
Use NAMES EXCLUDE/INCLUDE to reduce storage footprint
The Debug Tool Setup Utility can optionally be used to debug
especially in CICS, and to completely eliminate programs/non-
batch programs under TSO. It is on the Debug Tool utility menu in
executable load modules from Debug Tool consideration
ISPF.
Use CALL %VER to display WA the version and level of Debug
How to invoke the debugger: Tool being used
CICS programs Set up a log file so you have a record of your debugging session.
Use the DTCN or CADP transaction to create a debugging profile If it isn’t needed, no harm is done, but if you need it, then you do
for CICS applications, depending on which of these is installed on not have to recreate the debugging session to get the log. A SET
your systems. LOG ON FILE file-name OLD command will open a log file.
CALL %HOGAN – invoke HOGAN application (CICS)
The DTCN transaction is used to define a profile to start the CALL %DUMP – invoke LE dump
debugger for one or more CICS programs, based on program CALL %FA – invoke Fault Analyzer (dump)
name, transaction id, user id, and other criteria. DTCN is a CALL %CEBR – invoke CICS temp storage browser
feature of IBM Debug Tool for z/OS. CALL %CECI – invoke command interpreter

There is an optional graphical user interface for DTCN (an DTCXXO – CICS transaction to TURN ON SUPPORT for non-LE
Eclipse plug-in) so you can set debugging profiles from a assembler and/or OS/VS COBOL in CICS (Must issue this
workstation without using a terminal. transaction in order to debug non-LE assembler or OS/VS
COBOL under CICS) (Use DTCXXF to turn support “off”)
The CADP transaction is used to define one or more profiles to
start the debugger for CICS programs, based on program name,
transaction id, user id, and other criteria. CADP is a feature of
CICS.
The Language Environment TEST option Working with program function (PF) keys
Set an AT CHANGE breakpoint based on a Modify storage
storage area
IBM AT CHANGE Set a change breakpoint to watch the
1. MON LIST var to
display the variable in
Follow these steps to modify the
value of a variable using the monitor
%STORAGE storage area beginning at address the monitor window
( X’12B4C’,20) 12B4C for a length of 20 bytes 2. Overtype the value of
Debug Tool (Note: X’12B4C’ is assembler syntax. the variable in the
For C it is 0x12B4C. For COBOL it is monitor
Terminal interface H’12B4C’) 1. ZOOM MEM to Follow these steps to modify storage
display the memory using the memory window
IBM’s Interactive Debugger for applications running in z/OS
Display storage in the MEMORY window window
2. MEM address to
Commands used to work with ZOOM MEM Display (zoom in to) the memory
window
position to the address
3. Overtype
storage and registers and Note: ZOOM again will zoom out of the hexadecimal values in
memory window. the memory window
assembler programs MEM variable-name Position the memory window to the A1 = 1 Replace variable A1 with a value or
address of variable-name (note: decimal 1) expression
For detailed descriptions of commands, command syntax, and A1 = 'Text'
MEM X'A500' Position the memory window to the A1 = X'123C'
command options, refer to the Debug Tool for z/OS Reference MEM X'A500'+20 specified address or offset
and Messages manual. A complete set of Debug Tool manuals A1 = A1 + 5
MEM X'A500'+X'B6' Note: If the address has more than 8
can be obtained from the IBM Debug Tool website. MEM X'A500'-32 significant hexadecimal digits, it is STORAGE(X'5F000',4) Update 4 bytes of storage at an
www.ibm.com/software/awdtools/debugtool/ taken as a 64-bit address. If it has 7 or = 256 address with the binary equivalent of
select the “Library” link 8 significant digits, it is a 31-bit decimal 256
address. Otherwise, it is a 24-bit STOR(X'5F000',4) = Update 4 bytes of storage at an
Manuals: address.
Summary of Commands, User’s Guide, Reference and X'100' address with a right-justified
Messages, and Customization Guide MEM %GPR12-> Position the memory window to an hexadecimal value
address pointed to by register 12 STOR(X'5F000') = Update 4 bytes of storage at an
X'00000100' address with a hexadecimal value
The following paragraph does not apply to the United Kingdom or Display storage in the log or monitor STOR(X'5F000') = Update 9 bytes of storage at an
any other country where such provisions are inconsistent with Note:
'Some Text' address with a text string
local law: LIST … will display an item in the log.
MONITOR LIST … will display an item in the monitor. %GPR8->+8 <l'x> = x Assign the value of X to the 4 bytes at
INTERNATIONAL BUSINESS MACHINES CORPORATION
LIST STOR(var,20) Display 20 bytes of storage beginning offset 8 from the contents of R8
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY at the address of variable var
OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, MONITOR LIST %GPR2->+6 <14> = Move a string of 14 bytes pointed to
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON- STOR(var,20) R8->+0 by the contents of R8 (where R8 is an
equated register in the program) to 6
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A LIST Display storage at an address or offset bytes past the location pointed to by
PARTICULAR PURPOSE. Some states do not allow disclaimer or register 2
MONITOR LIST
of express or implied warranties in certain transactions, therefore, followed by one of: %GPR6->+0 <X'20'> = Set 32 bytes pointed to by register 6
this statement may not apply to you. STOR(X'5F000',64) X'00 to zero.
or Note: specify the length of the
STOR(X'5F000'-> receiving storage within < >
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the +256,64)
information herein; these changes will be incorporated in new or
editions of the publication. IBM may make improvements and/or STOR(X'5F000'->
changes in the product(s) and/or the program(s) described in this +X'100')
at any time without notice. LIST Display 16 bytes of storage at the
or address pointed to by a register, or an
MONITOR LIST offset of a register address
For Use with Debug Tool Version 12 followed by one of:
STOR(R1->,16)
or
© Copyright International Business Machines Corporation STOR(%GPR1-> ,16)
2012. All rights reserved. or
Revised June 30, 2012 STOR(%GPR1->
+256,16)
Display registers in the log or monitor
Note: Modify the contents of a register
LIST … will display an item in the log. 1. MON LIST %GPRn Follow these steps to modify the
MONITOR LIST … will display the item in the monitor. (or one of the other contents of a register using the monitor
LIST REG Display the sets of different types of register types) to window
registers in the log or monitor display the register in
the monitor
MON LIST REG Display all general purpose registers in 2. Overtype the
the log contents of the register
in the monitor
LIST Display all of different types of registers
or in the monitor or log %GPR1 = x’1afc3’ Replace the contents of a register with
MONITOR LIST %GPR12 = 10 a value or expression
followed by one of: %GPR5 = %GPR5 + 1 Note: The other register types can be
64BIT REG modified:
or %GPRGn (64-bit general purpose)
SHORT FLOAT REG %FPRn (floating point)
or %EPRn (extended floating point)
LONG FLOAT REG
LIST %GPR12 Display general purpose register 12 in
Display the address, length, and type of a
or the log or monitor variable
MONITOR LIST DESC ATTR var List (describe) the attributes of variable
%GPR12 var in the log
LIST %GPRGn Display a 64-bit general purpose
or register in the log or monitor Display the program PSW (program status word)
MONITOR LIST
LIST %PSW Display the PSW in the log
%GPRGn
LIST %FPRn Display a short-precision floating point
or register in the log or monitor in MON LIST %PSW Display the PSW in the monitor
MONITOR LIST hexadecimal format
%FPRn
LIST %FPRDn Display a short-precision floating point Display the address of a program or module
or register in the log or monitor in decimal
DESC PROG pgm1 List (describe) the attributes of
MONITOR LIST format
program ASAM1, including it’s address
%FPRDn
in storage
LIST %FPRBn Display a short-precision floating point
DESC LOAD lmod1 List (describe) the attributes of load
or register in the log or monitor in binary
module LMOD1, including it’s address
MONITOR LIST format
in storage
%FPRBn
LIST %EPA Display the entry point address of the
LIST %EPRn Display a extended-precision floating
current program
or point register in the log or monitor in
MONITOR LIST hexadecimal format LIST %AMODE Display the current addressing mode
%EPRn
LIST %EPRDn Display a extended-precision floating
or point register in the log or monitor in LIST %BLOCK Display the name of the current block
MONITOR LIST decimal format point (a CSECT is a block, for
%EPRDn example)
LIST %EPRBn Display a extended-precision floating
or point register in the log or monitor in
MONITOR LIST binary format
%EPRBn

Das könnte Ihnen auch gefallen