|
Henrik, Thanks for the advice on the archives, Re:OV/400. Also, I didn't realise that I was using html-formatted mail, as I normally don't use yahoo.! Apologies. Brian. --- Henrik Krebs <hkrebs@hkrebs.dk> wrote: > Hi > > Are you telling me that (OV/400)... would still be > available on 5.1??? > > What I am telling is that you CAN make OV/400 run > unsupported on V5R1M0 > STRWP, MRGDOC, PRTDOC and more works for me and many > other. Several guidelines could be found about how > to do it. Basicly it is SAVLICPGM on V4, changing a > new switch on V5R1M0 and RSTLICPGM. Search the > archive for more about this. > > Also I tell that STROFC does not work for me (and at > least for some others). Apart from some applications > (doing a merge with an OV/400 doc) that need to be > replaced but hasn't been, I found an application > that does a SNDDST TYPE(*MSG). This is really not an > OV/400 function, rather an good ol' SNA > distribution, and I (emphasize I) can read it using > QRYDST and RCVDST. Users can't! My question was if I > need to write a program to allow the users to read > it, or if I can find another way. I already know > that I will not write a program - it's easier to > switch the program sending the sistribution to send > an smtp, but it might be even easier to use an > existing way to do the old 'work with mail'. > > Henrik > > PS: Why do you send html-formatted mail til > MIDRANGE-L? > > > Date: Fri, 3 May 2002 14:02:31 +0100 (BST) > > From: =?iso-8859-1?q?Brian=20Hughes?= > <b7ryn_midrange@yahoo.co.uk> > > Subject: Re: OV/400 on V5R1M0 > > To: midrange-l@midrange.com > > Reply-To: midrange-l@midrange.com > > > > -- > > [ Picked text/plain from multipart/alternative ] > > > > Hi, > > One of our stumbling blocks for moving to V5R1M0 > is that we still have some= > > need for WP mail merging (via STRWP), and we > don't actually use anything e= > > lse in OV/400. > > Are you telling me that this, although no longer > supported, would still be = > > available on 5.1??? > > If this is the case, then this potentially solves > several problems for us, = > > as we were are currently debating OV > replacements/writing in house LNotes s= > > oftware to replace it. I know it won't be > supported, but can someone enligh= > > ten me to how serve that really is, when it's only > used for simple mail mer= > > ging? > > Rgds, > > > > Brian. > > "hkrebs@hkrebs.dk" <hkrebs@hkrebs.dk> wrote: Hi > > > > We are running V5R1 on some systems together with > (unsupported) > > OV/400. > > o STROFC does not work (MCH3601 from program > =C6cfochkr to the CPP: > > QOFCPP). > > o WP (used in some older applications in order to > do user and system > > managed mail merge) works fine. > > o Sending distributions type *MSG works fine > > o Recieving distributions (with QRYDST + RCVDST) > works fine > > However: Anybody found a way for the user to > display the > > distributions? - this is the old STROFC option > 2=3DMail > > > > I could code it based on QRYDST/RCVDST, but I'm > lazy by nature. > > > > > --------------------------------------------------------- > > This mail was sent through TJGROUP Webmail: > http://webmail.tjgroup.dk > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
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.