About Sandhyaa

Jagadishkatam · ‎02-12-2013

Hi Sandhyaa, I am not sure if it is possible to get the seq no as you want in DI studio without coding. May be other members can you help you if they have come across similar situation. Here is a small piece of code which i hope can help you data have; input src_col $; datalines; a a a b b c ; proc sort data=want; by src_col; run; data want; set have; retain seq_no; by src_col; if first.src_col then seq_no=1; else seq_no+1; run; Thanks, Jagadish

LinusH · ‎01-16-2013

Another option would be to: Use Extract to split the src_col3 into all necessary columns (depending on the maximum length of src_col3) Try to master the Transpose transformation to generate for each new src_col3 column.

Sandhyaa · ‎01-15-2013

Thanks Linush. Its working fine.

Patrick · ‎02-16-2013

@Sandhyaa In the library definition under Data Server/Database Schema use instead of the schema name something like &db_schema_1. Then in the autoexec define and populate this macro variable with the schema name you want to use for registering the tables. I would use an autoexec which gets processed by all servers (at least the batch, stored process and workspace server should get it) so I would use ..\Config\Lev<n>\<server, eg. SASApp>\appserver_autoexec_usermods.sas and then %let db_schema_1=<schema name>;

LinusH · ‎12-10-2012

It could be a challenge to rely on code within a SAS sessions that has a failing step. The risk is that it will occur a situation that is not prepared for, and not possible for at post process to log/audit. What is the purpose? The usual requirements are monitoring, and that should be handled outside SAS, usually by the scheduler. Other auditing/logging: I would say this might be interesting for keeping statistics, like process time, resources consumed etc, so that you can see changes over time, making prognosis on future use etc,

Astounding · ‎12-05-2012

OK, that's a good start. I just want to set the bigger picture first. When you use terms like "job" and "step" and "failure" those can vary in meaning depending on the operating system. What is the operating system? Is this all one long SAS job, so that "step" refers to a DATA or PROC step within the same job? Does "failure" mean there was a SAS error message, or does it mean something else? The solution may be as simple as adding something like this just before the PROC EXPORT: options nosyntaxcheck; You should certainly consider reversing that right after the PROC EXPORT: options syntaxcheck; So here's a possible solution, as well as more questions.

LinusH · ‎11-26-2012

Use the MOD option of the FILE statement.

shivas · ‎11-21-2012

I guess there would be mapping issue.Just check if your source column and target column are mapped correctly in Mapping tab in table loader transformation. If the source col and target col are not same then you need to do manually mapping each source to target variable(automatic mapping will not work if column names are different). As suggested by Linus you an check the log for more information. Thanks, Shiva

LinusH · ‎11-12-2012

If you can't control the jobs so they won't write to the audit table at the same time, there are a number of options available to you. have the audit table store in a schema that supports simultaneous updates. Examples of this is SAS/SHARE, SAS SPD Server, end practically any other RDBMS. Make a macro that checks if a lock is available on the audit table, if not, wait for n seconds and then retries, and so on. Have the individual audit tables. They could be appended in an ordered fashion once a day (or any other time interval that suits your needs).

DanK · ‎11-08-2012

Use SAS XML Mapper tool. This will create the SAS code and XML maps needed to read your XML into a SAS dataset.

Sandhyaa · ‎11-08-2012

Thanks Linus. The abort statement works.

Patrick · ‎11-07-2012

No. Exactly as Linus explained. If you want this to happen then you will have to code it (user written transformation) - or you use a SQL join instead.

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: can library name be parameterized in sas datasets?

sequence no based on an input field

Re: how to split a column into rows dynamically in sas di?

how to split a column into rows dynamically in sas di?

Re: how to implement qualify statement in SAS DI?

Re: how to implement qualify statement in SAS DI?

Re: how to implement qualify statement in SAS DI?

Re: how to implement qualify statement in SAS DI?

Re: how to implement qualify statement in SAS DI?

how to implement qualify statement in SAS DI?

Re: sequence no based on an input field

Re: how to split a column into rows dynamically in sas di?

Re: how to implement qualify statement in SAS DI?

Re: can library name be parameterized in sas datasets?

Re: Job execution when a transformation fails

Re: job's post code execution on failure case

Re: How to appen Data in a flat file?

Re: Issue with table loader

Re: how to avoid table locks in sas dataset?

Re: how to convert inline xml into SAS dataset?

Re: can a sas job exit code be defined manually?

Re: can a lookup transformation return multiple rows?