Once the application is tested and ready for use in
the production environment, you must provide a mechanism for users
to invoke the application. Typically, you can either create a command
file or a program item that contains the SAS command plus a reference
to the custom configuration file.
The Windows operating
environment has graphical interface features for launching application
programs. In such an environment, you can create a program item for
your application and make your application accessible to users via
a desktop icon or folder.
For some environments,
you might want your users to access the application by using a shell
script or a batch file. For example, the following shell script starts
an application in a UNIX environment:
APPS=/u/apps
export APPS
sas -sasuser /u/apps/sasuser
-rsasuser
-autoexec /u/apps/autoexec.sas
-printcmd nlp
-xrm 'SAS.windowWidth: 80'
-xrm 'SAS.windowHeight: 32'
-xrm 'SAS.windowUnitType: character'
-xrm 'SAS.awsResizePolicy: variable'
-xrm 'SAS.sessionGravity: CenterGravity'
-initcmd "af c=corprept.app.MAINMENU.FRAME"
You can give users “execute” permission to the script
file, and they can simply enter the script's name at a shell prompt
to launch the application.