HP3000-L Archives

March 2001, 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:
Tracy Pierce <[log in to unmask]>
Reply To:
Tracy Pierce <[log in to unmask]>
Date:
Wed, 28 Mar 2001 15:53:27 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
> -----Original Message-----
> From: Philip Yantis [mailto:[log in to unmask]]
> Sent: Wednesday, March 28, 2001 3:14 PM
> To: [log in to unmask]
> Subject: HP INTRINSIC STATUS
>
>
> HPCIPUTVAR and HPCIGETVAR return a 32bit signed integer
> status. But to interpret it you have to access it as two
> 16bit integers. One 16bit integer is the error code and the
> other is the subsystem identifier.
>
> Question 1:
> How do I interpret the 32bit integer as two 16bit integers in COBOL.

Already answered by Brian, something like
01 int32 pic s9(9) comp.
01 redefines int32.
   05  int16a pic s9(4) comp.
   05  int16b pic s9(4) comp.
>
> Question2:
> Where can I find what the error integers mean once I
> successfully get them in COBOL. The Intrinsic Manual says to
> look at the Error Message Manual but the Error Message Manual
> doesn't have info for subsysytem 166 (HCIGETVAR & HCIPUTVAR).

You can try MSGUTIL.PUB.SYS.  IIRC the high-order half of int32 ie int16a is
the subsystem number, the low-order half ie int16b is the message number.

ATOM RSS1 RSS2