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

REXX compiled via RXTCOMP


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2010
Location: USA

PostPosted: Tue Feb 07, 2017 9:41 pm
Reply with quote

Sorry, but I cannot find any explanation from available sources.

When already tested REXX code has been successfully compiled using REXXTOOLS RXTCOMP compiler, and then a binary load module created, it fails at run time when trying to call any TSO function, like OUTTRAP or whatever:
Quote:
212 +++ X=OUTTRAP("RES.")
IRX0043I Error running TESTMOD1, line 212: Routine not found

Kindly give me a clue where the external TSO functions (or any other external functions?) must be defined to be used with load module created from a compiled REXX code?
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2545
Location: Silicon Valley

PostPosted: Tue Feb 07, 2017 9:48 pm
Reply with quote

What environment are you running it on?

If it is a batch job, remember that you still need to provide a TSO environment.
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Tue Feb 07, 2017 10:53 pm
Reply with quote

I do not know about the REXXTOOLS compiler

but the IBM REXX compiler is very sensitive to the STUB linked into the executable

Using the wrong STUB would usually result in an odd behavior
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2010
Location: USA

PostPosted: Wed Feb 08, 2017 10:35 pm
Reply with quote

After long investigation I was able to find the answer as fine print in the Open Software Inc. manual icon_rolleyes.gif
Quote:
Note: If your compiled REXX program utilizes any TSO service, you must run it under IKJEFT01 (the batch TMP).
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2545
Location: Silicon Valley

PostPosted: Thu Feb 09, 2017 10:27 pm
Reply with quote

repeating:
Quote:
remember that you still need to provide a TSO environment.


That is, not sure you need a long investigation.
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2010
Location: USA

PostPosted: Fri Feb 10, 2017 1:03 am
Reply with quote

Pedro wrote:
repeating:
Quote:
remember that you still need to provide a TSO environment.
That is, not sure you need a long investigation.

0) This requirement might be interpreted as "ADDRESS TSO" which could be executed in compiled version, but did not help to access TSO services.

1) Then, WTF compiled REXX version is needed? The widely used standard REXX instruments unpredictably do not run from successfully(!) compiled REXX (and linked load module).

2) Despite of what manual says, the compiled REXX just fails with S0C4 when started via IKJEFT01, as recommended by manual...

So, finally even "long investigation" did not help so far icon_rolleyes.gif
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Fri Feb 10, 2017 1:39 am
Reply with quote

What did the vendor say when you asked your question there?
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2010
Location: USA

PostPosted: Sat Feb 11, 2017 2:34 am
Reply with quote

Robert Sample wrote:
What did the vendor say when you asked your question there?

I am subcontractor, and not supposed to contact the vendor directly.

After some investigation I was able to find the reason. The client's Endevor team provided so called "processor group" to "automatically perform REXX compilation, and link edit the load module". Noone of that support group was able to clarify any minor question.

Further investigation discovered that the "standard processor group" for REXX compilation has internal hardcoded REXX compiler option PREFIX(RXTRXPRC), the one compatible with... calling REXX from COBOL only! The created object/load modules became incompatible with calls from JCL/TSO/Assembler etc.

The Endevor team has been notified of their own problem. So far I use my own JCL to perform REXX compilation. Now it's working as described.

Thank you
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 -> CLIST & REXX

 


Similar Topics
Topic Forum Replies
No new posts Running REXX through JOB CLIST & REXX 13
No new posts Error to read log with rexx CLIST & REXX 11
No new posts isfline didnt work in rexx at z/OS ve... CLIST & REXX 7
No new posts run rexx code with jcl CLIST & REXX 15
No new posts Execute secondary panel of sdsf with ... CLIST & REXX 1
Search our Forums:

Back to Top