View previous topic :: View next topic
|
Author |
Message |
Skss
New User
Joined: 16 Feb 2010 Posts: 46 Location: India
|
|
|
|
Hi,
I have implemented a new job in my shops production server.
But it is often failing while it is trying to access the remote UNIX box to get the file into Mainframe. The job runs 4 times a day and it runs successfully thrice and abends once giving the bellow error
debug1: fd 1 clearing O_NONBLOCK
debug1: fd 2 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.4 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 1
Sink: .scp: /data/xfer/gsp/nar/wmcs/out/SPP_****_****.txt: Permission denied
scp: /data/xfer/gsp/nar/wmcs/out/SPP_****_****.txt: Permission denied
SCPRECV: 2011/08/17@22:37:39 *****
SCPRECV: 2011/08/17@22:37:42 Max tries (7) exceeded. Giving up.
SCPRECV: 2011/08/17@22:37:44 !!!!!scp from remote host - max retries FAILED
SCPRECV: 2011/08/17@22:37:47 !!!!!Exiting with RC=26.
wrapper.RC=26
SCPRECV: 2011/08/17@22:37:50 Cleaning up files /data/xfer/misc/WORKFILE/CS*****
As you would all agree that there would be no permission problem as it runs fine 3 times a day.
Please suggest if there is anything that can be done from the Mainframe end to prevent this error |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
As you would all agree that there would be no permission problem as it runs fine 3 times a day. |
I do not agree, and I think you are being VERY presumptious in so stating.
You need to contact whoever is in charge of the server you are connecting to and have them research the problem. It is possible, as an example, that there is a CRON job running on the Unix machine at the time you are attempting to run your fourth job of the day, and that CRON job has changed the permissions of the directory to disallow all access while a backup is being made, after which the CRON job restores the permissions. Such an process, which is quite possible, would account for the permissions problem -- and such an issue could ONLY be resolved by someone in charge of the Unix server. There are other possibilities -- I only noted that one to point out that your assumption that there is not any permission error is only an assumption, and as such, could quite easily be wrong. |
|
Back to top |
|
|
Skss
New User
Joined: 16 Feb 2010 Posts: 46 Location: India
|
|
|
|
Hi Robert,
Yes the problem was from the UINX side as Mainframe is just a client when it tries to copy the file to Mainframe.
The issue was fixed from the UNIX side yesterday as the 4th file was not generated with proper rights which was causing the permission problem.
Even though the problem was from the UNIX side but till the very last moment they kept saying that it needs to be fixed from Mainframe side.
But anyway they finally agreed and fixed it at there end |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Let this be a lesson: not all problems that show up on a mainframe are mainframe-related. Any time a mainframe connects to another machine, be it mainframe, minicomputer, PC, Unix server, or whatever, the potential is there for "mainframe" problems to arise that are actually not mainframe issues. I suspect many "mainframe" issues are called that because the controlled environment makes problems more obvious, even though the root problem may be on another machine entirely. |
|
Back to top |
|
|
|