<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Parameters but no parameters in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Parameters-but-no-parameters/m-p/4812#M1543</link>
    <description>Hi:&lt;BR /&gt;
  When you register your stored process in the Metadata, using the Stored Process Wizard in EG (or using SAS Management Console) you CAN define a default parameter value, which will be used if there is nothing specified when the stored process is invoked (as when you write a custom app or invoke using the stored process web app.)&lt;BR /&gt;
 &lt;BR /&gt;
As described on this page:&lt;BR /&gt;
&lt;A href="http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/input.html" target="_blank"&gt;http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/input.html&lt;/A&gt;&lt;BR /&gt;
&lt;B&gt;&lt;BR /&gt;
Defining Parameters&lt;BR /&gt;
Most stored process client interfaces allow a client to pass any input parameter. There is no requirement to define parameters before executing the stored process, but there are many advantages to describing parameters in stored process metadata:&lt;BR /&gt;
&lt;BR /&gt;
--Parameter definitions can specify labels and descriptive text. This information can be used by client interfaces to present a more attractive and informative user interface. Other presentation options include grouping parameters and expert flags.&lt;BR /&gt;
&lt;BR /&gt;
--Default values can be specified. The default value is used if the parameter value is not specified by the client.&lt;BR /&gt;
&lt;BR /&gt;
--Default values can optionally be flagged as non-modifiable to allow a fixed parameter value to always be passed into a stored process. This can be useful when using an existing program that accepts many input parameters. You can register a new, simpler stored process that has some fixed value parameters and fewer client specified parameters. &lt;BR /&gt;
&lt;BR /&gt;
You can also register multiple stored processes for a single program. Each stored process definition can pass in unique fixed parameter values to the executing program to force a particular operation or otherwise affect the execution of the stored process.&lt;BR /&gt;
&lt;/B&gt;&lt;BR /&gt;
 &lt;BR /&gt;
You could also control the value for input parameters using macro program logic, such as this:&lt;BR /&gt;
[pre]&lt;BR /&gt;
%if &amp;amp;reptype = %then %let reptype = Date;&lt;BR /&gt;
  &lt;BR /&gt;
%if %upcase(&amp;amp;reptype) = DTAE %then %let reptype = Date ;&lt;BR /&gt;
[/pre]&lt;BR /&gt;
 &lt;BR /&gt;
which is testing for a null value for &amp;amp;REPTYPE and setting the value for Date in the first %IF statement and doing a minor adjustment in the second %IF statement (in case you let them type the parameter value instead of choosing it from a drop down list).&lt;BR /&gt;
 &lt;BR /&gt;
But, macro conditional logic must be contained within a macro program, it is not allowed in "open" code. For more help with macro programs, you should consult the SAS Macro Facility documentation or contact Tech Support.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
    <pubDate>Tue, 25 Sep 2007 17:40:55 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2007-09-25T17:40:55Z</dc:date>
    <item>
      <title>Parameters but no parameters</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Parameters-but-no-parameters/m-p/4811#M1542</link>
      <description>Oops!!  Sounds funny......&lt;BR /&gt;
&lt;BR /&gt;
Gurus,&lt;BR /&gt;
&lt;BR /&gt;
I want to create a report. Report is created in EG and then a Stored Process is created out of it. The report should be with parameters (with prompt) so that the testing team can test the monthly/daily reports by entering the month and date parameters. The parameters may be "Month and Year" for Monthly reports and "Date" for Daily reports.&lt;BR /&gt;
&lt;BR /&gt;
But acctually these reports are going to be scheduled later. i.e the Stored Process (.sas file) will be executed.&lt;BR /&gt;
&lt;BR /&gt;
Can I create parameters with default values as Last month or Last Day so that when these reports are run through a schedule the parameters are NOT prompted and the default values are used.</description>
      <pubDate>Tue, 25 Sep 2007 11:16:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Parameters-but-no-parameters/m-p/4811#M1542</guid>
      <dc:creator>SanjayM</dc:creator>
      <dc:date>2007-09-25T11:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Parameters but no parameters</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Parameters-but-no-parameters/m-p/4812#M1543</link>
      <description>Hi:&lt;BR /&gt;
  When you register your stored process in the Metadata, using the Stored Process Wizard in EG (or using SAS Management Console) you CAN define a default parameter value, which will be used if there is nothing specified when the stored process is invoked (as when you write a custom app or invoke using the stored process web app.)&lt;BR /&gt;
 &lt;BR /&gt;
As described on this page:&lt;BR /&gt;
&lt;A href="http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/input.html" target="_blank"&gt;http://support.sas.com/rnd/itech/doc9/dev_guide/stprocess/input.html&lt;/A&gt;&lt;BR /&gt;
&lt;B&gt;&lt;BR /&gt;
Defining Parameters&lt;BR /&gt;
Most stored process client interfaces allow a client to pass any input parameter. There is no requirement to define parameters before executing the stored process, but there are many advantages to describing parameters in stored process metadata:&lt;BR /&gt;
&lt;BR /&gt;
--Parameter definitions can specify labels and descriptive text. This information can be used by client interfaces to present a more attractive and informative user interface. Other presentation options include grouping parameters and expert flags.&lt;BR /&gt;
&lt;BR /&gt;
--Default values can be specified. The default value is used if the parameter value is not specified by the client.&lt;BR /&gt;
&lt;BR /&gt;
--Default values can optionally be flagged as non-modifiable to allow a fixed parameter value to always be passed into a stored process. This can be useful when using an existing program that accepts many input parameters. You can register a new, simpler stored process that has some fixed value parameters and fewer client specified parameters. &lt;BR /&gt;
&lt;BR /&gt;
You can also register multiple stored processes for a single program. Each stored process definition can pass in unique fixed parameter values to the executing program to force a particular operation or otherwise affect the execution of the stored process.&lt;BR /&gt;
&lt;/B&gt;&lt;BR /&gt;
 &lt;BR /&gt;
You could also control the value for input parameters using macro program logic, such as this:&lt;BR /&gt;
[pre]&lt;BR /&gt;
%if &amp;amp;reptype = %then %let reptype = Date;&lt;BR /&gt;
  &lt;BR /&gt;
%if %upcase(&amp;amp;reptype) = DTAE %then %let reptype = Date ;&lt;BR /&gt;
[/pre]&lt;BR /&gt;
 &lt;BR /&gt;
which is testing for a null value for &amp;amp;REPTYPE and setting the value for Date in the first %IF statement and doing a minor adjustment in the second %IF statement (in case you let them type the parameter value instead of choosing it from a drop down list).&lt;BR /&gt;
 &lt;BR /&gt;
But, macro conditional logic must be contained within a macro program, it is not allowed in "open" code. For more help with macro programs, you should consult the SAS Macro Facility documentation or contact Tech Support.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Tue, 25 Sep 2007 17:40:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Parameters-but-no-parameters/m-p/4812#M1543</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2007-09-25T17:40:55Z</dc:date>
    </item>
  </channel>
</rss>

