HP3000-L Archives

November 1999, Week 1

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:
James Clark <[log in to unmask]>
Reply To:
James Clark <[log in to unmask]>
Date:
Mon, 1 Nov 1999 11:11:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
I would say the quickest is to have all socket routines written in C and
called from SPL. Haven't tried to use sockets in SPL. You could probably
look at HP's documentation of IPL since some of it is old enough to include
SPL examples.

James

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Emerson, Tom # El Monte
Sent: Friday, October 29, 1999 6:35 PM
To: [log in to unmask]
Subject: "External" variables -- possible in SPL?


I think I'm running into a conceptual problem here -- I've taken a recent
example posted here on doing SOCKET I/O within a COBOL program and converted
it to SPL, but there is one *tiny* bugaboo -- the COBOL source defines one
variable as "PIC S9(9) BINARY EXTERNAL"

This is the ever-famous "errno" variable, and I understand how and why it is
"external" to the main [source] of the program you're working upon, but how
exactly does one specify that a VARIABLE is "external" to the
main/outer-block of an SPL program?

[or is doing SOCKET I/O in SPL too much of a headache to be worth it?    The
long term answer to my situation is to re-write the SPL program in C, but
time constraints prohibit that at the moment -- gotta make a 6000+ line SPL
program work WITH "sockets" by the end of the week...]

Tom Emerson
Sr. Systems Analyst
NDC | e COMMERCE
[log in to unmask]
626-258-4309
626-350-3832 FAX

ATOM RSS1 RSS2