Since the Excel file resides on a UNIX system, how do you check it?
Also be aware that
Stock_RU.xlsx
and
Stock_Ru.xlsx
will be two different files existing next to each other on UNIX. And a Windows-based client tool can only access one of them, as such a situation is impossible there.
... View more
In my experience, the best translator sits on the chair in front of the keyboard, and the more complex code is, the more true this gets.
With porting code to SAS, in-depth SAS knowledge is necessary, as you will often solve issues better with non-SQL tools.
... View more
When you can be positively sure your code takes care of the file handles, then something in the procedure(s) "leaks" them, which should not happen; this means that a call to SAS technical support is necessary.
As a stopgap measure, increasing the maximum file handles of the service account will help, but it's not the real solution.
As a side note: I always made sure that the batch job account had greater limits than the personal developer accounts used during code development; that way I could be reasonably sure that codes would work without issues in production.
... View more
The purpose of a tool like Control-M is that EVERYTHING is run FROM THERE.
Have all dependencies implemented in the scheduler; if you need to react to the result of a SAS job, use clearly defined exit codes for this.
... View more
As I already said, you must define a location for the files in the command that is the main element of the desktop link. You might do this by including a cd command in the link before the SAS invocation, or by using the options as already stated.
... View more
The PC Files Server is a tool which enables SAS on non-Windows platforms to access MS Office files where Windows-only modules are needed (anything before MS switched to the XML-in-ZIP-archive format). The newer XLSX files do not need such modules and are openly documented, so SAS could write the necessary code themselves.
... View more
I see no entry for a NOW function in the SAS documentation.
So this is either an undocumented function (which should not be trusted), or something created with PROC FCMP at your site (go looking for the source code).
... View more
The time displayed for a step does not (IMHO) include the time needed to prepare (fetch the text from the program source) the next step, so don't expect the values to exactly sum up. Particularly with lots of quick steps.
And the time needed for resolving macro code is recorded nowhere at all, only in the total sum for the runtime of a complete SAS session..
... View more
