Re: Find a binary value with CL (V5R4)

On 06-Dec-2011 13:45 , Dennis wrote:

The equivalent is x'08' [or x'0800' per addendum]. To be pure, you
need Logical AND capability, but I believe you will be OK with a
straight compare, since (AFAIK) source files cannot have those other
bits set.

That specific bit Qdbfhfsu should be tested anyway, because any of the "reserved" bits could be exposed in the future [PTF or release]. Whether such bits would be mutually exclusive of the "source" indicator, would be unpredictable.

Besides that, the specific bit still needs to be tested, because even in the first byte, each non-reserved bit is valid to be "on" even when "source" is "on"; i.e. already the exposed bits are not mutually exclusive of "source" file indicator. For example, a file type *SRC both can be keyed other than with "Arrival" such that Qdbfhfky would be "on" to indicate "keyed access path" and can be a "logical" file such that Qdbfhfpl would be "on"; noting, both CRTPF and CRTLF have the FILETYPE(*SRC) capability. Additionally necessary, because AFaIK the "reserved" bits already may be non-zero; i.e. while the "reserved" for input implies zeroed values are expected by an API, the same does not hold true for output from every API, such that for output values, the "reserved" may serve only as a warning: "Do not refer to [nor depend on] this value".

Regards, Chuck