Hi,
anyone familiar with the error below?
I use a small script that appends data to an existing table and there is no calculation involved. This is the 1st time I am receiving this error. Any suggestions please?
ERROR: Floating Point Overflow.
ERROR: Termination due to Floating Point Exception
ERROR: You cannot open WORK.EDI.DATA for output access with member-level control because apparently, the blocking lock was acquired 
by calling yzlrlok() directly. XOENLOCK/XLEINUSE message is: "ERROR: MEMBER lock is not available for SASUSER.EDI.DATA, lock held 
by REB name length returned is zero..".
Please post the code causing these errors.
I am investigating the two excel files if some weird data in them. Been running this script for a few years. Never had this error before
%macro edi(dat);
proc import datafile="/ab/edw/general/general1/edwoth/DAI/TMI/Claims_EDI_Files/&dat..xlsx" 
            dbms=xlsx out=EDI replace;
run;
data  EDI(drop=CLMAAZ);
 set EDI;
 Creation_Date=put(today(),yymmddn8.);
 Claimant_Age=input(CLMAAZ,best.);
 rename
 PERIOD=Reporting_Month
 POLBRZ=Policy_Branch
 POLTYZ=Policy_Type
 RSKTYZ=Risk_Type
 POLPMZ=Claim_Class
 CLMKYZ=Claim_Number
 CLMNOZ=Number_of_Claimants
 POLNOZ=Policy_Number
 UWCLAS=Underwriting_Class
 CLTKYZ=Claimant_Key
 DATOLC=Date_of_Loss
 DATRPC=Date_Reported
 REPOLC=Replaces_Policy_Number
 APLDTZ=Application_Date
 INCPTC=Inception_Date
        EXPRYC=Expiry_Date
 CLMNAZ=Cause_of_Claim
 CLMNPZ=Claimant_Province
 KDDOBZ=Date_of_Birth
 SEXMFZ=Gender
 ACPMVZ=Actual_Paid_Movement
 ACRMVZ=Actual_Recovered_Movement
 ESPMVZ=Estimated_Paid_Movement
 ESRMVZ=Estimated_Recovered_Movement
 STATCZ=Claim_Status
 ICDCOD=ICD_Code
 AGTBRZ=Agent_Branch
 AGTNOZ=Agent_Number
 STRSKZ=State_of_Risk
 LSSLCZ=Loss_Location
 BLANK=Blank
 CLMFEE=Claim_Fees; run;
proc append base=xx.claims_master_edi new=EDI force;
run;
%mend edi(dat);
%edi(201511AB_EDI);
%edi(201512AB_EDI);
I just tried running the same script using an excel file that I could easily append last week and again ,same error and today I am scheduled to migrate to win10 so I am wondering if that causes this error?
EDIT:Ran another script in my EG SAS and it works so.... I am clueless as to why I am getting the error above
never mind, turns out I had a space issue
all good now
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.