Conference dssdev::decforms

3989.0. "IMGACT-F-NOTNATIVE" by TRN02::VIALE (Siamo in missione per conto di Dio) Tue Mar 11 1997 11:55

My customer told me that, while investigating another problem, he enabled 
the trace option and found the following error message.
This error doesn't affect the behaviour of the application that does work, 
but he would like to know the reason of the message.

The environment is AXP VMS system, ACMS 4.1, Decforms 2.1.
Any hint is fully appreciated.

Regards
Roberto

Here's the trace file:

Begin trace output to AS$ROOT:[AGI]TRACE.LOG;3 at 4-MAR-1997 17:06:42.19.
Begin ENABLE request.
 Begin Initialize request phase.
  Validate the arguments for this request.
  Begin searching image for form named 'AGI_MENU'.
  Attempting to resolve symbol FORMS$AR_FORM_TABLE in image AGI_TITOLO_NOTIZIE.
  %LIB-E-ACTIMAGE, error activating image $1$DKC301:[SVIL.AS_SVIL.][AGI]AGI_TITOLO_NOTIZIE.FORM;45
  -IMGACT-F-NOTNATIVE, image is not an OpenVMS Alpha AXP image
  Symbol resolution was unsuccessful.
   Search for form named 'AGI_MENU' failed.
  End search of image.
  Open form file named 'AS$ROOT:[AGI]AGI_TITOLO_NOTIZIE.FORM;45'.
  Read form file named 'AS$ROOT:[AGI]AGI_TITOLO_NOTIZIE.FORM;45'.
  Begin selecting a layout.
   Specified enable device is a Character Cell Terminal.
   Character cell terminal is a VT300. Width of 132. Height of 24.
   No layout with a matching language clause was found.
   Now searching layouts without language clauses for a suitable device match.
   Selected layout VT_LAYOUT.
  End selecting a layout.
  Records with unspecified alignment are BYTE aligned;/NOMEMBER_ALIGNMENT

    
    	DECforms attempts to load the image using LIB$FIND_IMAGE_SYMBOL and
    	the error indicates that the .FORM file is not an OpenVMS Alpha AXP
    	image (which it isn't).  DECforms then opens the file as a .FORM
    	and uses it as such.
    
    	Bill
    

Bill, thanks for the quick answer.

I'v a couple of questions, just to be sure to understand it correctly.

	a) is this the normal behaviour:
		DEcforms looks for a .EXE image - doesn't find it -
		logs the message - looks for a .FORM file, finds it,
		opens it and reads the content?

	b) if so, there's any workaround to avoid the error message on
	   the trace file?

Regards

Roberto

    
    	If the Task group definition does not specify a .EXE, then
    	DECforms will attempt to load the .FORM using
    	LIB$FIND_IMAGE_SYMBOL.  This is where the error is generated.  When 
    	the LIB$FIS fails, DECforms loads the .FORM file.
    
    	There error is transparent, it only shows up in the trace file.
    	Why is the customer so concerned about the error?  It's the
    	way it works.
    
    	Bill
    
    

    Bill, ok I got it.
    
    The customer was only concerned that the error might produce some delay 
    in the form activation. Actually the application is working fine.
    
    Thanks again
    
    Roberto

    
    	It does cause a small delay but it only happens once per CP.  Once
    	the file is opened, an additional references to form are satisfied
    	by the in-memory copy.
    
    	Bill