HP3000-L Archives

August 2002, Week 4

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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 27 Aug 2002 15:52:56 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
Re:
> Why can't I use the AIF intrinsics in a Cobol program?

You can.

> Can the AIF intrinsics be included in the intrinsics file referenced by Cobol

Ah...

As Dennis Handly pointed out, they're in a separate include file.

I'd file a bug report / enhancement request against COBOL ... it should
have a directive to select a different instrinsic file, just like SPLash! and
Pascal have.  (Even C/ix has: #pragma INTRINSIC_FILE "path")

In the meantime, you've got three choices:

   1) simply use a correct calling sequence;

      <plug> CSEQ from Lund can help you by telling you the actual parameter
      sequence of the intrinsics (i.e., with necessary information that isn't
      in the manual) </plug>

   2) you can file equate SYSINTR.PUB.SYS = AIFINTR.PUB.SYS and then
      reference the AIFs you want.  Note: if you do the file equate technique,
      you can't then reference standard system intrinsics.

   3) create your own merged intrinsics file, and use it instead of
      SYSINTR.PUB.SYS (either by replacing the real one (which has
      drawbacks) or by a file equate.

      It sounds like Dennis has a utility to merge intrinsic files.
      ...I know I'd be interested in a copy of that!

--
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2