CA Repository for z/os 7.2 1 CA RS 1511 Service List Release Service Description Type 7.2 RO85297 CONVERT SOC7 IN COBOL SCAN TO RC=12 PTF RO85308 CORRELATION ID ON SQL COLUMNS PTF RO85459 RESOLVING PROBLEM FOR RO70097, RO58507 AND RO83227 PTF The CA RS 1511 service count for this release is 3
CA Repository for z/os 2 CA RS 1511 Service List for CNW7200 FMID Service Description Type CNW7200 RO85308 CORRELATION ID ON SQL COLUMNS PTF RO85459 RESOLVING PROBLEM FOR RO70097, RO58507 AND RO83227 PTF The CA RS 1511 service count for this FMID is 2
CA Repository for z/os 3 CA RS 1511 Service List for CP$7200 FMID Service Description Type CP$7200 RO85297 CONVERT SOC7 IN COBOL SCAN TO RC=12 PTF The CA RS 1511 service count for this FMID is 1
CA Repository for z/os 7.2 4 CA RS 1511 - PTF RO85297 Release Service 7.2 RO85297 RO85297 M.C.S. ENTRIES = ++PTF (RO85297) DESC (CONVERT SOC7 IN COBOL SCAN TO RC=12) /*------------------------------------------------------------------- PRODUCT: CA Repository for z/os RELEASE: 7.2 DATE: 6 OCT 2015 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XSC PROBLEM NUMBER: 107 CONVERT SOC7 IN COBOL SCAN TO RC=12 The COBOL scanner, MSCANDB2 (SCAN1), abends with a S0C7 when it encounters a program listing that does not contain an IDENTIFICATION DIVISION or a DATA DIVISION. Customer has requested that the response be changed to a RC=12 and a message. A scan of a COBOL "program" that does not contain an IDENTIFICATION DIVISION ends with a: CEE3207S The system detected a data exception (System Completion Code=0C7). The S0C7 is reported as a system failure, even though this is a normal situation at some customers sites. Request is to convert the abend to a RC=12. PRODUCT(S) AFFECTED: CA Repository for z/os Release 7.2 CA Repository Exchange for COBOL Release 7.2 -------------------------------------------------------------------*/. ++VER (Z038) FMID(CP$7200) SUP (T54R645).
CA Repository for z/os 7.2 5 CA RS 1511 - PTF RO85308 Release Service 7.2 RO85308 RO85308 M.C.S. ENTRIES = ++PTF (RO85308) DESC (CORRELATION ID ON SQL COLUMNS) /*------------------------------------------------------------------- PRODUCT: CA Repository Exchange for COBOL RELEASE: 7.2 DATE: 6 OCT 2015 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XSC PROBLEM NUMBER: 103 CORRELATION ID ON SQL COLUMNS The CORRELATION ID is not being resolved into the correct TABLE name when the CORRELATION ID is used in a sub-query (a SELECT within a WHERE clause, for instance). A COBOL program that contains an SQL EXEC which uses a Correlation Id instead of the Table Name in a sub-query, such as: SELECT DISTINCT B.DPOS_CDE FROM CCVEV01T A, CEDPR01T B WHERE A.CUST_ID_NBR = :WS-CUST-ID-NBR AND NOT EXISTS ( SELECT D.DPOS_CDE <<<<<<< FROM CCVEV01T C, CEDPR01T D WHERE C.CUST_PRT_NBR = :WS-CUST-PRT-NBR will get an incorrect intermediate SQL output file from the SCAN1 program, which will in turn cause the DBXSCNC load program to get the message THE COLUMN "DPOS_CDE" COLUMN of "DB2P.PROD.CCVEV01T" WAS NOT FOUND. The PRG DB2 relationship between the Column and the Program is not created in the Repository. none. PRODUCT(S) AFFECTED: CA Repository Exchange for COBOL Release 7.2 -------------------------------------------------------------------*/. ++VER (Z038) FMID(CNW7200) PRE (RO85297) SUP (T54R647,T54R412,T54R231,T54R181,T54R148,T54R068, T54R016,RO58240,RO70096,T54R404,RO57536,T5QV182, T5QV106,RO26865,RO30379,RO58507,RO56794,T5QV998, T5QV101,RO26994,RO64650,RO65311,T5QV576,RO44218, RO55369,T5QV970,AR48152,T5QV590,T54R029,T54R058, T54R207,RO70097,RO60101,RO61368,RO44941,RO48152, T5QV647,RO50702,T5QV822,T5QV922,RO73111,RO73304, RO77103,RO83227,AO70097,AR58507,AR83227,RO85459, AR70097).
CA Repository for z/os 7.2 6 CA RS 1511 - PTF RO85459 Release Service 7.2 RO85459 RO85459 M.C.S. ENTRIES = ++PTF (RO85459) DESC (RESOLVING PROBLEM FOR RO70097, RO58507 AND RO83227) /*------------------------------------------------------------------- PRODUCT: CA Repository Exchange for COBOL RELEASE: 7.2 DATE: 9 OCT 2015 HYPER: NO STARTRAK PROBLEM PRODUCT NAME: XSC PROBLEM NUMBER: 109 RESOLVING PROBLEM FOR RO70097, RO58507 AND RO83227 RO70097 (XSC 97) introduced a problem where PRG DATA relations were formed with incorrect paragraph names. The problem was propagated to RO73111 (XSC 99), RO73304 (XSC 100) and RO77103 (XSC 101). In addition, certain COBOL listings, for instance those containing the keyword SKIP3, have been found to go into an infinite loop, requiring that the program be cancelled This solution corrects the looping problem, as well as the PRG DATA relations with incorrect paragraph names introduced by RO70097 (XSC 097), and also incorporates corrected solutions for RO73111 (XSC 99), RO73304 (XSC 100) and RO77103 (XSC 101). It is also the resolving fix for RO58507 (XSC 91) and RO83227 (XSC 104 and XSC 102) which had an SMP/e MASS MODE problem. The descriptions of all these fixes (in reverse order) are listed below: (XSC 104,RO83227) Certain COBOL listing, for instance ones that contain SKIP3, can go into an infinite loop and the scan job has to be cancelled. The SCAN1 job simple does not end. No error messages are produced. The associated listing simply cannot be scanned into the Repository. (XSC 102) The COBOL scanner, MSCANDB2 (SCAN1), is incorrectly outputting the REFER and REFERSUM output files. The REFER-PARAGRAPH values are not correct for any COBOL listing. The Paragraph Name on the PRG DATA relationships which are formed from the metadata in these files is incorrect. The PRG DATA relationship will be formed with a Paragraph Name that is certainly incorrect and probably not even a paragraph name. (XSC 101, RO77103) The COBOL scanner, MSCANDB2 (SCAN1), does not recognize that identifiers defined in an SQL cursor statement do not define columns. It therefore treats them as columns, and makes a corresponding entry in the SQL output file as a column. This results in a "COLUMN" not found error message and a RC=04. A COBOL program containing (for example): EXEC SQL DECLARE C3_ROLE CURSOR FOR SELECT ROLES.DIRECTORY_ID,
CA Repository for z/os 7.2 7 CA RS 1511 - PTF RO85459 Release Service ROLES.PRODUCT_CODE, ROLES.ROLE_SEQUENCE, SUBSTR(ADDRX.ADDRESS_LINE_5,31,2) STATE_CODE <<< FROM ADDRX JOIN ROLES ON ADDRX.DIRECTORY_ID = ROLES.DIRECTORY_ID - Will add STATE_CODE to the SQL output file. When run into the subsequent load step this will result in the message: Error: THE COLUMN "STATE_CODE" OF TABLE "DB2P.PJ1P.ADDRX" WAS NOT FOUND. A COBOL program containing a cursor with an implicit define cannot be scanned into the Repository without generating warning messages. (XSC 100, RO73304) The COBOL scanner, MSCANDB2 (SCAN1), does not recognize the DB2 function TIMESTAMP_FORMAT and treats it as a column name. This results in a "COLUMN" not found error message and a RC=04. A COBOL program containing (for example): *****EXEC SQL ***** SELECT * ***** FROM QEPUL01T ***** WHERE (DATE(CRET_TMSP) < ***** DATE(TIMESTAMP_FORMAT(:WK-CURR-CYC-DATE,'DDMMYYYY')) will get the message: THE COLUMN "TIMESTAMP_FORMAT" OF TABLE "PROD.QEPUL01T" WAS NOT FOUND. A COBOL program containing the function TIMESTAMP_FORMAT cannot be scanned into the Repository without warnings. (XSC 99, RO73111) The COBOL scanner, MSCANDB2 (SCAN1), does not always ignore SQL INCLUDE statements which have been "commented out " by the programmer This results in a PRG COPY relationship which should not be created. A COBOL program containing (for example): CR0512* EXEC SQL CR0512* INCLUDE COPYBOOK CR0512* END-EXEC. Will create an entry PROGRAMCOPYBOOK (where PROGRAM is the name of the PROGRAM), in the COPY output file. A PRG COPY association will be created between the program "PROGRAM"and the copybook "COPYBOOK". (XSC 97, RO70097) The CA Repository COBOL scanner, MSCANDB2, does not correctly scan listings that are produced by the Serena Changeman(R) code manager. In particular, when a DCLGEN is introduced via a COPYBOOK, the copybook name will be used in the RECORD name, instead of the actual 01 Record name. When a program contains a COPY ESAIDTBL statement, and the
Release Service CA Repository for z/os 7.2 8 CA RS 1511 - PTF RO85459 copy book contains a DCLGEN, such as EXEC SQL DECLARE M0B.TB097_PROG_SERV_USER_MAP TABLE ( APPL_PROG_ID CHAR(8) NOT NULL,... ) END-EXEC. The REFER file will be produced with ESAIDTBL as the 01 Record name instead of DCLTB097-PROG-SERV-USER-MAP. A COBOL program containing a DCLGEN copybook will not scan properly into the Repository (XSC 91, RO58507) The COBOL scanner, MSCANDB2, does not recognize the reserved word "POSITION". This results in a "COLUMN" not found error message and a RC=04 for the step when processing any COBOL program that contains this particular reserved word. A COBOL program containing (for example): EXEC SQL DECLARE CURCLAIM CURSOR FOR SELECT CLM_RPT_NBR, CLM_NBR_ID_CODE, CNTRCT_NBR, CLM_TERMIN_RSN_CDE, CUST_ID_NBR FROM CLAIM01T WHERE CUST_ID_NBR = :WS-CUST-ID-NBR ORDER BY POSITION <<<<<<<<<<<<<<< (CLM_NBR_ID_CODE,'MS LTCPW DI HC ',OCTETS), CLM_RPT_NBR DESC, CNTRCT_NBR ASC, CLM_TERMIN_RSN_CDE ASC will get the message: THE COLUMN "POSITION" OF TABLE "<creator>.claim01t" WAS NOT FOUND. A COBOL program containing the reserved word (FUNCTION) "POSITION" cannot be scanned into the Repository because the Repository is treating the reserved word as a DB2 column name and generating a warning message "THE COLUMN "POSITION" OF TABLE "XXXXXXX.CLAIM01T" WAS NOT FOUND." PRODUCT(S) AFFECTED: CA Repository Exchange for COBOL Release 7.2 -------------------------------------------------------------------*/. ++VER (Z038) FMID(CNW7200) PRE (RO85297) SUP (T54R662,T54R412,T54R231,T54R181,T54R148,T54R068, T54R016,RO58240,RO70096,T54R404,RO57536,T5QV182, T5QV106,RO26865,RO30379,RO58507,RO56794,T5QV998, T5QV101,RO26994,RO64650,RO65311,T5QV576,RO44218, RO55369,T5QV970,AR48152,T5QV590,T54R029,T54R058, T54R207,RO70097,RO60101,RO61368,RO44941,RO48152, T5QV647,RO50702,T5QV822,T5QV922,RO73111,RO73304, RO77103,RO83227,AO70097,AR58507,AR83227,T54R647, AR70097).