IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

EZA1735I Std Return Code = 15504, Error Code = 00002


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sampaul4u

New User


Joined: 27 Mar 2010
Posts: 19
Location: folirida

PostPosted: Wed Dec 15, 2010 6:09 pm
Reply with quote

Hi,
My FTP statements:
cd /main/country
pwd
ebcdic
put 'XXXX.XX.XX.XXX' xx.txt
quit

The above FTP statements were working without any issues for years now. Currently I am trying to enhance this FTP job to capture any issues by FTP itself by coding PARM=’(EXIT=nn’. But unfortunately this new FTP command with PARM='(EXIT=nn' threw an error and terminated the FTP process.

Job spool message:
EZA1736I /main/country
EZA1701I >>> CWD /main/country
250 CWD command successful.
EZA1460I Command:
EZA1736I pwd
EZA1701I >>> PWD
257 “/main/country" is current directory.
EZA1460I Command:
EZA1736I ebcdic
EZA1701I >>> TYPE E
504 Type E not implemented.
EZA1735I Std Return Code = 15504, Error Code = 00002
EZA1701I >>> QUIT
221

Any guidance to resolve this issue would be greatly appreciated.

Thanks,
Sam.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Wed Dec 15, 2010 6:17 pm
Reply with quote

Do you get any clues from this:
Code:
EZA1736I ebcdic
EZA1701I >>> TYPE E
504 Type E not implemented.
especially knowing that using EXIT means any FTP error will set a step return code, whereas NOT using EXIT means you'll get a zero return code -- always?
Back to top
View user's profile Send private message
sampaul4u

New User


Joined: 27 Mar 2010
Posts: 19
Location: folirida

PostPosted: Wed Dec 15, 2010 6:38 pm
Reply with quote

Thank you Robert.

Yes I did see it and I guess it is because that EBCDIC is not supported/implemented on the server side. This job used to get the same error (504 Type E not implemented) and RC=0 when EXIT not coded.
Is it possible to avoid the FTP termination at this level even with EXIT parm coded?

Please advise me if I am not clear on my question.

Thanks,
Sam.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Wed Dec 15, 2010 6:58 pm
Reply with quote

Quote:
Is it possible to avoid the FTP termination at this level even with EXIT parm coded?
Yes -- either get rid of the EBCDIC statement or change it to a supported type such as BINARY or TEXT. The whole point of the EXIT parameter is that without it, you'll get a zero return code in the job step no matter what happens to the FTP. If you need to have EXIT, then you need to validate every FTP statement to make sure they are valid statements.
Back to top
View user's profile Send private message
sampaul4u

New User


Joined: 27 Mar 2010
Posts: 19
Location: folirida

PostPosted: Wed Dec 15, 2010 7:01 pm
Reply with quote

That helps me a lot. I am going to get rid of EBCDIC. Thank you very much again.

Thanks,
Sam.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Wed Dec 15, 2010 7:04 pm
Reply with quote

Glad to hear it helped!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts run rexx code with jcl CLIST & REXX 15
No new posts Compile rexx code with jcl CLIST & REXX 6
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
Search our Forums:

Back to Top