DDE Connect errors

[precisonline]

I'm seeing references in here to TU.DDE.WRITE, TU.DDE.DISCONNECT, etc.  Still thinking the TU.xxx routines are in this mix somehow.

[davisd]

I'd already used strings on UT.DDE.   I can see TU.LAUNCH.APP in there and a couple of others between the "System" and "Topics" strings.

DMCONT differences don't look like they matter - the one that doesn't work has the "prefix" set to keep the GUI definitions separated on the client.

I might try a small subroutine tomorrow to see if I can get any more information.

The "DDE" entries in DMSYSDEFN are the same on both systems - so I don't think it's that either - but the message sure makes it look like it is.

[davisd]

I compiled alternate versions of TU.DDE.CONNECT in a local directory with the trace set.

The version I ran here (where it works) - put this in the trace entry:

DDE.CONNECT(@VM)EXCEL(@VM)System
DDE.CONNECT(@VM)EXCEL(@VM)AceBook1.XLS
DDE.CONNECT(@VM)EXCEL(@VM)System
DDE.CONNECT(@VM)EXCEL(@VM)PR339.xltm

This is consistent with the code, which does a

DDECONNECT TO "EXCEL,AceBook1" RETURNING L.HEXCEL WITH PATH "$EXCELPATH\EXCEL C:\MyPath\AceBook1.XLS"
then opens the PR339.xltm macro from that connection, does a DDEDISCONNECT FROM L.HEXCEL, and then does a:

DDECONNECT TO "EXCEL,PR339.xltm" RETURNING L.HEXCEL

and then runs the macro in that to populate the spreadsheet.

The version I ran that DOESN'T work just has:

DDE.CONNECT(@VM)EXCEL(@VM)

Notice no "Topic" is showing up.

So I think it's something in UT.DDE, which of course I don't have the code for.

[precisonline]

Just wondering, is the object size of the catalogued UT.DDE the same on both systems?

[davisd]

The object size is identical.
The object itself is identical.

[precisonline]

Hmmm.

So by process of elimination it has to be configuration somehow.  What about differences in DMPROCESS?

[davisd]

No difference in that file.
I am able to get a different error message by taking out the DDE entry in DMSYSDEFN entirely, or copying it to a local system definition file (one of the xxDEFN files), or leaving a blank DDE entry in DMSYSDEFN

So at this point I know it is successfully reading the DDE entry in DMSYSDEFN, and finding the System and Topics lines - otherwise it would display a blank in the DDE error message instead of "System" and "Topics"

[precisonline]

Interesting.  Is the AIX "LANG" setting the same on both boxes?

[davisd]

en_US on both.

The only difference I see between boxes is where the one that isn't working os on AIX 5.1.

[precisonline]

That's really interesting.. 5.3 works and 5.1 does not.  Same version of Unidata, same SB+, can't imagine how the underlying OS would have this kind of impact.