08-21-2013 01:31 PM
08-21-2013 04:13 PM
for 1/ agree with ballardw.
for 2/ Turn results off. SAS(R) 9.3 Output Delivery System: User's Guide, Second Edition (ODS NORESULTS)
08-21-2013 07:12 PM
Options linesize= indicates how many print columns are available in the text output window (ODS LIsting). It is limited between 64 to 256, at least in 9.2.3. Anything out of that range would be ignored.
What value are you trying to set and does it really need to be the output window? What are you trying to accomplish?
09-18-2013 02:50 PM
I am writing custom warnings and messages to the log but they keep wrapping to the next line. This creates problems when my programs to read the logs (checking warnings, errors, etc) only gets part of the message because it wrapped to the next line in the log.
09-18-2013 03:28 PM
For custom warnings or errors in a datastep it may be better to send them directly to an output set;
data want (drop=errormsg) error (keep=errormsg);
length errormsg $ 400 ; /* or as long as you think the message needs to be*/
if <error condition> then do;
Errormsg = "Your custom error message";
put errormsg; /* so it can be seen in log if desired*/
There have been several threads related to parsing log files and all of them seem to have many gyrations to get what you want.
08-22-2013 03:01 AM
ad 1) linesize. Is this something happening with 9.3?
This is the evolving way of leaving the monospace world.
HTML does not know linesizes and pagesizes like the old hardcopy paper experience.
The old ls/ps are still there but are getting overruled (ballardw) sometimes (datapage)
08-22-2013 02:07 PM
Two things to try:
1) Use: ODS LISTING FILE="mvs.file.name" and then use PROC PRINT. This may bypass the pagesize/linesize limits. I would preallocate the output file with the attributes you want first.
2) Use a FILE statement and write the data with PUT statements. Files can be up to 32,767 char wide (the MVS limit last I heard - may have changed since).