Skip to main content

Call-By-Name (CBL_) library and managed code

  • March 2, 2016
  • 2 replies
  • 0 views
A
  • Anonymous
Is the Call-By-Name library available in managed code? Do the calls provide the same functionality? We have a "utility" native COBOL DLL program that uses several file handling CBL_ calls; CBL_CHECK_FILE_EXIST, CBL_COPY_FILE, etc. We are attempting to convert this program to managed code and during execution we are getting "file not found" errors. We use dd_xxx-style environment variables to define data file paths and "xxx\\filename"-style file references in SELECT clauses. In the current test-subject solution an ASPX program calls a converted COBOL DLL that creates a "CNV\\WYP46D01.098" on the path specified by the value of dd_CNV, but the converted "utility" COBOL DLL called by the ASPX program immediately after gets "file not found" (9/13) returned from CBL_CHECK_FILE_EXIST when the filename parameter contains the same "CNV\\WYP46D01.098" value as the SELECT clause in the first COBOL DLL?

    2 replies

    Chris Glazier
    Forum|alt.badge.img+2
    Is the Call-By-Name library available in managed code? Do the calls provide the same functionality? We have a "utility" native COBOL DLL program that uses several file handling CBL_ calls; CBL_CHECK_FILE_EXIST, CBL_COPY_FILE, etc. We are attempting to convert this program to managed code and during execution we are getting "file not found" errors. We use dd_xxx-style environment variables to define data file paths and "xxx\\filename"-style file references in SELECT clauses. In the current test-subject solution an ASPX program calls a converted COBOL DLL that creates a "CNV\\WYP46D01.098" on the path specified by the value of dd_CNV, but the converted "utility" COBOL DLL called by the ASPX program immediately after gets "file not found" (9/13) returned from CBL_CHECK_FILE_EXIST when the filename parameter contains the same "CNV\\WYP46D01.098" value as the SELECT clause in the first COBOL DLL?

    Hi Don,

    I just tested this here and there does appear to be a compatibility issue in the library routines when dealing with embedded dd_ names. In native code this works as expected but in managed code they are not being expanded.

    Please open up a support incident with Customer Care and add my name to the description so that it comes to me. I will then create a bug report for this,

    Thanks.

    A
    • Anonymous
    • March 2, 2016
    Is the Call-By-Name library available in managed code? Do the calls provide the same functionality? We have a "utility" native COBOL DLL program that uses several file handling CBL_ calls; CBL_CHECK_FILE_EXIST, CBL_COPY_FILE, etc. We are attempting to convert this program to managed code and during execution we are getting "file not found" errors. We use dd_xxx-style environment variables to define data file paths and "xxx\\filename"-style file references in SELECT clauses. In the current test-subject solution an ASPX program calls a converted COBOL DLL that creates a "CNV\\WYP46D01.098" on the path specified by the value of dd_CNV, but the converted "utility" COBOL DLL called by the ASPX program immediately after gets "file not found" (9/13) returned from CBL_CHECK_FILE_EXIST when the filename parameter contains the same "CNV\\WYP46D01.098" value as the SELECT clause in the first COBOL DLL?

    Micro Focus SupportLine incident 2855891 has been created for this issue.  As instructed I have referenced you by name in both the Subject field and in the step-by-step field.

    Thank you!

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement