RE: DTAARA keyword, IN opcode, and sub-procedure

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

That explains it I think.

The compile was done in WDSc.  The message may have been there but farther down 
the list and I didn't see it.  Because I wasn't using it I didn't think to look 
at *DTAARA DEFINE.

Thanks Barbara.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Tuesday, June 22, 2004 1:59 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: DTAARA keyword, IN opcode, and sub-procedure


Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
> 
> Other than finding out by trial and error is this documented somewhere?
> 

You should also have got a compiler error message on the DTAARA keyword
saying it wasn't allowed in a subprocedure.

     4 d JEControl       ds            46   
DtaAra(IS2551DTA)                
======>                                     
aaaaaa                           
*RNF3757 20 a      000400  The keyword is not valid for definitions in
subprocedures.

The restriction is documented for the *DTAARA DEFINE opcode, but
unfortunately not for the DTAARA keyword.

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.