|
View previous topic :: View next topic
|
| Author |
Message |
dinguduse
New User
Joined: 24 Jun 2005
Posts: 8
|
|
|
|
Hi all,
I am facing a problem now. One of my mainframe job fails with SOC4 error. Apparently, the job goes through fine when I restart the job after some time.
I got this error 5-6 times in last 3 months and every time the job will go to good EOJ when I restart.
Do any of you guys know /guess what could be the problem
The program is compiled with the below options. Will this could be the error?
AMODE(31) ,===>,N
DATA(31) ,===>,N
Thanks in advance for your help.
Regards, |
|
| Back to top |
|
 |
dinguduse
New User
Joined: 24 Jun 2005
Posts: 8
|
|
|
|
The SOC4 error, came with the reason code 11.
The manual says :
Page-translation exception. This error is caused by
one of the following:
o A program that was running disabled attempted to
reference storage while that storage was paged
out. To correct the error, page-fix the storage
before a program running disabled attempts to
reference it.
etc...etc
If any one can decently decode the above, it would be great !!
Thanks ! |
|
| Back to top |
|
|
HIRAKI81
New User
Joined: 17 Aug 2005
Posts: 5
|
|
|
|
Hi,
Pls add REGION = 4M or REGION = 8M in your job statement and try running it.
Regards, |
|
| Back to top |
|
|
dinguduse
New User
Joined: 24 Jun 2005
Posts: 8
|
|
|
|
Hi Ram,
Thanks for looking into.
My JCL is already coded with the parameter REGION=4096K.
The strange issue is, I was not able to simulate the error in test at all..
and in production, every time, yup, each and every time the job goes through fine when i restart !
Regards,
Aravind (Alias Dinguduse) |
|
| Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003
Posts: 1592
|
|
|
|
| Showing the JCL and the sysmsg re. the abend might help. |
|
| Back to top |
|
|
solid_18
New User
Joined: 11 Oct 2005
Posts: 2
Location: Manila, Philippines
|
|
|
|
| try with REGION=0M |
|
| Back to top |
|
|
mvanandkumar
New User
Joined: 01 Sep 2005
Posts: 11
|
|
|
|
Hi dinguduse
My 2 cents of advice....
If you are calling a program...then check the COMMAREA length....
If you calling program is RMODE/AMODE 24.....then it cannot call RMODE/AMODE 31 programs.....
What do you mean by - when you restart the program ? it works ?...restart from where ?  |
|
| Back to top |
|
|
samitcmathur
New User
Joined: 05 Feb 2006
Posts: 4
|
|
|
|
the region =4096??
the max region size is 2047000 KB
that could be the reason that you are getting error due to trying to access the memory you don't have the access for |
|
| Back to top |
|
|
samitcmathur
New User
Joined: 05 Feb 2006
Posts: 4
|
|
|
|
region = 2047000 KB
that could be the reason that you are getting the error due to accessing storage locations you don't have access to |
|
| Back to top |
|
|
souryab
New User
Joined: 23 May 2007
Posts: 10
Location: India
|
|
|
|
I got a similar problem. The options when compiling are DATA = 31 and RMODE = ANY. Will any changes to compilation solve the problem?
Also, REGION=OM is specified in Job. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
I got a similar problem. The options when compiling are DATA = 31 and RMODE = ANY. Will any changes to compilation solve the problem?
Also, REGION=OM is specified in Job. |
Does this fail every time or only in certain situations (like test/prod or daily/weekly, etc)?
As was mentioned earlier, posting the jcl and diagnostic info may help. Also, posting the select/assign/fd (not the entire record), may help.
For anyone who might not realize,
| Quote: |
| My JCL is already coded with the parameter REGION=4096K |
is the same as 4M. |
|
| Back to top |
|
|
|
|
