Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

IKJEFT01 - REXEC return code 001

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
Jim Kellom

New User


Joined: 12 Aug 2008
Posts: 4
Location: Grand Blanc, MI

PostPosted: Wed Aug 13, 2008 5:19 pm    Post subject: IKJEFT01 - REXEC return code 001
Reply with quote

We have been run REXEC commands using IKJEFT01 to load data into an SYBASE data base. Lately on some of the larger tables we are loading we are receiving a Condition code 001 returned.

I can't tell whether the condition code is coming from the server or if it is something from REXEC or IKJEFT01.

Any thoughts or insight will be greatly appreciated.
Back to top
View user's profile Send private message

Srihari Gonugunta

Active User


Joined: 14 Sep 2007
Posts: 295
Location: Singapore

PostPosted: Wed Aug 13, 2008 5:24 pm    Post subject:
Reply with quote

try to trace the error by using the option -d

REXEC -d
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Wed Aug 13, 2008 6:05 pm    Post subject:
Reply with quote

What message(s) are returned from REXEC on the batch log? i would think a condition code 1 would be from the remote server since REXEC is going to throw a 12 if it has problems; anything else is usually coming from the other side of the connection. You might also check the SYBASE log to see what's showing up there.
Back to top
View user's profile Send private message
Jim Kellom

New User


Joined: 12 Aug 2008
Posts: 4
Location: Grand Blanc, MI

PostPosted: Fri Aug 15, 2008 5:24 pm    Post subject:
Reply with quote

Robert Sample wrote:
What message(s) are returned from REXEC on the batch log? i would think a condition code 1 would be from the remote server since REXEC is going to throw a 12 if it has problems; anything else is usually coming from the other side of the connection. You might also check the SYBASE log to see what's showing up there.


The REXEC messages show that the SYBASE table is loaded and that the alternate index is being built then it just stops. I have had our SYBASE support team look at the logs and they do not find anything wrong.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Fri Aug 15, 2008 7:11 pm    Post subject:
Reply with quote

Sounds like a time out issue. Maybe related to a firewall?
Back to top
View user's profile Send private message
Jim Kellom

New User


Joined: 12 Aug 2008
Posts: 4
Location: Grand Blanc, MI

PostPosted: Fri Aug 15, 2008 7:28 pm    Post subject:
Reply with quote

Robert Sample wrote:
Sounds like a time out issue. Maybe related to a firewall?


That's what makes sense, but it doesn't happen everytime the job runs.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Fri Aug 15, 2008 8:09 pm    Post subject:
Reply with quote

If it's not happening every time the job runs, it even more sounds like a time out issue; amount of data to be indexed could be causing the time out, perhaps. There are TCP/IP parameters for keep alive and inactive times; contact your systems programmer to double-check what these are set to. I'd definitely run with the debug tracing option to get more information.
Back to top
View user's profile Send private message
Jim Kellom

New User


Joined: 12 Aug 2008
Posts: 4
Location: Grand Blanc, MI

PostPosted: Fri Aug 15, 2008 8:12 pm    Post subject:
Reply with quote

Robert Sample wrote:
If it's not happening every time the job runs, it even more sounds like a time out issue; amount of data to be indexed could be causing the time out, perhaps. There are TCP/IP parameters for keep alive and inactive times; contact your systems programmer to double-check what these are set to. I'd definitely run with the debug tracing option to get more information.


I did and did not get any additional information.

Thanks for your input, it re-enforces that we are looking at the correct things. Just not finding what changed.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Fri Aug 15, 2008 8:28 pm    Post subject:
Reply with quote

I wonder if a TCP/IP trace would show anything more than the other system starting the indexing and going away; it sounds like there's something going on with the other system that needs investigating. Maybe IT has a time out associated with tasks?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Job failing with USER = 4093 REASON C... Pradeepa S ABENDS & Debugging 1 Wed May 17, 2017 3:35 pm
No new posts COBOL Code Parsers and Lineage Establ... balimanja COBOL Programming 2 Tue May 02, 2017 3:30 am
No new posts Cobol upgrade - source code missing f... gthmrj IBM Tools 1 Wed Apr 26, 2017 6:04 pm
No new posts QUESTION: RETURN CHANNEL pahiker CA Products 21 Thu Apr 20, 2017 12:31 am
No new posts JCL to Set Return code based on DB2 S... vinu78 DB2 17 Mon Mar 13, 2017 9:47 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us