CICS and DB2
Has anyone managed to configure a connection from CICSTS running on z/OS to a DB2 UDB running on Windows? Specifically without having to have DB2 on z/OS. This email message and any accompanying materials may contain proprietary, privileged and confidential information of CIT Group Inc. or its subsidiaries or affiliates (collectively, "CIT"), and are intended solely for the recipient(s) named above. If you are not the intended recipient of this communication, any use, disclosure, printing, copying or distribution, or reliance on the contents, of this communication is strictly prohibited. CIT disclaims any liability for the review, retransmission, dissemination or other use of, or the taking of any action in reliance upon, this communication by persons other than the intended recipient(s). If you have received this communication in error, please reply to the sender advising of the error in transmission, and immediately delete and destroy the communication and any accompanying materials. To the extent permitted by applicable law, CIT and others may inspect, review, monitor, analyze, copy, record and retain any communications sent from or received at this email address. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CICS and DB2
If you have not done so you might try posting on either the CICS or DB2 lists To join, use these URLs DB2 http://www.idug.org/ CICShttp://www.listserv.uga.edu/archives/cics-l.html Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Porowski, Kenneth > Sent: Monday, May 07, 2018 12:24 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: CICS and DB2 > > Has anyone managed to configure a connection from CICSTS running on z/OS to a > DB2 UDB running on Windows? > Specifically without having to have DB2 on z/OS. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CICS and DB2
On Mon, May 7, 2018 at 2:23 PM, Porowski, Kenneth wrote: > Has anyone managed to configure a connection from CICSTS running on z/OS > to a DB2 UDB running on Windows? > Specifically without having to have DB2 on z/OS. > > As Lizette indicated, you might get some better answers over on the CICS-L or DB2-L forums. But I don't think you will have any luck. This is just a "gut feeling" that I have. The reason is that you need to be able to coordinate syncpoints, or "two phase commits" between CICS & DB2 (whether on z/OS or UDB). And that piece of software, although it runs in CICS, is only supplied when you get z/OS DB2. ref: https://www.idug.org/p/fo/et/topic=19 (db2) ref: http://www2004.lsoft.se/scripts/wl.exe?SL1=CICS-L&H=LISTSERV.UGA.EDU (how to subscribe to CICS-L) -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CICS and DB2
I believe there is a DB2 JDBC driver. How, exactly, you get it installed and running under CICS should be documented by IBM. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Cobol and PreCompile for CICS and DB2
Does anyone remember when the Cobol Compiler could do the PreCompile function for CICS or DB2 without running the actual standalone step for Precompile? Thanks Lizette Koehler statistics: A precise and logical method for stating a half-truth inaccurately -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Cobol and PreCompile for CICS and DB2
>Does anyone remember when the Cobol Compiler could do the PreCompile >function for CICS or DB2 without running the actual standalone >step for Precompile? Yes, it started with COBOL V2R2 in 2000 with the SQL compiler option, then was continued in 2001 with the CICS option in COBOL V3R1. Both have been supported and extended in every release since! Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
I'm not quite sure what you are asking. Do you mean, which release of COBOL first included the integrated CICS translator within the compiler itself? Or are you asking something else? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
Yes, exactly. I remember in the past you had two steps for compile for DB2 or CICS Cobol programs. One to translate the SQL or CICS EXEC statements to COBOL and then the Compile step itself. I was wondering when that was changed so the Cobol Compiler could do it all in one step without the pre-compiler step. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Bill Woodger > Sent: Thursday, January 12, 2017 12:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Cobol and PreCompile for CICS and DB2 > > I'm not quite sure what you are asking. Do you mean, which release of COBOL > first included the integrated CICS translator within the compiler itself? Or > are you asking something else? > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
"The integrated translator function requires IBM COBOL for OS/390 and VM Version 2 Release 2, with "PTF UQ52879 (APAR PQ45462)" or Enterprise COBOL for z/OS and OS/390 Version 3. Note, however, that the COBOL3 translator option must be active". ...what fun that was changing all the compile procedures. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, January 12, 2017 7:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Cobol and PreCompile for CICS and DB2 Yes, exactly. I remember in the past you had two steps for compile for DB2 or CICS Cobol programs. One to translate the SQL or CICS EXEC statements to COBOL and then the Compile step itself. I was wondering when that was changed so the Cobol Compiler could do it all in one step without the pre-compiler step. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Bill Woodger > Sent: Thursday, January 12, 2017 12:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Cobol and PreCompile for CICS and DB2 > > I'm not quite sure what you are asking. Do you mean, which release of > COBOL first included the integrated CICS translator within the > compiler itself? Or are you asking something else? > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
Hi Lizette, Not sure if you are looking for a calendar 'when' or release level. The linked article shows it back to CICS TS 2.2. The Announcement Letter shows that 2.2's availability date was January 25, 2002. Ralph enterprisesystemsmedia.com/article/cics-integrated-translator -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
The last time I looked into doing that we had problems because certain scenarios were not supported using the integrated translator during the compile step. EXCI applications are what come to mind off the top of my head. Have all the restrictions been lifted at this point? If so, at what levels of COBOL and CICS T/S? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
On Thu, 12 Jan 2017 09:15:37 -0600, David Magee wrote: >The last time I looked into doing that we had problems because certain >scenarios were not supported using the >integrated translator during the >compile step. EXCI applications are what come to mind off the top of my head. >Have all >the restrictions been lifted at this point? If so, at what levels of >COBOL and CICS T/S? The following Technote says that you can Compile an EXCI COBOL program with the Integrated Translator and it should run OK. You will get an informational Compile message saying it's not supported, but it should Compile and run correctly. http://www-01.ibm.com/support/docview.wss?uid=swg21661391 My main beef with the Integrated Translator is that it does not support Batch IMS (EXEC DLI) programs the same way the separate Translator does. The Integrated Translator always assumes your programs contain EXEC CICS commands and forces NODYNAM and RENT Compiler options on. Normally our Batch programs are Compiled with DYNAM and NORENT. It's possible that despite the initial overhead, there may be some benefit to using RENT for Batch COBOL programs on modern hardware. I have not tried to measure the difference yet. So we could probably live with RENT. NODYNAM would be a problem though since most of the programs use "Call 'program'" static calls so they would all have to be changed to dynamic calls to use the Integrated Translator. I only have access to Enterprise COBOL V4.2, but I don't believe it has changed for V5 or V6 of Enterprise COBOL. Lizette, I believe the Integrated Translator, (EXEC CICS, EXEC DLI), and the Integrated PreCompiler (EXEC SQL) were added in Enterprise COBOL V3.1 and enhanced with several releases after that. -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Cobol and PreCompile for CICS and DB2
We use CALL 'CBLTDLI' rather than EXEC DLI, but if we did use EXEC DLI I agree that this forcing of NODYNAM would be quite an irritant! Sounds like an RFE might be in order. As for NORENT, I don't think we've used that since before COBOL II! (In other words, before my time.) Frank From: IBM Mainframe Discussion List on behalf of Dale R. Smith Sent: Thursday, January 12, 2017 9:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Cobol and PreCompile for CICS and DB2 On Thu, 12 Jan 2017 09:15:37 -0600, David Magee wrote: >The last time I looked into doing that we had problems because certain >scenarios were not supported using the >integrated translator during the >compile step. EXCI applications are what come to mind off the top of my head. >Have all >the restrictions been lifted at this point? If so, at what levels of >COBOL and CICS T/S? The following Technote says that you can Compile an EXCI COBOL program with the Integrated Translator and it should run OK. You will get an informational Compile message saying it's not supported, but it should Compile and run correctly. http://www-01.ibm.com/support/docview.wss?uid=swg21661391 IBM Use of integrated CICS translator for EXCI batch programs - United States<http://www-01.ibm.com/support/docview.wss?uid=swg21661391> www-01.ibm.com When compiling code with option CICS(EXCI) using the integrated translator, you recieve message DFH7006I W the EXCI option is not supported by the integrated translator. However, the application program seems to work okay. So you would like to know, can an external CICS interface (EXCI) batch program compiled with the integrated translator be used without problems? My main beef with the Integrated Translator is that it does not support Batch IMS (EXEC DLI) programs the same way the separate Translator does. The Integrated Translator always assumes your programs contain EXEC CICS commands and forces NODYNAM and RENT Compiler options on. Normally our Batch programs are Compiled with DYNAM and NORENT. It's possible that despite the initial overhead, there may be some benefit to using RENT for Batch COBOL programs on modern hardware. I have not tried to measure the difference yet. So we could probably live with RENT. NODYNAM would be a problem though since most of the programs use "Call 'program'" static calls so they would all have to be changed to dynamic calls to use the Integrated Translator. I only have access to Enterprise COBOL V4.2, but I don't believe it has changed for V5 or V6 of Enterprise COBOL. Lizette, I believe the Integrated Translator, (EXEC CICS, EXEC DLI), and the Integrated PreCompiler (EXEC SQL) were added in Enterprise COBOL V3.1 and enhanced with several releases after that. -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Monitoring - managing zOS, CICS and DB2 metrics and thresholds
How much time does it take you to define which metrics in z/OS, CICS and DB2 to monitor and set thresholds? Does anyone use different thresholds throughout the day? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
