To Olav and Ray, and any others participating in this discussion.
 
First, thanks to all of you for taking the time to look at this problem.
 
Just to clear up one point.  Neither the calling program nor the
subroutine have been recompiled for over one year.  The OS upgrade
happened about 10 days ago.  So it is not a matter where one or the
other was recompiled since the upgrade and thereby got out of sync with
each other.  
 
Yes, compilation makes the problem go away, but it may not be feasible
to recompile all our software.  
 
Quite of bit of what we run comes from vendors who do not give us access
to their source code and compilation scripts.  And since we do not
understand the problem, who can say that subroutines compiled in other
languages may not also have problems with parameter passing?  We have
vendor-supplied Cognos Quick screen programs that call Cobol subroutines
resident in XLs.  How can we know that they will not have problems?
Even if we could get at all the source code and possessed correct
compilation scripts and library files for everything, it would be a
massive effort to recompile everything -- and very scary as well.
 
Personally speaking, if that were our only way to deal with this, I
would recommend that we wait for the problem to manifest, and then
correct it by recompiling.  But I would not feel happy or safe with this
approach.
 
As for COBCNTL.PUB.SYS,  we have not modified it to my knowledge.  The
subroutine itself only overrides the following commands on the $CONTROL
statement: DYNAMIC, POST85, CROSSREF.
 
I have requested any release notes or install notes that accompanied our
latest upgrade from our Operations Manager.  He has opened a case with
HP on this issue.

Ed Walsh 
Preferred Care -- Systems Analyst II 
259 Monroe Ave. 
Rochester, NY 14607 
585.327.2489 

 

________________________________

From: okappert [mailto:[log in to unmask]] 
Sent: Tuesday, May 08, 2007 12:36 PM
To: Ray Shahan; Walsh, Edward
Cc: [log in to unmask]
Subject: Re: Subroutine Returns Parameters Displaced


Ray:

If recompiling fixes the problem, then the best method of action would
be to do a full recompile of all programs.

Regards, Olav.

Ray Shahan wrote:


	Just to add this thought:  all of the resolutions/tests
suggested thus
	far, while certainly worth trying, should not be required.
There is no
	reason that I'm aware of why a linkage section that's been
working for
	years screws up because you've upgraded the OS version (if there
is a
	reason, then it should be documented in the OS release notes).
I'd try
	to go back to the previous OS version to see if that corrects
the issue,
	and if it does, I'd get hp on the phone.
	
	The array bounds violation, COMP fields, etc. would have
presented
	themselves as a problem long ago if, in fact, theses data
constructs
	were in error.
	
	One suggestion might need to read through the install notes from
hp to
	see if they make any mention of issues related to COBOL linkage
sections
	for your OS upgrade.
	
	That your problem goes away with a recompile suggests that some
form of
	data alignment is being done under your new OS version that was
not done
	under previous OS versions. The install notes for your OS
version may
	show you how to set a run switch (or other parm) that allows
existing
	programs to run using an older data alignment scheme?
	
	
	HTH,
	
	 
	
	Raymond Shahan
	Information Systems
	 REPUBLIC TITLE OF TEXAS, INC.
	  2701 W Plano Parkway 
	Plano, TX 75075
	 
	
	direct 214.556.0202
	main 972.578.8611
	fax 972.424.5621
	 www.republictitle.com
	[log in to unmask]
	Life is not a journey to the grave with the
	intention of arriving safely in a pretty and
	well preserved body, but rather to skid in
	broadside, thoroughly used up, totally worn out,
	and loudly proclaiming: 
	-- WOW!!! What a Ride!!!
	


Confidentiality Notice:
The information contained in this electronic message is intended for the exclusive use of the individual or entity named above and may contain privileged or confidential information.  If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that dissemination, distribution or copying of this information is prohibited.  If you have received this communication in error, please notify the sender immediately by telephone and destroy the copies you received.


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