View previous topic :: View next topic
|
Author |
Message |
mrgnndhmk
New User
Joined: 01 Feb 2006 Posts: 51 Location: India
|
|
|
|
Hi All,
In our Mainframe, we run jobs to FTP mainframe files to the unix server.
We frequently get the below mentioned problem for which we could not find any solution.
Enter Foreign Password, null, or "LOGOFF"
F: PASS XXXXXXXX
F: 530 Not logged in
Error: during , OPNFBDPR RC=00000000 RS=0000092C
FTP124W Flushing the rest of system input
FTP102I TCP/IP -- FTP Client -- Complete
FTP118I Terminating connection
There is no problem with the password but still the step fails. When we restart the job in the same step without any change to the job, it completes successfully.
I am not able to get any reference when I google "Error: during , OPNFBDPR"
If any of you faced the same problem in your mainframes and implemented some solution to prevent this, please let me know
~Muruganandham k |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
There is no problem with the password |
You are assuming here that the password is the problem. All the 530 means is that you're attempting to connect to an FTP server and you're not logged in. The problem could be the time of day (some systems restrict hours that a given user id can log in), the user id, the password, extraneous characters (such as z/OS line numbers) in the input stream, etc.
Are you using NETRC for the log in?
In any case, this almost certainly will require your communicating with the Unix sysadmin to determine what the issue is and how to resolve it. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
There is more diagnostic info available somwhere. . .
Please post the complete jcl and control statements as well as all of the sysout generated by a failed ftp step (using the "Code" tag).
Has anyone talked with the system/network admin for the unix system? There may also be something logged on that system by the ftp service. |
|
Back to top |
|
|
mrgnndhmk
New User
Joined: 01 Feb 2006 Posts: 51 Location: India
|
|
|
|
Hi,
The JCL I mentioned is in VSE
Code: |
// EXEC PROC=FTP
// EXEC FTP,PARM='IP=172.20.3.45,RETRY=02'
userid
password
CD DATA
DELETE XXDATA.TXT
QUIT
/*
|
As I mentioned, the FTP failure happens frequently but without any pattern. The Job runs daily but in last two weeks, we received 2 failures on different days.
This is the complete log of the failed step
Code: |
FTP100I TCP/IP -- FTP Client -- Version 01.05 F , 11/29/07
FTP101I Copyright 1995, 2008 (C) XXXXXXXXXXXXXXXXXXXXXXXXx
FTP105I Processing the execution parm override
FTP131I Retry Counter is set to 2
FTP109I IP Address is set to 172.20.3.45
FTP106I Processing of parm override complete
FTP115I Connecting with TCP/IP for VSE partition
FTP117I Now connected with partition
F: 220-TCP/IP for VSE Internal FTPDAEMN 01.05 F 20080229 09.58
Copyright (c) 1995,2006 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxx
220 Ready for new user
Enter Foreign User ID, null, or "LOGOFF"
userid
F: USER userid
F: 331 User name okay, need password
Enter Foreign Password, null, or "LOGOFF"
F: PASS XXXXXXXX
F: 530 Not logged in
Error: during , OPNFBDPR RC=00000000 RS=0000092C
FTP124W Flushing the rest of system input
FTP102I TCP/IP -- FTP Client -- Complete
FTP118I Terminating connection
FTP120I Connection has closed, successfully
|
Please let me know if some help can be rendered to identify the root cause and the preventive action.
~Muruganandham k |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
I have found a list of VSE FTP error (Google is my friend), and it says:
Quote: |
530 Not logged in.
You are attempting to perform an operation without first logging in (specifying user ID and password).
Action: Follow the procedures necessary for logging in before entering other commands. |
Since you seem convinced you are logged in, and VSE is definitely saying you are not, I suggest you talk to the VSE support person to trace your login attempt to see what happens. This may need to be done until you get the error, but it should show what's happening. |
|
Back to top |
|
|
mrgnndhmk
New User
Joined: 01 Feb 2006 Posts: 51 Location: India
|
|
|
|
Thanks for the answer. I would try running diagnostic tests. Since there is no identified pattern, we are not able to simulate the condition again.
We will have to wait for the next failure.
~Muruganandham k |
|
Back to top |
|
|
|