Re: Orhan control block in a FIFO chain

Ed... You may have found the problem... I had defined the PLT in CSA but never set R1. Changed the programs and testing (but of course if it works it really will not show anything because testing in our environment always worked). I have asked for more CPs on our VM system. Testing with

Re: Orhan control block in a FIFO chain

> On Jul 7, 2017, at 12:28 PM, Walt Farrell wrote: > > On Fri, 7 Jul 2017 09:59:01 -0500, Donald Likens > wrote: > >> We run our product on somewhere around 15 client site. We have had this >> problem on one

Re: Orhan control block in a FIFO chain

On Sat, 8 Jul 2017 09:50:00 -0500, Donald Likens wrote: >Walt... Thanks for asking questions. I will answer you questions as best as I >can. > >Does that duplication include number of CPs and processor speed? I have seen >test environments that were setup as single

Re: Orhan control block in a FIFO chain

On 7/8/2017 7:54 AM, Donald Likens wrote: Question... We use PLO to serialize. Is there another layer of control to handle multiple CPs? If you're using PLO, then make damn sure the PLT (program lock token) address in R1 contains *exactly* the same value for all related invocations! --

Re: Orhan control block in a FIFO chain

​My SWAG is that there is a problem with serializing the addition and/or deletion of entries in the FIFO queue. I.e. two different CPUs are trying to add (maybe delete) a FIFO entry and one CPUs update is "lost". Without looking at code, this is just a guess.​ Question... We use PLO to serialize.

Re: Orhan control block in a FIFO chain

Walt... Thanks for asking questions. I will answer you questions as best as I can. Does that duplication include number of CPs and processor speed? I have seen test environments that were setup as single CP, which does little to help debug problems related to multi-tasking or -processing.

Re: Orhan control block in a FIFO chain

On Fri, 7 Jul 2017 09:59:01 -0500, Donald Likens wrote: >We run our product on somewhere around 15 client site. We have had this >problem on one client site (multiple LPARs) since we started running there. We >have only seen this problem on one other system during a

Re: Orhan control block in a FIFO chain

On Fri, Jul 7, 2017 at 9:59 AM, Donald Likens wrote: > We run our product on somewhere around 15 client site. We have had this > problem on one client site (multiple LPARs) since we started running there. > We have only seen this problem on one other system during a trial

Re: Orhan control block in a FIFO chain

We run our product on somewhere around 15 client site. We have had this problem on one client site (multiple LPARs) since we started running there. We have only seen this problem on one other system during a trial (they did not keep the product). The client site that sees this problem sees it

Re: Orhan control block in a FIFO chain

I see I have a typo in the title... It should be Orphan. Thank you for looking at this. The user knows there are orphans because I have created what one might call a "variable length cell pool system above the bar". The way it works is I obtain a meg of storage above the bar. When obtained the

Re: Orhan control block in a FIFO chain

Donald Likens wrote: >The follow code supports a FIFO control block chain in CSA. When nothing is in >the queue the first and last pointers are zero. It must not be working >properly because one of my users gets orphan control blocks periodically. How does that user know these blocks are

Orhan control block in a FIFO chain

The follow code supports a FIFO control block chain in CSA. When nothing is in the queue the first and last pointers are zero. It must not be working properly because one of my users gets orphan control blocks periodically. I’ve looked at this until my eyes hurt. Does anyone see the problem in