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

Conference orarep::nomahs::dbintegrator_public_public

Title:DB Integrator Public Conference
Notice:Database Integration - today! Kit/Doc info see note 36
Moderator:BROKE::ABUGOV
Created:Mon Sep 21 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1171
Total number of notes:5187

1077.0. "3.1 on AXP X 2.0 on IBM" by ORAREP::VAXRIO::CSANTOS () Tue Jul 09 1996 13:35

    
    	Hi,
    
    	We have a customer running DBI for DB2 version 3.1 on VAX side
    	and 2.0 on IBM side.
    	Is this supported???
    
    	They are getting SQL code when running DBI under ACMS, they say
    that when they run it from a "normal"process it works fine (same
    program).
    
    			Any hints??
    
    				Thanks in advance
    
    						Claudia
T.RTitleUserPersonal
Name		DateLines
1077.1What is the error code?BROKE::ABUGOVTue Jul 09 1996 15:2113
    
    Hi Claudia,
    
    It is supported to have V2 on the client side. A quick thing to look at
    would be AUTHORIZE parameters and SYSGEN parameters to make sure the
    ACMS process has more then the interactive process that works.  There
    are significant additional resources required by ACMS that wouldn't
    show up in the interactive environment.  What error message are you
    seeing?
    
    Thanks,
    
    Dan
1077.2SQLCODE -1ORAREP::VAXRIO::63198::CSANTOSClaudia Nogueira - CSC/BrazilWed Jul 10 1996 07:539


	It just returns SQLCODE -1... We will try increasing quotas...


				Thanks
	
					Claudia
1077.3some more informationORAREP::VAXRIO::63198::CSANTOSClaudia Nogueira - CSC/BrazilWed Jul 10 1996 09:1311

	Some more information...  They have the ACMS servers 
	defined with DCL AVAIABLE clause (they used to have this problem
	when using the VAX, that clause did solve the problem).  Now 
	that they are using a AXP and new version, should it still be
	used, would there be any compatibility problem??

				Thanks once more

						Claudia
1077.4No ACMS expertise here...BROKE::ABUGOVWed Jul 10 1996 09:2512
    
    Hi Claudia,
    
    I'm sorry, my lack of ACMS expertise is a real hinderance in answering
    these questions.  Could it be that there are logical names or some such
    that need to be seen by the ACMS server process?  I'm not sure what DCL
    AVAILABLE gets you, but if they had a similar problem without it on VAX
    then I would think it would be required for AXP.
    
    Sorry I'm not more help,
    
    Dan
1077.5DCL_Available is required on alpha alsoBROKE::ALAWLERWed Jul 10 1996 10:2423
    
    
      DCL_Available simply maps DCL into the ACMS 'server procedure' 
    process context.  It was added in acms V3.3(?) to allow calls to
    Vida For DB2  from within ACMS server procedures.
    
    Your question isn't clear,  but I'm assuming you just rebuilt 
    the Task Group on alpha with no changes, in which case,  
    DCL should already be present there as well.  (IF not,  then
    this would indeed cause the error.) 
    
      Do you see any specific errors in ACMSATR or ACMSSWL?
    
      To the best of my knowledge, DCL_AVAILABLE worked correctly 
    on ACMS V4.0 on alpha without any tuning changes,  but you might 
    want to check the release notes (or check with somebody in ACMS 
    land to be sure.)
    
    
    						-al