Re: [Oorexx-devel] Mainframe OORexx Build

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

All;

I could have been clearer:  Boiling the ocean is, of course, out of the
question.  The bullets under each number were intended as alternatives and
options, to be pruned down to a cohesive, optimal set.

Some possibly relevant notes on my background.

Professionally, I go back to the OS/360 and CP-67 days.  I used to speak
regularly on converting JCL to REXX, at SHARE and elsewhere, based on
techniques I had developed entirely on my own.  I have supported 3 in-house
REXX mainframe change control systems.  Two did automatic "builds".  The
third was written from scratch.  I think my only personal limitations in the
z/OS (except-USS) and z/VM (non-z/Linux) arenas are time and
over-confidence.

On a *nix system (including USS and z/Linux), very little of my work
experience is professional.  I probably couldn't hold a candle to kids now
coming out of college.

For starters, I'll be happy just to run ooRexx on any mainframe, in any
mainframe environment.  Seamlessly replacing the interpreter(s) is probably
beyond my current capabilities.  It is definitely beyond my goals at this
time.  There is always later.

So, the basic question is do I try to build using (1) TSO/batch/CMS to run
on same or (2) using USS/Linux/Knoppix/Ubuntu/*nix to run on USS/z-Linux?

In favor of TSO/JCL/CMS:

   - My strong skills in REXX, PIPES, ISPF, JCL, etc. and knoing how they
   interact the platform.
   - Almost no learning curve.
   - Little need for help.
   - Experience that should help me do it "right,' the first time.  (E.g.,
   interfacing to IKJCV441 would be an early goal.)
   - Good assembler skills if need be.
   - Possible time and/or resource buy-in from current client.
   - My perception that a build for TSO/batch/CMS execution has a wider
   audience than that for USS.  TSO users are starving for good tools.
   - My current assignment would be emensely helped by having any access
   to ooRexx.

In favor of *nix:

   - Easy to learn and use GUI interfaces.
   - Lots of tools like make.
   - Lots of compiler choices.
   - Lots of potential help.
   - Lots of potential build platforms.

Making the question this simplistic camouflages cross-platform options
like build on *nix for TSO/JCL/CMS execution.  (Hence the option lists in my
first note.)  Other than that, have I missed anything major?

Since it looks like I will be working alone, I vote for building on
TSO/JCL/CMS for execution on TSO/JCL/CMS.  Would that be a mistake?

Thanks in advance.

- Hobart

On 6/6/07, Rick McGuire <obj...@gm...> wrote:
>
> I strongly encourage you to keep as much of the conversation "on list" as
> possible.  The more eyes looking at the problem, the more good suggestions
> you can receive.
>
> Rick
>
> On 6/6/07, David Ashley <da...@us...> wrote:
> >
> >
> > Hobart -
> >
> > Let's keep it simple to start with.
> >
> > The source code as stored in the repository is designed around using
> > either Windows-based or GNU-based tools to create the binaries/installation
> > files. Obviously the Windows tools don't port at all to the mainframe so you
> > need to either use the GNU tools or port the entire built process to the
> > standard mainframe tools. Let's start by using the GNU tools.
> >
> > You will need the following environment.
> >
> > - Red Hat or Suse Linux running either natively or as a virtual machine.
> > - Be sure all the GNU tools are installed - GCC, Libtool and Autoconf
> > are all required.
> > - If you are checking code out of the repository then Subversion is
> > required.
> > - If you are going to build an installation RPM then rpmbuild is
> > required.
> >
> > Once you have the proper environment you can perform the following.
> >
> > - If you have checked out the code from Subversion then you will need to
> > run "./bootstrap". Otherwise skip this step.
> > - Run "./configure".
> > - Run either "make" or "make rpm" (you do not need to be logged on as
> > root to create an rpm).
> >
> > I have a report that on some mainframe systems the build process seg
> > faults while building the image file (rexx.img). If it does please
> > contact me so I can help you debug it.
> >
> > It is unwise to run "make install". Although it will work, ooRexx will
> > not be available for daemon processes like cron. This is due to where make
> > installs the binaries.
> >
> > If you have questions don't hesitate to contact me. If you want to take
> > the conversation off list then send me email at da...@us....
> >
> > Thanks,
> > W. David Ashley
> > IBM Systems and Technology Group Lab Services
> > Open Object Rexx Team
> > Office Phone: 512-838-0609 T/L 678-0609
> > Mobile Phone: 512-289-7506
> >
> >
> >
> >   *"Hobart Spitz" <ore...@gm...>*
> > Sent by: oor...@li...
> >
> > 06/05/07 07:47 PM   Please respond to
> > Open Object Rexx Developer Mailing List <
> > oor...@li...>
> >
> >    To
> > oor...@li...  cc
> >
> >  Subject
> > [Oorexx-devel] Mainframe OORexx Build
> >
> >
> >
> >
> >
> >
> > All;
> >
> > At the REXX Symposium, I offered to attempt to do a mainframe build of
> > OORexx.  I've never been thru such a process without some sort of in-place
> > infrastructure, so I have lots of questions.  In an effort to get a handle
> > on the answers, I've come up with rough work plan options.  Could I impose
> > on those knowledgable to help me sort out a low effort, high chance of
> > success approach?  Once I've been thru the process, end-to-end, I'm sure
> > I'll be looking to make refinements.  For now, I'd like to keep it a simple
> > learning process . . . *really* simple.
> >
> > Here goes:
> > 1.        Build platform:
> >
> >    - Linux (RH, Knoppix, Ubunto)
> >    - z/OS (batch TSO REXX)
> >    - z.OS USS
> >    - z/VM (I'm a pipes fan.)
> >    - Window
> >    - other
> >
> > 2.        Compiler (depending mostly on platform)
> >
> >    - C
> >    - C++
> >    - Linux native cross compiler/asm
> >    - z/OS
> >    - z/VM
> >    - Windows cross platform compiler/asm
> >    - other
> >
> > 3.        Build process driver
> >
> >    - Linux make
> >    - z/OS REXX automation of JCL (I've done lots of this, so this is
> >    my current first choice.)
> >    - z/OS USS make
> >    - z/VM VM Download make or other.
> >    - Windows?
> >    - other
> >
> > 4.        Target instruction set (If compiler allows a choice.)
> >
> >    - S/370 (probably too limiting)
> >    - S/390 (halfword-immed and branch-relative)
> >    - z900 (12 bit offsets)
> >    - z990 (20 bit offsets)
> >    - z9
> >    - foat decimal
> >    - other?
> >
> > 5.        Assembler modules to be wriiten or modified
> >
> >    - DSECTs/control block
> >    - Drivers
> >    - Exits
> >    - other
> >
> > 6.        Target environment
> >
> >    - z/OS TSO
> >    - z/OS batch
> >    - USS
> >    - z/VM (CMS OS Simulation seems to be a lowest common denominator)
> >    - other
> >
> > Of course, a lot will depend on which platforms and software I can get
> > access to.  If you can provide some help here, please let me know.
> >
> > My thanks in advance for getting me going in the right direction.
> >
> > - Hobart
> >
> > --
> > OREXXMan
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/_______________________________________________
> >
> > Oorexx-devel mailing list
> > Oor...@li...
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Oorexx-devel mailing list
> > Oor...@li...
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> >
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>

-- 
OREXXMan

Re: [Oorexx-devel] Mainframe OORexx Build

REXX interpreter

Re: [Oorexx-devel] Mainframe OORexx Build