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

NAT6504 Error While invoking PREDICT through batch


IBM Mainframe Forums -> Java & MQSeries
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
atulbagewadikar

New User


Joined: 15 Jun 2006
Posts: 26

PostPosted: Thu May 27, 2010 2:52 pm
Reply with quote

While invoking PREDICT through batch, I got following error

Code:
NAT6504 SAG EDITOR buffer pool work file open error 4.


How do I avoid/fix this?
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen

PostPosted: Thu May 27, 2010 3:20 pm
Reply with quote

Text SAG EDITOR buffer pool work file open error ... .
Expl. During SAG EDITOR buffer pool initialization, the first access to
the work file has failed with one of the following return codes:
04: Work file cannot be opened or accessed
08: Invalid work file record length
12: Work file I/O error
16: Work file defined incorrectly or in use by another buffer pool.
Actn. Check the console operator log for more detailed messages.
Correct the problem with the work file and restart the SAG EDITOR
buffer pool.
Back to top
View user's profile Send private message
atulbagewadikar

New User


Joined: 15 Jun 2006
Posts: 26

PostPosted: Thu May 27, 2010 3:41 pm
Reply with quote

Hi,

Thanks. I know what manual says and description of the error. I am looking on some help on how could we track that why the WF is not accessible and if it is being used by other application/user...how do we fix it...like through Natural Admin/DBA?
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Thu May 27, 2010 4:01 pm
Reply with quote

I' don't speak Natural, however, what Peter has posted from that, looks like work file is being used by some other application. So, have a look at the console operator log.
Back to top
View user's profile Send private message
Ralph Zbrog

New User


Joined: 21 Nov 2009
Posts: 58
Location: California

PostPosted: Fri May 28, 2010 1:54 am
Reply with quote

Start with a review of the JCL expansion in your JES output. Look in the Natural PROC for DDname CMEDIT (although your DBA has the option to use a different DDname). This is the dataset causing the NAT6504 subcode 4.

You can try a temporary fix, as follows:

- Override the DDname with
Code:
//CMEDIT DD DSN=NULLFILE

- Then add a NatParm override on the EXEC card with
Code:
PARM='EDPSIZE=48'
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 -> Java & MQSeries

 


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 CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts How to get a stack trace on a looping... ABENDS & Debugging 5
No new posts Calling Java method from batch COBOL ... COBOL Programming 5
Search our Forums:

Back to Top