I've written a series of articles for EDM/2, the Electronic Developer Magazine for OS/2, which give some tips to improve your OS/2 applications:
You wondered what the BLDLEVEL utility is good for?
Well, then read this article on how to add a signature to your applications that
can be read by BLDLEVEL.
Ever wondered why OS/2 itself and some applications create dialogs containing notebooks
that are clipped off, over- or undersized or unreadable?
This article shows how easy such problems can be avoided, and the notebook
adjusts itself to the old and new notebook style
(introduced with Warp 4), depending on the OS/2 version it is running at.
Do you also think the notebook control lacks some functionality when processing
keys?
With little code you can circumvent the notebook's missing features easily.
You know SETBOOT can reboot a PC, but you don't want to start a program?
There is a undocumented IOCTL-call SETBOOT uses, and nothing prevents you from
doing the same.
You created your own controls? You want to draw them also in a disabled state?
A few lines of code can do this for you, your control will look like a standard
OS/2 control.
You want to controls the DOS Settings for sessions you're launching?
This article describes how you can access the DOS Settings dialog and pass
those settings to WinStartApp() or DosStartSession().
Ever wondered how e.g. the JAVA interpreter can access the PM API from an AVIO
session?
This article describes 2 methods to initialize the PM environment from an
an AVIO executable (AVIO executables are executables marked to be run in an
OS/2 window or fullscreen).