| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
ALL-IN-1 V2.4 I am posting this note in both the ALL-IN-1 and CLI_SUPPORT conferences. I have been assisting one customer in "integrating" an application. This application is intended for a third customer. The application is basically an image which does some processing including displaying an FMS form. It then issues a lib$spawn to invoke a command procedure. The "integration" is very weak. We are merely attempting to run the image in the subprocess. The developing customer did NOT have ALL-IN-1 installed, but it did have WPS-PLUS/VMS V3.0. At the time I didn't see any reason why we couldn't develope/test it on the WPS system. We created a commands procedure which invokes an A1MBX command procedure to define the oamilbox and dclmailbox. Then it issues a run ti their image. We invoke this command procedure using COMMAND x.com\clear. This works fine under WPS. When we tried running the same thing under ALL-IN-1 we fail; the image apparently is unable to issue the lib$spawn. In ALL-IN-1, if we use DCL @x.com then it does work fine. This however requires the user account to have DCL privs in ALL-IN-1. The developing customer is going to supply me with a debugged version of the image. But perhaps someone can tell me what is the difference between the subprocess being run by WPS-PLUS/VMS V3.0 and ALL-IN-1 V2.4. Also, in ALL-IN-1 why would DCL @x.com work when COMMAND x.com does not. Thanks, Cb.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3655.1 | Use /NOBROADCAST ... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Mon Dec 13 1993 11:00 | 12 |
I believe that I've diagnosed the problem. The developer sent me an image which was linked with DEBUG. The lib$spawn was failong with a CLI-E-TRMMBX. According to a STARS article, this happens whem ALL-IN-1 is invoked with /BROADCAST (the default). Invoking with /NOBROADCAST solves the problem. Now, I assume that WPSPLUS/VMS also is equivalent to /NOBROADCAST. However, I would still like to understand why only COMMAND fails and not $ @. Thanks, Cb. | |||||