I am using Status Handling tab in SAS DI Studio to handle different for Job with Success, Warning, and Error status.   I will then pass this status to a autocall macro script to update to a table accordingly. By right, when job success (JOB_RC = 0), it will pass in the value of success to my macro script via autocall. I did the same for warning and error. I also put  %print Job_rc is &JOB_RC; in the status handling to see what is the job_rc as every job_rc indicates different job status.   I tried with success run, run with warning, and error, all returned &job_rc = 0.     Now I am confused. Why is this happening? SAS DI Studio first assign job_rc =0 as standard in the job but there is no assignment again when the job ends? I am sure there must be a way for assigning the right job_rc value so that we can make use of this value under "Status Handling".   ... View more

I first developed a Macro script in SAS EG, which will update a set of records into a SAS BASE Table.   I then make this a Macro Script dynamic that will take in parameter based on every session. I stored this Macro script as .sas file in the physical path in the server. (Assume it is /sasapp/macro). The screenshot for this script(I cant copy the script out because the server doesnt allow us to copy paste😞   It works perfectly fine when i run the script in SAS EG.     I configured SASAUTOS in sasv9.cfg to include SAS Auto Macro in this directory. However, even after configuring and restarting objectspawner, it is not taking effect for this new directory. My plan is that I set to trigger this macro.sas everytime i run a job in SAS DI Studio.   To further troubleshoot, I re-trigger/re-run in the original sas macro script using SAS EG, It works. However, when i try the command below, It doesn't work. Now, I am not sure what is wrong.   filename ptmacro '/sasapp/macro/jobctrl.sas'; %include ptmacro; %startjob(1, test, started);     The error that I am getting:       My question is, why running %startjob in the original full macro script works in SAS EG, but if i use %include in a new SAS Session and try to trigger with %startjob (without full macro script this time), it gives error. ... View more

Hi, in SAS Credit Scoring, there is TIME_DIM table under DIM library. From my understanding, there is a macro script that will load new month and year into this table when we execute. I want to load new years into this table and i managed to find the macro for this. %bnkfdin; %bankfdn_create_time_dim(yr_start=2004, yr_end=2016, mapto=); When I run this in SAS Enterprise Guide, I get this error: WARNING: Apparent symbolic reference FM_GRAIN not resolved. ERROR: A character operand was not found in the %EVAL function or %IF condition where xxxxxxxxx The condition was : &FM_GRAIN ne 1 and &MapTo ne %sysfunc(dequote(&WEEK_START_FLG)) and &MapTo ne %sysfunc(dequote(&WEEK_END_FLG)) I have been trying to understand and browse through administrator guide for Credit Scoring, I still dont find any clue at all. In admin guide, I found this: Set the correct value of the FM_GRAIN parameter in the Custpara.Parameter table. Only numeric values are supported for this parameter. Here are the values: n 1 is Month (default value) 24 Chapter 2 / Installing SAS Credit Scoring n 3 is Day   I have no idea what is custpara.parameter. Why is this SAS CS Admin Guide has such instruction that is so vague?   Is there anyone that can help me with this? ... View more

I am using SAS Data Integration Studio and for my jobs with SCD Type 2 loader, I want my VALID END DTTM to be 1 sec before the next VALID START DTTM. Example as below: ID   Name   VALID_START_DTTM    VALID_END_DTTM 1    BEN       01JAN2011:00:00:00    01JAN5999:00:00:00   Ben changed his name to Ali. Therefore, we will expire his name and append a new record as below (This is what I want to achieve) ID   Name   VALID_START_DTTM    VALID_END_DTTM 1    BEN       01JAN2011:00:00:00     31JAN2011:23:59:59 1    ALI         01FEB2011:00:00:00     01JAN5999:00:00:00       As we can see, VALID_START_DTTM of ALI is just 1 sec after BEN's VALID_END_DTTM. This is what i want to achieve.   The default SCD Type 2 Loader in SAS DI Studio will set VALID_START_DTTM of ALI and BEN's VALID_END_DTTM to be at the same exact datetime when the previous/existing record expires. Example for the existing type 2 loader(that i do not want) ID   Name   VALID_START_DTTM    VALID_END_DTTM 1    BEN       01JAN2011:00:00:00    01FEB2011:00:00:00 1    ALI         01FEB2011:00:00:00     01JAN5999:00:00:00   Is there anyway to do so? ... View more

Hi, in SAS Credit Scoring, there is TIME_DIM table under DIM library. From my understanding, there is a macro script that will load new month and year into this table when we execute. I want to load new years into this table but I couldn't find the macro for this. Is there anyone that can help me with this? ... View more

I have tables that I want to set its own primary key and index. Most of the tables will use ID/RK as Primary Key whereas index will be ID/RK + STARTDT   In SAS Data Integration Studio, setting ID/RK as primary key will also auto set ID/RK as index. If I want to set STARTDT as one of the indexes, it will prompt error saying primary key doesn't have STARTDT as key bla bla. I can provide the exact error message if you need. Only if i set STARTDT as primary key, index will auto include STARTDT.   This is not what I want. If i copy the auto generated code from SAS DI and paste it in EG, i can set as below by executing script in SAS EG with slight modification on my own: Primary key: ID/RK Index: ID/RK + STARTDT   In DI Studio, there is no way for me to have Primary key as ID/RK while having ID/RK + STARTDT as index.   Or is there anyway or workaround for me to do so in SAS DI Studio?   ... View more

Hi, I want to list out all BASE tables and indexes in a SAS library and then recreate using data set statement.   Normal data set without modify statement will wipe out the index option of the original table.   Assuming I have 30 tables in the library, how can i list out all table name and its index columns? I don't see that in dictionary table. If it is found in anywhere, i can assign it to a macro to perform the magic loop for all tables.     ... View more

I am a SAS Developer and I am using SAS Data Integration Studio to build ETL jobs. I am facing an issue with SCD Type 2 Loader whereby all business key, changing columns, date, generate columns are properly set but is hitting the error below:   ERROR: no keys variable have been defined for file ACCOUNT_DIM   Upon googling, I think this has something to do with index and key. Currently, this SCD Type 2 Loader will generate "ACCOUNT_SK" but at the same time, this particular column in ACCOUNT_DIM table has index and key set to "ACCOUNT_SK". Is there any issue of conflict if a column is set as generate and index + key at the same time? If no, what could be the cause of this? ... View more