In an ongoing attempt to have production jobs in UNIX look similar to production jobs in MVS at my jobsite, I'm required to call an outside script to start a SAS jobs. This script is not under my control, but I must have my SAS log append to the file generated by this script.

The log file is declared as ${LOGDIR}/${SYSOUT} in the script.

If I call the SAS executable with the ALTLOG declared as follows, my log overwrites the original log file, but does not replace it completely. I can still see some residual text from the script I'm required to call. This is close, but what I need is an append to the existing log file used by the script.

sas program -ALTLOG ${LOGDIR}/${SYSOUT}

If I call the SAS executable using the appending option (>>) in UNIX, I get a warning message written to my existing log file that there is no value for ALTLOG and that it is IGNORED. My call is as follows. This is also close too. I'm getting a message from SAS written to my log, but it is not the SAS log that I need.

sas program -ALTLOG >> ${LOGDIR}/${SYSOUT}

Has anyone encountered this type situation, and if so, how did you resolve it?

TIA, Kim LeBouton KJL Computing A SAS Quality Partner (tm)