II09208: CICS CUSTOMERS USING UPGRADE WITH NSR FILES

APAR status

• Closed as canceled.

Error description

• ***************************************************************
  *                                                             *
  * -SUBJECT OF INFO APAR-    LAST UPDATE: 01/24/96 BCB for DCM *
  *  CICS/ESA r4.1 customers using UPGRADE with NSR files       *
  *                                                             *
  ***************************************************************
  +-------------------------------------------------------------+
  |                                                             |
  | - DETAIL DISCUSSION OF PURPOSE FOR INFO APAR -              |
  | With transaction isolation, an abend0c4 may occur in vsam   |
  | when updating an NSR file that requires UPGRADE processing. |
  | When the UPGRADE table is released by an rpl request, vsam  |
  | may continue processing another rpl under the same subspace.|
  | The abend0c4 may occur attempting to modify storage owned   |
  | by that rpl when running under the same subspace.           |
  | To circumvent this problem, LSR should be specified to      |
  | ensure the synchronous only requests are made to vsam.      |
  |                                                             |
  |                                                             |
  |-------------------------------------------------------------|
  |                                                             |
  | - ADDITIONAL REFERENCES - OW16189                           |
  |-------------------------------------------------------------|
  |                                                             |
  | -TECHNICAL INFORMATION -                                    |
  | NSR requests are asynchronous. We have found vsam may not   |
  | always schedule an IRB (which runs under base space) to     |
  | restart an asynchronous request when the UPGRADE table      |
  | becomes free. Since vsam does not switch subspaces, an      |
  | rpl may be resumed under the wrong subspace. When data is   |
  | validly moved into the area owned by that task, the         |
  | abend0c4 occurs because we are in the wrong subspace.       |
  | This problem can also occur on VSAM datasets when an        |
  | exclusive control error is encountered and VSAM needs to    |
  | update the RPL message area (RPLERMSA) with the request that|
  | is causing the conflict. So, this problem can occur for     |
  | tasks that do not have alternate index processing involved. |
  
  
  
  
  
  
  |-------------------------------------------------------------|
  |                                                             |
  | -IF THERE ARE ANY SUGGESTIONS TO IMPROVE THIS INFORMATIONAL |
  |    APAR, PLEASE SUBMIT A PROBLEM RECORD TO CICS LEVEL 2     |
  |           USING THE APPROPRIATE COMPONENT ID.               |
  |                                                             |
  |             WE APPRECIATE YOUR SUGGESTIONS.                 |
  |                                                             |
  |-------------------------------------------------------------|
  |                                                             |
  | KEYWORDS: CICS CICSINFO RALINFO                             |
  |                                                             |
  |                **** CICS/OS/MVS/ESA ****                    |
  | DESCRIPTION                    COMPID    FESN    REL        |
  | CICS/ESA         4.1.0         565501800 0566091  100       |
  |                  410 R410      565514700          200       |
  |                  R510 R520     5697E9300          300       |
  |                  R530 R210     5655M1500          400       |
  |                  R400 R500                        500       |
  |-------------------------------------------------------------|
  | END OF INFO                                                 |
  +-------------------------------------------------------------+
  NOTE: Upgrade processing does not have to be active to receive
  ABEND0C4 in VSAM csects. For instance, users may experience
  ABEND0C4 in IDA019R4 when VSAM moves the record area into
  the RPLAREA (VSWAREA) with a MVCL when there is no alternate
  index or path processing.
    Abend0c4 IDA019RA PIC4 during MVC from RPL +24 ( RPLARG )
  to PLHKEY.  NSR ASYNCHRONOUS TRansaction ISOLATION = YES
    Note also that an abend may be seen in VSAM module IDA019RM,
  due to the same underlying problem of NSR and transaction
  isolation.
    Isolate transiso traniso.
  It should be emphasized that transaction isolation and NSR
  can result in this problem occurring. Use of TRANISO for
  only some transactions (that don't use NSR files) will not
  guarantee the problem will not be seen, since VSAM can still
  asynchronously process work for an ISOLATE(YES) task during
  work for an ISOLATE(NO) task.
  Additional Keywords: PM07304 IDA019L1
  DFHFC0001 Abend0C4 at offset FFFF in DFHFCVR.  FFFFFFFF
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Close INFO APAR CAN
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels