topic Re: Data step failure in SAS Enterprise Guide

Data step failure

Rsadiq — Thu, 20 Apr 2017 14:54:10 GMT

Hello

I'm not sure what this error means,

%macro step0 ;
53         data sasdata.dialerfiles;
54         set /*dialer.mcp_manual_20170124*/
55         dialer2.qual_not_on_dialer_20170222_new ;
56         dialer2.march_dialer ;
57         run;
58         %mend step0;
59         %step0;

NOTE: Line generated by the invoked macro "STEP0".
59          data sasdata.dialerfiles; set dialer2.qual_not_on_dialer_20170222_new ; dialer2.march_dialer ; run;
                                                                                      ____________________
                                                                                      557
ERROR: DATA STEP Component Object failure. Aborted during the COMPILATION phase.
ERROR 557-185: Variable dialer2 is not an object.

Re: Data step failure

TheShark — Thu, 20 Apr 2017 15:00:26 GMT

The character limit for dataset names (I believe) is 32. Try to shorten that up a little bit and let us know if it works then! It also seems to be complaining about dialer2 library not being valid? Maybe it's the long name throwing SAS off into a tizzy but you may need to look into that as well if it doesn't clear up after shortening.

Re: Data step failure

Astounding — Thu, 20 Apr 2017 15:04:52 GMT

You have an extra semicolon in the middle of the SET statement. If you are reading multiple data sets on the SET statement, there should still be only one semicolon at the end.

Re: Data step failure

Kurt_Bremser — Thu, 20 Apr 2017 15:04:57 GMT

When posting log snippets, use the {i} icon/button to open a window that will preserve formatting.

You do have a semicolon between dialer2.qual_not_on_dialer_20170222_new and dialer2.march_dialer. Since the name.method notation is part of the hash object language (component objects), this explains the ERROR message.

Re: Data step failure

Kurt_Bremser — Thu, 20 Apr 2017 15:07:31 GMT

I also seriously doubt the necessity of a macro definition for what you are doing, since no dynamic code is created by the macro.

Also always test code for itself before wrapping into a macro definition. Makes debugging easier.