Working with an application that runs on several servers. The code is tightly controlled with Clearcase. An identical batch SAS program is run on each system being initiated by CRON. The CRON entry for each server uses the -noquotelenmax system option to turn off The Warning 262 error message. This application uses millions of macro variables that are over 262 bytes long so the warning message will generate millions of log messages if not surpressed.
The CRON and SAS program works fine on all but one server. On that one server the Warning 262 messages are generated even after CRON set the -noquotelenmax system option when executing the program.
Anybody know why the option would be ignored on one system and not others. They code is identical. The .profile and proc options are also identical.
This isn't really an ODS or PROC REPORT/PRINT/TABULATE question. Since you are experiencing issues on a particular server, but not on others, with the same code, this is the kind of problem that should be resolved with Tech Support.
They have access to all different kinds of servers in order to test and duplicate your results. AND, if there is an issue with NOQUOTELENMAX not working on a particular server, then they are the ones that would issue a Note about the behavior for other users who have the same server configuration.
sounds like a place where a developer implements the option to switch off the message before generating code that might cause it, but afterwards or at close of the XML libname engine handler, switches the option to the default rather than the prevailing value. So it should be an easy fix. (imho)
not much left to add to Cynthia's points, except that executing [pre] proc options option= quotelenmax define value ; run ;[/pre]among many details it reveals [pre]Restricted: Your Site Administrator can restrict modification of this option[/pre]
Do you think this may have happened on that special server ?