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

Conference ilbbak::ibi_focus

Title:	FOCUS, from INFORMATION BUILDERS

Moderator:	ZAYIUS::BROUILLETTE

Created:	Thu Feb 19 1987
Last Modified:	Mon May 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	615
Total number of notes:	1779

522.0. "IBM Focus to VAX/VMS Focus" by ZPOVC::LAYCHOO () Fri Jun 26 1992 07:08

    Hi,
    
    A customer is interested in porting their FOCUS application and data
    from IBM/VM environment to VMS Focus. 
    Can anyone enlighten me on how the process is done and also highlight
    any pitfalls to watch out for. According to our local Focus
    distributor, it is an extremely straight forward task of just backing up
    the application and data from the IBM machine and then restoring them on 
    the VAX machine and the application will run. It sounds too good to be
    true.
    Apprec. any info and/or experiences of doing this transfer,
    
    Thanks.

T.R Title User Personal
Name Date Lines

522.1 IBM Focus to VAX Focus EVTDD1::CARRIERE Jean-Claude Carriere Fri Jun 26 1992 13:13 39

T.R	Title	User	Personal Name	Date	Lines
522.1	IBM Focus to VAX Focus	EVTDD1::CARRIERE	Jean-Claude Carriere	`Fri Jun 26 1992 13:13`	39
	Hello, Well, if backing-up was all you had to do, It would be too easy Wouldn't it ? I haven't done it, but here are some guidelines (and I'm sure IBI as plenty of fellows with large experience in this domain) : o Porting the data : For FOCUS Database you'll need to run on the VAX a conversion utility (IMPORT) mainly for (floating point number conversion, EBCDIC->ASCII etc...) For other data files : VSAM or so you may have to do similar work (except no conversion utility) o Porting Application code The first thing is to identify the level of release require to run the application (does it use feature from FOCUS/VM 6.0 which ones ... etc ... Then you need to identify portion of the code which are system dependant (and have been isolated to few Focexecs if the developper was smart) : Things like FILEDEF's or -CMS command are going to require changes to adapt to VAX file directory structure and VMS DCL syntax... I'm sure this is incomplete, but people with experience can probably give you time estimates based on the number of Focexec's. One criteria might be how isolated the system dependant code is, e.g. how smart developper were in the first place. It is certainly more than just doing a backup, however for what I have heard it generally works out pretty well. Hope this shed some light on the subject.

Hello,

	Well, if backing-up was all you had to do, It would be too easy
	Wouldn't it ?

	I haven't done it, but here are some guidelines (and I'm sure
	IBI as plenty of fellows with large experience in this domain) :

	o Porting the data :

		For FOCUS Database you'll need to run on the VAX a
		conversion utility (IMPORT) mainly for (floating
		point number conversion, EBCDIC->ASCII etc...)

		For other data files : VSAM or so you may have to do
		similar work (except no conversion utility)

	o Porting Application code

		The first thing is to identify the level of release
		require to run the application (does it use feature
		from FOCUS/VM 6.0 which ones ... etc ...

		Then you need to identify portion of the code which
		are system dependant (and have been isolated to few
		Focexecs if the developper was smart) : Things like
		FILEDEF's or -CMS command are going to require changes
		to adapt to VAX file directory structure and VMS DCL
		syntax...

	I'm sure this is incomplete, but people with experience can
	probably give you time estimates based on the number of Focexec's.
	One criteria might be how isolated the system dependant code is,
	e.g.  how smart developper were in the first place.

	It is certainly more than just doing a backup, however for what
	I have heard it generally works out pretty well.

Hope this shed some light on the subject.