Certain DI Studio functionality is enabled by pre-assigned libraries in metadata and seems to be the preference of most developers. However, when DIS jobs are deployed to run in batch mode they need to pick up some of the same sasv9.cfg configurations but not all the preassigned libraries which are assigned using the metaautoresources option. If a scheduler is used, then metadata credentials must be embedded in the jobs.
By default, sasbatch.sh is used by the SAS Batch Server configuration and adds all the default configurations to the startup but only -metautoresources cannot be disabled cleanly.
If you look at any sasv9.cfg under any Logical Server e.g.
/opt/sas/ServerConfig/Lev1/SASApp/sasv9.cfg on our system, you will see the following:
* Do NOT modify this file. Any additions or changes should be made in sasv9_usermods.cfg.
other options and comments
Without a -nometaautoresources option that can be added to sasv9_usermods.cfg, every batch job using the defaults has to connect to the metadata server and will fail if it is unavailable.