InterForm Manual - System & Method

to ease the changes necessary to your sources.
Displaying unicode *SCS spooled files
A problem related to the special unicode spooled is, that unicode characters are represented
by 2 bytes and thus cannot be fully displayed via a normal DSPSPLF command. To help you to
around that problem InterForm400 is delivered with a command simular to DSPSPLF:
APF3812/DSPUNISPLF.
Where a normal DSPSPLF command will not show any unicode text the DSPUNISPLF
command will display any unicode character that is represented in the code page of the
current 5250 session.
The DSPUNISPLF command is included in the APF3812/APFWRKOUTQ command so if you
display an *SCS spooled file with USRDFNOPT('IF-UCS2') the DSPUNISPLF command is
used instead of DSPSPLF.
Printing out unicode *SCS spooled files (without merge)
W hen using the special *SCS unicode spooled file you will normally merge them in
InterForm400, but you might want to print them out directly without merging.
The special unicode sequences are not supported by the standard printing process so you
need to do a small change of the used output queues (for remote writers) or printer devices to
print out the *SCS unicode spooled files.
InterForm400 is delivered with a special program, APF3812/IFWTRTRP, that can be used as
a Data Transfer Program with the parameter: USRDTATFM(APF3812/IFWTRTRF) on either
output queue or printer device.
For any spooled file that does not have USRDFNOPT(‘IF-UCS2') the program will run as if it
was not there. Only spooled files with this option will be inspected and any unicode text will
printed (all supported characters will be printed).
If you are using a data transfer program you will be forced to specify TRANSFORM(*NO) i.e.
disabling host print transform. That is no problem as host print transform is done in the called
program (IFWTRTRF).
Using the data transfer program with your own WSCST
If you have defined your own workstation customizing object (*WSCST) and you want to use
that combined with a data transfer program like above you will need to do a workaround to
make it work.
Please note, that this is a problem only if you are using MFRTYPMDL(*WSCST) combined
with a *WSCST object in field WSCST on the output queue (for remote writers) or printer
device description. It is NOT a problem if you are using any of the predefined *W SCST objects
in QSYS, that are selected via the MFRTYPMDL parameter on output queues and printer
devices.
If you try to combine a *WSCST object with MFRTYPMDL(*WSCST) you will get the error
message: CPD83F0 Device class of the customizing object mismatched.
The workaround
The workaround can according to IBM be done by replacing any of the predefined *WSCST
objects in QSYS (use one that you would never use e.g. QW PIBM4019 might be a candidate..)
with your own *W SCST object. It is a very good idea to just rename the *W SCST object in
QSYS and then move or copy you own *W SCST object into QSYS - with that same name..
InterForm A/S 415