Hi,
here is an update... According to the article I found in the OnDemand Newsletter (2nd Quarter 2013), The arsstash password usage seems to behave as they describe. Seems like we'll have to include the path and filename of the ars.stash file in the -p parameter after all...
Here is an exerpt:
The stash file to be used by an instance is specified in the ars.ini file (or in the Registry on
Windows) with the SRVR_OD_STASH parameter. For example,
SRVR_OD_STASH=/opt/IBM/ondemand/V9.0/config/ars.stash
The stash file can be used by these commands: arsadmin, arsdoc, arsload, arsmaint, arsrd, and
arsxml. In our example we will use arsload. The supported values for the -a parameter are
available in the arsstash help text.
1) The preferred method is to set a userid and password for the each command in the stash
file. After doing so, the arsload command can be invoked without specifying either the -u
userid or the -p password parameters. This method is always recommended when
running the arsload command as a daemon. To use this method, first run the arsstash
command to store the userid and password for the arsload command: arsstash -a 3 -s
ars.stash -u <userid> and then enter and verify the password when prompted. Then,
when running the arsload command, omit the -u and -p parameters. The arsload
command will obtain the arsload userid and password from the stash file.
2) A second method is to specify the -u parameter for another OnDemand userid that exists
in the stash file. To use this method, first run the arsstash command to store the userid and
password in the stash file: arsstash -a 1 -s ars.stash -u <userid> and then enter and verify
the password when prompted. Then, when running the arsload command, specify the -u
<userid> and -p <stash file> parameters. The arsload command will obtain the password
for the specified userid from the stash file.
cheers,
Patrick