Using IBM Application Development Tools for z/OS and OS/390

310 Using IBM Application Development Tools for z/OS and OS/390

TEST(ALL,,,MFI%F100:*) For CICS Dual Terminal and Batch CICS transactions

Debug Tool will be started at CICS terminal F100 after

initialization. Alternatively F100 could be a very short VTAM

LU id that is used to define a terminal for debugging a batch

or IMS transaction. No preference file is expected

TEST(ALL,,,MFI:foo) or TEST(ALL,,,foo) Are equivalent instructions when used in TSO that

cause the full screen interface to be used in single screen

mode (the same place that the program was called from). In

both cases the preference file is the file referenced by the

foo DD.

TEST(ALL,,,MFI%LU000001:*) For environments other than CICS. The MFI full screen

debugger will be started on the VTAM LU whose ID is

LU000001. The LU must be known to VTAM and not in

session when the debugger is started.

TEST(,,,VADTCPIP&9.30.62.149%8000:*) Bring up the IBM Distributed Debugger or the

VisualAge Remote Debugger listening on channel 8000 on

the terminal at TCP/IP address 9.30.62.149.

TEST(,,,TCPIP&cello%8001:*) Bring up the WebSphere Studio Enterprise Developer

listening on port 8001 on the machine named cello. This

method does not work in all environments and requires an

up to date name server to be available. We have found using

the actual machine address to be more consistently

effective.

13.2 Specifying the TEST runtime option

Language Environment has several ways of specifying the runtime options for a program.

The following list gives them in ascending order of precedence (that is, things lower on the list

can override things higher on the list).

򐂰 CEEDOPT — Language Environment options specified at installation

򐂰 CEEROPT — Region-wide CICS or IMS default options

򐂰 CLER — transaction under CICS

򐂰 CEEUOPT — also #pragma runopts, or PLIXOPTS

򐂰 Command Line, or _CEE_RUNOPTS

򐂰 CEEBXITA — which is used by IMS Single Point of Control (SPOC) and Debug Tool IMS

utilities

򐂰 Language Environment Storage Tuning User Exit

򐂰 Options defined at installation time that have the non-overridable attribute.

For more information on how to specify a Language Environment runtime option see the

Language Environment Programming Guide.

13.2.1 Defining runtime options using CEEUOPT

In some cases, where runtime options cannot be passed to a Language Environment, a

CEEUOPT must be generated including only your TEST runtime option. In Example 13-1 the

original sample can be found as member CEEUOPT on your SCEESAMP.

Chapter 13. Specifying the TEST runtime option in Debug Tool 311

Example 13-1 Defining runtime options using CEEUOPT

*/****************************************************************/

*/* LICENSED MATERIALS - PROPERTY OF IBM */

*/* */

*/* 5694-A01 */

*/* */

*/* (C) COPYRIGHT IBM CORP. 1991, 2001 */

*/* */

*/* US GOVERNMENT USERS RESTRICTED RIGHTS - USE, */

*/* DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP */

*/* SCHEDULE CONTRACT WITH IBM CORP. */

*/* */

*/****************************************************************/

CEEUOPT CSECT

CEEUOPT AMODE ANY

CEEUOPT RMODE ANY

CEEXOPT TEST(ALL,*,PROMPT,MFI%LU0TCP08:INSPREF)

END

13.2.2 Specifying the TEST runtime option on the command line

Where you specify the TEST runtime option on the command line is dependent on the

language of your program’s entry point.

C/C++ and PL/Ithe slash (/)should be after the runtime options and before any program

parameters.If the slash is not present the runopt will be handed to the program as a

parameter. Some correct examples are:

call dev.load(civp) ‘TEST /’

call ‘redbk1.dev.load(civp)’ ‘TEST / Testing one two three’

COBOLThe slash should appear after the program parameters and before the runtime

options. If there are no program parameters the PARM string should start with a slash. For

example:

call dev.load(cblprg) ‘my program arguments / TEST’

call dev.load(cblprg) ‘/TEST(,,,*)’

13.2.3 Specifying the TEST runtime option on JCL

Like TSO invocation, where one specifies the TEST runtime option on a JCL PARM is also

dependent on the language of your main entry point. In fact, the rules are the same:

򐂰 For C/C++ and PL/I, the PARM should start with the run-opts and have a slash (/) before

the program parameters.

򐂰 For COBOL, the PARM should start with the program parameters and have a slash before

the runtime options.

312 Using IBM Application Development Tools for z/OS and OS/390