re(2): Cross-Version Integration

Remember that System Manager (Application Manager) i.e. the Menu System does 
not need to only refer to JBA programs.  We have a development machine here (we 
are a software house dealing with multiple JBA customers - some of whom have 
different versions of JBA (for bespoke reasons).  You can have menus point to 
V2 tasks and V3 tasks (and bespoke tasks for that matter).  I would suggest 
first checking the environment that V2 is defined for, then do the same for V3. 
 (After selecting a V2 task have a look at the LDA (pos 141-143).  I suspect 
these will be different.

You should then be able to look at menus in each of these environents 
(regardless of which environment you are signed on as) and like wise you should 
be able to maintain menus that refer to tasks in both versions (remember 
library lists are set at an application (version) level so as long as you point 
the menu to the right task everything else should work ok.

As I have said this is not difficult to accomplish.

Let me know if you require any further information.  (or if I have picked 
things up wrongly)


Barry

>>>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<<<

To:             JBAUSERS-L@midrange.com
From:           DAsmussen@aol.com (DAsmussen@aol.com)
Subject:                Re: Cross-Version Integration

Dave,

In a message dated 10/31/00 2:46:37 PM Eastern Standard Time, 
DBarry@dawnfoods.com writes:

> Wow what a challenge!
>  
>  Are all your V2 application definitions under one roof?  That is, are they
>  all defined under the V3 Application Manager.   If you can get this done
>  you might have a chance because under Application Manager just about
>  everything is driven based on application and version number.  So you
>  should be able to have some menus pointing to V2 tasks and others pointing
>  to V3 tasks.

Frankly, I don't know.  That's why I'm asking.  Our JBA is run out of a "home 
office" on the other side of the country that hasn't exactly been forthcoming 
about the infrastructure.  The "home office" attitude seems to be "ask us and 
we'll do it for you" (in about 3-6 weeks), instead of "ask us and we'll tell 
you".  Our project only lasts until the end of the year, so spending 3-6 
weeks for every single thing that we want to do is a bit unreasonable.  All I 
know is that issuing STRM400 only seems to impact V2 applications, even if 
you're in V3.  For example (V2 is all inventory, sales order, warehousing, 
manufacturing applications) STRM400 from a V2 application allows menu 
maintenance of those applications.  The same from a V3 application (GL, AP, 
AR) still does not recognize menus from that application -- as if we were 
still under V2.  We have "bridge" libraries for the files, but appear to have 
no means of maintaining menus and tasks for V3.

TIA,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"There is something fascinating about science. One gets such wholesale 
returns of conjecture out of such a trifling investment of fact." -- Mark 
Twain
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---


+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---