HP3000-L Archives

March 1999, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Walter Murray <[log in to unmask]>
Reply To:
Walter Murray <[log in to unmask]>
Date:
Tue, 16 Mar 1999 18:29:51 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
TechServ TechServ ([log in to unmask]) wrote:
: Just to let you know, it appears it does not matter what the case of =
: the intrinsic name is.  I also compiled with the intrinsic "Clock" and =
: "ClocK" and they both compiled without any errors, warnings,  or =
: questions.

Right.  Even though the name of a called routine may be specified as
a nonnumeric literal, the compiler transforms that name according to
certain rules, in order to conform to MPE naming conventions for
intrinsics and other library procedures.  For COBOL II/iX these
rules are documented unser "External Names" in the "Interprogram
Communication" section of Appendix H in the reference manual
(page H-27).

There was a recent change in that area as part of the enhancement
to permit alternate entry points in COBOL main programs, but that
change should not affect intrinsic calls in any way.  (This
enhancement is documented in the MPE/iX 5.5 PowerPatch 5 Communicator,
page 117).

I suspect a clobbered SYSINTR file.

Walter Murray
Hewlett-Packard
Support Technology Lab

ATOM RSS1 RSS2