HP3000-L Archives

June 1998, 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:
Patrick Santucci <[log in to unmask]>
Reply To:
Patrick Santucci <[log in to unmask]>
Date:
Wed, 17 Jun 1998 16:35:00 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
Randy Medd wrote:
>
> Patrick wrote:
>
> >Problem #3: The user procedures must be written in SPL (again,
> >according to the RJE User/Programmer Reference Manual, Appendix
> >E). And I don't know SPL.
>
> Not true.  The _examples_ are in SPL, but any CM language (other than
> Basic) could be used.

You're right, I misinterpreted it. It says, "All user-written procedures
can be coded for execution in compatibility mode (SPL) or in native mode
with defined compatibility mode switch stubs... RJE expects the
user-written #RJCONTINUE procedure to conform to the formal procedure
specification indicated in SPL." So it *can* be SPL, not *must* be.

> The parameter types, translated to COBOL, are:
>
>   01 FILE-NUM             PIC S9(4) COMP.
>   01 ACTION               PIC S9(4) COMP.
>   01 ERROR-TABLE.
>      05 ERROR-1           PIC S9(4) COMP.
>      05 ERROR-2           PIC S9(4) COMP.
>      05 ERROR-3           PIC S9(4) COMP.
>   01 CMD-IMAGE            PIC X(256).
>   01 CMD-FILE             PIC X(256).
>
> RJE will call the procedure, passing all of the above by reference.

Thanks, this was very helpful since, as I've said before, I'm a system
programmer by title but a system admin by profession.

> The RJCONTINUE routines no longer need to be Privileged, so you don't
> have to worry about creating them with PM.

Does this mean the manual is also incorrect when it says, "Caution: When
a user-written procedure either attempts to expand the locked stack or
uses a significant amount of data stack space (for instance, arrays
local to the procedure), it may be necessary to specify additional stack
space. If RJE executes with its stack locked, where LOCK=NO is not
specified in the #RJLINE command and the stack overflows, a system abort
will occur."??? I about had a heart-attack when I read this. Ordinarily
a stack-overflow in a program causes a *program* abort, not a *system*
abort. Can this be right? (Not that I want to test it!)

Patrick
--
Patrick Santucci
Technical Services Systems Programmer
Kirke-Van Orsdel, Inc.
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Why is it that when I was young life was complex because
I lacked experience and now that I'm experienced life is
complex because I'm not young?" - James "Rainman" Trudeau

ATOM RSS1 RSS2