DATA _NULL_;
RETAIN CNT3 0;
SET CLMEXP;
BY KEYVALUE;
IF FIRST.KEYVALUE THEN CNT3=0;
CNT3=CNT3+1;
IF LAST.KEYVALUE THEN
FILE OUTEXP;
FORMAT CNT3 ZD10.;
PUT @1 CLAIM
@4991 CNT3
While running data is getting writtern into the SASLOG is there any way to avoid this.
Here is the JCL. And no there are error or warning messages. All DD satements are provided. Actually the data is getting written into the PS file as expected, but the same data is getting writtern into the saslog also. The i/p will be quite big and if the o/p gets writtern into the saslog it will cause space issues for saslog.
DATA _NULL_;
RETAIN CNT3 0;
SET CLMEXP;
BY KEYVALUE;
IF FIRST.KEYVALUE THEN CNT3=0;
CNT3=CNT3+1;
IF LAST.KEYVALUE THEN DO;
FILE OUTEXP;
FORMAT CNT3 ZD10.;
PUT @1 CLAIM
@4991 CNT3
;
END;
RUN;
I think this was a programming logic error after the
Code:
IF LAST.KEYVALUE THEN
the DO was missing which caused the FILE statement to be executed alone and after that when PUT statement was executed the data was writtern into log instead of PS file in FILE statement.
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
Is there anything of value in the saslog? Is it difficult to rerun this if there is a problem? Might it be possible to simply dummy the saslog and only create it on a rerun if needed?
Suggest you change the disp= and not use (old,catlg,catlg). DISP=OLD should be all that you need. . .
.jpg)
I think this was a programming logic error after the 
