Non-Formatted (NOF) Message Routing
The figure above shows the message routing for Non-Formatted (NOF) Input and Output. For a flow diagram of the supplied skeleton NOF program, refer to Routines within the NOF Program Skeleton within the NOF Program Skeleton.
This process is summarized as follows:
NOF programs are assigned to different windows that use the Direct file interface to COMS, and are given the following default name:
systemNOFThe NOF program generates messages that are sent directly to the COMSTP program using a TP-to-TP message.
The message is processed as normal, except that the final output is routed back to NOF using a TP-to-TP message.
Stations can also be declared as NOFORM terminal types, so that raw output (without screen formatting) is returned directly to the requesting station, without involving the NOF program. Refer to the Communication Management System (COMS) documentation for more information on declaring NOFORM-type terminals using the COMS Utility.
There are no special requirements for dealing with COMS in a NOF program. COMS handles NOF messages as for any Agile Business Suite terminal.
Since a NOF program is user-written, recovery is your responsibility.
It is recommended that your NOF program ensures only one message is outstanding for any terminal at a time.
During a recovery of the application, your NOF program does not need to take any special action. It only needs to wait until normal processing resumes.