Re: RNF7701 interpretation?

["Alan (cfuture) Cassidy" <cfuture@xxxxxxxxxxx>]

THe data structure KMT is defined thusly: 
DCL-DS KMT EXTNAME('CS15L00105') QUALIFIED END-DS ;

Thank you, Mark...

--Alan 


> On 03/28/2024 5:46 PM EDT Alan (cfuture) Cassidy <cfuture@xxxxxxxxxxx> wrote:
>
>  
> I got one here where the compiler thinks the external data structure has no subfields.
> In context: 
> NOTE:
> KMT is an externally described data structure based on the same file that the MT data structure ia based on. 
> CS15L00105 is a logical file based on that same PF, and its only record format is CS15R05K. I want 
>
> KMT = MT ;
> CHAIN (<Key-field list>) CS15L00105
> UPDATE CS15R05K KMT
>
>
> The Update statement gets this diagnostic error: 
>
> Message . . . . :   The data structure KMT is not allowed for the operation.
> Cause . . . . . :   For operation codes CHAIN, READ, READC, READE, READP,
>    READPE, and UPDATE, the data structure does not consist of the input 
> fields
>    of the specified file or record format. For operation code WRITE, the 
> data
>    structure does not consist of the output fields of the specified record
>    format. For operation code EXFMT, the data structure does not consist 
> of all
>    the fields fields of the specified record format. The data structure is
> ignored.
> Recovery  . . . :   For an input or update operation, define the data
>    structure using *INPUT or *ALL for the usage parameter of LIKEREC or
>    EXTNAME. For an WRITE operation, use *OUTPUT or *ALL for the usage
>    parameter. For an EXFMT operation, use *ALL for the usage parameter. 
> Compile again.
> -- 
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.