REXX sample compiler JCL

[Jake anderson]

Hello,

I would like to compile my REXX exec. So that the source codes are not
visible for the endusers.

Could somone please share a sample REXX compile JCL ?

What would be the format of the dataset to store the Rexx compiled Module ?

I am trying to find some samples from manual but not really getting a one.

Jake

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

[Steve Coalbran]

Hi Jake,

I don't do this too much but understand your need.

I think there may be improved ways to do both of these and some redundancy
can probably be removed (guys?) - but...

I used this last on IBM DEMO at Montpellier MOPZT01. It worked as I
remember!
Obviously libraries for STEPLIB and SYSEXEC will vary by installation?

//useridC JOB (DUMMY),'COMPILE',MSGCLASS=H,NOTIFY=&SYSUID,
// MSGLEVEL=(1,1),CLASS=A,TIME=(5,0)
//*--------------------------------------------------------------------
//COMPILE EXEC PGM=IKJEFT01,REGION=0K
//STEPLIB DD DISP=SHR,DSN=REXX.SFANLMD
//SYSEXEC DD DISP=SHR,DSN=REXX.SFANCMD
//SYSTSPRT DD SYSOUT=*
//SYSPUNCH DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTSIN DD *
PROFILE PREFIX(userid) MSGID
REXXC 'userid.USER.EXEC(rexname)' +
BASE('userid.USER.EXEC(rexname)') +
OBJECT NOCEXEC SLINE DLINK SOURCE PRINT(**)
//*--------------------------------------------------------------------
//LINKCPPL EXEC PGM=IKJEFT01,COND=(4,LT)
//SYSEXEC DD DISP=SHR,DSN=REXX.SEAGCMD
//SYSLIB DD DISP=SHR,DSN=REXX.SEAGLMD
//SYSTSPRT DD SYSOUT=*
//SYSPUNCH DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTSIN DD *
PROFILE PREFIX(userid) MSGID
REXXL CPPL 'userid.USER.OBJ(rexname)' +
'userid.USER.LOAD(rexname)'
//*--------------------------------------------------------------------

You may want to skip the LINK and just run with CEXEC?

//*--------------------------------------------------------------------
//REXXC EXEC PGM=IKJEFT01
//SYSEXEC DD DISP=SHR,DSN=CENTER.CLIST
// DD DISP=SHR,DSN=REXX.SFANCMD
// DD DISP=SHR,DSN=REXX.SEAGCMD
//*SYSEXEC DD DISP=SHR,DSN=REXX.SFANCMD
//* DD DISP=SHR,DSN=REXX.SEAGCMD
//SYSPUNCH DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
PROFILE PREFIX(userid) MSGID
REXXC 'userid.USER.EXEC(rexname)' +
BASE('userid.USER.EXEC(rexname)') +
CEXEC('userid.USER.CEXEC(rexname)') +
OBJECT DLINK SOURCE PRINT(**)
//*-------------------------------------------------------------------

A word of warning.
I have found modules compiled (to CEXEC), in my case in ENDEVOR, on one
codepage don't work on another.
In my case compiled on 1143 and don't-run on 037. Rude message, forget the
actual words.
It may be an ENDEVOR specific problem, but I am stuck with it on my
Customer development system.

Any answers or corrections to this gladly awaited. ;-D

/Steve

Såvida annat inte anges ovan: / Unless stated otherwise above:
IBM Svenska AB
Organisationsnummer: 556026-6883
Adress: 164 92 Stockholm

[Steve Beaver]

Look in the SAMPLES for the PROC FAN140. The REXX Compiler is not free

Steve

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf Of Jake anderson
Sent: Wednesday, February 18, 2015 4:03 AM
To: TSO-...@VM.MARIST.EDU
Subject: [TSO-REXX] REXX sample compiler JCL

[Peete Baer]

Also be aware that, depending on the compiler options, the source may become part of the compiled REXX module.

Yes the REXX compiler is definitely not free. And if you happen to be using PIPES, that's not free either.

Peete Baer

[Steve Beaver]

The caveat for the REXX compiler is -- I you are an IBM Business partner, you can PURCHASE a development machine, then pay the $5,000 per year to license the zVM / zOS software And that will give you more than you ever thought.

First you will have to create an LLC then become a member of Partner World and that will take a couple of months. Then you can go to www.p390.com and put out your $25,000 for the machine and the first years license

[richard rozentals]

Hi,
You assume is the panels are not installed it is not purchased. That is not always the case. This can happen when ISPF is installed. If these panels are over looked it would take years to discover it as thewy are seldom used . I found at my site I have this case. I have no REXX panels to compile but the batch job works.
Try this. This is the simplest form of REXX compile.It's a rexx CEXEC(not a compiled and linked load)
//REXX      EXEC  PGM=REXXCOMP,PARM='CEXEC'//SYSIN        DD DSN=MY.INPUT.SOURCE(REXX),DISP=SHR//SYSTERM  DD SYSOUT=* //SYSPRINT  DD SYSOUT=* 
//SYSCEXEC DD DSN=MY.OUPUT.SYSCEXEC(REXX),DISP=SHR
This will produce a compiled REXX that is called just like a normal REXX. The compiled REXX can be put in the same library as normal REXX (but not recommended) As I understand it no limitations as in the compiled and linked REXX. I never tested that.
Richard Rozentals