Looking at data over rows is not SQL's strong point.  You really need some sequential processing which in SAS means the data step.  I'd rewrite the proc SQL to pull in DecDecision and DecPos from t1 and t2 (make sure to give thm different names like DecDecision2 and DecPos2) and leave the case logic out.  Then I'd code another data step using the output from your proc sql. Assuming that you have your data sorted so that the DecDecision2 and Decpos2 values that would determine the sys_manual are first for every application id: data outthere; retain SYS_MANUAL; set last_dcsn_sys_manual by APPLICATION_ID; if first.application_id then do; sys_manual='Manual'; if DECPOS = 1 and DecDecision = 1001 then do; if (DecDecision2 = 1 and DECPOS2 =2) or  (DecDecision2 = 2 and DECPOS2 =2) or  (DecDecision2 = 4 and DECPOS2 =2) then sys_manual='SYSTEM'; end; end; run; ... View more

I, for one would like to export the log to a time-stamped text file automatically.   Unfortunately that is not an option in EG.    What I've done is set up a task exporting the log to a work location and then using a SYSTASK step to rename the log and move it to a more permanent location.  This keeps the current version in the project and current/old versions externally. ... View more

Wow, that's a complicated query and it's quite possible one of your joins or conditions is kicking out your null values. Are there any messages in your log saying something like 'proc_cd already exists'?   That said, there is a difference between a character field filled with blanks and one that is null.   You might want to run this query again and output your proc_cd in hexadecimal format.  You could also try putting your null criterion right in the first join like this:  galaxy.unet_ub92_revenue_code_statistical_service                                   unet inner join galaxy.unet_claim_header                                                 head       on unet.unet_clm_head_sys_id = head.unet_clm_head_sys_id       and       unet.mbr_sys_id = head.mbr_sys_id AND unet.proc_cd is null inner join etc. ... View more

Well that makes a good argument for setting up a stored process server.  We've only got a logical workspace server.  But I still think we should be able to turn off that wrapper code just like you can in SAS EG. ... View more

Yes, including Adobe Acrobat Reader.  Think I should put something in? ... View more

Thanks for your reply! I considered picking them from a file but the passwords change all the time for which I am not responsible.  I can't encrypt them either because they go to platforms that can't understand the encryption routine.  The way I've been handling it now is to open up the stored process from SAS EG, run it and then remove it from the project.  What I really want is to turn off the wrapper code so my parms aren't visible. ... View more