browse lookup in report

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-
> list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Enrique
> Arredondo
> Sent: Friday, December 11, 2009 2:32 PM
> To: filepro-list at lists.celestial.com
> Subject: browse lookup in report
> 
> Why can't we use browse lookups at the selection processing of a report ?
> 
> Is there a scientific explanation for that?
> 
> thanks
> 
> EA

The only way to get a browse lookup in a report is to create your selection
process in *clerk and then using system to run the report.

The pass the parameters to the report's actual select process by either
using  -r on the command line or by setting environmental variables from
*clerk and the get these in the select process.  Use @pm etc to get these
values.

Sy="/fp/rreport foobar -f this_repeort -v sel_options -a
-r"<var1"<"-rx"<var2.  

System sy
END

You could also use 1 variable and hash it for the values.

I did this by using commas between values(no value contained a comma) and
then used strtok to get the first position of the comma.  Next a mid
statement from 1 to 1 less the value of strtok got me the first variable.
Did another mid statement to strip this value off and then repeated until
all the variables were set.

Then the selection process ran.

As far as the *clerk process goes, you can create a screen with dummy fields
and use @w processing or just use input("r","c") to put up the select
fields.  And, yes, a browse will work here.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net