Re: Logical file has Allow Write == No

Ah ha!

Message . . . . : Output operations to file RIVRCVER in OLSBASQUAL not

allowed.

Cause . . . . . : Logical file RIVRCVER in library OLSBASQUAL was
created so
that output operations to its members are not allowed. One or more of
the
logical files based-on files is a Structured Query Language (SQL) table

containing a field or fields that do not have default values. The
logical
files format does not have a corresponding field or fields to supply
values
for these non-default value fields. Therefore, file RIVRCVER in library

OLSBASQUAL was created in a way that will not allow output operations to
its
members. For more information about SQL tables see the DB2 for i5/OS
SQL


On Fri, Apr 17, 2015 at 11:00 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Scratch this part.. "Interestingly, within our CMS, the file has allow
write == YES. It's only the copy deployed to our test library that ends up
with allow write == NO."

Glanced at the wrong copy...

On Fri, Apr 17, 2015 at 10:55 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Why would a non-join logical have

Allow write operation . . . . . . . . . . . : No

As shown from DSPFD?

DSPFFD shows that all the fields are defined as BOTH.

Found this thread: http://forums.iprodeveloper.com/forums/aft/77631
But there didn't seem to be a conclusion.

Interestingly, within our CMS, the file has allow write == YES. It's
only the copy deployed to our test library that ends up with allow write ==
NO.

Charles