Re: COBOL Migration v4 to v6.1 - CONDITIONS OF INITIALIZATION
Thanks, we have moved on by identifying the groups with the issue and dealing with them. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Ross Sent: Friday, November 08, 2019 12:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: COBOL Migration v4 to v6.1 - CONDITIONS OF INITIALIZATION >Since migrating from COBOL v4 to COBOL v6.1 a few runtime abends have occur= >red which seem to have a root cause of data items not being initialized. = >These data-items seem to be under a group level where the group level >is in= itialized. >The compile's diagnostic errors listing shows al warning messages of: >IGYPS2047-W "INITIALIZE" STATEMENT OPERAND DID NOT MEET CON= >DITIONS FOR INITIALIZATION WAS NOT INITIALIZED. Sorry to be so late on this... Could you post the description of the group item and the INITIALIZE statement? It would appear that none of the items under the group were of a type that could be initialized, but I would like to take a look, if you have not already moved on frmo this problem! Also, I would be surprised if the behavior of COBOL V4 was different from COBOL V6, I do not think that have not changed this code in the compiler! Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
COBOL Migration v4 to v6.1 - CONDITIONS OF INITIALIZATION
>Since migrating from COBOL v4 to COBOL v6.1 a few runtime abends have occur= >red which seem to have a root cause of data items not being initialized. = >These data-items seem to be under a group level where the group level is in= >itialized. >The compile's diagnostic errors listing shows al warning messages of: >IGYPS2047-W "INITIALIZE" STATEMENT OPERAND DID NOT MEET CON= >DITIONS FOR INITIALIZATION WAS NOT INITIALIZED. Sorry to be so late on this... Could you post the description of the group item and the INITIALIZE statement? It would appear that none of the items under the group were of a type that could be initialized, but I would like to take a look, if you have not already moved on frmo this problem! Also, I would be surprised if the behavior of COBOL V4 was different from COBOL V6, I do not think that have not changed this code in the compiler! Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
COBOL Migration v4 to v6.1 - CONDITIONS OF INITIALIZATION
Since migrating from COBOL v4 to COBOL v6.1 a few runtime abends have occurred which seem to have a root cause of data items not being initialized. These data-items seem to be under a group level where the group level is initialized. The compile's diagnostic errors listing shows al warning messages of: IGYPS2047-W "INITIALIZE" STATEMENT OPERAND DID NOT MEET CONDITIONS FOR INITIALIZATION WAS NOT INITIALIZED. Our Quick Ref did not have info on this message but I did find one mention of it in both the v6.1 migration and customization guide. However the text of the message was completely different and referred to the ALPHA parm. IGYPS2047-W "INITIALIZE" statement receiver "ALPHA" was incompatible with the data category(s) of the "REPLACING" operand(s). "ALPHA" was not initialized. Does anyone have insights on what the term "CONDITIONS FOR INITIZATION" refers to and what these conditions are? This might help us determine why some data-items do not meet these condition under its group level. Bill __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
