🚀 go-pugleaf

On 5/1/2013 12:06 PM, Harold Mains wrote:
> What code is required in a COBOL program to call a REXX exec? One data item
needs to be passed to the REXX and two different data items returned to the
COBOL program.
>
> What code is required in the REXX exec to be called from the COBOL program
> above and handle the data items?
>
>
> Thanks,
>
> Harold Mains
> California State Controller's Office
> ISD Enterprise Systems Support
> Phone (916) 324-7284

You can call a REXX exec from a COBOL program by invoking
(calling) IKJEFTSR passing six parameters:

* full word of zeros (e.g.: 01 zs binary pic s9(9) value 0. )

* address of buffer holding the TSO EXEC command including parameters
   (e.g.: 01 cmd.
             02 pic x(05) value "EXEC ".
             02 pic x(27) value "'SCOMSTO.MY.REXX(RUNNER)' ".
             02 pic x(nn) value " parm_string ".

where 'nn' is the length of the string in quotes.

Note: you may only pass a single parameter; it may have
separate words, but the called exec will only see one
string

* fullword length of buffer (e.g.: 01 bufsz binary pic s9(9) value mm.
      where 'mm' is the length of the cmd data item)

* place to put the return code (e.g.: 01 retcode binary pic s9(9) value 0. )

* place to put the reason code (e.g.: 01 reascode binary pic s9(9) value 0. )

* place to hold an abend code (e.g.: 01 abcode binary pic s9(9) value 0. )

After the call, check the return code value.

Now, the rexx exec will see the parm string you passed, but it
cannot modify it.

----

To access REXX variables from a COBOL program, you need to
have an exec at the top of the chain: the exec can CALL
your COBOL program and your COBOL program can access rexx
variables in the calling exec using the IKJCT441 service

Alternatively, your top level exec can invoke your COBOL
program using ADDRESS LINKMVS or ADDRESS LINKPGM, but this
is not the direction you seem to be heading.

----

   http://www.trainersfriend.com/TSO_Clist_REXX_Dialog_Mgr/a780descrpt.htm

Hope this helps.


--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
   + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
     for training dollars at
   http://www.trainersfriend.com/ROI/roi.html

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

On 2013-05-01, at 12:06, Harold Mains wrote:

> What code is required in a COBOL program to call a REXX exec?    One data item needs to be passed to the REXX and two different data items returned to the COBOL program.
> 
> What code is required in the REXX exec to be called from the COBOL program above and handle the data items?
>  
The interfaces are described in:

Title: z/OS V1R13.0 TSO/E REXX Reference
Document Number: SA22-7790-10

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A3A0/12.0
12.0 Chapter 12. TSO/E REXX programming services

-- gil

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

Yes I know of this manual.  Unfortunately, the only example this manual provides is for PL/1, not COBOL.  It does not describe the COBOL code requirements, the REXX code, the JCL and library requirements, and how the COBOL program is to send data to the REXX for processing and how the REXX programs passes data back to the COBOL program for further work. 


Thanks,  

Harold Mains
California State Controller's Office
ISD Enterprise Systems Support
Phone (916) 324-7284

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of Paul Gilmartin
Sent: Wednesday, May 01, 2013 9:26 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

On 2013-05-01, at 12:06, Harold Mains wrote:

> What code is required in a COBOL program to call a REXX exec?    One data item needs to be passed to the REXX and two different data items returned to the COBOL program.
> 
> What code is required in the REXX exec to be called from the COBOL program above and handle the data items?
>  
The interfaces are described in:

Title: z/OS V1R13.0 TSO/E REXX Reference Document Number: SA22-7790-10

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A3A0/12.0
12.0 Chapter 12. TSO/E REXX programming services

-- gil

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

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

See if this manual and COBOL example helps.


  IBM Compiler and Library for REXX on zSeries V1R4 User's Guide and
Reference  (there may be a more current copy, I found the z/OS V1.4 manual)


http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ib
m.zos.r12.rexa100%2Fh1981605302.htm



Lizette

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Harold Mains
Sent: Thursday, May 02, 2013 12:28 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

Yes I know of this manual.  Unfortunately, the only example this manual
provides is for PL/1, not COBOL.  It does not describe the COBOL code
requirements, the REXX code, the JCL and library requirements, and how the
COBOL program is to send data to the REXX for processing and how the REXX
programs passes data back to the COBOL program for further work.


Thanks,

Harold Mains
California State Controller's Office
ISD Enterprise Systems Support
Phone (916) 324-7284

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Paul Gilmartin
Sent: Wednesday, May 01, 2013 9:26 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

On 2013-05-01, at 12:06, Harold Mains wrote:

> What code is required in a COBOL program to call a REXX exec?    One data
item needs to be passed to the REXX and two different data items returned to
the COBOL program.
>
> What code is required in the REXX exec to be called from the COBOL program
above and handle the data items?
>
The interfaces are described in:

Title: z/OS V1R13.0 TSO/E REXX Reference Document Number: SA22-7790-10

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A3A0/12.0
12.0 Chapter 12. TSO/E REXX programming services

-- gil

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

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

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

I have a code example f�r an ISPF Panel <---> COBOL ISPF Panel exit <---> REXX pgm (compiled) call chain.
You can use some parts of it I suppose. Some code snippets:

Panel:
------
"PANEXIT ((X1,X2,X3,X4),LOAD,PANEXIT,&XD)"

COBOL pgm:
----------
IDENTIFICATION DIVISION.
 PROGRAM-ID.
     PANEXIT.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 6 Line(s) not Displayed
 SPECIAL-NAMES.
     SYSIN IS RETPARMS.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   88 Line(s) not Displayed
 DATA DIVISION.
/
 WORKING-STORAGE SECTION.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 5 Line(s) not Displayed
 77  W-LENGTH-OF-VARIABLES       PIC S9(9) COMP.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 2 Line(s) not Displayed
 01  RXX-EXITDATA-H.
     05  RXX-EXITDATA-LEN        PIC S9(4) COMP.
     05  RXX-EXITDATA            PIC S9(9) COMP.
     05  RXX-EXITDATA-X REDEFINES RXX-EXITDATA PIC X(4).
 01  RXX-PANEL-NAME-H.
     05  RXX-PANEL-NAME-LEN      PIC S9(4) COMP.
     05  RXX-PANEL-NAME          PIC X(8).
 01  RXX-PANEL-SECTION-H.
     05  RXX-PANEL-SECTION-LEN   PIC S9(4) COMP.
     05  RXX-PANEL-SECTION       PIC X.
 01  RXX-MESSAGE-ID-H.
     05  RXX-MESSAGE-ID-LEN      PIC S9(4) COMP.
     05  RXX-MESSAGE-ID          PIC X(8).
 01  RXX-NUMBER-OF-VARIABLES-H.
     05  RXX-NUMBER-OF-VARIABLES-LEN PIC S9(4) COMP.
     05  RXX-NUMBER-OF-VARIABLES PIC S9(9) COMP.
     05  RXX-NUMBER-OF-VARIABLES-X
         REDEFINES RXX-NUMBER-OF-VARIABLES PIC X(4).
 01  RXX-LENGTH-OF-VARIABLES-H.
     05  RXX-LENGTH-OF-VARIABLES-LEN PIC S9(4) COMP.
     05  RXX-LENGTH-OF-VARIABLES PIC S9(9) COMP.
     05  RXX-LENGTH-OF-VARIABLES-X
         REDEFINES RXX-LENGTH-OF-VARIABLES PIC X(4).
 01  RXX-ARRAY-OF-VAR-NAMES-H.
     05  RXX-ARRAY-OF-VAR-NAMES-LEN PIC S9(4) COMP.
     05  RXX-ARRAY-OF-VAR-NAMES.
         15  RXX-VARNAME OCCURS 10
                         DEPENDING ON RXX-NUMBER-OF-VARIABLES
                         INDEXED BY IX-RXX-NAME PIC X(8).
 01  RXX-ARRAY-OF-VAR-LENGTHS-H.
     05  RXX-ARRAY-OF-VAR-LENGTHS-LEN PIC S9(4) COMP.
     05  RXX-ARRAY-OF-VAR-LENGTHS.
         15  RXX-VARLEN  OCCURS 10
                         DEPENDING ON RXX-NUMBER-OF-VARIABLES
                        INDEXED BY IX-RXX-LEN PIC S9(9) COMP.
 01  RXX-STRING-OF-VAR-VALUES-H.
     05  RXX-STRING-OF-VAR-VALUES-LEN PIC S9(4) COMP.
     05  RXX-STRING-OF-VAR-VALUES.
         15  RXX-STRVAL OCCURS 4000
             DEPENDING ON RXX-LENGTH-OF-VARIABLES
                                 PIC X.
/
 LINKAGE SECTION.
 01  EXITDATA                    PIC S9(9) COMP.
01  PANEL-NAME                  PIC X(8).
 01  PANEL-SECTION               PIC X.
 01  MESSAGE-ID                  PIC X(8).
 01  NUMBER-OF-VARIABLES         PIC S9(9) COMP.
 01  ARRAY-OF-VAR-NAMES.
     05  VARNAME OCCURS 10 DEPENDING ON NUMBER-OF-VARIABLES
                 INDEXED BY IX-NAME  PIC X(8).
 01  ARRAY-OF-VAR-LENGTHS.
     05  VARLEN  OCCURS 10 DEPENDING ON NUMBER-OF-VARIABLES
                 INDEXED BY IX-LEN   PIC S9(9) COMP.
 01  STRING-OF-VAR-VALUES.
     05  STRVAL OCCURS 4000 DEPENDING ON RXX-LENGTH-OF-VARIABLES
                                 PIC X.
/
 PROCEDURE DIVISION USING EXITDATA
                          PANEL-NAME
                          PANEL-SECTION
                          MESSAGE-ID
                          NUMBER-OF-VARIABLES
                          ARRAY-OF-VAR-NAMES
                          ARRAY-OF-VAR-LENGTHS
                          STRING-OF-VAR-VALUES.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   15 Line(s) not Displayed
     PERFORM VARYING IX-LEN FROM 1 BY 1
       UNTIL IX-LEN > NUMBER-OF-VARIABLES
       ADD VARLEN (IX-LEN) TO RXX-LENGTH-OF-VARIABLES
     END-PERFORM
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   39 Line(s) not Displayed
     MOVE EXITDATA
       TO RXX-EXITDATA
     MOVE LENGTH OF RXX-EXITDATA
       TO RXX-EXITDATA-LEN
     MOVE PANEL-NAME
       TO RXX-PANEL-NAME
     MOVE LENGTH OF RXX-PANEL-NAME
       TO RXX-PANEL-NAME-LEN
     MOVE PANEL-SECTION
       TO RXX-PANEL-SECTION
     MOVE LENGTH OF RXX-PANEL-SECTION
       TO RXX-PANEL-SECTION-LEN
     MOVE MESSAGE-ID
       TO RXX-MESSAGE-ID
     MOVE LENGTH OF RXX-MESSAGE-ID
       TO RXX-MESSAGE-ID-LEN
     MOVE NUMBER-OF-VARIABLES
       TO RXX-NUMBER-OF-VARIABLES
     MOVE LENGTH OF RXX-NUMBER-OF-VARIABLES
       TO RXX-NUMBER-OF-VARIABLES-LEN
     MOVE LENGTH OF RXX-LENGTH-OF-VARIABLES
       TO RXX-LENGTH-OF-VARIABLES-LEN
     MOVE ARRAY-OF-VAR-NAMES
       TO RXX-ARRAY-OF-VAR-NAMES
     MOVE LENGTH OF RXX-ARRAY-OF-VAR-NAMES
       TO RXX-ARRAY-OF-VAR-NAMES-LEN
     MOVE ARRAY-OF-VAR-LENGTHS
       TO RXX-ARRAY-OF-VAR-LENGTHS
     MOVE LENGTH OF RXX-ARRAY-OF-VAR-LENGTHS
       TO RXX-ARRAY-OF-VAR-LENGTHS-LEN
     MOVE STRING-OF-VAR-VALUES
       TO RXX-STRING-OF-VAR-VALUES
     MOVE LENGTH OF RXX-STRING-OF-VAR-VALUES
       TO RXX-STRING-OF-VAR-VALUES-LEN
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 3 Line(s) not Displayed
     CALL 'PANEXIT2' USING BY REFERENCE
                     RXX-EXITDATA-H
                     RXX-PANEL-NAME-H
                     RXX-PANEL-SECTION-H
                     RXX-MESSAGE-ID-H
                     RXX-NUMBER-OF-VARIABLES-H
                     RXX-LENGTH-OF-VARIABLES-H
                     RXX-ARRAY-OF-VAR-NAMES-H
                     RXX-ARRAY-OF-VAR-LENGTHS-H
                     RXX-STRING-OF-VAR-VALUES-H
*
     ACCEPT RXX-EXITDATA-X FROM RETPARMS
     ACCEPT RXX-PANEL-NAME FROM RETPARMS
     ACCEPT RXX-PANEL-SECTION FROM RETPARMS
     ACCEPT RXX-MESSAGE-ID FROM RETPARMS
     ACCEPT RXX-NUMBER-OF-VARIABLES-X FROM RETPARMS
     ACCEPT RXX-LENGTH-OF-VARIABLES-X FROM RETPARMS
     ACCEPT RXX-ARRAY-OF-VAR-NAMES FROM RETPARMS
     ACCEPT RXX-ARRAY-OF-VAR-LENGTHS FROM RETPARMS
     ACCEPT RXX-STRING-OF-VAR-VALUES FROM RETPARMS
     MOVE +81 TO W-1
     PERFORM  UNTIL W-1 > W-LENGTH-OF-VARIABLES
         COMPUTE W-2 = W-LENGTH-OF-VARIABLES - W-1 + 1
         ACCEPT RXX-STRING-OF-VAR-VALUES (W-1 : W-2)
           FROM RETPARMS
         ADD +80 TO W-1
     END-PERFORM
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   39 Line(s) not Displayed
     MOVE RXX-EXITDATA
       TO EXITDATA
     MOVE RXX-PANEL-NAME
       TO PANEL-NAME
     MOVE RXX-PANEL-SECTION
       TO PANEL-SECTION
     MOVE RXX-MESSAGE-ID
       TO MESSAGE-ID
     MOVE RXX-NUMBER-OF-VARIABLES
       TO NUMBER-OF-VARIABLES
     MOVE RXX-ARRAY-OF-VAR-NAMES
       TO ARRAY-OF-VAR-NAMES
     MOVE RXX-ARRAY-OF-VAR-LENGTHS
       TO ARRAY-OF-VAR-LENGTHS
     MOVE RXX-STRING-OF-VAR-VALUES
       TO STRING-OF-VAR-VALUES
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 6 Line(s) not Displayed
     GOBACK.

REXX pgm:
---------
/* REXX
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -   228 Line(s) not Displayed
  Parse Arg in_exitdata, in_panelname, in_panelsect, in_msgid, in_numofvars,
           ,in_lenofvarvalues, in_arrayofnames, in_arrayoflengths,
           ,in_arrayofvalues
  numofvars = C2d(in_numofvars) - 1
  lenofvarvalues = C2d(in_lenofvarvalues)
  panxrxxvallen = C2d(Substr(in_arrayoflengths,1,4))
  panxrxx = Strip(Substr(in_arrayofnames,1,8))
  panxrxxl = Length(panxrxx)
  panxrxxvar = Substr(in_arrayofnames,1,8)
  If  panxrxxvallen > 0        Then ,
      panxrxxval = Substr(in_arrayofvalues,1,panxrxxvallen)
   Else ,
      panxrxxval = ''
  arrayofnames = ''
  x1 = Substr(in_arrayofnames,9)
  Do  While  x1 ^= ''
      Parse Value  x1  With  x2 9 x1
      arrayofnames = arrayofnames x2
      End
  arrayofnames = Space(arrayofnames)
  arrayoflengths = ''
  x1 = Substr(in_arrayoflengths,5)
  Do  While  x1 ^= ''
      Parse Value  x1  With  x2 5 x1
      arrayoflengths = arrayoflengths C2d(x2)
      End
  arrayoflengths = Space(arrayoflengths)
  arrayofvalues = Substr(in_arrayofvalues,panxrxxvallen + 1)
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  4 Line(s) not Displayed
  If  x_testmode                     Then  Do
      Say 'PANEXIT2 in_exitdata       >'C2x(in_exitdata) !!'<'
      Say 'PANEXIT2 in_panelname      >'in_panelname     !!'<'
      Say 'PANEXIT2 in_panelsect      >'in_panelsect     !!'<'
      Say 'PANEXIT2 in_msgid          >'in_msgid         !!'<'
      Say 'PANEXIT2 in_numofvars      >'C2d(in_numofvars)!!'<'
      Say 'PANEXIT2 lenofvarvalues    >'lenofvarvalues   !!'<'
      Say 'PANEXIT2 in_arrayofnames   >'in_arrayofnames  !!'<'
      Say 'PANEXIT2 in_arrayoflen.(1) >'panxrxxl         !!'<'
      Say 'PANEXIT2 in_arrayofvalues  >'in_arrayofvalues !!'<'
      End
  rec. = ''
  rec.1 = in_exitdata
  rec.2 = in_panelname
  rec.3 = in_panelsect
  rec.4 = in_msgid
  rec.5 = in_numofvars
  rec.6 = in_lenofvarvalues
  rec.7 = in_arrayofnames
  rec.8 = in_arrayoflengths
  rec.9 = Left(in_arrayofvalues,Max(lenofvarvalues,80))
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 44 Line(s) not Displayed
  rec.0 = 9
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 13 Line(s) not Displayed
  Address Tso
  'ALLOC F(SYSIN) NEW REUSE' ,
    'RECFM(F B) LRECL(80) BLKSIZE(800) TRACKS SPACE(1 1)'
  'EXECIO * DISKW SYSIN (STEM REC. FINIS'
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  2 Line(s) not Displayed
  Exit Strip(rcode)
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -   462 Line(s) not Displayed



Regards
Thomas Berg
____________________________________________________________________
Thomas Berg   Specialist   z/OS\RQM\IT Delivery   SWEDBANK AB (Publ


> -----Original Message-----
> From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On
> Behalf Of Harold Mains
> Sent: Thursday, May 02, 2013 9:28 PM
> To: TSO-REXX@VM.MARIST.EDU
> Subject: Re: [TSO-REXX] COBOL calling REXX
>
> Yes I know of this manual.  Unfortunately, the only example this manual
> provides is for PL/1, not COBOL.  It does not describe the COBOL code
> requirements, the REXX code, the JCL and library requirements, and how
> the COBOL program is to send data to the REXX for processing and how
> the REXX programs passes data back to the COBOL program for further
> work.
<snip>
> -----Original Message-----
> From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Wednesday, May 01, 2013 9:26 PM
> To: TSO-REXX@VM.MARIST.EDU
> Subject: Re: [TSO-REXX] COBOL calling REXX
>
> On 2013-05-01, at 12:06, Harold Mains wrote:
>
> > What code is required in a COBOL program to call a REXX exec?    One
> data item needs to be passed to the REXX and two different data items
> returned to the COBOL program.
> >
> > What code is required in the REXX exec to be called from the COBOL
> program above and handle the data items?
> >
> The interfaces are described in:
>
> Title: z/OS V1R13.0 TSO/E REXX Reference Document Number: SA22-7790-10
>
> http://publibz.boulder.ibm.com/cgi-
> bin/bookmgr_OS390/BOOKS/IKJ4A3A0/12.0
> 12.0 Chapter 12. TSO/E REXX programming services

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

I am sending you the code I used to call a Rexx which walked the control
blocks to get the info on a tape file which was opened, written to, but not
yet cataloged. I cannot post it here because it screws up the columns (I
just LOATHE proportional spacing)

Mickey



-----Original Message-----
From: Harold Mains
Sent: Thursday, May 02, 2013 3:28 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

Yes I know of this manual.  Unfortunately, the only example this manual
provides is for PL/1, not COBOL.  It does not describe the COBOL code
requirements, the REXX code, the JCL and library requirements, and how the
COBOL program is to send data to the REXX for processing and how the REXX
programs passes data back to the COBOL program for further work.


Thanks,

Harold Mains
California State Controller's Office
ISD Enterprise Systems Support
Phone (916) 324-7284

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Paul Gilmartin
Sent: Wednesday, May 01, 2013 9:26 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

On 2013-05-01, at 12:06, Harold Mains wrote:

> What code is required in a COBOL program to call a REXX exec?    One data
> item needs to be passed to the REXX and two different data items returned
> to the COBOL program.
>
> What code is required in the REXX exec to be called from the COBOL program
> above and handle the data items?
>
The interfaces are described in:

Title: z/OS V1R13.0 TSO/E REXX Reference Document Number: SA22-7790-10

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A3A0/12.0
12.0 Chapter 12. TSO/E REXX programming services

-- gil

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

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

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

On 2013-05-08, at 10:31, Mickey wrote:

> I am sending you the code ... I cannot post it here because it screws up the columns (I
> just LOATHE proportional spacing)
>  
Proportional spacing shouldn't be an insuperable problem.
The recipient can save the message to a file then view that
with a monospaced-savvy viewer.

But, yes, I LOATHE proportional spacing when viewing code.
And I LOATHE mailers that convert '>' (as in Rexx traces)
to quotation marks.  And that enforce the conventions of

    Content-type text/plain;format=flowed

And I used to LOATHE MS Exchange for interpreting numeric
JCL option values as Quoted-Printable encoded characters.

Leave my text alone!

-- gil

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

-----Original Message-----
From: Paul Gilmartin
Sent: Wednesday, May 08, 2013 1:07 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

On 2013-05-08, at 10:31, Mickey wrote:

> I am sending you the code ... I cannot post it here because it screws up
> the columns (I
> just LOATHE proportional spacing)
>
Proportional spacing shouldn't be an insuperable problem.
The recipient can save the message to a file then view that
with a monospaced-savvy viewer.

But, yes, I LOATHE proportional spacing when viewing code.
And I LOATHE mailers that convert '>' (as in Rexx traces)
to quotation marks.  And that enforce the conventions of

    Content-type text/plain;format=flowed

And I used to LOATHE MS Exchange for interpreting numeric
JCL option values as Quoted-Printable encoded characters.

Leave my text alone!

-- gil


My feelings exactly Gil, I too wish MS would learn to leave things as they
are. If I want a proportional font, I will select one.

Mickey

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

What am I missing?  Since this listserv uses plain text, and since my email
client allows me to select a different default font for plain text emails
(as opposed to RTF or HTML), I always see these emails in a fixed-spacing
font.  Clearly not everyone is in the same case, but how does it work for
you guys?

---
Bob Bridges
  rhbridg@attglobal.net, cell 336 382-7313
  rbridges@InfoSecInc.com

/* Sometimes you feel like a nut.  After a day of working on a walnut farm,
you don't.  -Mike Rowe of the TV show "Dirty Jobs" */

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Mickey
Sent: Wednesday, May 8, 2013 13:28

My feelings exactly Gil, I too wish MS would learn to leave things as they
are. If I want a proportional font, I will select one.

-----Original Message-----
From: Paul Gilmartin
Sent: Wednesday, May 08, 2013 1:07 PM

Proportional spacing shouldn't be an insuperable problem.
The recipient can save the message to a file then view that
with a monospaced-savvy viewer.

But, yes, I LOATHE proportional spacing when viewing code.
And I LOATHE mailers that convert '>' (as in Rexx traces)
to quotation marks.  And that enforce the conventions of

    Content-type text/plain;format=flowed

And I used to LOATHE MS Exchange for interpreting numeric
JCL option values as Quoted-Printable encoded characters.

Leave my text alone!

--- On 2013-05-08, at 10:31, Mickey wrote:
> I am sending you the code ... I cannot post it here because it screws up
> the columns (I just LOATHE proportional spacing)

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

The operative words there being "my email client". Most webmail clients do
not allow you to select the font.

Mickey

-----Original Message-----
From: Bob Bridges
Sent: Thursday, May 23, 2013 12:08 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] COBOL calling REXX

What am I missing?  Since this listserv uses plain text, and since my email
client allows me to select a different default font for plain text emails
(as opposed to RTF or HTML), I always see these emails in a fixed-spacing
font.  Clearly not everyone is in the same case, but how does it work for
you guys?

---
Bob Bridges
  rhbridg@attglobal.net, cell 336 382-7313
  rbridges@InfoSecInc.com

/* Sometimes you feel like a nut.  After a day of working on a walnut farm,
you don't.  -Mike Rowe of the TV show "Dirty Jobs" */

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Mickey
Sent: Wednesday, May 8, 2013 13:28

My feelings exactly Gil, I too wish MS would learn to leave things as they
are. If I want a proportional font, I will select one.

-----Original Message-----
From: Paul Gilmartin
Sent: Wednesday, May 08, 2013 1:07 PM

Proportional spacing shouldn't be an insuperable problem.
The recipient can save the message to a file then view that
with a monospaced-savvy viewer.

But, yes, I LOATHE proportional spacing when viewing code.
And I LOATHE mailers that convert '>' (as in Rexx traces)
to quotation marks.  And that enforce the conventions of

    Content-type text/plain;format=flowed

And I used to LOATHE MS Exchange for interpreting numeric
JCL option values as Quoted-Printable encoded characters.

Leave my text alone!

--- On 2013-05-08, at 10:31, Mickey wrote:
> I am sending you the code ... I cannot post it here because it screws up
> the columns (I just LOATHE proportional spacing)

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

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

On 2013-05-23 17:52, Mickey wrote:
> The operative words there being "my email client". Most webmail clients do
> not allow you to select the font.
>
Well, I don't use webmail; I use an IMAP client for all my email
accounts.  But I know that COMCAST doesn't support IMAP.  (Well,
I see they're offering a beta signup for IMAP.)

And I read IBM-MAIN off https://listserv.ua.edu, which does allow
selecting a monospaced font, when reading, but not when composing.
And when I try to Reply to a message on that listserv that contains
BASE64 encoded Unicode, it shows me the unrendered BASE64.  Things
are tough all over.


> -----Original Message-----
> From: Bob Bridges
> Sent: Thursday, May 23, 2013 12:08 PM
>
> What am I missing?  Since this listserv uses plain text, and since my email
> client allows me to select a different default font for plain text emails
> (as opposed to RTF or HTML), I always see these emails in a fixed-spacing
> font.  Clearly not everyone is in the same case, but how does it work for
> you guys?

-- gil

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

Ah, webmail, of course.  I've been using clients on my own PC a long time; I
know webmail exists, but whenever I have to use it myself I teach my client
to go fetch it as soon as possible, and usually after that I forget it
exists even though I know better.  Having to check multiple locations for
email is a real pain.

Nowadays [he says shamefacedly] I use Outlook.  But I promise I use it only
because I have to keep around a copy of Office Pro for my work; otherwise
I'm sure I'd find some satisfactory freeware or shareware client.

---
Bob Bridges
  rhbridg@attglobal.net, cell 336 382-7313
  rbridges@InfoSecInc.com

/* Nor did [C S] Lewis present God's message as "vacuous bromides."  He saw
it as just the opposite: a love so consuming that our natural reaction to it
is shock, almost terror....God's love is fierce, burning, and, like the love
of any real father, troubling; he demands that we love him back with all of
our energy.  In truth, God loves us far more than we want to be loved.  At
times his love feels to us like hatred and tyranny.  No wonder we're tempted
to hate him.  -Joe Sobran */

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Mickey
Sent: Thursday, May 23, 2013 19:53

The operative words there being "my email client". Most webmail clients do
not allow you to select the font.

-----Original Message-----
From: Bob Bridges
Sent: Thursday, May 23, 2013 12:08 PM


What am I missing?  Since this listserv uses plain text, and since my email
client allows me to select a different default font for plain text emails
(as opposed to RTF or HTML), I always see these emails in a fixed-spacing
font.  Clearly not everyone is in the same case, but how does it work for
you guys?

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Mickey
Sent: Wednesday, May 8, 2013 13:28

My feelings exactly Gil, I too wish MS would learn to leave things as they
are. If I want a proportional font, I will select one.

-----Original Message-----
From: Paul Gilmartin
Sent: Wednesday, May 08, 2013 1:07 PM

Proportional spacing shouldn't be an insuperable problem.
The recipient can save the message to a file then view that with a
monospaced-savvy viewer.

But, yes, I LOATHE proportional spacing when viewing code.
And I LOATHE mailers that convert '>' (as in Rexx traces) to quotation
marks.  And that enforce the conventions of

    Content-type text/plain;format=flowed

And I used to LOATHE MS Exchange for interpreting numeric JCL option values
as Quoted-Printable encoded characters.

Leave my text alone!

--- On 2013-05-08, at 10:31, Mickey wrote:
> I am sending you the code ... I cannot post it here because it screws
> up the columns (I just LOATHE proportional spacing)

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

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

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