Definition
External transaction data:
The transaction field contents are read from external text files, notfrom the CATT buffer.
The field contents are constant values in TCD data records, not CATTparameters.
This procedure is a precursor of the 'External variants', in which CATTprocedure parameter values are saved as datasets.
This procedure is still supported for reasons of compatibility. Itshould only be used by experienced users.
Functionality:
The field contents for the transaction are read from external textfiles whose names are specified by the procedure or test module.Because of this name assignment, external TCD data are only possiblefor one transaction in a CATT module.
The transaction runs repeatedly under external control, up to a maximumof 999 times.
The screen sequence in the external data must be identical with themodel screen sequence in CATT.
The values for BDC_OKCODE and BDC_CURSOR are always fetched from theCATT data.
The values for other screen input fields are usually read from theexternal files. You can indicate that the CATT field values should beused for specified screens.
The path is in the SPA/GPA parameter CTP. If this is empty, thestandard path of the host is used.
Text file structure:
management record WS_UPLOAD from file ABLAUFNR.000
can be changed and written back
transaction records WS_UPLOAD from file ABLAUFNR.nnn
are not written back
Management record:
One record for general control followed by
other records for transaction control
First record for general control:
Flag from offset 0 length 3
000... general control (1st record in set)
flag from offset 3 length 1
000X... productive execution of all TCD data records,
changed to 000R... after execution
000R... not to be executed again, has already been
executed productively, log Rcode=10
000T... test mode, transaction records can run
repeatedly, management record unchanged
text from offset 4 length 30
000Xtext... general text not used internally
result field for productive runs from offset 34 length 80
000Rtext...procedure data (with SPACE separators):
System ID (3-character)
procedure number (8-character)
date (YYYYMMDD) (8-character)
time (HHMMSS) (6-character)
Release (3-character)
client (3-character)
language (1-character)
user name (12-character)
following records for transaction control:
TCD data record ID from offset 0 length 3
nnn Transaction control; a transaction record exists
for TCD data record nnn under
ABLAUFNR.nnn (screens and fields).
TCD data record ID in range 001 .. 999
flag from offset 3 length 1
nnnX... execute TCD data record nnn, changed
in productive execution to:
nnnS... TCD data record ran successfully
nnnE... TCD data record errors
nnnA... TCD data record cancelled
WS_UPLOAD error log Rcode=01..08
screen error in log Rcode=11..99
current screen number from Rcode - 10
text from offset 4 length 30
nnnXtext... TCD data record text is passed to the log
in <X
result field for productive runs from offset 34 length 80
nnnStext...message: last message in the transaction
Transaction records:
sequence of screen records and field records
screen records from offset 0 length 12 or 13
ProgramScrnno Program = module pool (8-character)
Scrnno = screen number (4-character)
X = CATF flag (1-character), i.e.
use original CATF field contents
field records begin with Space, then from offset 1
LnLiNameContents Ln = field name length (2-character)
Ln = field contents length (2-character)
Name = field name (length in Ln)
Contents = field contents (length in Li)
field records always refer to the most recent screen record