Brian Peterson wrote:
Sounds like you're not looking in IBMLink. APARs are generally released to the public web interfaces once the APAR has closed. OA25468 is open.
My speculation is that the feed from IBMLink to the public system is not continuous or automatic. They probably "copy" the APAR text from one system to another at APAR closure time. If this speculation is correct, the public system misses out on those not infrequent subtle updates that can come after APAR closure e.g., adding a new symptom. Perhaps someone at IBM can tell us exactly what their process is...
The description in the APAR text is actually a bit "muddled" as it sometimes uses the term "R2" to mean the "storage pointed to by R2". But, you can still grasp what's happening. If a picture is worth 1,000 words, a code snippet should be "golden". The code is _obviously_ compiler generated ... not hand written. It's doing "OC 0(1,R2),X'190'(R13)" to OR a byte of zeros from the work area pointed to by R13:
LIST 03D5BF28. ASID(X'009C') POSITION(X'+0556') LENGTH(X'1000') INSTRUCTION ASID(X'009C') ADDRESS(03D5C47E.) KEY(00) 03D5BF28 | 18F5 | LR R15,R5 03D5BF2A | 1EF4 | ALR R15,R4 03D5BF2C | 18E3 | LR R14,R3 03D5BF2E | 5EEF 0078 | AL R14,X'78'(R15) 03D5BF32 | 50E0 D140 | ST R14,X'140'(,R13) 03D5BF36 | 1823 | LR R2,R3 03D5BF38 | D600 2000 D190 | OC X'0'(X'1',R2),X'190'(R13) 03D5BF3E | 18F3 | LR R15,R3 03D5BF40 | 5EF0 B9F1 | AL R15,X'9F1'(,R11) 03D5BF44 | 54F0 BA09 | N R15,X'A09'(,R11) 03D5BF48 | 183F | LR R3,R15 03D5BF4A | 153E | CLR R3,R14 03D5BF4C | 47B0 C592 | BC X'B',X'592'(,R12) And here is the APAR text: APAR Identifier ...... OA25468 Last Changed ........ 08/06/12 ABEND0C4-4 IN IEWLFORK DUE TO STORAGE THAT IS PAGE PROTECTED. Symptom ...... AB ABEND0C4-4 Status ........... INTRAN Severity ................... 3 Date Closed ......... Component .......... 5752SCLDR Duplicate of ........ Reported Release ......... 740 Fixed Release ............ Component Name LOADER Special Notice Current Target Date .. Flags SCP ................... Platform ............ Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: Customer experiences Abend0C4-4 in IEWLFORK+566 at UA34041. IEWLFORK is touching the pages that represent module segments to make sure that they have been brought into storage so that USS will capture them correctly as it takes its storage snapshot for a fork. This abend occurs because the module segments are page protected. The customer was using REFRPROT parm in PROGxx which will page protect all refreshable modules and is a new parm as of z/OS 1.9. IEWLFORK is using an OC instruction to references this storage. This is a fetch and store instruction. It is OR'ing 1 byte from R2 with R13+190 and storing the result of that OR in R2. R2 contains the address of the beginning of the page protected module. R13+190 contains x'00'. Since the storage pointed to by R2 is page protected the OC instruction can not store the results of its OR'ing and we take the Abend0C4-4. This OC instruction is also being used at IEWLFORK+580 at UA34041. Verification Steps: 1. Check to see that the Abend0C4-4 occurs in IEWLFORK+566 at UA34041. If the customer's IEWLFORK is at a different level then bring up the module and find the OC instruction and see if the Abend0C4-4 occurred on that instruction. 2. The PSW key at the time of failure and the storage being referenced in R2 will be key 0. There will NOT be a key mismatch. 3. Review the dump to see if the address in R2 is page protected. If it is this APAR describes your problem. LOCAL FIX: 1. Refrain from using the PROGxx REFRPROT parm. if possible. 2. Re-link the affected module so it is not using the REFRESHABLE attribute. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
