CA Repository for z/os CA RS 1412 Service List

Transcription

1 CA Repository for z/os CA RS 1412 Service List Release Service Description Type 7.2 RO74584 SOURCE CPYBK NAME BLANK ON COPYCOPY RELATIONSHIP PTF RO75485 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 PTF RO75486 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 PTF RO75952 ABEND S000 U4038 ONCODE=520 SUBSCRIPT RANGE ON COPYIN PTF The CA RS 1412 service count for this release is 4

2 CA Repository for z/os 2 CA RS 1412 Service List for COH7200 FMID Service Description Type COH7200 RO75486 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 PTF The CA RS 1412 service count for this FMID is 1

3 CA Repository for z/os 3 CA RS 1412 Service List for CP$7200 FMID Service Description Type CP$7200 RO74584 SOURCE CPYBK NAME BLANK ON COPYCOPY RELATIONSHIP PTF RO75485 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 PTF RO75952 ABEND S000 U4038 ONCODE=520 SUBSCRIPT RANGE ON COPYIN PTF The CA RS 1412 service count for this FMID is 3

4 CA Repository for z/os CA RS PTF RO74584 Release Service 7.2 RO74584 RO74584 M.C.S. ENTRIES = ++PTF (RO74584) DESC (SOURCE CPYBK NAME BLANK ON COPYCOPY RELATIONSHIP) /* PRODUCT: CA Repository for z/os RELEASE: 7.2 DATE: 8 OCT 2014 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XTR PROBLEM NUMBER: 762 SOURCE CPYBK NAME BLANK ON COPYCOPY RELATIONSHIP When importing a copybook which itself calls in another copybook, either with a COPY stmt, or an -INC stmt, the copycopy relation which will be created between the source copybook and the included (target) copybook, should have a name formed as: <s.copybook_name>.<t.copybook_name> but in most cases this will actually come out as <blank>.<t.copybook_name> SYMPTOMS: After running the DBXRCIN (COPYIN) program on a copybook which has statements like: COPY ARC9GRPC. COPY ARC9RQDC. COPY ARC9RQSC. the NAME of the generated COPYCOPY relations will come out with a blank source copybook name. If you navigate to VD: SYSTEM, VT: COPYBOOK, select the copybook you scanned in, and do a GOTO COPYCOPY, you will see: SIZE CURRENT DIALOG: SYSTEM ENTITY TYPE: COPYCOPY FILE EDIT VIEW OPTIONS S/T: NAME: COPYCOPY NAME ARC9GRPC 2..ARC9RQDC 3..ARC9RQSC and if you query the underlying table, you will likewise see: select * from RZOZ722.DBX_DDL_COPYCOPY where status = 'TFSCPYIF'; ENT_ID NAME ARC9GRPC ARC9RQDC ARC9RQSC IMPACT: The Repository metadata for the name of the COPYCOPY relationship is incorrect. CIRCUMVENTION: If you hit Enter with the screen as shown above, the screen map will reconstruct the relationship name from the map definition, which will be correct. So the screen will become: SIZE CURRENT DIALOG: SYSTEM ENTITY TYPE: COPYCOPY FILE EDIT VIEW OPTIONS SYSTEM PR S/T: NAME: COPYCOPY NAME ARCIF109.ARC9GRPC 2. ARCIF109.ARC9RQDC 3. ARCIF109.ARC9RQSC Where ARCIF109 is the name of the copybook you originally scanned in. However, the table will still be incorrect. If you now SELECT the lines which have blank source names or use TAG to SELECT all of them, and then do an EDIT/UPDATE to update the SELECTed lines, the table will be

5 Release Service CA Repository for z/os CA RS PTF RO74584 updated with what is showing on the screen, and the problem will be solved for the lines in question. This procedure would have to be repeated for each copybook, or group of copybooks, affected. However, it could be used on selected lines which were already correct without causing any harm. Products Affected: CA Repository for z/os r */. ++VER (Z038) FMID(CP$7200) SUP (T54R403,RO38712,T5QV260). ++HOLD(RO74584) SYSTEM REASON(DB2BIND) FMID(CP$7200) COMMENT( Product: CA Repository for z/os Release: 7.2 * Sequence: After Apply. * Purpose: DB2 Bind * Relevance: If you are applying the re-compiled module, you must bind the DBRM into the DB2 subsystem. Knowledge required: Bind procedures on relevant DB2 subsys. Access required: Bind authority on relevant DB2 subsys Steps to be performed: Once the SMP/e portion of the fix application is complete, the following instructions should be turned over to the DB2 DBA in charge of the repository for customization to your site's specific procedures. * Bind package DBXRCIN into the HOST system with the following parameters: DSN SYSTEM(SUBSYS) BIND PACKAGE(Collection name) - QUALIFIER(REPOSITORY QUAL) - MEMBER(DBXRCIN ) - LIBRARY('DBRMLIB') - VALIDATE(BIND) - DYNAMICRULES(BIND) - ISOLATION(CS) - ENCODING(EBCDIC) - EXPLAIN(NO) - FLAG(I) - RELEASE(COMMIT) - ACTION(REPLACE) - CURRENTDATA(NO) - ENABLE(DB2CALL,BATCH,CICS) END * Make the following substitutions for the values of the parameters so they conform to your site's environment. - subsys to the db2 subsystem - collection name to the repository package collection - repository qual to the repository owner. - dbrmlib to DBRM library that contains the DBRMs associated with the PTFs that are applied. ).

6 CA Repository for z/os CA RS PTF RO75485 Release Service 7.2 RO75485 RO75485 M.C.S. ENTRIES = ++PTF (RO75485) DESC (MSSQL EXCHANGE - SUPPORT FOR SERVER 2012) /* PRODUCT: CA Repository for z/os RELEASE: 7.2 DATE: 30 OCT 2014 STARTRAK PROBLEM PRODUCT NAME: XMSS PROBLEM NUMBER: 60 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 The error handling syntax in the provided script 'dbxmss.25' is not compatible with sql 2012 and above. Refer to RI75484 for corresponding documentation changes. SYMPTOMS: Running the provided script against sql 2012 will result in the following errors: Msg 102, Level 15, State 1, Procedure dbx_sync_table, Line 16 Incorrect syntax near '20001'. Msg 102, Level 15, State 1, Procedure dbx_sync_database, Line 13 Incorrect syntax near '20001'. IMPACT: Cannot run the provided script against SQL Server 2012 CIRCUMVENTION: Changing the current syntax (in 2 places) in DBXMSS.25 as follows corrects the errors. From: raiserror 'stored procedure dbx_sync_table cannot be run while in a transaction' To: raiserror (20001, 10, 1, 'stored procedure sp_dbx_sync_table cannot be run while in a transaction') and From: raiserror 'stored procedure dbx_sync_table cannot be run while in a transaction' To: raiserror (20001, 10, 1, 'stored procedure sp_dbx_sync_database cannot be run while in a transaction') PRODUCT(S) AFFECTED: CA Repository for z/os r */. ++VER (Z038) FMID(CP$7200) SUP (T54R480). ++IF FMID(COH7200) THEN REQ(RO75486). ++HOLD(RO75485) SYSTEM REASON(ACTION) FMID(CP$7200) COMMENT ( CA Repository for z/os Release: 7.2 SEQUENCE After Apply PURPOSE Install required Windows solution USERS All users AFFECTED KNOWLEDGE Windows Administartion REQUIRED ACCESS CA MS SQLServer Exchange 7.2 Installation REQUIRED directory

7 Release Service CA Repository for z/os CA RS PTF RO75485 * STEPS TO PERFORM * Install Windows solution RO75487 ).

8 CA Repository for z/os CA RS PTF RO75486 Release Service 7.2 RO75486 RO75486 M.C.S. ENTRIES = ++PTF (RO75486) DESC (MSSQL EXCHANGE - SUPPORT FOR SERVER 2012) /* PRODUCT: CA Repository Exchange for MS SQLServer RELEASE: 7.2 DATE: 30 OCT 2014 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XMSS PROBLEM NUMBER: 60 MSSQL EXCHANGE - SUPPORT FOR SERVER 2012 The error handling syntax in the provided script 'dbxmss.25' is not compatible with sql 2012 and above. Refer to RI75484 for corresponding documentation changes. SYMPTOMS: Running the provided script against sql 2012 will result in the following errors: Msg 102, Level 15, State 1, Procedure dbx_sync_table, Line 16 Incorrect syntax near '20001'. Msg 102, Level 15, State 1, Procedure dbx_sync_database, Line 13 Incorrect syntax near '20001'. IMPACT: Cannot run the provided script against SQL Server 2012 CIRCUMVENTION: Changing the current syntax (in 2 places) in DBXMSS.25 as follows corrects the errors. From: raiserror 'stored procedure dbx_sync_table cannot be run while in a transaction' To: raiserror (20001, 10, 1, 'stored procedure sp_dbx_sync_table cannot be run while in a transaction') and From: raiserror 'stored procedure dbx_sync_table cannot be run while in a transaction' To: raiserror (20001, 10, 1, 'stored procedure sp_dbx_sync_database cannot be run while in a transaction') PRODUCT(S) AFFECTED: CA Repository Exchange for MS SQL Server r */. ++VER (Z038) FMID(COH7200) SUP (T54R481,T5QV117,RO31180) REQ (RO31179). ++IF FMID(CP$7200) THEN REQ(RO75485). ++HOLD(RO75486) SYSTEM REASON(ACTION) FMID(COH7200) COMMENT ( CA Repository Exchange for MS SQLServer Release: 7.2 SEQUENCE After Apply PURPOSE Install required Windows solution USERS All users AFFECTED KNOWLEDGE Windows Administartion REQUIRED ACCESS CA MS SQLServer Exchange 7.2 Installation

9 Release Service CA Repository for z/os CA RS PTF RO75486 REQUIRED directory * STEPS TO PERFORM * Install Windows solution RO75487 ).

10 CA Repository for z/os CA RS PTF RO75952 Release Service 7.2 RO75952 RO75952 M.C.S. ENTRIES = ++PTF (RO75952) DESC (ABEND S000 U4038 ONCODE=520 SUBSCRIPT RANGE ON COPYIN) /* PRODUCT: CA Repository for z/os RELEASE: 7.2 DATE: 13 NOV 2014 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XTR PROBLEM NUMBER: 763 ABEND S000 U4038 ONCODE=520 SUBSCRIPT RANGE ON COPYIN When importing a copybook which contains a syntax error, the CA Repository copybook scanner (DBXRCIN) may very well receive a subscript range error (ONCODE 520). At current this results in receipt of an ABEND=S000 U4038 REASON= or an ENCLAVE error but the program should issue a return code of 8 and end normally. SYMPTOMS: After running the DBXRCIN (COPYIN) program on a copybook which has statements like: 05 MTHY-TRAILER-RECORD. 10 MTHY-TRL-HIGH-VALUES. PIC X(12). << invalid '.' 10 MTHY-TRL-CNTR PIC 9(11). the job will get: CAPE006E INTERNAL ABEND ENCOUNTERED IEF450I <jobname> COPYPRG - ABEND=S000 U4038 REASON= IMPACT: The COPYIN job ends with an abend, when it should end normally with an error code. CIRCUMVENTION: none. PRODUCTS AFFECTED: CA Repository for z/os r */. ++VER (Z038) FMID(CP$7200) SUP (T54R468,T54R403,RO38712,T5QV260,RO74584). ++HOLD(RO75952) SYSTEM REASON(DB2BIND) FMID(CP$7200) COMMENT( CA Repository for z/os r7.2 Release: 7.2 SEQUENCE After Apply PURPOSE Rebind DB2 objects because DBRMs have been changed. USERS All Users AFFECTED KNOWLEDGE Database Administration REQUIRED ACCESS Database update REQUIRED * STEPS TO PERFORM * Once the SMP/e portion of the fix application is complete, the following instructions should be turned over to the DB2 DBA in charge of the repository for customization to your site's specific procedures. Bind solution DBRMs DSN SYSTEM(SUBSYS) BIND PACKAGE(collection name) -

11 CA Repository for z/os CA RS PTF RO75952 Release Service QUALIFIER(repository qual) - MEMBER(DBXRCIN) - LIBRARY(DBRMLIB) - VALIDATE(BIND) - DYNAMICRULES(BIND) - ISOLATION(CS) - ENCODING(EBCDIC) - EXPLAIN(NO) - FLAG(I) - RELEASE(COMMIT) - ACTION(REPLACE) - CURRENTDATA(NO) - ENABLE(DB2CALL,BATCH,CICS) END Make the following substitutions for the values of the parameters so they conform to your site's environment. - subsys to the db2 host subsystem or db2 foreign subsystem - collection name to the repository package collection - repository qual to the repository owner. - dbrmlib to DBRM library that contains the DBRMs associated with the PTFs that are applied. ).