Initial Estimate guideline for a straight green-screen Axiant migration

[Glenn Baxter]

Hello Wilbert, 
I have watched this thread, but have not ventured down the "green screen"
under NT/Axiant yet!

I am close to wrapping up an extensive conversion from Hp3000 to Nt which
has been based 
on Axiant so am glad to offer some thoughts with respect to Axiant's
migration method/s.
We are using SqlServer2000 under Win2k, utilising a Thin Client deployment.
Axiant 3.4 Build 1799.51
Powerhouse 8.41c

The database conversion {some 120 tables across 10 databases and 2
applications} was pleasingly straight forward, data-types were readily
compatable. We utilised an unload/transfer/load method via portable
subfiles. {Create on Hp, Transfer and Qtp Load}.
I have a VB script generating app which is fed from a list of tables {based
on a Qshow Report}.
We then reviewed and flagged tables as required or not required to ease this
process. Overall we excluded Auto Masters etc.
The VB Code {within Access} generates Unload and Reload code for execution
on the Hp and then under Nt.
Some manual work was required with respect to the reload "Item" statements
mostly with respect to Null date fields and 
Array initialisations. The object here was to utilise the Powerhouse "common
name initialisation" feature of Qtp by 
editing the Portable Subfile Dictionary changing dashes to underscores!
Essentially

Access *ULSFNNN
Output  TABLE Add
Go

This saved a lot of work. (120 tables and a lot of column names)

Axiant was then used to generate the data structures from the PDL import, as
relational objects of type Microsoft Sql Server, adding
INDENTITY_COL{umns} where uniqueness was not able to be applied. {some
detail sets}
Axiant will generate sql script to build the databases within Sql Server
Query Analyser.
This all works well, despite some minimal changes for those IDENTITY
columns.
Qtp was then used to load the tables. Axiant/Quiz and Sql Server
Administrator for verification.

All Quiz/Qtp code was examined with respect to our Thin Client deployment,
looking for PARM PROMPT/CHOOSE items and
setting a common Print/Disc output target and report naming convention for
output Quiz programs.

The change Manager within Axiant manages dash to underscore changes, removal
of Numbered source files etc.
It can be supplemented with element syntax changes to manage arrays and
subscripts to those arrays, which 
dissapear within the relational world.
Some "obsolete" statements are not addressed such as the "SUBFILE SIZE"
statement in quiz. It is highlighted in
subsequent compiles though.

We found most work was required with respect to command files {stream and
use files} from the Hp.
Some global editing of Quick code was done prior to import to remove "group
names" from many of these calls.

Extensive re-work of menus was required to relate the new command files to
buttons, as we are deploying only the GUI forms.
Understanding the inheritance within Axiant is imperative to achieve a
standard look and feel across the system, prior to
migrating screens objects.

Multipass Quiz and Quiz/Qtp/Quiz subfile dependencies require solid
attention. The use of Axiant folders and shortcuts can assist in managing
this messy aspect of Powerhouse code.
We joined many "multi-pass" objects into "Suites" to enable ready
compilations.

You had said that you were aware of the Printing issues. You will understand
the requirement to send output to disc files.
Thin client deployment adds another layer with respect to parms and prompts
and environment variables.
We have created an Sql database and VB application which encapsulates the
relationships between

Command File {Submit Item}
..Submittable Components {Qtp, Quiz, OS Command} / Programs
....Submittable Item Parm Objects {Unbound or Bound using Sql, Choose or
plain Parm & Prompt}

Users
..Powerhouse Printers
....Users_Default Printers.

and Scheduling of tasks using
WinCron for Nt.

The VB program reads the Sql Database for the targetted Batch File and
populates a dynamic form with Sql generated list boxes 
or unbound boxes with variables captions. The App basically builds "bat" and
input paramater files {.IPF}  to paths 
predefined by environment variables for each user.

Printer dialogue is also provided where "Printed Output" is required,
offering a choice of "Powerhouse Printers" and Report Copies.
Each user has her/his own "spooler" folder, controlled through environment
variables and LOGONID or User_Id.

Summary!
The Axiant Migration tools are good, but much depends on the nature of your
application. Ours was predominantly
batch based, which we now manage through our data driven "Batch/Submit"
system.

We have found Sql server to be robust and easily managed.
Performance is also very good. Many say Quiz is slow, but compared to a
Hp917 task at 15 minutes, we
are achieving a ~1-2 minute turnaround. The replacement of Access statements
with Sql cursors is also an 
option here.

Let me know if we can be of further assistance.
Replacing the Hpe!!3000 is not an easy task!
Although considered daggy by many it's reliability, database integrity,
session, job, spooler, scheduling 
and monitoring features are not readily replaced!

Sincerely, 
Glenn Baxter
Baxter IT Solutions
==============================
15 Flora Grove Ivanhoe Victoria Australia 3079
==============================
telephone: 61-3-9499-8687
mobile: 0412-826-503
fax: 61-3-9499-8344
email: glenn@baxterit.com.au <mailto:glenn@baxterit.com.au> 
 
This e-mail message (and attachments) may contain information that is
confidential to Baxter IT Solutions. If you are not the intended recipient
you cannot use, distribute or copy the message or attachments. In such a
case, please notify the sender by return e-mail immediately and erase all
copies of the message and attachments. Opinions, conclusions and other
information in this message and attachments that do not relate to the
official business of Baxter IT Solutions are neither given nor endorsed by
it.

-----Original Message-----
From: VISSERS,WILBERT (HP-NewZealand,ex1)
[mailto:wilbert.vissers@hp.com]
Sent: Thursday, 16 October 2003 7:58 am
To: 'powerh-l@cube.swau.edu'
Subject: RE:Initial Estimate guideline for a straight green-screen
Axiant migration


Thanks Blue, Mark, Jon,  

Have spoken to our Customer and PH8.41 and Eloquence is now a base-line
option if the business decision is 'go the minimum cost option'.  Thanks
that was good.

The IT Manager wants the migration to go to the platform that allows modern
stuff to evolve best, because he expects that the percentage of people
seeing the value of Windows/Gui/Web will grow soon.  We need to be in best
position to respond.  Also the competitor option is all new stuff.

Decision on the database is down the track a bit, either SQL Server for
perhaps ease of future integration with Microsoft-written apps which the
customer has, or Oracle for robustness.  or Eloquence.  See the future of
the application as evolving into a mix of Competitive-advantage, local
efficiency modules,  interfacing with standard ERP modules.   Current app is
well-designed and modular so this looks feasible.

Need that ballpark guidance on Axiant's automated conversion tools.  All we
have to compare with so far is migration projects done in other technologies
'by hand', and PH conversions where significant proportion of the project
was spent writing home-grown code-altering utilities. 

cheers
Wilbert
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.