Text 1018, 58 rader
Skriven 2008-08-23 09:04:42 av Mike Luther (1:117/3001.0)
Ärende: SOMD questions
======================
I hope someone here can help me!

The SOM (System Object Model) incantation for OS/2 uses the SOM.IR files to
make a database of installed software that is written for OS/2 which uses it. 
Inncluded in the use of this are OLE oriented applications,which go, among
other things, toward operating system independent program applications. THings
that work, at least in theory, between OS/2 and Windows, for example.

The 'database' of working and operational code for all this is, as far as my
feeble understanding of this, in the \OS2\ETC\DSOM subdirectory. If you look in
it, you will see four files, normally.  Most important here is the 'fact' that
on all of my boxes I normally work with, the date and time for each of them is
the time of boot up for the as-booted box.  However, not on ALL boxes!  For
example, on this Warp 4 latest FP17 BBS box here these files show up as:

  8-09-96   2:49a      6384           0  SOMDCLS.DAT
  8-09-96   2:49a      6844           0  SOMDCLS.TOC
  8-09-96   2:49a      1012           0  SOMDIMPL.DAT
  8-09-96   2:49a        60           0  SOMDIMPL.TOC

Duhh?  Yet all my MCP2 boxen but one I am working on show up with the as booted
date and time!  Why?

Well, two things are focusing here to me.  The boxes I normally see this on are
all equipped with Lotus SmartSuite for OS/2, latest version 1.7 with all the
three released IBM Lotus fixes for it.  So is this part of that reason?  Lotus
SmartSuite is heavily oriented toward SOM.IR operations.  Which if anything
goes wrong in that stuff, SmartSuite remains dead or worse in it's hard drive
coffin until you fix the SOM.IR files by restoring them to original,  Including
even the OS/2 as-installed such files in your \OS2\ETC directory.

Well, I have one lately installed MCP2 latest everything box I just updated
SmartSuite 1.5 to 1.7.  In which Lotus 123 produces OLE errors every time you
attempt to save or abandon a file on it!  Re-installing it doesn't fix this as
the error pop suggests.  And guess what?

THe SOMD files on this box still show a 2004 date!  Despite the whole updates,
fix packs, everything, the SOMD files are definitely *NOT* being updated.  For
example, the SOMDIMPL.DAT file has a ZERO size!  I suspect this is part of the
cause of the Lotus 123 OLE errors, as also suggested from heavy help site and
Google Newsgroup searches.

Well it just hit me!  The REXX SOM.IR library isn't on either this Warp 4 BBS
box, nor the bad boy MCP2 box with the OLE errors in SmartSuite!

Does anyone here have any help thoughts over this?

What program updates these SOMD files?  When?  Why?

Thank you!


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)