Skip to main content

We were getting 153 ("Subscript out of range") error during runtime with Cobol 6.0.5 we used the below compilation options.

-C SSRange=2
-C NoCheck
-C Bound

With Cobol migration to 7.0.6 we with the same set of compilation options we are not getting the 153 ("Subscript out of range") error. But when I remove the -C NoCheck I am getting the error.

Is there any changes implemented in NoCHECK , SSRANGE, BOUND directives of Cobol v7.0.6? 


#nativecobol
#MicroFocus
#VisualCOBOL
#COBOLENVIRONMENT
#MicroFocusVisualCobol
#debug

We were getting 153 ("Subscript out of range") error during runtime with Cobol 6.0.5 we used the below compilation options.

-C SSRange=2
-C NoCheck
-C Bound

With Cobol migration to 7.0.6 we with the same set of compilation options we are not getting the 153 ("Subscript out of range") error. But when I remove the -C NoCheck I am getting the error.

Is there any changes implemented in NoCHECK , SSRANGE, BOUND directives of Cobol v7.0.6? 


#nativecobol
#MicroFocus
#VisualCOBOL
#COBOLENVIRONMENT
#MicroFocusVisualCobol
#debug

Hi Vinoth,

The following was fixed in 7.0: "The NOBOUND directive specified after the SSRANGE option is now correctly respected"

It sounds like this might have affected the options that you are setting as well and that NOCHECK is overriding the BOUND directive by turning it off even though BOUND comes after NOCHECK.

Both SSRANGE and CHECK turns on BOUND automatically.
NOCHECK turns off all bounds checking in generated code.

If you would like us to investigate this further, please open up a support case for this issue.

Thanks


Hi Vinoth,

The following was fixed in 7.0: "The NOBOUND directive specified after the SSRANGE option is now correctly respected"

It sounds like this might have affected the options that you are setting as well and that NOCHECK is overriding the BOUND directive by turning it off even though BOUND comes after NOCHECK.

Both SSRANGE and CHECK turns on BOUND automatically.
NOCHECK turns off all bounds checking in generated code.

If you would like us to investigate this further, please open up a support case for this issue.

Thanks

Ok, Thanks, we will raise a support ticket.