I wonder if you use EXECUTE without any CLAUSES, the compiler converts it to a PERFORM?
sounds like I'm anti-Santa here....EXECUTING CLAUSES! > -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of George Gallen > Sent: Friday, September 04, 2009 4:33 PM > To: U2 Users List > Subject: Re: [U2] Hmmmm...Learn something new every day! > > But the question is, why does removing the CAPTURING CLAUSE > fix the problem (allow passing the data). > > with the CAPTURING, user0 won't pass > without the CAPTURING, user0 passes fine > > I thought PERFORM and EXECUTE were the same? > > George > > > -----Original Message----- > > From: [email protected] [mailto:u2-users- > > [email protected]] On Behalf Of Tom Whitmore > > Sent: Friday, September 04, 2009 4:30 PM > > To: U2 Users List > > Subject: Re: [U2] Hmmmm...Learn something new every day! > > > > EXECUTE creates a new environment, try PERFORM. From BASIC Help: > > > > EXECUTE creates a new environment for the executed command. > > This new environment is initialized with the values of the > > current prompt, current printer state, Break key counter, the > > values of in-line prompts, KEYEDITs, KEYTRAPs, and KEYEXITs. > > If any of these values change in the new environment, the > > changes are not passed back to the calling environment. In the > > new environment, stacked @variables are either initialized to > > 0 or set to reflect the new environment. Nonstacked @variables > > are shared between the EXECUTE and calling environments. > > > > Tom > > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
