text: **Multiplatforms:**Stash files are the method of choice for securely storing passwords on a 
  Content Manager OnDemand for Multiplatforms server. Unified login does not work when 
  you use a Content Manager OnDemand for Multiplatforms server. Therefore, stash files 
  are the only mechanism that is provided to prevent passwords from being specified in 
  “clear text” for the various Content Manager OnDemand commands that require 
  passwords. 
  
  **Special case for z/OS and IBM i**
  If you are using a z/OS server, consider using the z/OS unified login mechanism instead of 
  the stash file. Unified login provides the same functionality as stash files, which means that 
  the passwords are not stored unencrypted when at rest (for example, in JCL or scripts) but 
  without the additional burden of managing stash files. For example, when a password is 
  changed for a user, stash files that contain the encrypted password for that user must also be 
  changed. 
  
  If you are using an IBM i server, you might not need to use stash files because if you are 
  signed on to the IBM i server with a user profile that is defined to Content Manager 
  OnDemand and that has enough authority to perform the function you are running, Content 
  Manager OnDemand uses the IBM i user profile for that function (such as**ARSDOC**or**ARSLOAD**). 
  The**-u**and**-p**parameters are not required, therefore relieving you of the need to show or 
  store a password in clear text. 