CA Datacom VSAM Transparency 14.0 CA RS 1403 Service List Release 14.0 Service RO63523 1 Description Hiper SA03 ABEND AT EOP IF FILES ARE NOT CLOSED The CA RS 1403 service count for this release is 1 CA Datacom VSAM Transparency CA RS 1403 Service List for CABGE00 FMID CABGE00 Service RO63523 2 Description Hiper SA03 ABEND AT EOP IF FILES ARE NOT CLOSED The CA RS 1403 service count for this FMID is 1 CA Datacom VSAM Transparency 14.0 CA RS 1403 - PTF RO63523 Details Release Service 14.0 RO63523 RO63523 M.C.S. ENTRIES Details = ++PTF (RO63523) SA03 ABEND AT EOP IF FILES ARE NOT CLOSED PROBLEM DESCRIPTION: Batch application programs that do not CLOSE CA Datacom VSAM Transparency (DBVT) files before ending normally, i.e. returning to z/OS, experience abend SA03. The SA03 abend will cause transaction backout to occur if specified in the VSAM Interface Table (VIT). On first OPEN, CA Datacom/DB (DB) attaches a subtask to the application to prevent z/OS controlled time-outs, for instance during long exclusive control WAITs. This subtask is detached at last CLOSE. If the subtask is still attached at end of program, z/OS abends the application with code SA03. This solution provides auto-close processing at end of program similar to native VSAM. For this solution to take effect, at least one of the DBVT subsystem DD statements in the job step must specify CLOSE=DEFER. Auto-close is not performed if the application abends before returning to z/OS. SYMPTOMS: Application programs abend with code SA03 at normal end, i.e. when returning to z/OS. DB performs transaction backout if specified in the VIT. IMPACT: DBVT applications that do not close their DBVT files encounter SA03 abends. Since the application has ended successfully, the abends are merely unneccessary overhead, unless the VIT specifies transaction backout. In that case all maintenance to rows in the DBVT files is backed out. CIRCUMVENTION: Closing DBVT files before returning to z/OS not only circumvents the problem, it is strongly recommended if possible. PRODUCT(S) AFFECTED: CA Datacom VSAM Transparency Release 14.0 Star Problem(s): DBVT 314 Copyright (C) 2013 CA. All rights reserved. R00012-DCV140-SP1 DESC(SA03 ABEND AT EOP IF FILES ARE NOT CLOSED) . ++VER (Z038) FMID (CABGE00) PRE ( RO58341 ) SUP ( TR63523 ) ++HOLD (RO63523) SYSTEM FMID(CABGE00) REASON (ACTION ) DATE (13284) COMMENT ( PRODUCT: CA DATACOM VSAM TRANSPARENCY RELEASE 14.0 SEQUENCE: IN ORDER FOR THE SOLUTION TO TAKE EFFECT, THE DBVT SUBSYSTEM must be re-initialized. Purpose: The DBVT subsystem modules need to be replaced with the updated solution copies in memory. Relevance: The solution does not take effect until the subsystem and the subsystem modules have been replaced. Knowledge required: 1. DBVT product administration 2. SMP/E 3. z/OS Systems Programming Access required: Product libraries Steps to Perform: When using CAIRIM: If no DBVT subsystem currently exists, follow the instructions in the Installation Guide to install the DBVT subsystem after applying the solution to the DBVT product libraries (see INSTJCL sample member BGRIM01). If a version 14.0 subsystem already exists, follow the instructions in the Installation Guide to install a new subsystem with a new 3 CA Datacom VSAM Transparency 14.0 CA RS 1403 - PTF RO63523 Details Release Service Details name and a new suffix (see INSTJCL member BGRIM01). Verify the solution with the new subsystem. Then switch to the new subsystem by deleting the old subsystem and re-installing it with the same name, but using a suffix different from all previously used suffixes (since the last IPL) and pointing the LOADLIB to the one with the solution applied (see sample INSTJCL member BGTRN01). ). 4
© Copyright 2024 ExpyDoc
