Fragment 6 - Printer object creation
class = 'WPPrinter'
title = 'Test Printer'
location = '<WP_DESKTOP>'
setup =,
'QUEUENAME=MYTEST;' ||,
'OUTPUTTOFILE=NO;' ||,
'PORTNAME=LPT2;' ||,
'PRINTDRIVER=IBMNULL;' ||,
'DEFAULTVIEW=ICON;' ||,
'JOBDIALOGBEFOREPRINT=NO;' ||,
'QUEUEDRIVER=PMPRINT;' ||,
'PRINTWHILESPOOLING=YES;' ||,
'OBJECTID=<MY_PRINTER>;'
call SysCreateObject class,,
title,,
location,,
setup,,
'R'
class = 'WPPrinter'
title = 'Test Laser Printer'
location = '<WP_DESKTOP>'
setup =,
'QUEUENAME=MYLASER;' ||,
'OUTPUTTOFILE=NO;' ||,
'PORTNAME=LPT3;' ||,
'PRINTDRIVER=' ||,
'LASERJET.HP LaserJet Series II;' ||,
'DEFAULTVIEW=ICON;' ||,
'JOBDIALOGBEFOREPRINT=NO;' ||,
'QUEUEDRIVER=PMPRINT;' ||,
'PRINTWHILESPOOLING=YES;' ||,
'OBJECTID=<MY_LASER_PRINTER>;'
call SysCreateObject class,,
title,,
location,,
setup,,
'R'
Object REXX
After a long awaited delivery preceded with many "real soon now"s, Object REXX was
released as part of The Developer Connection, Volume 6. While I haven't had a chance to use
these enhancements to traditional or "classic" REXX as one IBMer termed it, I have read some
reviews that lead me to believe that, while the extended features of Object REXX may be
substantial, it is not for the faint-at-heart. The idea of having a built-in interface to System
Object Module (SOM) classes and methods is very exciting. However, the absence of
documentation on the Volume 6 CD-ROM with Object REXX relating to the workplace
classes and methods indicates that either IBM doesn't think that this product is ready for the
big-time or they have intended it for commercial programmers.
In order to use Object REXX, it will be necessary to obtain a copy of the OS/2 Technical
Library. Along with that, it will be necessary for the user to understand the format of C++
language calls and to interpolate what is written for C++ into the format required by Object
REXX. This is not a very pretty way to introduce a "language neutral" facility.
REXX For DOS
While I know that both this magazine and this column are intended for OS/2 users, I
would be remiss if I didn't mention the availability of REXX as an integral part of DOS 7.0.
The DOS documentation calls it the "language of choice" for DOS users beginning with 7.0.
Because of the lead time necessary to submit this column, I have only had the
opportunity to exercise beta copies of the DOS REXX interpreter. The PARSE VERSION
instruction returns REXXSAA as the language processor along with a level of 4.0 and a date
of 08 Jul 1992. Yet, this REXX interpreter, at least the version I have been testing, does an
injustice to the System Application Architecture concept in which IBM states:
"Programs written in REXX according to SAA specifications are portable to all other
SAA environments. For example, a REXX program written for the OS/2
environment can be run in a CMS or TSO/E environment, if the program does not
use OS/2-specific features."
Unfortunately, this is not the case. As a matter of fact, the DOS REXX interpreter is
a long way from being compatible with the OS/2 REXX interpreter. Furthermore, without an
external data queue capability along with the general system and file functions available in
OS/2 REXX, DOS REXX will probably serve very little useful purpose for OS/2 REXX
programmers.