The addCaslib action does not fail if you specify an invalid path. The caslib is still created, but it will not be functional for data access until the path is corrected.
To create a session-scoped caslib, set the 'session' parameter to TRUE. Tables loaded into this caslib will not be accessible from other sessions and the caslib will be dropped when the session ends.
The addCaslib action supports a wide variety of data source types, including: PATH (for file system paths), DNFS, HDFS, S3, ORACLE, TERADATA, POSTGRES, MYSQL, SQLSERVER, SNOWFLAKE, BIGQUERY, REDSHIFT, and many others available through JDBC or ODBC.
The 'activeOnAdd' parameter is set to TRUE by default, which automatically makes the new caslib the active one for the current session. You can set it to FALSE if you do not want this behavior.
Use the 'caslib' parameter to specify the caslib where the format library resides, and the 'name' parameter for the format library's table name within that caslib. Note that if you are adding a format library from a SASHDAT file, you can specify the name with or without the .sashdat file extensio...
Use the 'path' parameter to provide the direct string path to a format library file. This path must be readable from the control node of the server. The 'path' parameter should not be used at the same time as the 'name' or 'caslib' parameters.
You can specify the output table using the 'funcTable' parameter, which is a casouttable that defines the name, caslib, and other properties of the table.
The 'caslib' parameter specifies the target caslib where the table will be created or appended on the server.
When the 'replace' parameter is set to TRUE, it overwrites an existing table with the same name in the target caslib. The default value is FALSE.
By setting the 'promote' parameter to TRUE, the table is added with a global scope, making it accessible to other sessions, provided they have the necessary permissions. The target caslib must also have a global scope.