An explicit pass-through request with the CASCADE= option will truncate a table. However, if you do so for a PostgreSQL database, you might see a warning message in your SAS^® log, which results in SAS setting a nonzero return code. An example of the SAS log output is shown here:

SAS interprets the informational message from PostgreSQL as a warning. SAS then writes the warning message to the log and sets the SAS automatic macro variable SYSCC to 4.

Workaround

You must instruct PostgreSQL to generate messages for message values that are for WARNING or above.

The PostgreSQL documentation states the following:

“client_min_messages (string)
Controls which message levels are sent to the client. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2,
DEBUG1, LOG, NOTICE, WARNING, ERROR, FATAL, and PANIC. Each level includes all the levels that follow it.
The later the level, the fewer messages are sent. The default is NOTICE.”

Use the following EXECUTE statement:

This workaround can be used for other informational messages, such as the following:

After you apply the workaround, informational or NOTICE messages are no longer passed back from PostgreSQL to SAS, and related warning messages are not triggered in your SAS program.

 

Operating System and Release Information