'Strings' in the RXS program - that is lines in the program not being commands, assignments, selections or iterations - are as a default handled over to an environment called 'stdout'. It is possible to deviate from this default (Section 7).
The handling over of strings to 'stdout' implies the strings are written to the current RXS dataset. Depending on the situation, this dataset is automatically created as RXS.DATA or RXS.COBOL. It is possible to deviate from this default (Section 7).
As default the RXS program terminates by bringing the current RXS dataset up in an edit session - providing that something is written in this dataset. It is possible to deviate from this default.
Example 4.1:
)action
nbr = random() /* get a random number */
'Square of' nbr 'is' nbr**2
)endaction
The third line in the program describes a string. Therefore this line will be written to the dataset <user>.rxs.data -where <user> is the actual TSO userid. The RXS program terminates by bringing this dataset up in ISPF edit.
Default environment for the receiving of strings (that is stdout) may be changed: By the general order address=... strings may be sent to another environment or milieu. For instance address='tso' sends all following strings in the action block to TSO. Over here, the strings will be handled 'the tso way' that is: strings are seen as commands and are executed.
See Section 32 for a more detailed discussion of output from RXS.
See Section 33 for a more detailed discussion of the general order address.