× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The equivalent is x'08'. 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.
++
Dennis
++
File Allocation Table Corrupt. Who CAN you trust?




Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"Jim Oberholtzer" <midrangel@xxxxxxxxxx> wrote:

Folks:

I am working on a project where I have to determine if a file is a
source file or physical file. The problem is it will be too slow to
call DSPFD to an outfile and read it for each of the files that will be

looked at. So I was trying to use the API QDBRTVFD which is perfect
for
the problem, except: The data structure IBM used for the attributes is
a
16 _BIT_ field. (Maybe Bruce can explain the logic behind that choice)

Dec Hex Bit Type Field Description
0 0 BINARY(4) Qdbfyret Length of the data
returned
in bytes.
4 4 BINARY(4) Qdbfyavl Number of bytes provided
for the file definition data.
8 8 BIT(16) Qdbfhflg Attributes bytes.
8 8 0 BIT(2) Reserved_1 Reserved.
8 8 2 BIT(1) Qdbfhfpl Type of file.
8 8 3 BIT(1) Reserved_2 Reserved.
8 8 4 BIT(1) Qdbfhfsu File type (FILETYPE). If
on, *SRC If off *DATA
8 8 5 BIT(1) Reserved_3 Reserved.
8 8 6 BIT(1) Qdbfhfky Access path.
8 8 7 BIT(1) Reserved_4 Reserved.
9 9 0 BIT(1) Qdbfhflc Record format level check
(LVLCHK).
9 9 1 BIT(1) Qdbfkfso Select/omit.
9 9 2 BIT(4) Reserved_5 Reserved.
9 9 6 BIT(1) Qdbfigcd Double-byte character
Graphic data.
9 9 7 BIT(1) Qdbfigcl

Constraints: Must use CL and must work at V5R4.

Any ideas how to get after that fifth bit?


--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.