|
Al, He was using those documents with the HLPDOC family of keywords in DDS. (Remember DDS?) I don't think that Domino or TMS/38 would be a viable option. We just removed OV/400 from a V4R5 machine. Some commands remained, as outlined in the redbook. These commands include EDTDOC, PRTDOC, and what not. However if you try to run EDTDOC you will get a message OFC8019-Required module not on system. The redbook said that EDTDOC would be there but nonfunctional. I've yet to get the point of leaving it there. We have better luck with PRTDOC. But with no EDTDOC we are migrating in a hurry. Rob Berendt ================== Remember the Cole! "Al Barsa, Jr." <barsa2@barsaconsul To: MIDRANGE-L@midrange.com ting.com> cc: Sent by: Subject: Re: Help Text and Officevision/400 owner-midrange-l@mi drange.com 03/07/01 10:08 AM Please respond to MIDRANGE-L At 01:11 PM 3/7/01 +0000, you wrote: There are lots of bad options here. Several points: Option 1 - A small amount of work (with no $), and a lot of risk: It's rumored that the install of V5R1 will uninstall OV/400. Although I'm relatively sure (from past experience that RSTLICPGM is smart enough to not let you re-install it), but save/restore is not. So you could trying the following on a "scratch system": Install OV/400, add some users, yada, yada, yada. Turn on object auditing. Save your whole system DLTLICPGM OV/400 Check your audit logs to see what was deleted. This will provide you with a TODO list of what to manually reinstall after the install of V5R1 removes OV/400 as rumored. At that point, there OV will not be supported, and there are no guarantees that it will work. Option 2 - The least amount of risk, (lots of $$$$$) and low risk: IBM sold the editor, mail/merge and calendaring to a European vendor, but I don't know their name. (It's been posted here before.) You could buy this product for lots of $$$$, and assuming that the product works, you're in. Option 3 - IBM's preferred approach, moderate risk (very expensive) and moderate risk: Migrate your help to LOTUS Notes, assuming that all of your applications work from big PCs, and not dumb workstations. Root canal sounds like more fun to me. Option 4 - Print out your help documents, and migrate then to Text Management/38 - very low risk: If you already own the product, it costs no $$$$, otherwise it sells for about $6K, not tiered. I know several users that have done this. Use QSYS38/DSPDOC to replace OV's DSPDOC. There will be no re-keying, but there will be editing, clean-up, adding extra lines, highlighting and underlining. F3 will not exit, but enter will. (You will not have to use F1 to exit.) I know of a few companies that have tried this approach, and they say it worked well. They used programmers to convert the text to source, and had clericals who know the application edit the source for prettiness. Al Hi all, We are currently using the HLPDOC keyword in our display file dds to enable users to display the appropriate helptext for a field or function. In light of the withdrawal of OV/400 from the scene by IBM, the displaying of these 'Office' documents could potentially be problematic for our application if they do not work after v4r5. Does anyone know what will happen on a V5R1 platform when an application that uses Officevision help is run? Will the program fail immediately or only when F1 is pressed? Will a nice message be displayed and the function carry on regardless? We do not need OV/400 for maintaining or storing our help text as we can find another approach. For example, we might keep our help text in a database on the AS/400 or in a text file in QDLS. The real problem is the runtime usage of OV/400 to display the office document when F1 is pressed. What we would really like to do is call our own help text program with the same parameters that must be going to the OV/400 program when F1 is pressed. This would be the least intrusive solution to our application as we would not have to change our DDS or our RPG programs. Does anyone know of a Red Book or API we can use to solve our problem ? Kind regards, Jeff Bull. Senior Support Consultant Certified IBM AS/400 System Administrator Midas Kapiti International Ltd Tel: 44 (0) 175 370 8224 Fax: 44 (0) 175 357 0233 Mailto:Jeff.Bull@Midas-Kapiti.Com << == Replies to The views and opinions expressed in this e-mail are the senders own and do not necessarily represent the views and opinions of Misys Plc. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the intended named recipient of this email then you should not copy it or use it for any purpose, nor disclose its contents to any other person. You should contact Midas-Kapiti International as shown below so that we can take appropriate action at no cost to yourself. Midas-Kapiti International Ltd, Key West, 53-61 Windsor Road, Slough, Berkshire, SL1 2DW, England Email: Postmaster@midas-kapiti.com Tel: (44) 1753 573244 Fax: (44) 1753 570233 Midas-Kapiti International Ltd is registered in England and Wales under company no. 971479 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--------------------------------------------------+ | Please do not send private mail to this address. | | Private mail should go to barsa@ibm.net. | +--------------------------------------------------+ Al Barsa, Jr. - Account for Midrange-L Barsa Consulting Group, LLC. 400 > 390 Phone: 914-251-1234 Fax: 914-251-9406 http://www.barsaconsulting.com http://www.taatool.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.