Re: Office Vision in V5R1 -- MIDRANGE-L

--
[ Picked text/plain from multipart/alternative ]
Al:

Thanks for the explanation.

>
>
>
>Dave:
>
>>Is anybody using Office Vision in V5R1?.   If so are you finding it
>>works with all the features?   V4R5 is the last release it is supported.
>>I recently heard that it will work on V5R1 but IBM will not guarantee it.
>>
>
>It's my understanding that most of OV/400 will not work in V5R1.  First of
>all, IBM has disabled/removed most of the underlying API support that had
>proven very expensive to maintain.  Secondly, when you install V5R1, OV/400
>is automatically removed, and V5R1 RSTLICPGM is supposed to me too smart to
>allow you to re-install it.  On the other hand, if you can isolate the
>libraries/objects/DLO's and related to OV, SAVOBJ/SAVLIB/RSTOBJ... is
>stupid enough to allow you to get the parts back, although it will not me a
>"registered licensed program:.  Parts of it will work, some poorly.
>
>The only success that I have heard of are people that have done one of the
>three following things:
>
>1).  Moved to Lotus Domino
>     a).  EXPENSE(*NOMAX)
>     b).  Many more capabilities, but different
>     c).  Some less capabilities, but different
>     d).  WORK(*MAX)
>     e).  BUGS(*MORE) - This is not a Rochester product, it's a port.
>
That means I need pc's in the desk and replace the green screens.  Go
through a education session of how i can replicate mrgdoc, prtdoc etc.
 No thanks.  Besides buying licenses for office, domino :-(

>
>2).  Bought the replacement package from the European vendor.
>     a).  EXPENSE(*MAX)
>     b).  WORK(*NONE)
>
Evergreen/400 claims it can still do the green screen.  But it is
pricey.  ITS/400 wants to help you move to domino and word ... yuck.

>
>3).  Migrated back to Text Management/38
>     a).  EXPENSE(*MIN to *NONE) (depending if you already owned System/38
>Utilities)
>     b).  Many different capabilities and yet some the same.  Good solution
>for mail merge of static letters and help text, EDITOR(*80s)
>
>     c).  WORK(*MIN to *MODERATE).
>
Never used this, where would I find it? is it in every release installation?

>
>Al
>
I had received the following from a source a while ago.  I am
reproducing it fyi.  Do note that it confirms what you said about V5R1.
 The reason I asked the question earlier is because as users we are very
creative and wondered who was able to go around the restriction and was
willing to share the knowledge.


DAVE,

IF YOU WANT ME TO STOP SENDING YOU THIS OV/400 RELATED JUNK EMAIL THAT
IS FINE, MY FEELINGS WON'T BE HURT.  HOWEVER I THOUGHT THEY MIGHT
INTEREST YOU, WHICH IS THE ONLY REASON I AM FORWARDING THEM...

        I have had similar questions regarding these commands from solution
providers in different parts of the country -- usually an indication that
this is of concern to many of you and to your customers. The first part of
this note was received from contacts within the Rochester Development Lab
(where the AS/400 is manufactured and supported) and is very detailed about
many of the commands commonly associated with Officevision, but really part
of OS/400. It is very detailed and technical (but that's what many of us get
paid for!)

        The second section discusses "putting together a strategy for moving
your customers off of OV/400." It includes links to the OV/400 to Domino
migration web site, as well as the three third party alternatives to
Officevision mentioned in my earlier TECHNOTE. This is what the rest of us
get paid for (and how our companies usually generate the revenue to pay us
technical types.)

 > ===================QOGCHGOE example===========================
 > The history of OV/400 and OS/400 is that the commands were constructed
 > with OV/400 functions being set as the default when those functions were
 > required.  Therefore, when OV/400 is not on the system, these functions
 > must be provided by other applications or appear to be provided by other
 > applications.  This is done by an exit program registration interface
 > called QOGCHGOE (Change Office Exit Program).  Note: Refer to the System
 > API Reference or the OV/400 V3R1 Planning Guide  A redbook (OV/400
 > Application Enabler V2R3 (GG24-4072)) is also helpful.
 >
 > Here is an example using the Create Document (CRTDOC) command.  If
you try
 > to use the CRTDOC command with OV/400 installed, a message appears
stating
 > that folder is needed for that document,  If you try to create a folder
 > (CRTFLR) , a message appears stating you need to be in the system
 > distribution directory.  If you try using the Add Directory Entry
 > (ADDDIRE) command, it works.  Now you can create the folder,  At this
 > point you try to use the CRTDOC command, but you receive a message that
 > the "required system module not found."  The message is generated because
 > the command processor for CRTDOC looked to see if OV/400 is in the "entry
 > point table", found that is not, and posted the message.
 >
 > An alternative to OV/400 is needed.  This is where the QOGCHGOE comes
into
 > play.  The kind of document that is created is determined by a document
 > profile (this is a document that you want your new one to look like) that
 > must exist in folder QPRFFLR.  So, put a document (use and existing
one or
 > a PC file ) in QPRFFLR.  If QPRFFLR does not exit, use the CRTFLR command
 > again, optionally changing folder details if a specific profile document
 > is to be used.  Now we get to QOGCHGOE and an exit program to use
 > QOGCHGOE.
 >
 > Here is a simple Command Language (CL) program (called QPGNOOP (for no
 > operation)).  If you want an alternative editor, specify it in the fifth
 > line of this program (in the &FUNCTION variable.  This "no operation"
 > program tells OS/400 not to look for OV/400 to perform any of the
 > functions (the last lien with a return code of 0000).
 >
 > QOGNOOP: PGM PARM(&DOCUMENT &FOLDER &TYPE &FUNCTION &INFO &EXIT)
 > DCL VAR(&DOCUMENT) TYPE(*CHAR) LEN(12)
 > DCL VAR(&FOLDER) TYPE(*CHAR) LEN(63)
 > DCL VAR(&TYPE) TYPE(*CHAR) LEN(4)
 > DCL VAR(&FUNCTION) TYPE(*CHAR) LEN(26)
 > DCL VAR(&INFO) TYPE(*CHAR)
 > DCL VAR(&EXIT) TYPE(*CHAR) LEN(4)
 > CHGVAR VAR(&EXIT) VALUE(0000)
 > ENDPGM
 >
 > After placing this program in library QGPL, you can call the API per the
 > command below on the OS/400 command line:
 >
 > CALL PGM(QOGCHGOE) PARM('QOGNOOP QGPL ''1''NA NALIB '0)
 >
 > Now if you tried using CRTDOC and subsequently MOVDOC, CPYDOC and DLTDLO
 > on that document, those commands work as expected.  However, if you
try to
 > Display Document (DSPDOC) or Edit Document (EDTDOC), no functions will be
 > performed because in the "no operation" program above, no application was
 > specified to perform that function (in the &FUNCTION variable).  The
 > &FUNCTION variable covers function such as edit, create, fill form, mail
 > edit, mail view, mail reply, merge, print spell check, view, etc. (see
 > reference mentioned above for details.).
 >
 > =======================End of QOGCHGOE
 > example=============================
 >
 > One should know that there are functions of OS/400 that are often thought
 > of as OV functions, when in fact they are not.  As broad categories -
 > Document support (DLS) and System Distribution Directory (SDD) are OS/400
 > functions and not OV functions.
 > Below is a list (see the redbook for the exhaustive list) of  some 80+
 > commands that a user does not need OV/400 installed to use these
commands:
 >
 > Note they are almost all dealing with documents (DLS) and directory
(SDD).
 > The list can cause some puzzlement - if you will note EDTDOC is on the
 > list.  It turns out that EDTDOC is built to have as its default the
OV/400
 > text editor - but it doesn't have to be.  Programmatically a user can
 > change the editor to be other editors - including PC editors - but this
 > setup work must be done.
 >
 >
 >    ADDDIRE          DLTDLO         RMVDIRE
 >    ADDDIRSHD        DLTDST         RMVDIRSHD
 >    ADDDLOAUT        DLTDSTL        RMVDLOAUT
 >    ADDDSTLE         DTSPADCT       RMVDSTLE
 >    ADDNCK             DMPDLO         RMVNCK
 >    ADDRMTDFN   DSPAUTLDLO     RMVRMTDFN
 >    CFGRPDS          DSPDIRE        RNMDIRE
 >    CHGDIRE          DSPDLOAUD      RNMNCK
 >    CHGDIRSHD        DSPDLOAUT      RNMDLO
 >    CHGDSTA          DSPDLONAM      RNMDSTL
 >    CHGDSTL          DSPDOC         RTVDLONAM
 >    CHGDLOAUD        DSPDSTL        RPLDOC
 >    CHGDLOAUT        DSPFLR         RSTDLO
 >    CHGDLOOWN   DSPHLPDOC      RTVDOC
 >    CHGDLOPGP        DSPNCK         RVKUSRPMN
 >    CHGDOCD          DSPRMTDFN      SAVDLO
 >    CHGDSTD          DSPUSRPMN      SNDDST
 >    CHGRMTDFN   EDTDLOAUT      WRKDIRE
 >    CHGNCK      EDTDOC         WRKDIRLOC
 >    CHKDLO      FILDOC              WRKDIRSHD
 >    CPYDOC      GRTUSRPMN      WRKDOC
 >    CPYFRMDIR        MOVDOC         WRKDOCLIB
 >    CPYFRMPCD        OVRPRTF        WRKDOCPRTQ
 >    CPYTODIR         PRTDOC         WRKDSTL
 >    CPYTOPCD         QRYDOCLIB      WRKFLR
 >    CRTDOC      QRYDST         WRKNCK
 >    CRTDSTL          RCLDLO         WRKRMTDFN
 >    CRTFLR      RCVDST
 >    CRTSPADCT        RGZDLO
 >
==========================================================================
 > =============
 > Over two years ago, IBM announced that support for OV/400 would terminate
 > on May 31, 2001. Initially, V4R4 was to be the last supported release and
 > then support for V4R5 was accepted, although the termination date
remained
 > constant. Numerous customers and Business Partners have begun to ask if
 > there is any chance that this maybe extended in terms of date or version
 > or release. The answer is absolutely NO in terms of version or release.
 > The next OS version will comprise some significant code base changes that
 > will make some portion of OV/400 in-operative. There is no test plan to
 > determine what might work and what might not. As many of you know, a
great
 > deal of the code base for OV/400 is contained within OS/400 so the
 > likelihood that the function that you desire will work is very suspect. A
 > decision was made that the next release of OS/400 would actually
 > de-install the OV/400 code in order to protect the supported portions of
 > OS/400. Customers will have the capability to re-install but they do
so on
 > their own.
 >
 > We highly encourage all OV/400 installed customers to establish a
 > migration plan to move their workloads to Domino on the iSeries and
to use
 > some of the Business Partner solutions that were created to mirror
some of
 > the unique OV/400 functions.  Customers who have mail and calendaring
 > needs should move to "Domino for AS/400".  This gives them an opportunity
 > to
 > building modern groupware, internet-enabled applications. However,
 > customers must consider the AS/400 line of business applications they
have
 > that use OfficeVision/400 APIs. In many cases, they may not even know
that
 > they are using OfficeVision/400 APIs. They need to identify in what ways
 > they depend on OfficeVision/400. Customers also need to select the best
 > option to replace functions using OfficeVision/400 services. This may be
 > to redesign the  application to become a partly Domino application, to
 > change the AS/400 program to call Domino APIs, or to use an add-on
product
 > to Domino. It also may be using other AS/400 available functions or
 > applications. Read the redbook "How to Replace OfficeVision/400 in Your
 > Applications: Looking at Domino for AS/400 and AS/400 Alternatives,
 > SG24-5406-00"  (available at " http://www.redbooks.ibm.com ") to
learn about
 > the alternatives that are available.
 >
 > The following web sites are very good:
 >
 >      http://www.dominodotoffice.com   (good overall information -
FAQs and
 > downloads with duplication of what is in the redbook- but also
information
 > on business partners in different areas of the world who have
expertise in
 > helping OV users to migrate to alternatives.  Links to the three
 > alternative providers listed below are on this web site)
 >
 >      http://www.bluenotes.com (provide a datatext merge solution based on
 > Lotus notes)
 >
 >      http://www.inventivedesigners.com (provides "DTM for AS/400e
Servers"
 > which  offers a 5250 wordprocessing and data/text merge function based on
 > XML architecture. Integration into Lotus Domino environments is supported
 > with a graphical editor and integration with Domino groupware and
workflow
 > functions. Additionally, MS Word can be used as graphical editor.
Existing
 > OV/400 documents can be reused and existing AS/400 applications continue
 > to run with little or no modifications.)
 >
 >      http://www.aia.nl                       (provide a data-text merge
 > function based on client editors)
 >


--
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net


--