Wait forever

We have a situation we do not understand. The code I am sharing was developed on a z/OS 1.3 system and has been executed millions of times but from what I can tell it simply did not work once on a z/OS 2.1 system. This code has not been changed for over a year. This execution ran for a day befor

Re: Wait forever

One thing I like to do in these types of situations is redo the code. If this is a home grown program, I would reassemble/lked (compile/lked) on the z/OS V2.1 system and try it that way. Or do a compare between the two versions. There might be some changes in z/OS V2.1 that are not obvious. Li

Re: Wait forever

I have no idea whether it is THE problem or not but I see a small logic flaw in your code. You should clear STIMECB *before* issuing the STIMER. There is a possibility that STIMERX gets driven before the XC. What sort of intervals are we talking about here? Any possibility that the interval was

Re: Why major financial institutions are growing their use of mainframes

In <55818f2f.8050...@vse2pdf.com>, on 06/17/2015 at 11:15 AM, Tony Thigpen said: >Good story, but my BS meter is pegged on this one. Change "a mainframe" to "mainframes" and I'm prepared to believe it. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: OT STCK question

In <20150617214111.5353554.62004.40...@yahoo.ca>, on 06/17/2015 at 05:41 PM, Ted MacNEIL said: >The only reason for they (singular) is for formal documentation and >the press. ... >But, it's all for the sake of political correctness. Nonsense. They (singular) was around centuries before PC

Re: How is CAMASTER started?

In <20150618144101.75ef6133e1b938e944115...@gmx.net>, on 06/18/2015 at 02:41 PM, "nitz-...@gmx.net" said: >According to the ibmmain post ICHALTSP is an (IBM) IRIM that receives >control in master scheduler (but you're right, I cannot find it in my >SMPE environment either). Could it be a NUCL

Re: Network Switch Refresh

In , on 06/18/2015 at 11:49 AM, zos reader said: >The switch is connected from the outside Mainframe from Network >server to the IBM Mainframe box Is there an alternate path? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: OMVS segment Issue

In , on 06/18/2015 at 03:17 PM, Mainframe Mainframe said: >2. Allow the TSO user IDs to execute BPX* programs Read it again. >So, I am not sure what kind of access do I need to give for their >user id to have ping access. Preumably program control. What's in the OMVS segment? >On Thu, J

Re: OMVS segment Issue

In , on 06/18/2015 at 06:27 PM, Mainframe Mainframe said: >USER user1 IS ASSIGNED AN OMVS UID, BUT DEFAULT GROUP $ADT DOES NOT >HAVE A GID PROCESSING CONTINUES. Assign an appropriate group; don't assume that the default is usable. If $ADT is really what you want then assign a GID. --

Re: OMVS segment Issue

In , on 06/18/2015 at 05:48 PM, Mainframe Mainframe said: >I just checked the user id and found that we have not set UID for >this user.Can it be reason for this issue. Yes. Fix it and then see if there are other issues. If that is the problem, send an RCF or SR for the incomplete documentati

Re: Wait forever

In <6634895484326311.wa.dlikensinfosecinc@listserv.ua.edu>, on 06/20/2015 at 08:32 AM, Donald Likens said: >Does anyone have any ideas or recommendations to help fix this >problem? Move the XC. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: Wait forever

In <056701d0ab61$d42730e0$7c7592a0$@mcn.org>, on 06/20/2015 at 07:03 AM, Charles Mills said: >I'm sure you also know that the AL3 makes your code incapable of >RMODE 31? WAIT ECB=STIMECB would make your code a little simpler. It would also break the code. -- Shmuel (Seymour J.) Metz,

Re: Network Switch Refresh

Radoslaw Skorupka wrote: >Not so long time ago, when z800 was current machine *every* eth link >down event required CHPID OFF/ON for the affected OSA card. >So, assuming your system is communicating with rest of the wolrd (using >OSA card) it was comparable to POR or IML, because *all* LPARs lost >

OpenSSL for z/OS

Does anyone know where an up to date verson of OpenSSL that will run on z/OS can be found. The version shipped in IBM Ported Tools is not current. I understand that at least version 1.0.1n is needed to address the POODLE and other exposures. -

Re: OpenSSL for z/OS

It's really *easy* to build yourself with a few patches. This is maybe a little out of date wrt the patches but it worked for me with a little bit of tweaking http://blog.ondruska.com/2012/07/openssl-on-zos-unix-system-services.html for 1.0.1i build last year. On 21/06/2015 11:58 AM, Anthony

Re: Wait forever

Thank you all for taking the time to look at this. The interval is 1 second but this has happened only once in millions of executions so I think moving the XC is what I am going to do to fix this problem. If it is possible it will happen. Thanks again ---