About yus03590

cameronmuir · ‎12-02-2021

thanks for this, very helpful!

Patrick · ‎07-07-2018

@yus03590 I believe you're dealing with an asynchronous process and the only thing you can get is the response that your request for sending an email was successful. You would need to find a way to query the email server directly. You can find quite a few non-SAS related discussions on the Internet around this topic. If any of these can give you a solution approach will depend on your level of access to the email server.

RobPratt · ‎06-13-2018

You can call PROC APPEND from a SUBMIT block: submit; proc append base=ds1 data=ds2; run; endsubmit; Another approach is to save the results in a numeric parameter, indexed by sources and sinks, and then call CREATE DATA only once, outside the COFOR loop. This approach is illustrated in this documentation example. Note that you can also use the network solver (instead of LP) to solve shortest path problems in PROC OPTMODEL. In fact, the default is all-pairs shortest paths, so you would need to call the network solver only once.

ruchi11dec · ‎06-12-2018

when we use quotes for macro it resolves with the quotes i.e. %let a = "sas"; %put &=a; a="sas" Hope I made it clear

RobPratt · ‎05-14-2018

Your FOR loop was reading the first line of the data set each time. To read one observation per employee (with name as the key column), do this instead: read data Preferences into [name] {sh in shifts} <preferencesArray[name, sh] = col(sh)>; You can in fact combine your two READ DATA statements as follows: read data Preferences into employees=[name] {sh in shifts} <preferencesArray[name, sh] = col(sh)>; For more examples, see SAS/OR User's Guide: Mathematical Programming Examples. The pdf version has a subject index that contains entries on reading various types of data, including two-dimensional.

RobPratt · ‎05-08-2018

Your constraint declaration should use algebraic expressions instead of programming statements. You might find this documentation example helpful as a starting point for your scheduling problem. This book of examples is also useful.

ballardw · ‎02-02-2018

Do you get any warning or such in your log? If so you might show the log results. Paste the log into a code box opened with the forum {I} icon to preserve formatting of the text.

Astounding · ‎01-30-2018

In this more complete version of the program, you need quotes in the SQL code, but not in the macro comparisons: proc sql; ... where %if &TYPE = Y %then %do; person.age_group = 'Y' AND %end; %if &TYPE = S %then %do; person.age_group = 'S' AND %end; final sql condition; quit; Also, it looks like that final %END was intended to be: %MEND; Still, it would be a good idea to apply the earlier suggestion, as long as &TYPE will always be Y or S: proc sql; ... where person.age_group = "&TYPE" AND final sql condition; quit; Be sure to use double quotes (not single quotes) .... necessary to allow &TYPE to resolve into its value.

Cynthia_sas · ‎01-29-2018

Hi, It looks like you're using Enterprise Guide. In my sample code, I was NOT using EG and I was controlling my ODS Destination with programming statements. My suggestion is that you put an ODS _ALL_ CLOSE; before the ODS PDF statement and make sure that your FILE= option is pointing to a location where you have WRITE access. Also, harder to check is that you will need to make sure your program, which is running on a server, can access a URL from the server machine. If your web folks have locked down the server so it cannot use an HTTP address, then you will have to move your images to an accessible location on the server. You may need an administrator's help with that. My image was just a picture of Lewis Carroll that I found and used because it had a direct HTTP address. If you have your images on a network drive, then perhaps a simple folder path will work for you. cynthia

yus03590 · ‎01-11-2018

Hmm... That doesn't seem to be working. Is there a way to compress the size of the table directly?

LinusH · ‎12-09-2017

Well this is the correct area for DI Studio questions. But about your question. I'm not an ODS expert so I can't help with your exact requirement. But it seems you are trying to use DI Studio as a report generator, or? I would try to keep DIS doing only ETL stuff, and leave reporting to other tools. That said, you can export to Excel in several ways in a more ETL like fashion, including LIBNAME EXCEL engine and PROC EXPORT.

Online Status	Offline
Date Last Visited	‎07-06-2018 07:17 PM

Error Handling With Sending Emails (Checking whether an email sent suc...

Call a Macro With Each Observation In a Dataset

Appending to a Dataset in Optmodel

macro variable in a DATA Step

Read Data From Two Dimensional Array

Set and Array Indexing and Size Within SAS OR Constraint Statement Wit...

Resizing an Image in Report Writing Interface

Re: Problem with PROC SQL Macro If

Re: Problem with PROC SQL Macro If

Problem with PROC SQL Macro If

Re: Call a Macro With Each Observation In a Dataset

Re: Error Handling With Sending Emails (Checking whether an email sent...

Re: Appending to a Dataset in Optmodel

Re: macro variable in a DATA Step

Re: Read Data From Two Dimensional Array

Re: Set and Array Indexing and Size Within SAS OR Constraint Statement...

Re: Resizing an Image in Report Writing Interface

Re: Problem with PROC SQL Macro If

Re: Insert Image into Report Writing Interface via URL

Re: Preventing Line Wrapping in Report Writing Interface

Re: How to control new sheets with ODS Excel in Data Integration Studi...