|
View previous topic :: View next topic
|
| Author |
Message |
Slade2000
New User
Joined: 06 Apr 2010
Posts: 4
Location: South Africa
|
|
|
|
We are testing at our DRP(Disaster recovery) site. We do have a identical copy of what we have at the office. we did a restore this side but one of our jobs abend with a, code=0c4 reason code=00000010, no active module found, on a specific vsam file.
What can this reason maybe be? |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
S0C4 is protection exception. Perhaps your "identical copy" is not so identical?
How did you create the "identical copy"? How did you verify that it is identical? With a typical site having hundreds of disk packs, it would be a very long and time-consuming process to verify that the DR system was identical to the original system. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
You could review the job-step where the S0C4 occurred and then look at the invoked program and if the invoked program called any sub-program(s), their presence (as well as the caller's) needs to be ensured.
Then check the job/step target loadlib(s) and make sure all these load modules (programs) are present.
Welcome to the trials and tribulations of DR. 
That's about it....
Bill |
|
| Back to top |
|
|
Slade2000
New User
Joined: 06 Apr 2010
Posts: 4
Location: South Africa
|
|
|
|
| All sub programs are fine did test them and they work fine. we now wil try a ipl and make sure all our lode modules are fine. |
|
| Back to top |
|
|
Slade2000
New User
Joined: 06 Apr 2010
Posts: 4
Location: South Africa
|
|
|
|
| Quote: |
| S0C4 is protection exception. |
Can this be on hadware side maybe? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Wanting the S0C4 to be hardware-related is wishful thinking. The manual says for S0C4-10:
| Quote: |
10
Segment-translation exception. This error is caused by one of the following:
* A program that was running disabled attempted to reference storage while the page table for that storage was paged out. To correct the error, page-fix the storage before a program running disabled attempts to reference it.
* A program attempted to reference storage that had not been obtained. To correct the error, allocate the storage before attempting to reference it.
* A program running in a subspace attempted to reference storage that was not accessible to the subspace at the time of error. To correct the error, ensure that the program running in a subspace references only the storage assigned to that subspace, or storage that can be referenced by all subspaces. |
You can ask your site support group to look at the need to page-fix storage (but this is not a likely cause), or to look at subspace storage (again not a likely cause) but once they come back and tell you everything is fine, you'll still have to look at the S0C4.
Have you talked to your site support group about verifying the DR system is "identical" to the original system? If not, that is the first place to start -- because unless your original system is down, the original and DR systems cannot be "identical" (for example, the IP addresses assigned in TCP/IP to the LPAR cannot be the same if your network accesses both of them). |
|
| Back to top |
|
|
Slade2000
New User
Joined: 06 Apr 2010
Posts: 4
Location: South Africa
|
|
|
|
We also think it is a link to the storage that was antecedently overwritten so after ipl we will see what happen. We did confirm everything is identical even our ip and all those are as well. there is no link between our Main site and DR site that is why all internal systems are identical only on router side that is different to the web.
Will let know what happened after ipl.
Tnx allot |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| but one of our jobs abend with a, code=0c4 |
Which job?
If this is a restore job, suggest you look at the output of the job that created the file(s) to be restored. . . |
|
| Back to top |
|
|
|
|
