[an error occurred while processing this directive]

HP OpenVMS Systems

Ask the Wizard
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard
» OpenVMS FAQ

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

DEC COBOL vs VAX COBOL

The Question is:

A COBOL program with ACCEPT verb used produces
different results when run on both VAX and ALPHA platforms.
On VAX the ACCEPT statement positions the entry point on the next
line of the terminal to get the input.  On ALPHA the
entry position is at the top of the screen.  All info
previously on the screen remains, with the ACCEPT
entry point overlaid amongst the other details. The result is
mess of characters on the screen.  Is there a way to
get the ALPHA to behave like the VAX when the
ACCEPT statement is used.


The Answer is:

    As stated in the release notes, any COBOL Format 3
    or Format 4 ACCEPT statements, or Format 2 DISPLAY statements in a
    program will cause the COBOL RTL to use SMG for screen output. The
    customer had not realised that using the clause "WITH CONVERSION" makes
    an ACCEPT Format 3 and a DISPLAY Format 2.

    There is also a release note for a recent version of COBOL which
    explains the screen clearing behaviour. In early implementations, DEC
    COBOL would intentionally clear the screen prior to any output. This
    was changed in later releases due to customer demand. To clear the
    screen, it is now necessary to explicitly clear the screen using the
    "ERASE SCREEN" clause of the DISPLAY statement.

    This difference between the DEC COBOL RTL and the VAX COBOL RTL
    is documented in the DEC COBOL User Manual appendix on compatibility:

------------
    If your application uses the Digital extensions to the ACCEPT or
    DISPLAY statements, DEC COBOL positions the cursor in the upper left
    corner of the screen prior to the execution of the first ACCEPT or
    DISPLAY statement.

    This difference is clearly shown when the first ACCEPT or DISPLAY
    statement does not contain the LINE and COLUMN clauses.  In this case
    DEC COBOL moves the cursor to the top of the screen to perform the
    ACCEPT or DISPLAY, whereas VAX COBOL does not move the cursor.
------------