Any NOF input to your application (for example, a transaction sent to Runtime or a reply to an AUTO; from the application) must be in one of the formats listed in the following table.
| Function of Input | Format Used |
|---|---|
| To invoke a Page 2 request screen | HI |
| To send a Page 2 request | ispec |
| To invoke a Teach screen teach for an Ispec ispec | ispec teach |
| Transaction input | ispecTscreendata |
| To sign off the application | BYE |
| To enter an Administration command command | :command |
| Accept command input to Report | > input |
Note: HI returns the Page 2 screen, or if your application has a Fireup Ispec it returns Page 2 followed by the Fireup Ispec.
The following table explains the terms used in the preceding formats.
| Term | Description |
|---|---|
| ispec | A valid Ispec name for the application, always filled to 5 characters. |
| teach | A valid Teach screen name for the Ispec. |
| screendata | The properties for the input transaction. (Refer to Note below.) |
| command | A valid Administration command, including :RUN, if the Report is a ROC Report but is not VD. :REC is not valid. |
| input | Valid Accept input for the active Report. |
Note: The format of the input transaction must match the format that the application would receive from a terminal, including header details. Refer to NOF Ispec Screen Data Format for more information on the format of the Ispec and attributes that make up the screen data sent from the NOF program to the application.