Thanks to everyone for the responses

Ken, Thanks a lot for your detailed analysis.

I have worked on GIS 3.1 and Gentran NT and the visual mapper is pretty
similar. The unix one is really cumbersome. My client is on UNix 5.1 and not
planning to upgrade so the migration option is ruled out..

My Client is migrating to Tibco..

Looks like the analysis step has to be done with the Unix maps



On 9/8/06, KenCox(EDI) <[EMAIL PROTECTED]> wrote:
>
>  Hi Kumar,
> The standalone mapper in GIS is also known by Sterling Commerce as the
> "common mapper", because it is basically the same (is "in common
> with") across all the platforms;  however, this assumes you have already
> upgraded Gentran for Unix to at least version 6.0 and that you are using
> the Gentran "Application Integration" mapper.
>
> That is:  the Unix AI mapper and the Windows(NT) mapper are upwardly
> compatible to the GIS mapper.
>
> The Mentor or Visual Mapper is the old Unix mapper and is not compatible
> with the common mapper.  Prior to version 6.0 the map extension for
> Gentran for Unix Mentor/Visual mapper was .map.   When you upgrade to 6.0,
> the extension for the old mapper is changed to .vmp.   Don't be mislead by
> the Import function available starting with GIS 4.0.  It will read a .vmp
> and create a common mapper map, but you lose all extended rules;  that is,
> it will create the source and destination layouts, deactivate unused
> segments, and establish simple links, but not bring forward conditional
> logic.
>
> Which means that a mapping report from the imported map would not have the
> part of the documentation that you are looking for.  I would recommend
> printing the mapping report to a file (too cumbersome to waste paper on) and
> use it and drilling into the Mapping Instructions to accomplish your
> analysis.
>
> By the way, were you moving to the Common Mapper rather than another EDI
> product, I would tell you that for new maps, or once you've gone through the
> pain of recreating your VMP maps in the Common Mapper, you will like the new
> mapper MUCH better:  easier to use, more powerful, no problem with the order
> in which Mapping Instructions are executed, better mapping report, . . .
>
> Ken
>
>
>  ----- Original Message -----
> *From:* Brian Lehrhoff <[EMAIL PROTECTED]>
> *To:* Kumar Maganti <[EMAIL PROTECTED]>
> *Cc:* [email protected]
> *Sent:* Thursday, September 07, 2006 6:23 PM
> *Subject:* Re: [EDI-L] Gentran UNix map to NT conversion/migration
>
>
>
> oh, and you thing that mentor is hard to work with and hard to look at
> maps? it's a child's toy compared to
> other translators.
>
> Kumar Maganti wrote:
> > My objective is to view the Unix maps in the NT mapper..
> >
> > The UNix mapping report is very unfriendly and I need to reverse
> > engineer them to move to a different EAI/EDI software..
> >
> > The NT mapping report , even though it is clumsy is a little better to
> > understand..
> >
> > Thanks
> > Ram
> >
> >
> >
> > On 9/7/06, *Brian Lehrhoff* <[EMAIL PROTECTED]<blehrhof%40cybernex.net>
> > <mailto:[EMAIL PROTECTED] <blehrhof%40cybernex.net>>> wrote:
> >
> > You'll need to upgrade to either 5.3 or 6.1 first.
> >
> > Why don't you view the maps in Mentor? The maps and mappers are
> > nothing
> > alike.
> >
> > Kumar Maganti wrote:
> > > Hi All,
> > >
> > > Is it possible to import a Gentran Unix 5.1 map into the GIS
> > mapping tool?.
> > >
> > > All I have is a GIS 3.1 map Editor. I have a few Gentran Unix
> > maps that I
> > > would like to view in the map editor.
> > >
> > > Please let me know if there is an easy way to view the maps
> > visually in the
> > > Map editor of GIS.
> > >
> > > Thanks
> > > Ram
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > > ------------------------ Yahoo! Groups Sponsor
> > >
> > > ...
> > > 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
> > >
> > >
> > > mailto:[EMAIL PROTECTED]<EDI-L-fullfeatured%40yahoogroups.com>
> > <mailto:[EMAIL PROTECTED]<EDI-L-fullfeatured%40yahoogroups.com>
> >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> >
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > Brian Lehrhoff, EA ( [EMAIL PROTECTED] <blehrhof%40cybernex.net>
> > <mailto:[EMAIL PROTECTED] <blehrhof%40cybernex.net>>)
> > Messaging Consultant 201-913-4506
> >
> > Upgrade your Quickbooks for 20% off at http://www.brianlehrhoff.com
> > Circular 230 Notice is located at
> > http://www.brianlehrhoff.com/230notice.html
> >
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> >
> >
>
> --
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> Brian Lehrhoff, EA ([EMAIL PROTECTED] <blehrhof%40cybernex.net>)
> Messaging Consultant 201-913-4506
>
> Upgrade your Quickbooks for 20% off at http://www.brianlehrhoff.com
> Circular 230 Notice is located at
> http://www.brianlehrhoff.com/230notice.html
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
>  
>
>


[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:
    mailto:[EMAIL PROTECTED] 
    mailto:[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