02-21-2020
vijayanand
Obsidian | Level 7
Member since
06-27-2013
- 64 Posts
- 0 Likes Given
- 1 Solutions
- 1 Likes Received
-
Latest posts by vijayanand
Subject Views Posted 972 02-20-2020 08:20 AM 995 02-20-2020 07:05 AM 1025 02-20-2020 06:29 AM 2687 11-06-2019 01:09 PM 2698 11-06-2019 11:56 AM 2706 11-06-2019 10:21 AM 2731 11-06-2019 08:09 AM 2759 11-06-2019 07:29 AM 1455 10-29-2019 09:52 AM 621 10-24-2019 10:59 PM -
Activity Feed for vijayanand
- Posted Re: Unable To switch to a specific directory using call system routine on SAS Programming. 02-20-2020 08:20 AM
- Posted Re: Unable To switch to a specific directory using call system routine on SAS Programming. 02-20-2020 07:05 AM
- Posted Unable To switch to a specific directory using call system routine on SAS Programming. 02-20-2020 06:29 AM
- Posted Re: Unable to create an Index file on SAS Programming. 11-06-2019 01:09 PM
- Posted Re: Unable to create an Index file on SAS Programming. 11-06-2019 11:56 AM
- Posted Re: Unable to create an Index file on SAS Programming. 11-06-2019 10:21 AM
- Posted Re: Unable to create an Index file on SAS Programming. 11-06-2019 08:09 AM
- Posted Unable to create an Index file on SAS Programming. 11-06-2019 07:29 AM
- Posted Unable to resume the metadata server on Administration and Deployment. 10-29-2019 09:52 AM
- Posted Migrating the SAS Repositories on SAS Programming. 10-24-2019 10:59 PM
- Posted Frequent connectivity issues on SAS Programming. 09-25-2019 06:13 AM
- Posted Re: I/O Error on SAS Programming. 09-05-2019 05:29 AM
- Posted I/O Error on SAS Programming. 09-05-2019 02:36 AM
- Posted Impact Of OS upgradation in the behaviour of SAS on SAS Programming. 09-03-2019 08:43 AM
- Posted SAS Application Migration From AIX to Linux Server on SAS Programming. 08-23-2019 09:28 AM
- Posted Unable To Access Libraries In SAS EG on SAS Enterprise Guide. 06-17-2019 01:21 PM
- Posted SPD Server ACL Issue on SAS Programming. 06-13-2019 01:45 AM
- Posted SPD Server ACL Issue on SAS Programming. 06-07-2019 03:15 AM
- Posted SAS Catalogs and Index files on SAS Programming. 06-03-2019 03:20 AM
- Posted Index files on sas datasets on SAS Programming. 05-21-2019 09:52 AM
-
My Liked Posts
Subject Likes Posted 1 11-30-2018 06:17 AM
02-20-2020
08:20 AM
Hi,
The problem is not with the cd command. It is getting into the given path , but it is coming out immediately.
data _null_; call system ("cd /PARENTFOLDER/SUBFOLDER "); run;
after the cd command I am running the below command. It seems I am losing the path and it is listing the contents from directory where sas is launched from.
filename datafile pipe " ls -p | grep -v / ";
... View more
02-20-2020
07:05 AM
The userid is the owner and also a part of the owning group.. For others it was r_x not r_w. Sorry ..it was typo
... View more
02-20-2020
06:29 AM
Hi,
We have a sas application running in a Linux server. This Linux server has an external NFS mount and one of the sas programs is trying to list the contents of a folder in the NFS mount. In the below example, I can do “cd /PARENTFOLDER” but not ("cd /PARENTFOLDER/SUBFOLDER ").The access levels on SUBFOLDER are 775 (rwxrwxr_w). The userid with which the program is being executed has full permission (rwx) on this folder. Not sure why it is still not accessible thru program. However, this path is accessible directly on the server with the same userid.
data _null_; call system ("cd /PARENTFOLDER/SUBFOLDER "); run;
This NFS mount is common to another Unix server and my sas program from the unix server is able access this location programmatically.
Any help could be much appreciated.
Thanks..
... View more
11-06-2019
01:09 PM
Thanks for these links Shmuel.
It is the same windows drive that was being used when teh application was running in AIX-SAS9.3.
Now the application is running in Linux SAS9.4 and using the same windows drive...very strange.
It is actually the code generated by SAS DI Studio Table loader transformation with Replace Entire Table as load technique. This code is being submitted in SAS EG as a standalone sas program.
Though the log says that the index "Permanent copy of file TP_OUT.AAAAAAA.INDEX was deleted, the index file (AAAAAAA.sas7bndx.lck) is physically present with a lock.
... View more
11-06-2019
11:56 AM
The same program ran fine with no errors in AIX. Please find attached the log of the program ran AIX - SAS9.3
NOTE: The data set TP_OUT.AAAAAAA has 0 observations and 9 variables.
NOTE: DATA statement used (Total process time):
real time 0.05 seconds
cpu time 0.00 seconds
MPRINT(ETLS_LOADER): ;
NOTE: Creating integrity constraints ...
MPRINT(ETLS_LOADER): proc datasets library=TP_OUT nolist;
MPRINT(ETLS_LOADER): modify AAAAAAA;
MPRINT(ETLS_LOADER): ic create not null (COL1);
NOTE: Integrity constraint _NM0001_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL2);
NOTE: Integrity constraint _NM0002_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL3);
NOTE: Integrity constraint _NM0003_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL4);
NOTE: Integrity constraint _NM0004_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL5);
NOTE: Integrity constraint _NM0005_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL6);
NOTE: Integrity constraint _NM0006_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL7);
NOTE: Integrity constraint _NM0007_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL8);
NOTE: Integrity constraint _NM0008_ defined.
MPRINT(ETLS_LOADER): ic create Index1 = primary key (COL1 COL2 COL3 COL4 COL5);
NOTE: Integrity constraint Index1 defined.
MPRINT(ETLS_LOADER): quit;
NOTE: MODIFY was successful for TP_OUT.AAAAAAA.DATA.
NOTE: PROCEDURE DATASETS used (Total process time):
real time 1.04 seconds
cpu time 0.03 seconds
MPRINT(ETLS_LOADER): ;
NOTE: Appending data ...
MPRINT(ETLS_LOADER): proc append base = TP_OUT.AAAAAAA data = TP_MART.AAAAAAA () force ;
MPRINT(ETLS_LOADER): run;
NOTE: Appending TP_MART.AAAAAAA to TP_OUT.AAAAAAA.
NOTE: There were 903 observations read from the data set TP_MART.AAAAAAA.
NOTE: 903 observations added.
NOTE: The data set TP_OUT.AAAAAAA has 903 observations and 9 variables.
NOTE: PROCEDURE APPEND used (Total process time):
real time 0.07 seconds
cpu time 0.00 seconds
... View more
11-06-2019
10:21 AM
NOTE: Creating table ...
MPRINT(ETLS_LOADER): data TP_OUT.AAAAAAA;
MPRINT(ETLS_LOADER): attrib COL1 length = 8 format = YYMMDD10.;
MPRINT(ETLS_LOADER): attrib COL2 length = $8 ;
MPRINT(ETLS_LOADER): attrib COL3 length = $10 ;
MPRINT(ETLS_LOADER): attrib COL4 length = $3 format = $3. informat = $3. ;
MPRINT(ETLS_LOADER): attrib COL5 length = $8 label = 'Currency sell code';
22 The SAS System 09:54 Wednesday, November 6, 2019
MPRINT(ETLS_LOADER): attrib COL6 length = 8 format = commax18.4 informat = commax18.4 ;
MPRINT(ETLS_LOADER): attrib COL7 length = 8 format = datetime23. ;
MPRINT(ETLS_LOADER): attrib COL8 length = 8 format = datetime23. ;
MPRINT(ETLS_LOADER): attrib COL9 length = 8 format = datetime23. ;
MPRINT(ETLS_LOADER): call missing(of _all_);
MPRINT(ETLS_LOADER): stop;
MPRINT(ETLS_LOADER): run;
NOTE: The data set TP_OUT.AAAAAAA has 0 observations and 9 variables.
NOTE: DATA statement used (Total process time):
real time 0.04 seconds
cpu time 0.00 seconds
MPRINT(ETLS_LOADER): ;
NOTE: Creating integrity constraints ...
MPRINT(ETLS_LOADER): proc datasets library=TP_OUT nolist;
MPRINT(ETLS_LOADER): modify AAAAAAA;
MPRINT(ETLS_LOADER): ic create not null (COL1);
NOTE: Integrity constraint _NM0001_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL2);
NOTE: Integrity constraint _NM0002_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL3);
NOTE: Integrity constraint _NM0003_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL4);
NOTE: Integrity constraint _NM0004_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL5);
NOTE: Integrity constraint _NM0005_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL6);
NOTE: Integrity constraint _NM0006_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL7);
NOTE: Integrity constraint _NM0007_ defined.
MPRINT(ETLS_LOADER): ic create not null (COL8);
NOTE: Integrity constraint _NM0008_ defined.
MPRINT(ETLS_LOADER): ic create Index1 = primary key (COL1 COL2 COL3 COL4 COL5);
ERROR: Permanent copy of file TP_OUT.AAAAAAA.INDEX was deleted.
ERROR: Permanent copy of file TP_OUT.AAAAAAA.INDEX was deleted.
MPRINT(ETLS_LOADER): quit;
NOTE: Statements not processed because of errors noted above.
ERROR: File TP_OUT.AAAAAAA.INDEX is not open.
NOTE: Statements not processed because of errors noted above.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set.
NOTE: PROCEDURE DATASETS used (Total process time):
real time 0.42 seconds
cpu time 0.01 seconds
MPRINT(ETLS_LOADER): ;
NOTE: Appending data ...
NOTE: File TP_OUT.AAAAAAA.INDEX does not exist.
ERROR: The open failed because library member TP_OUT.AAAAAAA.DATA is damaged.
MPRINT(ETLS_LOADER): proc append base = TP_OUT.AAAAAAA data = TP_MART.AAAAAAA () force ;
MPRINT(ETLS_LOADER): run;
Attached is the snippet of the log for the same issue. TP_OUT is the windows location and TP_MART is the Linux location. Earlier TP_MART was the AIX location.
... View more
11-06-2019
08:09 AM
It is actually not being copied...instead is being created on the windows drive using the below code
data TP_OUT.AAAAAAA; attrib COL1 length = 8 format = YYMMDD10.; attrib COL2 length = $8; attrib COL3 length = $10; attrib COL4 length = $3 format = $3. informat = $3.; attrib COL5 length = $8; attrib COL6 length = 8 format = commax18.4 informat = commax18.4; attrib COL7 length = 8 format = datetime23.; attrib COL8 length = 8 format = datetime23.; attrib COL9 length = 8 format = datetime23.; call missing(of _all_); stop; run;
proc datasets library=TP_OUT nolist; modify AAAAAAA; ic create not null (COL1); ic create not null (COL2); ic create not null (COL3); ic create not null (COL4); ic create not null (COL5); ic create not null (COL6); ic create not null (COL7); ic create not null (COL8); ic create Index1 = primary key (COL1 COL2 COL3 COL4 COL5); quit;
This code was working fine in SAS9.3 on AIX but failing in SAS9.4 on Linux.
... View more
11-06-2019
07:29 AM
Hi,
Recently we have migrated a sas application from AIX (SAS9.3) to Linux(SAS9.4). In this application, there is a functionality to write a sas dataset with it's index file to an external windows drive. This windows drive is mounted on the AIX and Linux servers.
In the Linux server,when the program is trying to write the sas dataset with it's index on to windows drive, it is throwing the below message.
ERROR: Permanent copy of file TP_OUT.AAAAAAA.INDEX was deleted. ERROR: Permanent copy of file TP_OUT.AAAAAAA.INDEX was deleted.
The program code is taken from a SAS Data Integration job and submitted as a standalone sas program. The functionality is , if the sas dataset with it's index is available, the process deletes them and creates them and then appends the data using proc append.
Also,in the Windows location, it is shown as locked. TP_OUT.AAAAAAA.SAS7BNDX.LCK
No clue why the index is failing here. Any help is appreciated.
... View more
10-29-2019
09:52 AM
Hi,
We run our SAS applications on SAS 9.4 with a metadata server , SAS DI Studio and SAS EG. One of the user repositories got corrupted and somehow the metadata server got paused. We are unable to resume the metadata server.
When tried to open DI Studio, it says server is paused. No pause comment was provided.
When tried to reusme the active server , it says com.sas.iom.SASIOMDefs.GenericError: The repository couldn't be accessed using path Metadata Repositories/user_name because that directory doesn't exist.
User _name is the name of the person whose repository was corrupted.
Any imformation is really helpful.
Thanks,
Vijayanand.
... View more
10-24-2019
10:59 PM
Hi ,
Currently we are migration a SAS application from AIX (SAS 9.3) to Linux (SAS9.4). This application has many DI Studio jobs. We could migrate all the jobs which are lying in project related folders.
Some of the jobs were checked out in the source (AIX) for editing as part of the current business activity. How do we migrate these checked out jobs also to the target (Linux).
One option we could find is to check out the same job int he target and then promote the metadata from Aix to Linux using Export and Import wizards. However, this is very time consuming process as there are many jobs in the check out folders. How do we move all of them in one go.
Thanks,
Vijay.
... View more
09-25-2019
06:13 AM
Hi,
We recently have migrated a sas application from AIX to Linux (RedHat 7.3) and the version of SAS is 9.4M3. The users connect to this server remotely using SAS/Connect. After the migration, most of the users are facing the connectivity issue with the below message. This was not the case in the old server.
ERROR: Conversation termination; status=1.
There are no firewalls in the network while connecting to the server.
We have added the variable CONNECTKEEPALIVE in the configuration file as a solution to this as shown below.
-set CONNECTKEEPALIVE 5
The users still are facing the connectivity issues.
Any suggestions pls...
Has this issue got anything to do with the load on the server
Thanks,
Vijay.
... View more
09-05-2019
05:29 AM
Yes Patrick.
It did work some times and failed some times.
The log has no additional information than what was shared.
Thanks.
... View more
09-05-2019
02:36 AM
Hi,
We have recently migrated the sas applications from AIX to Linux platform. In the AIX server, there was a Windows Shared rive mounted on the server. The same shared drive was mounted in the new Linux server.
Now some of the sas programs which write create sas datasets in the shared location are failing with I/O errors. This was not the case when the shared rive was mounted in the AIX server.
ERROR: An I/O error has occurred on file MASTER.table1.DATA. ERROR: File MASTER.table1.DATA is damaged. I/O processing did not complete.
ERROR: An I/O error has occurred on file OUTSQL.table2.DATA.
One possible reason fr this error is lack of storage space. However, the windows shared rive has enough space. Any help is much appreciated.
Thanks,
Vijay.
... View more
09-03-2019
08:43 AM
Hi,
We have SAS installed in the Linux machine and the user connect to this Linux server using SAS/Connect. Now, the Windows Operating System in the users PCs' was upgraded from Windows 8 to Windows 10.
With this upgrade , the below statement is demanding the Fully Qualified Host Name of the server instead of a simple hostname. Any specific reason for this.
%let rmtsrv= servername port; Also, the libname statements with simple hostname like "/servername/abcd/xxxx/zzzzz" are failing now with the Windows 10 upgrade.
Neither the fully qualified host name in the libname is working.
Also, we have an interface/set up called SAMBA with which the Linux server can be accessed as a windows server.
Any help in this regard is much appreciated.
Thanks,
VIjayanand.
... View more
08-23-2019
09:28 AM
Hi ,
We are migrating a sas application from a Unix server to Linux server.
We found the below files in each user folder in the Unix server.
sasmbc.sas7bdat sasmbc.sas7bndx parms.sas7bcat
Do these files get created by default for every user? or Should we migrate them from AIX machine to Linux Machine? Any help is much appreciated.
Thanks,
Vijay.
... View more