A new, empty screen operations file is created and the screen operations editor is automatically used to open the new file.
To control a terminal application, you need a screen operations file and a flow that references that screen operations file. In many situations it is easier to record these two files at the same time, rather than recording the screen operations file first and then later recording the flow file.
However, you might have design reasons for choosing to record a screen operations file separately from the flow file that references it. For example, your business organization might plan to develop three separate screen operations files in parallel and then record a single flow file that references the three screen operations files. Or, you might be updating an older flow that already a screen operations file associated with it.
To record a screen operations file and at the same time record a flow file that references that screen operations file, follow the steps described in Recording a flow, and make sure that the Working Set listbox of the Screen Operations File Selection drawer contains only the entry [Untitled] (this is the default setting).
To record a screen operations file by itself, follow the steps described in Recording a screen operations file.