Unformatted-mode simulator statements
Unformatted-mode simulator statements are used when the full screen image support (FSS) function or 3270-formatting is not used.
The first simulator statement of a message must begin with the transaction code to which it is related. The transaction code is specified beginning in column one of the first statement. Subsequent simulator statements, which define dependent segments and subsequent messages for conversational processing, must not start with a transaction code, because each simulator statement for teleprocessing applications represents a line or segment of input from a terminal.
For batch applications, only one simulator statement is coded, in addition to the command statements. That simulator statement is in fact a dummy statement and serves only to cause the initiation of the application program. As in the case of real simulator statements, a dummy statement of a batch application must also begin with the transaction code, as specified on the ./T command statement, to which it is related.
Syntax rules
The rules for coding the simulator statements are as follows:
- All simulator statements are coded beginning in column 1 and continuing through column 71.
- A non-blank character in column 72 indicates continuation. The contents of column 72 are not used.
- The simulator statement ends with either an end-of-segment indicator or an end-of-message indicator. This indicator can also be coded as either a single-EBCDIC character or as two hexadecimal digits.
Example
The following figure shows an example of BTSIN input. In this example, lines that start with ./T are the simulator commands, and the line that starts with PART and the subsequent lines are the unformatted-mode simulator statements. Each simulator statement ends with a dollar sign ($), which is the end-of-message indicator.