Re: Looking for consult help getting to 31-bit CICS Cobol
You could also look at MHTRAN2 to do your COBOL conversion. I used it to convert a whole portfolio of COBOL source and copybook code (around 1300 programs and related copybooks). I don't believe it has a "TRACKING" component to help you keep track of what has been converted and what has not. But it did a good job for me getting the code changed and ready for re-compile and re-link. Since I was the only one working on the project, I did not need a sophisticated source code portfolio manager to track what had been changed and converted. I did this conversion over 10 years ago, so my experience with the product is a bit dated. I used SAS to unload the source code libraries, build JCL streams of mass translates and compiles, etc. Prince Software. http://www.princesoftware.com/pages/mhtran2.html Kriss Davis [EMAIL PROTECTED] (309) 438-3101 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Looking for consult help getting to 31-bit CICS Cobol
Dumb question perhaps, but do you have the Enterprise COBOL Migration Guide? Latest version is here: http://publibfp.boulder.ibm.com/epubs/pdf/igy3mg40.pdf There are migration tools of course. Two commercial ones that I know about are Edge Portfolio Analyzer (from Edge Information Group, and via IBM as program number 5620-AZM) and the COBOL Conversion Aid, now part of IBM Debug Tool Utilities & Advanced Functions. The former is primarly for assessment, and the latter is primarily for actual conversion. (You buy these tools only if they provide net cost and/or risk mitigation benefits.) And there's the free Load Module Analyzer here: http://www.ibm.com/support/docview.wss?uid=swg24010925 Don Fowler wrote a good technical article on this subject here: http://www.mardon-y2k.com/Is%20There%20Still%20OS.htm with some more information, including a sample estimation spreadsheet which you can modify for your own use. This is a very well-worn migration path, and there's a lot of help and experience from which to draw. Please also be sure to browse the CICS-L mailing list archives if you haven't already and ask for more information there, too, if you need it. - - - - - Timothy Sipples IBM Consulting Enterprise Software Architect Specializing in Software Architectures Related to System z Based in Tokyo, Serving IBM Japan and IBM Asia-Pacific E-Mail: [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Looking for consult help getting to 31-bit CICS Cobol
In a message dated 6/19/2008 7:43:24 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: STRING is no long forbidden in Enterprise COBOL CICS code. The LE environment "knows" it is in CICS and replaces the z/OS GETMAIN with a CICS GETMAIN. >> Probably going to need 'Portfolio Analyzer', change management software and a new programmer? **Gas prices getting you down? Search AOL Autos for fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut000507) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Looking for consult help getting to 31-bit CICS Cobol
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of John Mattson > Sent: Wednesday, June 18, 2008 5:17 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Looking for consult help getting to 31-bit CICS Cobol > > We are looking for someone to help with our getting to 31-bit > addressing in CICS. > Running TS 2.2 on zOS 1.08. Major problems: lots of > VSCobol, a > good bit of use of CICS forbidden verbs such as STRING in the > VSCobol. I > have re-written our old Assembler exits to work in batch, but > CICS either > presents new challenges, or VSCobol is getting in the way. So we are > looking for someonewho has already done this, Must have > VSCobol, zCobol, > CICS, and assembler experience. eMail me, or call 562-290-4163 STRING is no long forbidden in Enterprise COBOL CICS code. The LE environment "knows" it is in CICS and replaces the z/OS GETMAIN with a CICS GETMAIN. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Looking for consult help getting to 31-bit CICS Cobol
We are looking for someone to help with our getting to 31-bit addressing in CICS. Running TS 2.2 on zOS 1.08. Major problems: lots of VSCobol, a good bit of use of CICS forbidden verbs such as STRING in the VSCobol. I have re-written our old Assembler exits to work in batch, but CICS either presents new challenges, or VSCobol is getting in the way. So we are looking for someonewho has already done this, Must have VSCobol, zCobol, CICS, and assembler experience. eMail me, or call 562-290-4163 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
