RE: Record lock wait times

Do you care? If we resolved the 19 hour lock would you have been perfectly happy with it only the 9 hour lock? Or are you saying that if we addressed the 19 hour lock you would adjust that parameter which affects the 9 hour lock and then you'd be happy?

Totally different answer...
*NOMAX may translate to 32767. However IBM's application program may consider 32767 as a flag for infinity. Let me explain. Let's say you write a program which accepts a numeric parameter. You front end that program with a *CMD object. Now, so an end user doesn't need to know the trick that entering all 9's is your flag for *HIVAL you create a command special value of *INFINITY. And that command object converts *INFINITY to all nines and passes that to your end program.
IBM does this. Let's look at the command CRTPF. That has a parameter on it for preferred disk unit. This was from back in the day when you would want to say put this file on disk 1 and this other one on this totally other disk. Perhaps to reduce arm swapping during a production run. This parameter has been deprecated, but still there, for quite some time. IBM resurrected it when SSD's came out. You pass it a special value of *SSD to say you want to store that on SSD disks instead of spinning disks. The command actually translates *SSD to unit 256 and passes that to the command processing program for CRTPF. You could say 256 and get the same result.


Rob Berendt