[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

828.0. "Write OAMAILBOX hangs in SPAWNED process" by TAV02::CHAIM (Semper ubi Sub ubi .....) Mon Jun 08 1992 12:13

I've been attempting to access the ALL-IN-1 mailboxes from a SPAWNED
subprocess. Following is the comm procedure which I run in the ALL-IN-1
subprocess to create the actual command procedure which will subsequently be
run the SPAWNED subprocess:

$oambx="''f$logical("OAMAILBOX")'" - "_" + ":"
$OPEN/WRITE 1 SYS$LOGIN:A1.TMP
$WRITE 1 "$OPEN/APPEND OAMAILBOX ''OAMBX'"
$WRITE 1 "OPEN/READ DCLMAILBOX ''F$LOGICAL(""DCLMAILBOX"")'"
$CLOSE 1

After running the a1.tmp in the SPAWNED subprocess, if I do a sho log oamailbox
or dclmailbox they define to the same mbx as shows in the ALL-IN-1 subprocess.

At this point any write to oamailbox will hang (in the ALL-IN-1 subprocess it
works fine:

$write oamailbox "oa get oa$curdoc_filename"
$@dclmailbox
$sho sym result

Thanks,

Cb.
T.RTitleUserPersonal
Name		DateLines
828.1Only a guess ...AIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCTue Jun 09 1992 00:3913
Could your sub-process be waiting for something to read what it had written to
the OAMAILBOX, ALL-IN-1 does not attempt to read the contents of OAMAILBOX
until an attempt is made by the sub-process to read DCLMAILBOX.

The 'wierd' sub-process you get with ALL-IN-1 handles this situation, maybe
your sub-process is doing a syncronous I/O that will not complete until the
mailbox (OAMAILBOX) is read by another process (i.e. ALL-IN-1).

It's only a guess but it may point you in the right direction.

HTH

Terry
828.2Try rolling your own mailboxesSHALOT::WARFORDRichard Warford @OPA DTN 393-7495Tue Jun 09 1992 15:3113
    Several years ago, I worked out a method of doing Spawned process
    communications. It wasn't pretty but it worked. Essentially it detailed
    a seperate set of mailboxes for talking between the ALL-IN-1 subprocess
    and the spawned process. Then a set of attaches back and forth to make
    it work. The VASIS integration actually used this method for a while.
    
    But that was in the old days. I've heard some people now use the
    TEXT_FILE functions and effectively create thier own mailboxes to
    talk with another process. Thus you avoid the ALL-IN-1 subprocess.
    Still requires timely attaches back and forth - as spawing tends to
    put a process on hold!
    
    Rick
828.3PointersMDCRAB::HOWARDBen. Our business is computers, not moneyFri Jun 12 1992 05:236
    I got this to work a couple of years ago.  The discussion that helped
    me through was in OAWEGO::ALL-IN-1_V23, notes 1996 and 2582.  I think I
    posted some questions about exiting problems, but they turned out to be
    programming errors in the program that was running in the sub-process.
    
    Ben