Explore topic-wise InterviewSolutions in .

The source code provided to RexxLA was maintained by one group of IBM DEVELOPERS. The source code for OS/2 is maintained by a different group of IBM developers, and that source code BASE was not supplied to RexxLA. One of the future tasks for this project is to PORT the OPEN Source code for ooRexx to OS/2.

The source code provided to RexxLA was maintained by one group of IBM developers. The source code for OS/2 is maintained by a different group of IBM developers, and that source code base was not supplied to RexxLA. One of the future tasks for this project is to port the Open Source code for ooRexx to OS/2.

Any POSIX-based, Unix-like platform is likely to already be AVAILABLE in the source distribution DUE to the use of the autoconf toolset. If not, then support for the PARTICULAR platform will need to be implemented in a FUTURE version of ooRexx.

Any POSIX-based, Unix-like platform is likely to already be available in the source distribution due to the use of the autoconf toolset. If not, then support for the particular platform will need to be implemented in a future version of ooRexx.

IBM's Object REXX was available in two formats; an Interpreter Edition and a DEVELOPMENT Edition. OOREXX will be available in one format which is half way between the two IBM offerings. There will be no functional DIFFERENCE between the Object REXX and ooRexx interpreters; code written for Object REXX will WORK with ooRexx.

IBM's Object REXX was available in two formats; an Interpreter Edition and a Development Edition. ooRexx will be available in one format which is half way between the two IBM offerings. There will be no functional difference between the Object REXX and ooRexx interpreters; code written for Object REXX will work with ooRexx.

OOREXX for AIX is AVAILABLE STARTING with the 3.1 RELEASE.

ooRexx for AIX is available starting with the 3.1 release.

YES!

Yes!

YES!

Yes!

uni-REXX comes with a sample library that includes a examples of a variety of application types.

These include:

• UTILITIES for: date calculations and CONVERSIONS printing on a remote host creating new userids (AIX) running dbxw debugger on a process in another window simulating the "which" command for UNIX implementations that do not have it printing a visual depiction of a directory structure.
• functions to: convert a system -independent filename into a local filename perform SPECIALIZED string SEARCH add math functions to uni-REXX.
• filters to: uppercase all characters in an input stream replace simulated box drawing (using "|", "+", "_") with real box drawing characters remove backspace characters from an input stream useful for reformatting the output of a man page for ASCII printing.
• illustrations of using the APIs to EMBED uni-REXX as a scripting language in compiled language applications.
• example of using the UNIX-specific functions for a client/server application.

uni-REXX comes with a sample library that includes a examples of a variety of application types.

These include:

30 SECONDS or LESS, DEPENDING on your HARDWARE.

30 seconds or less, depending on your hardware.

Further, uni-REXX is very easy to use, even if your previous experience with it is limited. The syntax is very natural (English-like); there are no DATA types to declare; interpretive execution facilitates rapid development and DEBUGGING; and the interface to the operating SYSTEM is SEAMLESS.

Further, uni-REXX is very easy to use, even if your previous experience with it is limited. The syntax is very natural (English-like); there are no data types to declare; interpretive execution facilitates rapid development and debugging; and the interface to the operating system is seamless.

YES!

Yes!

YES!

Yes!

YES!.

Yes!.

YES!.

Yes!.

On the command LINE in the editor, just use the name of the macro and list the PARAMETERS behind it. E.g. if you have a macro called FINDALL and it expects 3 parameters you would specify in the command line: FINDIT parm1 parm2 parm3. 

When you code the MACRO the first line should be like:

Since you are working with REXX you could have used:

You then parse the parm like this:

On the command line in the editor, just use the name of the macro and list the parameters behind it. E.g. if you have a macro called FINDALL and it expects 3 parameters you would specify in the command line: FINDIT parm1 parm2 parm3. 

When you code the MACRO the first line should be like:

Since you are working with REXX you could have used:

You then parse the parm like this:

Answer : /**REXX**/ ADDRESS TSO "ALLOC DD(INP1) DA('input-dataset') SHR REUS" "EXECIO * DISKR INP1 (STEM IN1. FINIS" MAX_OFFSET = 0 INP_OFFSET = 0 DO I = 1 TO IN1.0 PARSE UPPER VAR IN1.I INP INP_OFFSET = POS("VALUE",INP) IF INP_OFFSET > MAX_OFFSET THEN DO MAX_OFFSET = INP_OFFSET END END DO I = 1 TO IN1.0 PARSE UPPER VAR IN1.I INP Z = POS("VALUE",INP) SAY LEFT(SUBSTR(IN1.I,1,(Z - 1)),(MAX_OFFSET - 1))||, SUBSTR(IN1.I,Z,20) END "FREE DD(INP1)"

USE the Storage() function to extract the data from CONTROL blocks.

Use the Storage() function to extract the data from control blocks.

Held output (JES2 or JES3) can be captured by outtrapping the output of the following command:

Use command HELP OUTPUT for more information.

Furthermore there are output tools you can buy like SDSF, IOF, (E)JES, etc. But not all of these have got a rexx interface.

Held output (JES2 or JES3) can be captured by outtrapping the output of the following command:

Use command HELP OUTPUT for more information.

Furthermore there are output tools you can buy like SDSF, IOF, (E)JES, etc. But not all of these have got a rexx interface.

uni-REXX offers a complete set of Application Programming Interfaces (APIs). These APIs allow you to

• START a Rexx program from the compiled language program.
• define new host command environments for Rexx.
• ACCESS Rexx program variables.
• access the Rexx program stack.
• specify user-supplied exits.
• terminate the Rexx program.
• add user-defined functions that can be CALLED by the Rexx program.

uni-REXX offers a complete set of Application Programming Interfaces (APIs). These APIs allow you to

In addition to the standard language features, uni-REXX includes a rich set of functions designed specifically for a UNIX environment. These functions can be CLASSIFIED into the following categories (with examples of each SHOWN in parenthesis):

• environment control (CHDIR, GETENV, PUTENV, GETCWD, ETC).
• file and directory management (_OPENDIR, _READDIR, _STAT, etc).
• process management (_GETPID, _FORK, _WAIT, _KILL, etc).
• configuration management (_GETUID, _GETHOSTNAME, etc).
• system error processing (_ERRNO, _SYSERRLIST).
• REGULAR expression processing (_REGEX).
• interprocess communications (_SOCKET, _CONNECT, _SEND, _RECV, etc).

In addition to the standard language features, uni-REXX includes a rich set of functions designed specifically for a UNIX environment. These functions can be classified into the following categories (with examples of each shown in parenthesis):

Not at all. REXX includes an instruction that allows you to determine the environment in which your PROGRAM is running. PARSE SOURCE will give you a string in which the first TOKEN is the NAME of the system where the program is running. For uni-REXX, this is "UNIX"; on the mainframe, it would be "CMS" or "TSO". Then you can put conditional processing into your program based on the current execution environment. In a program that needed to display a current listing of files, you might set your master source up something like this:

parse source env:

Not at all. Rexx includes an instruction that allows you to determine the environment in which your program is running. PARSE SOURCE will give you a string in which the first token is the name of the system where the program is running. For uni-REXX, this is "UNIX"; on the mainframe, it would be "CMS" or "TSO". Then you can put conditional processing into your program based on the current execution environment. In a program that needed to display a current listing of files, you might set your master source up something like this:

parse source env:

"Yes, you can port existing applications with a minimum of modification". Only the following modifications are normally REQUIRED:

• references to DISK file names.
• statements in your program that execute operating system commands -- The exceptions are EXECIO and GLOBALV; uni-REXX has implemented these popular mainframe commands and made them accessible from within a uni-REXX program.
• portions of your program that stack data for use by another, non-Rexx program after the Rexx program has completed EXECUTION -- Programs in UNIX run in individual PROCESSES, and there is no concept of a persistent.
• stack available to all processes. The modifications required here are usually simple, and TWG Technical Support is available to provide guidance, suggestions, and sample solutions.

If your Rexx program is primarily a series of operating system commands, then it may not be a good candidate for direct portation. It may be, however, that the functions it performs have reasonable counterparts in the UNIX environment and the program can be converted to execute the equivalent UNIX functions. 

"Yes, you can port existing applications with a minimum of modification". Only the following modifications are normally required:

If your Rexx program is primarily a series of operating system commands, then it may not be a good candidate for direct portation. It may be, however, that the functions it performs have reasonable counterparts in the UNIX environment and the program can be converted to execute the equivalent UNIX functions. 

uni-REXX can be used for a wide variety of purposes. The most popular include:

• AUTOMATING system administration tasks.
• DEVELOPMENT of end-user applications.
• rapid prototyping of compiled-LANGUAGE applications.

uni-REXX can also be embedded as a scripting language or system-control language in other applications.

uni-REXX can be used for a wide variety of purposes. The most popular include:

uni-REXX can also be embedded as a scripting language or system-control language in other applications.

uni-REXX is now AVAILABLE on SUN's Solaris 7/8/9, H/P's HP/UX 10/11, IBM's AIX 4/5, SGI's IRIX 5/6, NCR UNIX, LINUX Intel and S/390.

uni-REXX is now available on SUN's Solaris 7/8/9, H/P's HP/UX 10/11, IBM's AIX 4/5, SGI's IRIX 5/6, NCR UNIX, Linux Intel and S/390.

uni-REXX is a UNIX IMPLEMENTATION of IBM's popular Rexx programming language as DEFINED by M. F. Cowlishaw in the Rexx Language.

uni-REXX is a UNIX implementation of IBM's popular Rexx programming language as defined by M. F. Cowlishaw in the Rexx Language.