I-Data 5250 ALLY - Manual (Page 101)

Page 4-7 CHAPTER 4 — PROGRAMMABLE FUNCTION STRINGS
4. The printer may not be listed in the supported configurations. The
user may want to build a table from scratch.
5. The user may want to evoke a PFS or printer command using a
System font request. Since the Escape sequence can be composed of
any characters, it is not restricted to font selection Escape
sequences. As such, GFIDs can be used as an extension to the PFS
capacity of the 5250 ALLY.
Each table can hold up to 128 entries up to a maximum of 20K (20480)
bytes. If the user attempts to download a font correspondence entry to the
5250 ALLY when either the maximum number of entries has been reached
or the total storage is full, the new entry will be ignored. In these
circumstances it is necessary to delete existing (and preferably unused)
entries to make room for the new entries.
PFS Descriptions
The following is a complete list of PFSs currently offered with the 5250
ALLY, along with the number used to edit each PFS. Each description
describes the action of the PFS and indicates when each PFS will be sent to
the printer by the 5250 ALLY. The descriptions also indicate the type of
command that should be entered by the user in the PFS definition, and
where appropriate, indicates related configuration options that may have to
be coordinated with the PFS definitions.
Note that PFSs are used by the 5250 ALLY only in IBM emulation mode
(!AGILE!03=00;), except for the initialization PFSs (00-06). Further, they
are not used if any type of PFS suppression is active (except for the
initialization PFSs and PFS 07 — FF, 08 — CR, 09 — LF, 23 — BOLD
ON, 24 — BOLDOFF, 25 — BSBOLD1, 26 — BSBOLD2, 27 — UNDL
ON and 28 — UNDLOFF, depending upon the configuration of Options
0601 and 3401). Please refer to Appendix A — Interfacing Xerox Printers
for information about PFS suppression and other special Xerox commands.
The only PFS definitions that are not empty in the “Generic” printer
configuration are 07 — FF, 08 — CR, 09 — LF and 0D — VERMOVE.
If the user is aware of how each of the PFSs is used and what conditions
will trigger them, the user may define them for any purpose. Please refer to
Appendix B — SCS/DCA Command Summary for detailed information on
the commands that will trigger each PFS.