Re: DB2 subsystem availability
On Tue, 2 Apr 2013 07:40:08 -0500, John Gilmore jwgli...@gmail.com wrote: A lot less cycles here replaces a derisory number of them by an exiguous one. Jantje's example could be further refined, but to what end? Granted: in the overall total of cycles needed to build up the client connection, validate the user's authority, parsing the SQL statement, returning the result to the client application, etc. the actual difference between the two proposed queries will not be huge. Still, if the same result can be achieved with less cycles, I would go for it. This sort of suboptimizing is not san appropriate use of anyone's time. Well... IMHO, it depends... Maybe, maybe not. Anyway, others have commented about what the actual purpose and aim might be and how to achieve it. They have a very valid point in stating that in the end the SLA is what matters. Cheers, Jantje. P.S. John, no offence. You're right. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
On Mon, 1 Apr 2013 08:21:06 -0500, John McKown john.archie.mck...@gmail.com wrote: SELECT CURRENT-TIME FROM sysibm.systables Make that SELECT 1 FROM SYSIBM.SYSDUMMY1 and test for SQLCode = 0. Uses quite a lot less cycles. Cheers, Jantje. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
Thanks. I'm not very DB2 literate. Not that stops me from shooting off my mouth. But I do get a number of misfires. grin/ On Tue, Apr 2, 2013 at 5:20 AM, Jantje. jan.moeyers...@gfi.be wrote: On Mon, 1 Apr 2013 08:21:06 -0500, John McKown john.archie.mck...@gmail.com wrote: SELECT CURRENT-TIME FROM sysibm.systables Make that SELECT 1 FROM SYSIBM.SYSDUMMY1 and test for SQLCode = 0. Uses quite a lot less cycles. Cheers, Jantje. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? 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: DB2 subsystem availability
A lot less cycles here replaces a derisory number of them by an exiguous one. Jantje's example could be further refined, but to what end? This sort of suboptimizing is not san appropriate use of anyone's time. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
John Gilmore wrote: A lot less cycles here replaces a derisory number of them by an exiguous one. Jantje's example could be further refined, but to what end? Your point is well taken. I think the OP wants to check whether a DB2 system is available or reachable from somewhere [1]. The only way to be sure is connect to a DB2 system and query something inside DB2. If the OP needs to check it regurlarly, your DB2 query must be fast and furious, not be a 'SQL from hell'. [1] - It is one thing to see that all your DB2 address spaces are up and running, but it is another thing try to access from somewhere all the way from, say, your PC, TCP/IP up to the DB2 master address space. I am sure the OP will get a good answer on DB2 List. Disclaimer: While I have worked with DB2 (setup from PARMLIB, Proclibs and RACF side), I'm not a DB2 guru. I am too lazy anyway... ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
At the risk of writing like an architect, let's pause to consider that the problem might be more than a one-off problem. DB2 might be one important ingredient in consistently delivering a particular business outcome, but it's probably only one ingredient among several. If the problem statement is, I want to make sure I'm consistently delivering a particular business outcome -- meeting my service level agreement(s), in particular -- and I want to find out quickly where the problem is if there is a problem and, preferably, automatically correct it then the point-level approaches aren't going to go very far. Yes, we're probably talking about an end-to-end service management solution of some kind here. One example is Tivoli Business Service Manager for z/OS at the highest level, with drill-down capabilities below that. There are others. Automation of some kind would be important, I would think. In other words, I'm sympathetic to the So what if DB2 is up-and-running if the network is down and nobody can get to it sort of issues. If you're addressing the general problem statement it's highly likely you've got DB2 well covered. I like the idea of addressing several issues simultaneously once and once well, if possible. Timothy Sipples GMU VCT Architect Executive (Based in Singapore) E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DB2 subsystem availability
Hello; Is there a way to determine if a DB2 or any subsystem is truly available? I know how to sweep the SSCT entries to see if they are defined, but, Is there a way to see if the subsystem is truly alive and can process requests? Kenneth J. Kripke k.kri...@comcast.net -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
Could you provide some more detail on what you are looking to do? What problem you are trying to solve. in the case of DB2, the early code is loaded at IPL time. So some commands maybe available. But it is not until the various started tasks are up, that the system is active. So what are you looking to do? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kenneth J. Kripke Sent: Sunday, March 31, 2013 11:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DB2 subsystem availability Hello; Is there a way to determine if a DB2 or any subsystem is truly available? I know how to sweep the SSCT entries to see if they are defined, but, Is there a way to see if the subsystem is truly alive and can process requests? Kenneth J. Kripke -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
Rexx connect? Command response from console? Control block scan? Many ways to get this info. Itschak On Mon, Apr 1, 2013 at 2:04 PM, Lizette Koehler stars...@mindspring.comwrote: Could you provide some more detail on what you are looking to do? What problem you are trying to solve. in the case of DB2, the early code is loaded at IPL time. So some commands maybe available. But it is not until the various started tasks are up, that the system is active. So what are you looking to do? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kenneth J. Kripke Sent: Sunday, March 31, 2013 11:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DB2 subsystem availability Hello; Is there a way to determine if a DB2 or any subsystem is truly available? I know how to sweep the SSCT entries to see if they are defined, but, Is there a way to see if the subsystem is truly alive and can process requests? Kenneth J. Kripke -- 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: DB2 subsystem availability
I'm not familiar with DB2, but to see if something is truly alive, why not just try something innocuous? I don't know how difficult this is with DB2, but could you use a SPFUI type program to do something like: SELECT CURRENT-TIME FROM sysibm.systables I don't know the name of the actual table to use. On Mon, Apr 1, 2013 at 1:07 AM, Kenneth J. Kripke k.kri...@comcast.netwrote: Hello; Is there a way to determine if a DB2 or any subsystem is truly available? I know how to sweep the SSCT entries to see if they are defined, but, Is there a way to see if the subsystem is truly alive and can process requests? Kenneth J. Kripke k.kri...@comcast.net -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? 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: DB2 subsystem availability
Thank you to all that have responded. What I am attempting to accomplish. I wish to perform a pre-emptive check on the availability of a DB2 subsystem on another sysplex prior to shipping a batch job over to that Plex. Yes, I could code a small SQL QUERY and check for the SQLCODE returned, but, I wanted to know how something like MSI can show that a subsystem is defined, but, is not active. Special Thanks to Wayne Driscoll. I will test this out, but, it looks like the solution I am seeking. Ken Kripke -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 subsystem availability
It occurred to me to add to my previous comment: For batch applications, you might have some console automation response to the DSN9022I message statingDSNYASCP 'START DB2' NORMAL COMPLETION on one hand and the DSNY002I message on shut-down on the other. You would use the response to activate/deactivate a Scheduling Environment and refer to it in your batch JCL. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kenneth J. Kripke Sent: Monday, April 01, 2013 3:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DB2 subsystem availability Thank you to all that have responded. What I am attempting to accomplish. I wish to perform a pre-emptive check on the availability of a DB2 subsystem on another sysplex prior to shipping a batch job over to that Plex. Yes, I could code a small SQL QUERY and check for the SQLCODE returned, but, I wanted to know how something like MSI can show that a subsystem is defined, but, is not active. Special Thanks to Wayne Driscoll. I will test this out, but, it looks like the solution I am seeking. Ken Kripke -- 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
