Show TOC

TCD Command InterfaceLocate this document in the navigation structure

Use

Field

Description

TCODE

Transaction code.

MODE

Processing mode. Possible values: A, N, E, X, or Y. See Start Options.

BINPT

Batch input mode. Set by X.

WAIT

Wait factor. This simulates the time required for a user to enter a character. It is only used when in processing mode N. Unit is 0.1 second. For example, a value of 5 simulates 0.5 seconds for each character.

Screen Modes

Screen modes before execution are visible in the structure editor. Screen modes after execution are visible in the XML data in the log.

Screen Modes Before Execution

Screen Mode

Meaning

D

Deactivated.

X

Active.

Screen Modes After Execution

Screen Mode

Meaning

D

Deactivated.

K

Skipped. It was dynamically deactivated.

0

Not executed.

1

Finished. There were no field checks to do.

2

Finished. All field checks are correct.

3

Finished. Some field checks are not correct.

4

Finished. Some field checks were not done.

Field Modes

Field modes before execution are visible in the structure editor. You can change the modes when parameterizing fields in the command interface. Field modes after execution are visible in the XML data in the log.

Field Modes Before Execution

Field Mode

Meaning

C

Check. The screen field will be compared to the value of the literal or parameter that is in the VALIN field. If these are not the same, the script will fail.

G

Get. The content of the screen field will be read into the parameter that is in the VALIN field.

S

Set. The screen field will be filled with the value of the literal or parameter that is in the VALIN field.

I

Input. This designates an input field. The value can be changed to 'S', 'G', or 'C' for parameterization.

O

Output. This designates an output field. The value can be changed to 'G' or 'C' for parameterization.

Field Modes After Execution

Field Mode

Meaning

Z

Field check was skipped dynamically.

5

Check was correct

6

Check was not correct.

7

Field was not checked.

G

Get returned.

8

Get did not return.

S

Set was performed.

P

Set was not performed. It was prevented dynamically.

Messages

This section remains for backward compatibility. The preferred way to handle messages is with the MESSAGE… ENDMESSAGE block.

All messages sent by a transaction are stored in an internal table called MSG. You can view the messages in the log.

Caution

Do not use the structure editor to parameterize messages.

MSG has the following fields:

Field

Description

TCODE

Transaction code from which the message was sent.

DYNAME

Program name.

DYNUMB

Screen number.

MSGTYP

Message type.

MSGSPRA

Message language.

MSGID

Message class.

MSGNR

Message number.

MSGV1

First variable part of message.

MSGV2

Second variable part of message.

MSGV3

Third variable part of message.

MSGV4

Fourth variable part of message.

ENV

Monitoring activities for batch input.

FLDNAME

The full text of the message.

To pass messages to parameters in the test script, use the script editor and the following syntax:

<parameter> = <command interface>-MSG[<number>]-<field>.

The number of messages sent by the transaction is contained in the eCATT variable &MSX.

Example

You can access all the messages from a transaction.

DO &MSX.

LOG ( <command interface>-MSG[&LPC]-FLDNAME ).

ENDDO.