I am getting this error while trying read files from a network location in sequential file stage. I am not able to figure out if this issue is related to the credential mappings and engine credential setup for dsadm or if the issue with access to files? Please advise.
Filename: `ls -name Historical Volumes*.csv #FilePath#`
Method: File pattern
Error:
Unable to open &COMO&: Permission denied.
Unable to open &HOLD&: Permission denied.
On a side note, how can we see the code written behind the scene for Sequential file stage?
Sequential file stage error
Moderators: chulett, rschirm, roy
the datastage login to the unix box is not allowed to open the file in question.
if you have a home or other folder that you can test with, just set that folder to full permissions (chmod 777 or winscp can do it) and try to write your file there. If that works, you need to get your sysadmin to grant access to the files to the datastage tools.
If it does not work, you may have some other weird issue.
if you have a home or other folder that you can test with, just set that folder to full permissions (chmod 777 or winscp can do it) and try to write your file there. If that works, you need to get your sysadmin to grant access to the files to the datastage tools.
If it does not work, you may have some other weird issue.
Re: Sequential file stage error
Is it the same issue you have raised before?chandu123 wrote:Filename: `ls -name Historical Volumes*.csv #FilePath#`
Method: File pattern
By looking your command i doubt it may not work.
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: Sequential file stage error
No.chandu123 wrote:On a side note, how can we see the code written behind the scene for Sequential file stage?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.