Skip to main content

Who has this Problem and have been able to find a solution?

Loading in DS is not a Problem, but when starting the program and loading the screenset i become the following window with a error Messages:

 

DSRUN error 28,0,0

Incorrect Dialog System vocabulary Information is stored in the screenset.

Make shure you have generated a vocabulary copybook for this screenset.

 

I works since many years and this is the first time and i don't find a solution.

I have exported the screenset and imported in a new screenset without Errors.

Who can help?

Who has this Problem and have been able to find a solution?

Loading in DS is not a Problem, but when starting the program and loading the screenset i become the following window with a error Messages:

 

DSRUN error 28,0,0

Incorrect Dialog System vocabulary Information is stored in the screenset.

Make shure you have generated a vocabulary copybook for this screenset.

 

I works since many years and this is the first time and i don't find a solution.

I have exported the screenset and imported in a new screenset without Errors.

Who can help?

Do you experience this issue on a machine that has both Net Express and Visual COBOL installed?
Can you reproduce the problem on another machine where it has either Net Express or Visual COBOL installed?

Who has this Problem and have been able to find a solution?

Loading in DS is not a Problem, but when starting the program and loading the screenset i become the following window with a error Messages:

 

DSRUN error 28,0,0

Incorrect Dialog System vocabulary Information is stored in the screenset.

Make shure you have generated a vocabulary copybook for this screenset.

 

I works since many years and this is the first time and i don't find a solution.

I have exported the screenset and imported in a new screenset without Errors.

Who can help?

The Problem was that i call a ds command from Cobol before ds-screenset was loaded!
That was the not documented error code
And i have search any days to solve this!
Thanks for your answer and help
Terms & ConditionsAccessibility statement