Probably a great question to ask IBM if you have a current maintenance 
agreement...    If you don't, I'd consider getting an additional knowledge & 
experienced resource that can help with the migration and the training to get 
your team up to speed.   It will be well worth the cost of using this type of 
resource and have an experienced guide in this journey, rather than try to do 
this yourself, take twice as long and then 

There are several competent professionals who belong to this list who can 
assist.  if you're not interested in that, I'd strongly recommend you consider 
getting some SI training at the least...

Ken
[email protected] 


________________________________
 From: S Sreedhara <[email protected]>
To: EDI-L <[email protected]> 
Sent: Thursday, August 30, 2012 11:25 PM
Subject: [EDI-L] Gentran to SI migration
 

  
Hi All,

At present we are using Gentran 5.2.

We are planning to Migrate to Sterling Integrator.

Can i get some suggestions as how much efforts are required, time taken for the 
change and what are the core things to be focussed on for the migration
 
Thanks,
Sreedhara.S.

[Non-text portions of this message have been removed]


 

[Non-text portions of this message have been removed]



------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to