[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

584.0. "ALL-IN-1 and INGRES - Any experience ?" by BELFST::LOGAN (DECkchair Attendant) Tue Apr 28 1992 12:57

	Has anyone in the ALL-IN-1 community any experience of developing an
	application, or do they know of an existing application that uses both
	INGRES and ALL-IN-1 ?

	Regards,
		Andy.
T.RTitleUserPersonal
Name
DateLines
584.1instead of opening a new note...NCBOOT::HARRISooopppsTue Jul 07 1992 23:4151
hi,

any ideas on this one?

customer has ALl-IN-1 2.4, INGRES 6.4  they have  a business application
that calls a .com file that calls an exe file (ingres).  
on the ingres menu, one of the choices is 
to spawn to DCL level. this works if its is called from a DCL prompt, but
will not work when called from within ALL-IN-1.
what happens is the user is put back to the ALL-IN-1 BA screen.

the customer is SURE that it is an ALL-IN-1 problem. a trace shows nothing
as does a 'set verify'.

the ultimate goal is to be able to bring a user into the editor (edt) from the 
ingres application that is called from ALL-IN-1. (does that make sense?)

here is the current .com file they are using. anyone have any ideas?

thanks - ann
_________________________________________________________________________________

$!WSP.COM  6-18-91
$!procedure to run WSP application from within ALL-IN-1
$!
$!get the current equivalence value for logical TT:
$ OLD_TT = F$LOGICAL("TT")
$!
$! ask AL-IN-1 parent process to tell subprocess the value of
$! symbol OS$TERM_DEVICE:
$!
$ WRITE OAMAILBOX "OA GET OA$TERM_DEVICE"
$@DCLMAILBOX:
$ING_TT = RESULT
$!
$!assign new value to logical TT based on results of preceding step:
$! preceding step
$!
$DEFINE/NOLOG/PROC TT 'ING_TT'
$!
$! set up app symbols
$RUNWSP = "$DIVISION$WSP:W0000.EXE W0000"
$set nocontrol =(y)
$RUNWSP
$set control =(y)
$!
$! Re-define TT to its previous value:
$ DEFINE/NOLOG/PROC TT 'OLD_TT'
$!
$EXIT

584.2Redefine SYS$INPUTUTRTSC::BOSMANThey sold you the view from a hillWed Jul 08 1992 07:595
    Hi,
    
    Try $ DEFINE /USER_MODE SYS$INPUT SYS$OUTPUT
    
    Sjaak.
584.3thanks!NCBOOT::HARRISooopppsWed Jul 08 1992 16:398
    thanks for the help sjaak!
    
    this almost works, i redefined the sys$input as in .2
    now instead of being returned back to the ALL-IN-1 BA screen, the user
    is returned to the INGRES screen.  its getting closer.  we'll keep
    playing with it.
    
    Thanks!!!!!!	ann
584.4The story goes on.UTRTSC::BOSMANThey sold you the view from a hillThu Jul 09 1992 07:5817
    And this one? Invoke with 'COMMAND mumble.COM \CLEAR'
    
    Regards,
    Sjaak.
    
$ main:
$    !
$    DEFINE /USER_MODE SYS$INPUT SYS$OUTPUT
$    !
$    runwsp = "$DIVISION$WSP:W0000.EXE W0000"
$    ctrl   = F$ENVIRONMENT( "CONTROL" )
$    !
$    runwsp
$    !
$    IF ctrl .NES. "" THEN SET CONTROL = ( 'ctrl' )
$    !
$ EXIT
584.5NCBOOT::HARRISooopppsTue Jul 28 1992 22:2716
    well, 
    
    i was finally able to access the form and the ND behind it.  the /CLEAR
    is on the line that calls the command
    
    	.TYPE
    ARG	/PRE="COMMAND DIVISION$WSP:WSP.COM"\CLEAR
    
    i found out that my predesesor had been given the same problem and
    determined that this wasn't an ALL-IN-1 problem.  my customer says that
    another comapny has this working, so we'll tryto find out what the
    diffs are between the 2 companies/systems.
    
    thanks for the helpful suggestions!
    
    	ann
584.6\CLEAR within /PRE_FUNCTIONUTRTSC::BOSMANThey sold you the view from a hillWed Jul 29 1992 08:3010
    Hi,
    
�   ARG /PRE="COMMAND DIVISION$WSP:WSP.COM"\CLEAR
                                          
    Should be:
    
    ARG /PRE="COMMAND DIVISION$WSP:WSP.COM \CLEAR"
    
    Regards,
    Sjaak.
584.7"further" clues to this INGRES mysteryOKBYUS::LUNDINWed Aug 26 1992 22:0818
    A follow on to Ann's notes.  We have done a little bit more research
    and found that the programmer who wrote the INGRES application did not
    really know of any other sites that were running this under the
    ALL-IN-1 umbrella.
    
    We have also found out that the INGRES application uses a command
    within INGRESS called 'CALL SYSTEM' to access DCL.  Again, from the DCL
    prompt it works fine, but from within ALL-IN-1, when the user takes the
    DCL option, the screen flickers and simply returns to the INGRES menu.
    
    Does anyone know of a method that we can get this INGRES application to
    access DCL from the BA menu within ALL-IN-1.
    
    Any ideas would be much appreciated.
    
    Thanks,
    
    Sandy 
584.8what about oaini.comNCBOOT::HARRISooopppsThu Sep 24 1992 21:1015
    still having nightmares on this one.....
    
    a totally differenet problem (for the same customer) was corrected
    witht the creationof OAINI.COM files in users .OA directorys.  now, the
    customer is asking if something needs to be inserted in the users or
    system wide OAINI.COM for this INGRES application to work from withing
    ALL-IN-1.
    
    the system OAINI.COM runs the SYSYMBOLS.COM and a common-login.com for
    all users.  the personal OAINI.COM re-runs users personal login.com.
    
    ALl-IN-1 2.4, VMS 5.5-1 (upgraded last weekend, but problem has been on
    going)
    
    	ann