About lethcons

lethcons · ‎12-05-2019

Jobs B and C are nested within A so as far as I can see from the generated code they are all one SAS instance. I think I've found a way to do it. In job A create the work data set as usual. In job B create a User Written Code node that has no code but has an output work data set. Manually give it the same name and variables as the work data set created in A. It will then work. See the attached package to see for yourself. Run job A and check the Output window. Please let me know if you have any better ideas. Thanks.

lethcons · ‎12-05-2019

I have DI Studio job A. Within it it calls job B and then job C. Is there any way I can share work tables and reference them as input/output tables in my jobs? Currently all I can think of is to write them to permanent data sets in permanent libraries that are registered in metadata. For various reasons this is far from ideal. Thanks.

lethcons · ‎08-09-2019

I suggest you look at PROC PRINTTO LOG=.

lethcons · ‎06-26-2019

Setting options ps=max; does not suppress the first log title line, only potentially subsequent title lines.

lethcons · ‎08-07-2018

Perfect Cynhia, thanks! I had tried playing with that but I must have had it in the wrong place.

lethcons · ‎08-07-2018

When I run this code (SAS 9.4M5) data a; kkkkkkkkk='A'; xxxxxxxxx=1; yyyyyyyyy=2; output; kkkkkkkkk='B'; xxxxxxxxx=11; yyyyyyyyy=22; output; run; ods html close; ods html file="<path>\Report.html" style=meadow; proc print data=a noobs; var kkkkkkkkk xxxxxxxxx yyyyyyyyy; sum xxxxxxxxx yyyyyyyyy; run; ods html close; The output in the SAS Results window is as expected, but in Report.docx (attached, contains the output Report.html but cannot attach .html file here ) you will see the SUM figures are centred. This doesn't happen if I use style=default. I can't find any way of getting the SUM values right-justified. Can anyone please advise? Many thanks. -Howard

lethcons · ‎07-04-2018

Thanks for this, sorry I've only just got round to looking at it. Maybe I've missed something but I can't see a reference to a transparent prompt group, only "The functionality of a hidden prompt is transparent to an end user.". -Howard

lethcons · ‎06-07-2018

Can someone please tell me what is a transparent group when building stored process prompts? When are they intended to be used? Or even just point me to some documentation. I can't find anything useful on these at all. Thanks -Howard

lethcons · ‎02-26-2018

Thanks to all who replied. It was the CONSTDATETIME option I was looking for.

lethcons · ‎02-22-2018

Consider this: proc sql; insert into mysastab(key, datetime) select key, datetime() from mysastab0 ; quit; I think I may have heard that the datetime() function gets evaluated once and then that constant value is used for each row inserted into mysastab from mysastab0. I want to avoid the situation where the value for datetime is evaluated for every input row and so may not show exactly the same time for each row inserted. Which is it? Can anyone give an authoritative answer? Thanks.

lethcons · ‎01-18-2018

I don't think that's correct. The value in the prompt is what was most recently set in the prompt, it does not get the value from a global macro variable.

lethcons · ‎01-15-2018

I don't think so. The prompt sets the initial value of the macro variable, but the macro variable does not set the initial value of the prompt. If there is a way I've never seen it.

lethcons · ‎01-15-2018

In the past I've copied and pasted the code for the whole job and pasted into column A of an Excel worksheet. Then done the same for the other job, pasting into column C. Then in cell B1 I insert the formula =A1=C1 and then copy that all the way down. Then I put a filter on column B and filter for FALSE. Where the code is different you may need to insert blank lines into one or the other in order to keep them in step, and then recopy the formula down. There will be lines which are only different because they came from different jobs - these should be easy to spot. Or, you could use something like WinMerge to compare the two sets of code. But I don't think there is anything more elegant.

lethcons · ‎01-04-2018

Thanks - one more term to tuck away in my own personal data at rest store.

lethcons · ‎01-04-2018

While I've not yet had the pleasure of playing with MBLs, a few points come to mind. Security If people wish to write their own libnames then they will need all the connection information, including passwords, in order to do this. Enforcing access through metadata will mean that connection details stay within the realm of admins. Portability A non-MBL libname will not be portable. Thus a program developed in a Dev environment and promoted through other environments, eventually to Prod, would need to change that libname statement in each environment. A MBL would pick up everything it needs from the metadata in the current environment, irrespective of the environment. Similarly, if a database is moved to a different server, or a password changed - a MBL libname statement would not need to be modified. Passthrough I may have this wrong, but I believe a MBL greatly simplifies specifying connection details for SQL passthrough and means that actual connection details are not required. By the way, what is "data at rest"? Never heard this term before.

Online Status	Offline
Date Last Visited	‎03-27-2025 07:24 AM

Re: Share SAS work tables across nested jobs in DI Studio

Share SAS work tables across nested jobs in DI Studio

Re: SAS DI - MGMT Console - Loop and Logs

Re: Can I supress the Page Number, Title (The SAS System), and Date in...

Re: PROC PRINT SUM values are centred

PROC PRINT SUM values are centred

Re: Transparent prompt group

Transparent prompt group

Re: Use of datetime() function in SQL

Use of datetime() function in SQL

Re: Compare DI Jobs

Re: Maximum length of job name in DI Studio

Re: How make SAS DI SQL transformation to use alternative library for ...

Re: Hide the code of a Stored Process