Dialog System - Character Mode

About 6 years ago I had a query about using the DS in MF Cobol. I have had another try at using it based on this: https://www.microfocus.com/documentation/net-express/nx40/dcchar.htm

I set up the DS environment and, in a Windows Terminal, defined the Data Block as per the tutorial. However when I tried to Save the Screen set I received a message: "Error creating file".

So either I have an incorrect environment or DS is supposed only to be used in UNIX or DS is crippled since MF do not expect it to be used for any new developments.

I can understand the latter and that MF consider it a 'legacy' system. However if this is not the case i.e. it's not crippled, what might have caused the error?

I'm using DSChar contained within Visual COBOL.

  • 0  

      Did you start dsch.exe from a 32-bit Visual COBOL command prompt ? If you didn't it may be worth trying that. I ran the executable from a VC command prompt, created a data definition and saved the file without any problem.

    If that does not work for you can you tell us which version of Visual COBOL you are using and which version of Windows you are using? I tried VC 9.0 on Windows 10.

    Gael  

  • 0 in reply to   

    Gael

    I have opened a 32-bit VC command prompt and navigated to the DSChar\bin folder. DS loads after entering dsch.exe. I can define the Data Block however I get the message "Error creating file" when I try to save the screens set. This is exactly what happened in my earlier attempt as per my previous email.

    I'm using VC Personal Edition 8.0 on Windows 11 23H2.

  • Verified Answer

    +1   in reply to 

    I receive the same error IF I try to save the screenset to a folder which is under C:\Program Files(x86) such as dschar\bin because this is a protected folder. Try saving to another location, which is not under C:\program files\(x86) such as C:\myDS.

    Chris Glazier
    Rocket Software - Principal Technical Support Specialist
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • Suggested Answer

    0 in reply to   

    Many thanks, Chris. Creating another folder which is not under C:\program files\(x86) solved this issue