DATA Step, Macro, Functions and more

Write access denied

Reply
Frequent Contributor
Posts: 104

Write access denied

[ Edited ]
1          ********************************************************************;
2            OPTIONS NODATE LS=132 OBS=MAX SORT=2430 SORTPGM=BEST               
3                    PS=59 NOBYLINE YEARCUTOFF=1920;                            
4                                                                               
5              *- FACT003.ROUTINE.T3-OP8(THRU1712) - JSA10 -*;                  
6                                                                               
7              *- EXTRACT ALL INSTITUTIONAL CLAIMS PROCESSED DURING THE PERIOD -
8              *- ORIGINAL CLAIMS ONLY (ADJ 099) -*;                            
9                                                                               
10             *- THIS DATASET IS FOR EDI AND CLAIM SELECTION FOR -*;           
11             *- DISCOUNT AND USAGE -*;                                        
12                                                                              
13             *- CURRENT MONTH ONLY -*;                                        
14             %LET DATE1 = '2017-12-01' ; *- SETTLEMENT FROM DATE -*;          
15             %LET DATE2 = '2017-12-31' ; *- SETTLEMENT THRU DATE -*;          
16                                                                              
WARNING: THE BASE PRODUCT PRODUCT WITH WHICH SQL IS ASSOCIATED WILL BE EXPIRING 
         THIS UPCOMING EXPIRATION. MOST TYPICALLY THIS WARNING PERIOD RUNS FOR 4
         INFORMATION ON YOUR WARNING PERIOD.                                    
17           PROC SQL;                                                          
18             CONNECT TO DB2(SSID=DBR0);                                       
19               EXECUTE(SET CURRENT DEGREE='ANY') BY DB2;                      
20                                                                              
21             CREATE TABLE CLMEXT01.DATA AS                                    
22               SELECT * FROM CONNECTION TO DB2                                
23                 (SELECT                                                      
24                    LN.REND_PROVIDER       AS     RENDPROV,                   
25                    LN.PROV_ZIP_CODE       AS     PROVZIP,                    
26                    LN.PROV_SPECIALTY      AS     PROVSPEC,                   
27                    LN.PROV_TYPE           AS     PROVTYPE,                   
28                    LN.TED_PRVDR_ST_CD     AS     TEDPRVST,                   
29                    HD.CLM_BASE_ID         AS     CLMNBR ,                    
30                    HD.CLM_BGN_SRVC_DT     AS     HBEGDT ,                    
31                    HD.CLM_END_SRVC_DT     AS     HENDDT ,                    
32                    HD.CLM_FRM_CD          AS     CLMFORM,                    
33                    HD.PATNT_ZIP_CODE      AS     BENEZIP,                    
34                    HD.SETTLE_CUTOFF_DATE  AS     ORIGSTLM,                   
35                    HD.T3_CNTRCT_IND       AS     T3IND                       
36                                                                              
37                  FROM PIWD.INST_CLM_LN   LN                                  
38                         INNER JOIN                                           
39                       PIWD.INST_CLM_HDR  HD                                  
40                                                                              
41                       ON  LN.CLM_BASE_ID     = HD.CLM_BASE_ID      AND       
42                           LN.CHAP_CLM_SUB_NO = HD.CHAP_CLM_SUB_NO  AND       
43                           LN.CLM_ADJ_ID      = HD.CLM_ADJ_ID       AND       
44                           LN.CLM_TRANS_TYP   = HD.CLM_TRANS_TYP              
45                                                                              
46                       WHERE (HD.SETTLE_CUTOFF_DATE BETWEEN &DATE1 AND &DATE2)
47                              AND                                             
48                              HD.CLM_ADJ_ID = '099'                           
3                                                          THE SAS SYSTEM       
                                                                                
49                              AND                                             
50                              HD.T3_CNTRCT_IND = 'T3'                         
51                 );                                                           
ERROR: WRITE ACCESS TO MEMBER CLMEXT01.DATA.DATA IS DENIED.                     
ERROR: WRITE ACCESS TO MEMBER CLMEXT01.DATA.DATA IS DENIED.                     
ERROR: WRITE ACCESS TO MEMBER CLMEXT01.DATA.DATA IS DENIED.                     
                                                                                
NOTE: PROC SQL SET OPTION NOEXEC AND WILL CONTINUE TO CHECK THE SYNTAX OF STATEM
52                                                                              
53           %PUT &SQLXMSG &SQLXRC;                                             
0                                                                               
54                                                                              
NOTE: THE SAS SYSTEM STOPPED PROCESSING THIS STEP BECAUSE OF ERRORS.            
NOTE: SAS SET OPTION OBS=0 AND WILL CONTINUE TO CHECK STATEMENTS. THIS MAY CAUSE
NOTE: THE PROCEDURE SQL USED 0.02 CPU SECONDS AND 15041K.                       
                                                                                
NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 700K BELOW THE LINE AND 15656K ABO
                                                                                
                                                                                
                                                                                
55           PROC PRINT UNIFORM DATA=CLMEXT01.DATA (OBS=10);                    
WARNING: THE BASE PRODUCT PRODUCT WITH WHICH PRINT IS ASSOCIATED WILL BE EXPIRIN
         INDICATE THIS UPCOMING EXPIRATION. MOST TYPICALLY THIS WARNING PERIOD R
         MORE INFORMATION ON YOUR WARNING PERIOD.                               
WARNING: THE BASE PRODUCT PRODUCT WITH WHICH SASODR IS ASSOCIATED WILL BE EXPIRI
         INDICATE THIS UPCOMING EXPIRATION. MOST TYPICALLY THIS WARNING PERIOD R
         MORE INFORMATION ON YOUR WARNING PERIOD.                               
56             TITLE1 "10 OBS FROM FACT003.A082633.CLMEXT01.THRU1712.SASS";     
57             TITLE2                                                           
58               "T3 ORIGINAL INST CLAIMS SETTLED DURING THE MONTH ENDING &DATE2
59             TITLE3 "FACT003.ROUTINE.T3-OP8(THRU1712) - JSA10";               
60           RUN;                                                               
                                                                                
NOTE: THE PROCEDURE PRINT USED 0.01 CPU SECONDS AND 15184K.                     
                                                                                
NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 700K BELOW THE LINE AND 15656K ABO
                                                                                
                                                                                
61                                                                              
                                                                                
ERROR: ERRORS PRINTED ON PAGE 3.                                                
ERROR: ERRORS PRINTED ON PAGE 3.                                                
ERROR: ERRORS PRINTED ON PAGE 3.                                                
                                                                                
NOTE: THE SAS SESSION USED 0.06 CPU SECONDS AND 15184K.                         
                                                                                

This program was running fine before; when I JEM there are no errors so I'm confused as to what's causing the errors.  Any help you can provide would be appreciated.

 

Super User
Posts: 13,333

Re: HELP!

An error message such as

ERROR: WRITE ACCESS TO MEMBER CLMEXT01.DATA.DATA IS DENIED.    

usually means that the process, either your login or the server executing the program if any, do not have the correct permissions.

 

 

If you have run the exact same program, same machine and same configuration before then you likely need to contact the DB admin for that data set / data base to see if your permissions have been changed or if that table has been locked for some reason such as co-use by someone.

If JEM means a different environment than this was submitted in then the current session likely has permission issues.

 

Did you get an proc print output?

Super User
Posts: 23,311

Re: HELP!


This program was running fine before; when I JEM there are no errors so I'm confused as to what's causing the errors.  Any help you can provide would be appreciated.

 


What does 'running fine' before mean? Were you running it, or was it running under the same user account? If not, you may not have privileges to replace the data set. Also, naming your data set DATA makes it harder to determine where the error is because the word/name is not unique and you can't search for it in the log. 

 

 

PROC Star
Posts: 2,318

Re: HELP!

Please change the title of your post to something meaningful and precise.

If everybody titles their post HELP! we are in trouble. 

Super User
Posts: 9,914

Re: Write access denied

I took care of that horrible subject line.

BTW you also should have your license updated ASAP.

 

Depending on how the library CLMEXT01 is defined, look at the permissions of the directory, or check with the DB admin why permissions were changed.

If it is a standard SAS library, your problem might simply be that someone else ran the same program in your absence and left their results there. Since the standard UNIX umask gives only the owner write permission, you can't overwrite the dataset. If that is the case, have the other user remove the dataset first.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
How to convert datasets to data steps
How to post code
PROC Star
Posts: 2,318

Re: Write access denied

This is a mainframe job and you seem to have used your space quota.

See your SAS colleagues or your SAS admin to know more about what you can use, and how you can free WORK space.

 

Ask a Question
Discussion stats
  • 5 replies
  • 371 views
  • 5 likes
  • 5 in conversation