× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Joe,
Why couldn't I just use take the IBM  replacement api's and execute them
from the same command name in a different library(i.e.qwebsys/wrksplf..etc).
When accessed from the web, the web users would have the command library
added to the top of their library list at start up....or perhaps you've
already come up with a better way to avoid source change.
Thanks
Don McIntyre

----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, June 17, 2003 12:04 PM
Subject: RE: webfacing and competing products


> > From: Don McIntyre
> >
> > Joe & others,
> > How do you handle, or suggest to handle the UI for non-dds based
> > applications (i.e.  os/400 menus, WRKSPLF, WRKSYSSTS...etc)?
>
> You need to balance the real business need with the how much work you are
> willing to do.  How many users actually need WRKSYSSTS?  Remember, a zero
> CPW machine still supports a single interactive display for operator
access.
> But if you really need some functions, you can roll your own using APIs.
> I'm currently working on partial replacements for some functions, such as
> WRKSPLF, using the APIs.  They're unlikely to be as fully featured as
IBM's
> commands, but in general they work fine.  And they'll be open source, so
you
> can use them as you please.  In fact, there used to be an open source
> version of WRKSPLF available.  And Brad Stone's got a WRKSPLF replacement,
> though it's not free, I don't think, and I don't know that he supplies
> source.
>
> And of course, if you need heavy access to certain features, OpsNav does
> alot of it for you.
>
> OS/400 menus can be replaced with DDS menus pretty quickly.  If you use
> command prompting rather than actual DDS, you're in a more difficult
> position.
>
> Your question needs to be addressed on a case by case basis.  The more
bound
> you are to the OS/400 command line or the 5250 data stream, the less
likely
> it will be that your application can move to the web.  If you simply
cannot
> live without certain OS/400 specific features, then you're bound to the
5250
> display.  The same holds true for people who used USRDFN data streams, or
> OV/400.  It's either change your approach, or stick with an emulator and
the
> intteractive tax.  At least now you can put an exact price on what those
> older technologies cost, and perhaps justify upgrading them.
>
> Joe
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.