The following table summarizes NOF features, capabilities and restrictions.
Capability/Feature | Scope/Limitations |
|---|---|
| Host types | All |
| Interface to other Systems | Yes |
| Interface to external systems | Yes (DMS II or non-DMS II) |
| Transaction initiated by | Either system |
| Response from other system | Yes |
| Multithreading | Yes |
| Recovery | User program must integrate recovery with external system. |
| Ispec logic performed | All logic, as for standard terminal input |
| Duplicate Protection | None (User must provide own logic within system or user program.) |
| Security | Yes (for direct-connect terminals and programmatic interface) |
| Multilanguage | Supported (Refer to Multiple Language and Translation Capabilities.) |
| External user program | Required (Skeleton program supplied on Release tape) |
| Glb.Work | Available |
NOF provides two methods of interfacing to a System:
Intelligent terminal interface
Programmatic interface for non-intelligent terminals and external programs
Refer to Non-Formatted (NOF) Message Routing for more information about the diagrammatic representation of NOF transaction flow (message routing).
Note: The length of a message to or from NOF must not exceed 2000 characters.
When you use a customized client to connect to an AB Suite MCP Runtime application, the format of the zero value in a primitive signed number attribute with decimals may be different to that in EAE. If the primitive is in the copy area of a CopyIspec or CopyEvent class, the format of the zero value in a primitive signed number attribute with decimals will be different between EAE and AB Suite. The following table describes the difference.
| ||||||||||||||||||||||||
Caution