As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
Our mainframe people are going to convert our Mainframe FOCUS to WebFOCUS. Reports are not a problem, but I was just asked a question by the manager. Can they run their MODIFY/CRTFORM apps or do they have to convert those to MAINTAIN? If so, is there any kind of utililty to help with the conversion?This message has been edited. Last edited by: Kerry,
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
jg, this is the biggest mental jump when making the move from mainframe to web, having done this now at 2 places; yes you can use Modify, but your forms aren't CRT forms, they're HTML forms. If you were using them to enter parameters to run reports, then html forms are the ticket. however, if you are using crt forms to collect massive amounts of data for updating, then MODIFY is the ticket. It depends how much data you want to pass thru at one time. MAINTAIN has benefits that ordinary html forms with modify might not provide. Check with your local sales office for a detailed demo. But you can certainly get started with hmtl and modify. The biggest thing to get your head around is that with mainframe and CRT forms, you could run a long fex with CRT forms popping out at various data extract levels, and continue processing the fex. with the web, you can't do that. once the fex produces output to the screen, whether its a report or a form, you're dropped. the connection with your fex doesn't exist any longer. Sounds like a bad thing, but actually its the best. I would recommend hiring a consultant to come in for a short bit to ease the transition. You'll enjoy the transition more having a guide.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Basically you would build your HTML page with all your named objects becoming WF variables and then use MODIFY to perform the update.
I have used such a process recently where I saved all the values in various objects on the HTML page, concatenated these into one long variable which was then passed to focexec. I didn't actually use form submission but used an activex process to call the focexecs URL. The upshot is that the user doesn't even notice that an update has been performed as the screen doesn't change.
If I get time I will give an example here to show the process.
Even though I prototyped the above process using a FOCUS database, I now use SQL Server to the same effect using SQL passthru in the called focexec.
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
MODIFY's do run on WEBFOCUS, however, only the MODIFY with FIXFORM, not CRTFORM. The problem is the "non-persistent connection" which would support T. etc. There are two options. One is to convert to MAINTAIN (But unfortunately there is not a utility to do that). It depends on the complexity of the MODIFY. Some can be easily converted, others it takes some work. Stacks are easier in MAINTAIN, and don't require as much code to display a GRID as CRTFORM, but you really have to look at each piece. Another alternative is to (again if it is a simple 1 CRTFORM type screen just for data entry) to create an HTML screen, and then create a FIXFORM input for the MODIFY. So, sorry if it is a CRTFORM MODIFY, then this has to be in most cases manually converted to MAINTAIN or FIXFORM in some fashion.
WEFOCUS - All releases starting at 4.3.6 MF FOCUS -- All releases starting at 3.8.68 OS/Platfor _ Predominately Z/OS, but all others as swell Expected Output Format -- *
Posts: 60 | Location: 2 penn | Registered: May 22, 2003
In the past, when we have converted Modify to Maintain, we have mapped out the logic paths in the Modify and then recreated them in Maintain. There are some major differences between the products that have made a converter impossible.
Actions that took 5 or 10 lines in Modify code, can be done in 1 line of Maintain code. The logic cannot be converted line by line.
I highly recommend trying the fanclub tutorial, included in the documentation, to get a feel for the Maintain product. I will be happy to answer any questions you may have.
Posts: 663 | Location: New York | Registered: May 08, 2003
Think of CRTFORM as the user interface component of MODIFY, and Forms as the user interface component of MAINTAIN.
CRTFORM was made to work for the character based Mainframe screens(3270, etc.), whereas Maintain Forms are designed to work with, more complex, HTML pages. There is very little common ground to support a conversion utility.
All you back-end MODIFY stuff will still work fine, but anywhere you have (-)CRTFORM user interface functions in your mainframe Focus code, either Modify or Dialog Manager, it will have to be re-written.
Converting mainframe FOCUS to WebFOCUS has never been easier! We have a formal methodology and software application to automate the process.
The upfront assessment effort is automated using the BI Analyzer tool, which can scan hundreds of files per second (FOCEXECs, MASTERS, JCL/PROCs, CLists, REXX, etc.), put everything into a database, and apply algorithms for analysis (e.g., purpose, complexity, active/obsolete, duplicate, redundant, business grouping, etc.).
The BI Transformer can automatically convert legacy reporting modules into WebFOCUS versions: FOCEXECs, JCL/Procs, schemas, HTML pages, SQL dialects, etc.