Re: Screen descriptions in HP Cobol on VMS

From: Richard Maher (maher_rj_at_hotspamnotmail.com)
Date: 05/20/05

  • Next message: Richard Maher: "Re: Dec RDB V6.1-14 under VMS 6.2" 
    Date: Fri, 20 May 2005 10:07:21 +0000 (UTC)

    Hi,

    You're on your own with the VT220, (Didn't that have a graphics capability?
    Could draw squiggly lines and circles?)

    For an FMS tutorial you should install it and look at
    fms$examples:sampcob.cob. If you run the example it will show you most of
    the main features. Be aware that YES FMS also paints the screen one line at
    a time and this will be visible at low baud rates. These days it's usually
    so quick that the naked eye can't pick it up, but it is there. If you want
    control over this then use SMG$.

    Cheers Richard Maher

    "Volker Englisch" <eh97@despammed.com> wrote in message
    news:d6ifq9$c26$1@rrz.allgaeu.org...
    > Hi,
    >
    > > Getting back to your original queries both here and in COV, what is the
    > > actual problem?
    > >
    > > 1) Your Screen-Section strategy is a perfectly acceptable way to go.
    > > What do you think is wrong with it?
    >
    > Well, some guy told here that the screen is built up very slow when a
    > COBOL program is run on a VT220 terminal. For I have the same problem
    > here, I just asked if there was a better way to code screen layouts.
    >
    > > 2) Was it you that was questioning the refresh time?
    >
    > No, it wasn't me.
    >
    > > Was it also you with the VT220 CRT? Have you tried with any
    > > reasonable VT terminal emulator and telnet? Is it still slow?
    >
    > I tried with PUTTY over Ethernet, there is no visible delay. I also
    > connected the VT220 directly to a unix machine and did a telnet to the
    > VMS box. Still slow like connected directly to the VMS.
    >
    > Maybe I had to mention here that tools like FLIST on VMS display their
    > screen with no delay, even at the serial VT220 CRT.
    >
    > > 4) Are you limited to a dumb terminal/character-cell interface?
    >
    > Yes, I am.
    >
    > > If not, then why don't you front end your application with VB (or
    > > whatever) and have VMS and COBOL serve the back-end?
    >
    > Scream :-) I don't love graphical interfaces really :-)
    >
    > > Then we can have another lengthy discussion about middleware :-)
    >
    > :-)
    >
    > > d) FMS Forms Management System
    > >
    > > This is the BEST character-cell forms product EVER invented! (There
    > > is also an FMS to Motif converter available) There is a fantastic
    > > full-function Panel-Editor and your forms are stored in separate
    > > files (or a library) and can be compiled and linked in with your
    > > COBOL object code for performance. See docs on the web.
    >
    > Is there any tutorial on the web? I didn't find one yet.
    >
    > However, thanks a lot for your patience and your detailled explanation.
    >
    > V.

  • Next message: Richard Maher: "Re: Dec RDB V6.1-14 under VMS 6.2"

    Relevant Pages

    • Re: Send data to an interactive VMS application from a Windows system?
      ... > FMS application. ... The VMS system still needs to be updated as it ... to find the relevant Cobol easily enough inside the ACMS transactions. ...
      (comp.os.vms)
    • Freely distributable FMS runtime ?
      ... Since FMS has been mature since the early 1990s, ... be to convince VMS management to make FMS run time included in VMS? ... have it check for a VMS licence instead of a FMS ... well as the run time shareable images), and the FMS Run Time licence ...
      (comp.os.vms)