IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Weird test results when Xpediter is turned on vs turned off


IBM Mainframe Forums -> Compuware & Other Tools
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Crunch

New User


Joined: 27 Jan 2010
Posts: 17
Location: Louisville, Ky

PostPosted: Tue Oct 06, 2015 7:48 pm
Reply with quote

We have a program that is performing an IMS message switch with another program. I'm getting some weird test results when Xpediting the program. When executing the program outside of Xpediter, the program does not pass the correct data to the program being called. However, when the program is re-compiled in Xpediter the program works as it should. The correct data gets passed to the called program. Has anyone else had this issue? Thanks in advance!!
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Tue Oct 06, 2015 8:53 pm
Reply with quote

Sounds like a bug in your code which is masked when you recompile it for Xpediter, most likely storage being overwritten.

Compile with SSRANGE. Check order, number, and lengths of parameters from CALL to PROCEDURE DIVISION.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 2567
Location: NYC,USA

PostPosted: Tue Oct 06, 2015 9:23 pm
Reply with quote

How does it execute in production then? if it is a new program then you have to explain what is "Correct data" means, is it truncated? check the copybook , it may happen you are picking up wrong one out side expd.
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2504
Location: Atlanta, Georgia, USA

PostPosted: Tue Oct 06, 2015 9:59 pm
Reply with quote

SSRANGE must be used together with the LE option CHECK being set to Y. You should NEVER use CHECK in Production.... icon_eek.gif
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Tue Oct 06, 2015 10:25 pm
Reply with quote

CHECK=YES is (usually) the installed default.

You can use SSRANGE and CHECK=NO in Production (until you get to Enterprise COBOL V5) but there is an overhead (less than doing the CHECK=YES, but still an overhead).

For V5, CHECK in Language Environment is redundant. You either compile with SSRANGE or NOSSRANGE. You can't compile with SSRANGE and decide not to use it at run-time.
Back to top
View user's profile Send private message
Crunch

New User


Joined: 27 Jan 2010
Posts: 17
Location: Louisville, Ky

PostPosted: Tue Oct 06, 2015 11:36 pm
Reply with quote

Solved. Somehow the module was compiled to the wrong LOADLIB, which happened to be the first library in the concatenation. We removed that load module from the first LOADLIB which corrected the problem. The correctly compiled version of the program used the 4th library in the concatenation.

I appreciate the input. Thanks!!
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Wed Oct 07, 2015 2:24 am
Reply with quote

It's always a waste of time when you execute the wrong version of a program. So, make sure you know for next time:

Code:
       01  W-WHEN-COMPILED                      PIC X(8)BX(8).
...
           MOVE WHEN-COMPILED           TO W-WHEN-COMPILED
           DISPLAY "prognm " W-WHEN-COMPILED


You do that "first time" in a program (store it somewhere in CICS instead of the DISPLAY, or route it to a log).

When the program fails or when looking into something, find the date/time of the actual program. Saved loads of time over the years.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> Compuware & Other Tools

 


Similar Topics
Topic Forum Replies
No new posts a copybook getting improper values in... COBOL Programming 7
No new posts Problème reproducing a production bu... ABENDS & Debugging 1
No new posts Feild level validation to test first ... JCL & VSAM 10
No new posts COBOL NOADVANCING strange results in ... COBOL Programming 4
No new posts Scripting TSO TEST CLIST & REXX 4
Search our Forums:

Back to Top