topic Re: First. understanding in SAS Programming

First. understanding

David_Billa — Mon, 02 May 2022 15:34:22 GMT

In the following code my understanding is to sort the input dataset by the provided variables. Curve_day value will be missing for the first curve value for the same combination of the variables PO, CURVE and POSTING_DT.

Can someone clarify how the values of CURVE_DAY are 2,3 and 4 in the results as the POSTING_DT values are different in each record?

DATA WORK.JAXMERGE;
     SET WORK.JAXMERGE;
     BY PO CURVE POSTNG_DT;
     IF FIRST.CURVE THEN CURVE_DAY = .;
     CURVE_DAY+1;
RUN;

Results:

Re: First. understanding

Kurt_Bremser — Mon, 02 May 2022 15:51:19 GMT

Because curve-day is reset at first.curve, not at first.postng_dt.

Re: First. understanding

mkeintz — Mon, 02 May 2022 15:53:35 GMT

In the program

DATA WORK.JAXMERGE;
     SET WORK.JAXMERGE;
     BY PO CURVE POSTNG_DT;
     IF FIRST.CURVE THEN CURVE_DAY = .;
     CURVE_DAY+1;
RUN

you set CURVE_DAY to missing at the start of a CURVE

but then you immediately incremented it by 1.

Your syntax for the increment was to use a "summing statement", i.e.

CURVE_DAY+1

which will treat a missing value for CURVE_DAY as a zero.

Now if you want a missing, followed by 1,2,3 etc, you could

DATA WORK.JAXMERGE;
     SET WORK.JAXMERGE;
     BY PO CURVE POSTNG_DT;
     IF FIRST.CURVE THEN CURVE_DAY = .;
     else CURVE_DAY+1;
RUN

Re: First. understanding

Astounding — Mon, 02 May 2022 15:59:18 GMT

You could answer these questions and more by adding to your DATA step.

DATA WORK.JAXMERGE;
     SET WORK.JAXMERGE;
     BY PO CURVE POSTNG_DT;
put 'Start:  ' curve_day=;
     IF FIRST.CURVE THEN CURVE_DAY = .;
put 'Middle:  ' curve_day=;
     CURVE_DAY+1;
put 'End:  ' curve_day=;
RUN;

That way, you can inspect the value of CURVE_DAY at various points, as the programming statements execute.

Re: First. understanding

Tom — Mon, 02 May 2022 16:26:09 GMT

It is only missing until the SUM statement executes. Then it becomes 1 because SUM(.,1) is 1.

POSTING_DT does not impact the group, just the ordering.

So the generated CURVE_DAY values are generated in POSTING_DT order.

Note that if you have multiple observations for the same POSTING_DT value (within the other two grouping variables) they will each get a different value of CURVE_DAY. Also if there are gaps in the values or POSTING_DT so that one or more dates are skipped the numbers assigned to CURVE_DAY will not reflect that gap. So CURVE_DAY is not really a relative day value, but just a number you can use to order the values.

Re: First. understanding

David_Billa — Thu, 05 May 2022 18:49:03 GMT

@Tom @Kurt_Bremser So in the following code we're doing operations as shown for first PO value and if it is last PO value, we just need to result it in output?

DATA WORK.HAVE;
     SET WORK.HAVE;
     BY FISC_YR FISC_PD FISC_WK PO;
     IF FIRST.PO THEN DO;
           TOT = 0;
           CS_TOT = 0;
           LB_TOT = 0;
     END;
           ZNL_TOT +ZNL;
           CS_TOT +CS;
           LB_TOT +LB;
     IF LAST.PO;
RUN;

Re: First. understanding

Kurt_Bremser — Thu, 05 May 2022 19:13:23 GMT

Maxim 4.