File Status 9/161 when opening a file with CALL 'EXTFH'

[Migrated content. Thread originally posted on 04 February 2011]

In order to bind ISAM data to ADO controls, we have set up a trial project in Visual Cobol R3 that uses the Microfocus File Handler (we also use this in our NetExpress 4.0 projects).
Opening a file with call 'EXTFH' returns a file status 9/161 (something wrong with the file header?).
When running the same code in NetExpress, this returns a file status zero (which is ok).
Does someone know what might be the solution to this problem?
Parents
  • You mention in your earlier post that you are trying to bind file data to ADO.
    Does this mean that you are compiling your file handler code as managed instead of native?

    If this is true then you cannot use the NOFCD3 directive as FCD3 is required for managed code regardless of whether you are compiling for x86 or x64.

    This is from the Visual COBOL documentation:

    COBOL Development System FCD Used

    Mainframe Express FCD2
    32-bit Visual COBOL FCD2
    64-bit Visual COBOL FCD3
    .NET Support within Visual COBOL FCD3
    32-bit Server Express FCD2 or FCD3
    64-bit Server Express FCD3


Reply
  • You mention in your earlier post that you are trying to bind file data to ADO.
    Does this mean that you are compiling your file handler code as managed instead of native?

    If this is true then you cannot use the NOFCD3 directive as FCD3 is required for managed code regardless of whether you are compiling for x86 or x64.

    This is from the Visual COBOL documentation:

    COBOL Development System FCD Used

    Mainframe Express FCD2
    32-bit Visual COBOL FCD2
    64-bit Visual COBOL FCD3
    .NET Support within Visual COBOL FCD3
    32-bit Server Express FCD2 or FCD3
    64-bit Server Express FCD3


Children
No Data