31.01.2013 Views

InterForm Manual - System & Method

InterForm Manual - System & Method

InterForm Manual - System & Method

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

With the AFPDS spooled file you do not need to change the USRDFNOPT field or add any<br />

special shift-in and shift-out sequences as for the special *SCS spooled file below.<br />

Introduction to the *SCS unicode format<br />

NOTE: It is highly recommended NOT to use the special format as described below. This<br />

format was necessary before *AFPDS support was added in <strong>InterForm</strong>400. If you want to use<br />

unicode spooled files as input in <strong>InterForm</strong>400 you should define them as AFPDS unicode<br />

spooled files like described above!<br />

When you want to combine <strong>InterForm</strong>400 with unicode *SCS spooled file there is one<br />

problem: To this date IBM have not yet defined a standard for unicode *SCS spooled file, so it<br />

have been necessary to define a special unicode standard (which have been defined by<br />

<strong>InterForm</strong>400) in order to print in unicode from <strong>InterForm</strong>400.<br />

If you create a special *SCS unicode spooled file you will need to set the value ‘IF-UCS2' for<br />

the User defined option (USRDFNOPT) as below:<br />

Type choices, press Enter.<br />

412 User’s <strong>Manual</strong> for <strong>InterForm</strong>400 ®<br />

Change Spooled File Attributes (CHGSPLFA)<br />

AFP Characters . . . . . . . . . AFPCHARS *NONE<br />

+ for more values<br />

Front side overlay: FRONTOVL<br />

Overlay . . . . . . . . . . . *SAME<br />

Library . . . . . . . . . .<br />

Offset down . . . . . . . . . *SAME<br />

Offset across . . . . . . . . *SAME<br />

Back side overlay: BACKOVL<br />

Overlay . . . . . . . . . . . *SAME<br />

Library . . . . . . . . . .<br />

Offset down . . . . . . . . . *SAME<br />

Offset across . . . . . . . . *SAME<br />

Constant back . . . . . . . . *SAME<br />

User defined option . . . . . . USRDFNOPT 'IF-UCS2 '<br />

- and it also requires that unicode text is marked with special and <br />

sequences. You can use either DEVTYPE(*LINE) or DEVTYPE(*SCS) for the unicode<br />

spooled file. This special kind of spooled file is described below.<br />

In the spooled file you can have both unicode text and normal single code page text so any<br />

unicode text must be surrounded by indicators in order to identify them as unicode.<br />

For DBCS (Double Byte Character Set) spooled files you use the two special 1 byte characters<br />

(which is hex ‘0E’) and (which is hex ‘0F’) to start and end any DBCS<br />

field.<br />

A simular and technique must be used for unicode fields as well, so the<br />

special <strong>InterForm</strong>400 *SCS unicode spooled file must use hex ‘0E’ for to mark the<br />

start of unicode text and hex ‘000F’ (Note that it is here a 2 byte sequence) as to<br />

mark the end of the unicode text.<br />

Limitations of the unicode *SCS spooled files<br />

Note that a unicode spooled file setup in the manner described above cannot be displayed or<br />

printed in a normal manner, but <strong>InterForm</strong>400 includes tools for that. These tools are<br />

described later in this appendix on page 415.<br />

Note also that there are other limitations to the functions supported in <strong>InterForm</strong>400 for the<br />

unicode spooled files at the moment. The limitations are:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!