[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

2289.0. "Receive from VMS error" by GANTRY::HULL (Digital Services Delivery - Motown) Thu Feb 18 1993 15:13

I'm running a Coexistant V3.0 system on VMS 5.5-2 along with the production
V2.4 system.

When I tried to migrate some customizations over to V3 using AM RV, the
receive action would fail to copy the files out of the receive area into
the dev area.  SITELOG records would get written, however.  Working with
the Support Center we tracked that down as caused by the OA$SITE_DEV*
logicals for V3 were missing. ???  I reran the startup and they were
defined and could now move the files correctly.

However, the RV procedure automatically gens some kind of report, and when
I queued it to our printer, I got the following fatal A1 error (it dropped
me out immediately to DCL:


%KOA-F-UNHKOAEXC, Unhandled KOALA exception INTEGER_CONVERSION
-KOA-F-EXCTRAHDR, Active exception traceback follows:

$

I successfully printed a document from WP menu right after getting back in,
so it doesn't appear to be a general printing problem.

Is this some side effect of running co-existant?  I hope this can be
resolved, as I have a huge application to port over.

	Al

T.R Title User Personal
Name Date Lines

2289.2 Not sure how UTES09::EIJS Simon Eijs @Utrecht, 7838-2558 Thu Feb 18 1993 16:51 19

T.R	Title	User	Personal Name	Date	Lines
2289.2	Not sure how	UTES09::EIJS	Simon Eijs @Utrecht, 7838-2558	`Thu Feb 18 1993 16:51`	19
	Hi Al, The report is a normal .WPL files, the result of a MERGE, and number of procedures and GET OA$MERGE_LINE functions. Next to a TRACE, it would be nice to have the actual .WPL in the end. Can you 'Print' the report to a FileCabinet Document and send it to me? As all good things come in two, you actually seem to hit quite a problem; the fact that an error status isn't picked up. However, the PUT_SOURCE routine should generate an status of #CM_STATUS = 0, and CM_TRANS_ELEMENT_FROM_VMS.SCP triggers that status, it deletes the record just created from CM$SITELOG and adds a line in the report concerning the error. So nothing seems wrong here. As said, a piece of TRACE would help. Ciao, Simon

    
    Hi Al,
    
    The report is a normal .WPL files, the result of a MERGE, and number of
    procedures and GET OA$MERGE_LINE functions. Next to a TRACE, it would
    be nice to have the actual .WPL in the end. Can you 'Print' the report
    to a FileCabinet Document and send it to me?
    
    As all good things come in two, you actually seem to hit quite a
    problem; the fact that an error status isn't picked up. However, the
    PUT_SOURCE routine should generate an status of #CM_STATUS = 0, and
    CM_TRANS_ELEMENT_FROM_VMS.SCP triggers that status, it deletes the
    record just created from CM$SITELOG and adds a line in the report
    concerning the error. So nothing seems wrong here. As said, a piece of
    TRACE would help.
    
    Ciao,
    
    	Simon