Thank you for recognising the merits of such an approach. Since we first want=need to set tags for documentation, we will also take this opportunity to set tags for "cutting". Whether this "cutting" will be done manually or automatically will be decided in the course of the project. Of course, we want to avoid having to manage two code versions (cut, uncut) for as long as possible. ... View more

I agree with you. However, it doesn't hurt to ask if someone has done this before, ideally using SAS. It would help to save a lot of manual work. These "lists" contain dozends of encapsulated macros....   You know I'm thinking of an approach using tags "#" like below.   overlongmacro.sas:      #BEGIN      #NAME  part1      #END      #BEGIN      #NAME  part2      #END   split or cut into   part1.sas:      #BEGIN      #NAME  part1      #END   and   part2.sas:      #BEGIN      #NAME  part2      #END   Sounds feasible, but devil's in the details, as per ususal ... View more

In this case, the grid variable is the only result. My original question tends to change to how to properly implement a _N_ equivalent using DS2... ... View more

Adjusting to integer didn't solve the issue. ... View more

Hello @ManoharNathGupta  I do not want to judge why you do not want to use macros. There are may reasons to do, but maybe some not to. In that case, see a SAS macro as a text with "slots". Also, see a macro call as a trigger to start this macro. You have two calls, so you trigger the same "text" two times. So, copy the "text" two times. Replace the so-called macro variables beginning with & with the values from the first macro call in the first text Replace the so-called macro variables beginning with & with the values from the second macro call in the second text That should be it.   ... View more

VALIDATE says the basic error is that the package method sqlstmt.sqlstmt call is not supported by DS2 in CAS. ... View more

I cannot provide real errors and log due to compliance. I know this isn't very helpful, I am sorry. If the logic of that stripped-down code is not too far from wrong than we can shift our attention on data or environment. As usual, it's the tiny things... Thank you very much for your efforts.   ... View more

I think this way it is simpler   package vmassst2;     dcl package logger logr('App.Test');     dcl package sqlstmt ss;     dcl package SQLStmt srollback;       method insert2( int quantity,                              in_out int rc );         if null( srollback ) then do;             srollback = _NEW_ sqlstmt( 'rollback' );                 if null( srollback ) then do;                 logr.log( 'e', 'SQLStmt ROLLBACK instantiation failed.' );                 rc = -1;                 goto Exit;             end;         end;                                                                                   if null( ss ) then do;             ss = _NEW_ sqlstmt( 'insert QUANTITY into ora_dstest1.vmassst2 select QUANTITY from MY_SAMPLE_TBL where QUANTITY is not missing' );                                              /* not tested. Logic: insert value QUANTITY of MY_SAMPLE_TBL in place of value QUANTITY of VMASSST2 */             if null( ss ) then do;                 logr.log( 'e', 'SQLStmt insert instantiation failed.' );                 rc = -1;                 goto Exit;             end;         end;         rc = ss.execute();         if ( rc ) then do;             logr.log( 'e', 'execute failed. rc=$s', rc );             goto tRollback;         end;                                                                                     tRollback:                                                                             logr.log( 'd', 'Rolling back uncommitted work...', k );             srollback.execute();         end;       Exit:     end;                                               endpackage;   ... View more

too many. we don't have the orignal data. so, we just replaced the VALUES expression 'insert into ora.... values (?,?), by a SELECT expression like 'insert into coldtemps select * from where...'  Just something based on SASHELP.CLASS to get it running. Nothing fancy. We can make it complicated ourselves. 🙂 ... View more

For whatever reason we cannot get it running. Does anybody have possible a completely stripped-down code snippet that updates just a single a numeric Oracle column? That would possibly rule out other root causes. Kind regards, guys ... View more

  We're surprised we could use sqlstmt as it could not be used on CAS. Way to go. Thanks very much! KR ... View more

Hit the spot. Thank you very much! ... View more