dbTalk Databases Forums  

Modernizing PICK applications

comp.databases.pick comp.databases.pick


Discuss Modernizing PICK applications in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Usha
 
Posts: n/a

Default Modernizing PICK applications - 05-01-2007 , 04:17 AM






Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha


Reply With Quote
  #2  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 11:28 AM






Excuse me, are you saying the way to modernize an MV application is to
migrate it to a relational DBMS?

Usha wrote:

Quote:
Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha


Reply With Quote
  #3  
Old   
Usha
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 12:03 PM



Tony, No, that's not what I mean.

In the PICK BASIC application that we converted, the file definitions
from the dictionary convert to a relational structure. The codes, i.e.
application logic present in the programs, some in the processes, some
even as validations in the dictionary fields then get converted to
codes in .NET or JAVA (they may go to the presentation, business or
database layer based on where they belong)

Of course, the process of converting from a MV file structure to a
relational schema is quite complicated, but there is a set of logical
steps that have been implemented in our toolset that makes this
easier.

Thanks,
Usha

On May 1, 9:28 pm, Tony Gravagno
<address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Quote:
Excuse me, are you saying the way to modernize an MV application is to
migrate it to a relational DBMS?

Usha wrote:
Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha



Reply With Quote
  #4  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 01:13 PM



I'm afraid you're not making a very good case for your offering and I
think this might just be a communication problem. Let's try again.

Are you offering to develop a new front-end using .NET, Java, and
other technologies for presentation - without moving the MV back-end
to another database?

T

Usha wrote:

Quote:
Tony, No, that's not what I mean.

In the PICK BASIC application that we converted, the file definitions
from the dictionary convert to a relational structure. The codes, i.e.
application logic present in the programs, some in the processes, some
even as validations in the dictionary fields then get converted to
codes in .NET or JAVA (they may go to the presentation, business or
database layer based on where they belong)

Of course, the process of converting from a MV file structure to a
relational schema is quite complicated, but there is a set of logical
steps that have been implemented in our toolset that makes this
easier.

Thanks,
Usha

On May 1, 9:28 pm, Tony Gravagno
address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Excuse me, are you saying the way to modernize an MV application is to
migrate it to a relational DBMS?

Usha wrote:
Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha



Reply With Quote
  #5  
Old   
dawn
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 01:18 PM



On May 1, 12:03 pm, Usha <usha.rai... (AT) gmail (DOT) com> wrote:
Quote:
Tony, No, that's not what I mean.

In the PICK BASIC application that we converted, the file definitions
from the dictionary convert to a relational structure. The codes, i.e.
application logic present in the programs, some in the processes, some
even as validations in the dictionary fields then get converted to
codes in .NET or JAVA (they may go to the presentation, business or
database layer based on where they belong)

Of course, the process of converting from a MV file structure to a
relational schema is quite complicated,
Not only is having to do an "OO"-RM mapping complex, it is
unnecessary. I predict that the trend within the coming decade will be
to move more and more from relational first-normal form structures to
data structures more like Pick (e.g. XML). So, I would advise anyone
interested in modernizing their applications to talk to folks like
those at intersystems.com or sierra-brava.com who allow you to
modernize your application while retaining the all-around bigger-bang-
for-the-buck data model in Pick. Just my two cents (you can get the
10 cent version at my blog at tincat-group.com/mewsings. Cheers! --
dawn

Quote:
but there is a set of logical
steps that have been implemented in our toolset that makes this
easier.

Thanks,
Usha

On May 1, 9:28 pm, Tony Gravagno



address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Excuse me, are you saying the way to modernize an MV application is to
migrate it to a relational DBMS?

Usha wrote:
Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha- Hide quoted text -

- Show quoted text -



Reply With Quote
  #6  
Old   
chandru murthi
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 03:08 PM



"Tony Gravagno" <address.is.in.posts (AT) removethis (DOT) com.invalid> wrote in
message news:fm0f33d0i1aph4r0idpoulih0104ph3od5 (AT) 4ax (DOT) com...
Quote:
I'm afraid you're not making a very good case for your offering and I
think this might just be a communication problem. Let's try again.

Are you offering to develop a new front-end using .NET, Java, and
other technologies for presentation - without moving the MV back-end
to another database?
Usha wrote: "...modernize to .NET / JAVA supported by an RDBMS like SQL
SERVER/ DB/2 or ORACLE."
I think that's pretty clear.

My questions would be how long does the process of migration take and what
does it cost-- time, effort, personnel after the shift?

Chandru
Quote:
T

Usha wrote:

Tony, No, that's not what I mean.

In the PICK BASIC application that we converted, the file definitions
from the dictionary convert to a relational structure. The codes, i.e.
application logic present in the programs, some in the processes, some
even as validations in the dictionary fields then get converted to
codes in .NET or JAVA (they may go to the presentation, business or
database layer based on where they belong)

Of course, the process of converting from a MV file structure to a
relational schema is quite complicated, but there is a set of logical
steps that have been implemented in our toolset that makes this
easier.

Thanks,
Usha

On May 1, 9:28 pm, Tony Gravagno
address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Excuse me, are you saying the way to modernize an MV application is to
migrate it to a relational DBMS?

Usha wrote:
Hi,

We specialise in providing application modernization services, for
multi-value applications. We do this with a robust migration
methodology, supported by automation tools that can convert to a
browser-based, n-tiered application in .NET or JAVA.

Our toolset supports various languages like COBOL, FORTRAN,
Powerbuilder, IBM RPG, PICK BASIC, Visual Basic (x) & can modernize
to .NET / JAVA supported by an RDBMS like SQL SERVER/ DB/2 or ORACLE.

We have successfully migrated an insurance application where :
Old application: (Raining Data) PICK/BASIC with D/3 database
New application: Browser-based JAVA application, with STRUTS, business
beans were deployed on BEA Weblogic & the database layer was created
with JDO (Java Data Objects) on Open Access Versant server. The RDBMS
converted to was IBM DB/2.

Pls. respond if you are looking for a solution like ours. We would
handle the entire scope of the migration project, from inventory,
planning, migration, testing & deployment.

Thanks & warm regards,
Usha




Reply With Quote
  #7  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 04:51 PM



dawn wrote:
Quote:
So, I would advise anyone
interested in modernizing their applications to talk to folks like
those at intersystems.com or sierra-brava.com who allow you to
modernize your application while retaining the all-around bigger-bang-
for-the-buck data model in Pick.
Hey! And don't forget Nebula R&D. That's is what the Research and
Development is all about!

TG@ removethisNebula-RnD.com


Reply With Quote
  #8  
Old   
dawn
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-01-2007 , 05:09 PM



On May 1, 4:51 pm, Tony Gravagno
<address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Quote:
dawn wrote:
So, I would advise anyone
interested in modernizing their applications to talk to folks like
those at intersystems.com or sierra-brava.com who allow you to
modernize your application while retaining the all-around bigger-bang-
for-the-buck data model in Pick.

Hey! And don't forget Nebula R&D. That's is what the Research and
Development is all about!

TG@ removethisNebula-RnD.com
Yes, of course, that's what I meant to say! DesignBAIS comes to mind,
along with mv.NET and such, all of which Nebula R&D knows.

Good point that there are many companies who know how to modernize
Pick/MultiValue apps, most of whom know how to do so without having to
ravage the elegant data model (even if the app's logical data model
should be re-engineered after years of maintenance, the underlying
data model is elegant).

Sorry, Usha, I can't jump on your bandwagon. But if you find some
folks using "current" tools and finding them bloated, overly complex,
difficult to maintain, making it expensive to refactor your solutions
over time, you might suggest they look at one of the many NF2 (non-
First Normal Form) databases available today, including Intersystems
Cache', IBM U2 and Ladybridge OpenQM.

It is feasible today to have a modern UI and a solid, best-bang-for-
the-buck data model and corresponding DBMS so as to avoid the
impedance mismatch that SQL-DBMS users must contend with.
http://www.tincat-group.com/mewsings...impedance.html

Cheers! --dawn



Reply With Quote
  #9  
Old   
Rob Tweed
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-02-2007 , 05:10 AM



On 1 May 2007 11:18:33 -0700, dawn <dawnwolthuis (AT) gmail (DOT) com> wrote:

Quote:
So, I would advise anyone
interested in modernizing their applications to talk to folks like
those at intersystems.com or sierra-brava.com who allow you to
modernize your application while retaining the all-around bigger-bang-
for-the-buck data model in Pick. Just my two cents (you can get the
10 cent version at my blog at tincat-group.com/mewsings. Cheers! --
dawn
....and if you take the InterSystems/Cache route, you then have the
option of exploiting the very latest Web 2.0 and Ajax techniques by
using our eXtc Web Developer technology (www.mgateway.com/ewd.htm)

---
Rob Tweed
Company: M/Gateway Developments Ltd
Registered in England: No 3220901
Registered Office: 58 Francis Road,Ashford, Kent TN23 7UR

Web-site: http://www.mgateway.com


Reply With Quote
  #10  
Old   
Usha
 
Posts: n/a

Default Re: Modernizing PICK applications - 05-03-2007 , 11:34 AM



Hi,

Yes, our solution will give you a new front-end layer in .NET/ JAVA,
the business will also be in a mid-tier on .NET/ JAVA, while the
database will be in an RDBMS. Everything can move out of the MV
environment to a open system, supported by an RDBMS.

Thanks,
Usha


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.