Migration to Axiant

[Whittall, Conrad]

I'd like to point out that, using Axiant 4GL 3.0, putting hot areas over
fields is no longer required as the new Events Section of an Axiant screen
program provides the capability to define what happens when a user clicks on
a field (or a label, or anything else on an Axiant form). By default, a
single-click triggers the ID associated with the underlying FIELD
statement...thus achieving what Martin has used hot-areas to do. I believe
that Martin was probably using Axiant 4GL 2.02 or 2.03 when he started his
migration, and so would have had no option but to use hot-areas to provide a
Windows-like click interface in his Axiant forms.

If you haven't already done so, I'd recommend downloading the latest Axiant
documentation from the Cognos web site, at www.cognos.com/axiant. I'd also
suggest taking a look at the Axiant Migration Planning Guide, at
www.cognos.com/products/axiant/guide.html.

Best regards,
Conrad

Conrad Whittall
Marketing Manager, Application Development Tools, Cognos Incorporated
3755 Riverside Drive, Ottawa, Ontario, K1G 4K9, Canada

Developer productivity never goes out of style!

For details of the Cognos PowerHouse family of high-productivity
development tools for Web, Windows and terminal-based business
applications just look here, http://www.cognos.com/powerhouse.


-----Original Message-----
From: Martin McDonough [mailto:MartinM@Rosebys.com]
Sent: Monday 8 January 2001 12:53
To: 'David Collado Zamarriego'; powerh-l@sphere.swau.edu
Subject: RE: Migration to Axiant


When migrating screens, the tasks to be done are:- replace your function
keys with buttons & place hot keys over fields to replace id numbers. Not
really a problem just a bit time consuming.

The major problem you might face is, if you use temporary files and system
values. There are two ways to run axaint on the 3000 - 1. The sub process
method and 2. The job stream method.

1.	the sub process method - all users who log on to axaint go through
the one batch job on the 3000. As we use system values to pass data from one
screen to another, this method is no good as multiple users  overwrite each
others system values.

2.	the job stream method. - all users who log on to axiant, are each
set up as an individual batch job (not a session). To do this successfully
you will need to have separate job queues on your 3000. To do this you will
need to upgrade to mpe 6.0

To answer your question it's not difficult to migrate, and when, in our
case, your company directors see pictures next to product data, they will be
greatly impressed and it will be worth all the effort. (and save your 3000
as well !!)

Regards

Martin McDonough


> -----Original Message-----
> From:	David Collado Zamarriego [SMTP:dcollado@musini.com]
> Sent:	08 January 2001 16:59
> To:	powerh-l@sphere.swau.edu
> Subject:	Migration to Axiant
> 
> Hi everyone!
> 
> We are running PowerHouse 8.19 on MPE/iX 5.5.
> 
> We are considering the possibility to migrate to Axiant, but we have many
> questions to answer before making this decision:
> 
> Is it hard to migrate?
> How many people is migrating to Axiant?
> 
> We are an insurance company in Spain, is there many people in Spain going
> to Axiant?
> 
> Thanks in advance. This is an strategic decision for us.
> 
> Regards.
> 
> David
> 
> 
> -------------------------------------------------------------
> David Collado Zamarriego
> Analista de Sistemas
> Musini, S. A. de Seguros y Reaseguros
> dcollado@musini.com
> C/ Manuel Cortina, 2
> 28010 Madrid - Espaņa
> Tf.  (+34) 91 550 9090
> Fax (+34) 91 550 9000
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.