Screen descriptions in HP Cobol on VMS

Hi,

I was used to describe screen layouts using the SCREEN SECTION or doing
a DISPLAY ... AT ... in a cobol program. In another newsgroup, someone
mentioned that there were much better ways to design and handle a
screen for dialogues.

On AS/400 et al., I'm used to define screens as (DDS) files and handle
them as TRANSACTIONAL files from within cobol. But this is a AS/400 or
Mainframe way, isn't it?

So I'm curious how you define and handle full screen i/o in Cobol on
VMS?

Volker

I am NOT a VMS programmer, but DEC was the "father" of the FIMS (Forms Inter
face
Management System) definition - that was adopted by CODASYL and *almost* bec
ame
a COBOL Standard.  There is a LONG PDF document about it at:


[url]http://h71000.www7.hp.com/doc/73final/documentation/PDF/decforms_prog_ref_gd.PDF[/
url]

If you are developing for VMS, I would check your reference material for "FI
MS".

--
Bill Klein
wmklein <at> ix.netcom.com
"Volker Englisch" <eh97@despammed.com> wrote in message
news:d6a0l3$2oq$1@rrz.allgaeu.org...
> Hi,
>
> I was used to describe screen layouts using the SCREEN SECTION or doing
> a DISPLAY ... AT ... in a cobol program. In another newsgroup, someone
> mentioned that there were much better ways to design and handle a
> screen for dialogues.
>
> On AS/400 et al., I'm used to define screens as (DDS) files and handle
> them as TRANSACTIONAL files from within cobol. But this is a AS/400 or
> Mainframe way, isn't it?
>
> So I'm curious how you define and handle full screen i/o in Cobol on
> VMS?
>
> Volker

William M. Klein schrieb:
> I am NOT a VMS programmer, but DEC was the "father" of the FIMS
> (Forms Interface Management System) definition - that was adopted by
> CODASYL and *almost* became a COBOL Standard.  There is a LONG PDF
> document about it at:
>
> If you are developing for VMS, I would check your reference material
> for "FIMS".

Thanks a lot, I guess you put me on the right way.

Volker