MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

RE: Re Removing a procedure from a service program



fixed

All well and good, except that 43rd program is a nice shiny new ILE
program that was inserted in the job stream after 42 OPM programs. I'm
not saying that was a good design choice, but probably a very common
situation.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of D*B
Sent: Friday, February 21, 2014 2:15 PM
To: Midrange Systems Technical Discussion
Subject: RE: Re Removing a procedure from a service program

<snip>
If this program happens to be the 43rd program in a 96-program job
stream where 42 programs have already updated the database, and it
happens to be running at 2am on a Sunday...
</snip>

@Trevor: I would recommend to read some manuals about some very basic
ILE
concepts, that might help!!!
The very diffrence between a signature violation and an error at calling
an
imported procedure is, that the signature violation will occur at
A C T I V A T I O N T I M E and most of activation is done, when an

activation group is created, long before any activity is starting.

D*B







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact