BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
ballardw
Super User

The displayed log appears to start at or about the call to the macro %hospice.

You have 5 other macros that are run before then. Perhaps one or more of those has either another DM 'log;clear'; or onther options that is affecting the log. Were any of those macros changed to take advantage of new features in 9.4?

jtran001
Fluorite | Level 6
Hi ballardw - I checked the 5 macros called in before %hospice and none of them used a DM 'log;clear;' statement. The only option they used are "options nomprint nosymbolgen;".

These scripts have been in production since SAS v9.0 or maybe before. They haven't been changed to take advantage of the new features in 9.4 yet.
Shmuel
Garnet | Level 18

Can you post the macro code used as:

%Locking_Log(measure=APC,run=NUM);  /* check for prior run in HDMPRD */
jtran001
Fluorite | Level 6

Sure.  Please see attached.

Shmuel
Garnet | Level 18

I have checked the code. It deals with a dataset called lock.Locking_Log which has nothing with the log file.

sas-innovate-2024.png

Available on demand!

Missed SAS Innovate Las Vegas? Watch all the action for free! View the keynotes, general sessions and 22 breakouts on demand.

 

Register now!

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 19 replies
  • 1804 views
  • 0 likes
  • 4 in conversation