Re: Can I build a Logical file over a physical file in QS36F?

Also remember that s/36 files don't allow for a "hard delete."  (You can't
even use a delete database trigger with them!)  You typically have to set a
status field to "D" and copy the file to get rid of unwanted records.  Yuck!

If it doesn't impact too many programs, you may consider avoiding the
band-aid fix and just re-create the file as a full-featured, db2/400
(native) file with all features and functions.

William
===============================
William Washington III
Njia Systems Incorporated
w.washington3@njiasystems.com
===============================

>
>>Can I build a Logical file over a physical file in QS36F?   The physical
>>file is a program-described file and I am wondering about creating a
>>logical over it with the actual field descriptions and then use the
>>logical as an Externally described file?
>
>You can create a logical, but you'll need derive the key fields as
>substrings of the alpha dataspace - do a dspffd on the s/36 file to see
>what I mean. The entire record will be defined as one field, unless it also
>has keys, in which case those will be split out as separate fields. You
>could also use the s36ee bldindex procedure, which will do the dirty work
>for you, and end up creating just such a logical.
>
>
>>Martin
>>
>>You shouldn't have any problems creating the logical over the file in
>>QS36F, using the substring function in the DDS, but beware that the
>>logical can only be used for input only.  No updating.
>
>You can update the dataspace, but not any derived (redefined) key fields,
>because they are defined as input only.
>