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
 

 

IDMS - Cobol (1473 abend)

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IDMS/ADSO
View previous topic :: :: View next topic  
Author Message
shankarm

Active User


Joined: 17 May 2010
Posts: 175
Location: India

PostPosted: Mon Jul 05, 2010 4:07 pm    Post subject: IDMS - Cobol (1473 abend)
Reply with quote

Hi all,

When i run my cobol program it abends with U1473.

My cobol program calls another module which accesses IDMS.
The error code is,

Quote:
CEE3250C The system or user abend U1473 R=NULL was issued.


As far as i referred, I got to know that this is because of 'MAXERUS'.
The MAXERUS limit is reached.

What is the solution for this problem?

Correct me If I am wrong.
Back to top
View user's profile Send private message

Meenakshi Selvaraj

New User


Joined: 30 Oct 2009
Posts: 36
Location: Chennai

PostPosted: Mon Jul 05, 2010 7:34 pm    Post subject: IDMS - Cobol (1473 abend)
Reply with quote

Hi,

Reason for the 1473 Error code:

A new run unit would exceed the MAXERUS (maximum external run-units) value, as specified in the SYSGEN.

The following possible causes, you can do.

1. This means the system is very busy now (or having sever problems like example given in third point ) and you should be able to just re-run the job again in a few minutes.

2. Or you can get the help from DBA

i.e. The DBA’s may need to change MAXERUS (maximum
external run units) in the SYSGEN.

3. Other than an abnormally busy system, here is an example that can cause the system to be “busy”. You have a batch job
running in protected update. Online transactions are trying to access the same area, so they go into a WAIT state (up to the number of seconds specified in the external wait time). So instead of finishing in 1 or 2 seconds, the stay in a WAIT state for 1 to 20 minutes. New transactions come in, and they try to access the area, and go into a wait state. So in a matter of minutes, you have 70 online tasks all active - but in a WAIT
state. If your MAXERUS is set to 70 - you have reached it - and all new income transactions will ABEND with a 1473.
Back to top
View user's profile Send private message
shankarm

Active User


Joined: 17 May 2010
Posts: 175
Location: India

PostPosted: Tue Jul 06, 2010 9:50 am    Post subject:
Reply with quote

thanks Meenakshi.
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 -> IDMS/ADSO All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. Cobol GUI (like Editor) Kala Mainframe COBOL Programming 14 Wed May 10, 2017 12:30 pm
No new posts IMS T-Pipe queue counts in a COBOL Pr... Siva NKK Kothamasu IMS DB/DC 0 Tue May 09, 2017 6:31 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 COBOL Programming Sandpit? jodrisco COBOL Programming 6 Wed Apr 12, 2017 3:47 am


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