Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Weird test results when Xpediter is turned on vs turned off

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Compuware & Other Tools
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    Post subject: Weird test results when Xpediter is turned on vs turned off
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

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7225

PostPosted: Tue Oct 06, 2015 8:53 pm    Post subject: Reply to: Weird test results when Xpediter is turned on vs turned off
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

Senior Member


Joined: 21 Sep 2010
Posts: 1609
Location: NY,USA

PostPosted: Tue Oct 06, 2015 9:23 pm    Post subject:
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: 2502
Location: Atlanta, Georgia, USA

PostPosted: Tue Oct 06, 2015 9:59 pm    Post subject: Reply to: Weird test results when Xpediter is turned on vs turned off
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

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7225

PostPosted: Tue Oct 06, 2015 10:25 pm    Post subject: Reply to: Weird test results when Xpediter is turned on vs turned off
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    Post subject:
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

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7225

PostPosted: Wed Oct 07, 2015 2:24 am    Post subject: Reply to: Weird test results when Xpediter is turned on vs turned off
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    IBMMAINFRAMES.com Support Forums -> Compuware & Other Tools All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts COOLGEN - TSO TEST FACILITY indianrajput CA Products 4 Wed Nov 02, 2016 9:28 pm
No new posts Low values Results from VARCHAR FORMAT balaji81_k DB2 10 Thu Oct 20, 2016 1:18 am
This topic is locked: you cannot edit posts or make replies. How to supply called sub-program from... dchristensen JCL & VSAM 25 Wed Sep 14, 2016 11:36 pm
No new posts Strange Results with ICETOOL Rohit Umarjikar DFSORT/ICETOOL 4 Tue Dec 22, 2015 4:12 am
No new posts Two different PDS production and test... Mani453 CLIST & REXX 6 Fri Nov 20, 2015 2:25 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us