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

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


The Question is:

How can I get the right line number from a COBOL
program for a Subscript out of range error in the
traceback. It looks like the compiler generates a GENTRAP
instruction, and then all the range checking code jumps
there to generate the crash.

The Answer is:

    Your analysis is correct. Thank you for bringing this issue to the
    attention of the COBOL engineering team. This problem has been logged
    into the problem tracking system used by COBOL engineering. A response
    will be posted here when the problem is resolved.

    In the meantime, be aware that more accurate traceback functionality
    is available with OpenVMS V7.0. Also, compiling the program /NOOPT
    should improve the behavior and reliability of the traceback
                    -< Fixed with DEC COBOL V2.4 compiler >-
    We have fixed this problem.  The fix will be available in the next
    release of DEC COBOL (tentatively called V2.4).

    If you are interested in field testing DEC COBOL T2.4 to evaluate the
    fix, send mail to