Table of contents:

• Block Letters Definitions Needed
• Can I run MVS-Rexx with source instream (inside the jcl)? (2 messages)
• Check existence of dsname with wildcards (2 messages)
• Check existence of dsname with wildcards -Reply (3 messages)
• Check existence of dsname with wildcards -Reply -Reply (5 messages)
• Check existence of dsname with wildcards -Reply -Reply -Reply (6 messages)
• Check existence of dsname with wildcards -Reply -Reply -Reply -Reply
• Creating a log for my Rexx programs (3 messages)
• DB2 access through REXX and OS/2 (2 messages)
• ENQ information from REXX (MVS) (2 messages)
• ENQ information from REXX (MVS) -Reply (2 messages)
• Emails in REXXLIST and comp.lang.rexx as well (2 messages)
• FW: Check existence of dsname with wildcards -Reply
• FW: Piping output of command into a shell variable
• Great Sex Site
• HELP !! How to fileread into an array .
• Internet Services
• Is there a compiler for REXX? (2 messages)
• JCL needed for Cobol to call REXX
• JCL needed for Cobol to call REXX -Reply (2 messages)
• New REXX Code Formatter/2 release
• Newbie Question: How to Make REXX Submit JCL (2 messages)
• Newbie Question: How to Make REXX Submit JCL -Reply (2 messages)
• Pipe problem (2 messages)
• Piping into Rexxes--or not
• Piping output of command into a shell variable (4 messages)
• REXX Newbie Qn. (4 messages)
• Regina/REXX Coding Examples (4 messages)
• RexxLA newsletter for December
• Symbols (3 messages)
• WANTED: REXX FOR WIN95 (2 messages)
• What is faster?
• adding my load module as a tso command (7 messages)
• adding my load module as a tso command -Reply (2 messages)
• baffled by a parse (10 messages)
• cms lines() bug?
• lowercase (3 messages)
• suppressing output buffering

1. Block Letters Definitions Needed
   • Block Letters Definitions Needed (27 lines)
     From: Brozewicz Robert F <brozewicz.rf@MELLON.COM>

2. Can I run MVS-Rexx with source instream (inside the jcl)?
   • Can I run MVS-Rexx with source instream (inside the jcl)? (19 lines)
     From: Julio Caragiulo <JVCBH@CUNYVM.CUNY.EDU>
   • Re: Can I run MVS-Rexx with source instream (inside the jcl)? (30 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>

3. Check existence of dsname with wildcards
   • Check existence of dsname with wildcards (27 lines)
     From: Clara Trzeciak <C.Trzeciak@ALCATEL.DE>
   • Re: Check existence of dsname with wildcards (44 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>

4. Check existence of dsname with wildcards -Reply
   • Re: Check existence of dsname with wildcards -Reply (34 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply (42 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
   • Check existence of dsname with wildcards -Reply (31 lines)
     From: Edgar Donaldson <edonalds@TUC.COM>

5. Check existence of dsname with wildcards -Reply -Reply
   • Re: Check existence of dsname with wildcards -Reply -Reply (43 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply (64 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
   • Check existence of dsname with wildcards -Reply -Reply (38 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply (38 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply (50 lines)
     From: Metz, Seymour <smetz@NSF.GOV>

6. Check existence of dsname with wildcards -Reply -Reply -Reply
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (28 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (31 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (38 lines)
     From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (58 lines)
     From: Metz, Seymour <smetz@NSF.GOV>
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (25 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply (37 lines)
     From: Metz, Seymour <smetz@NSF.GOV>

7. Check existence of dsname with wildcards -Reply -Reply -Reply -Reply
   • Re: Check existence of dsname with wildcards -Reply -Reply -Reply -Reply (46 lines)
     From: Mike Hall <MJHall@US.FORTIS.COM>

8. Creating a log for my Rexx programs
   • Re: Creating a log for my Rexx programs (33 lines)
     From: Mike Ruskai <thanny@SPAMBEGONE.HOME.COM>
   • Re: Creating a log for my Rexx programs (35 lines)
     From: jpedone_no_spam@FLASH.NET
   • Re: Creating a log for my Rexx programs (15 lines)
     From: Buck, Peter INS <PBUCK@ITP.EDS.COM>

9. DB2 access through REXX and OS/2
   • Re: DB2 access through REXX and OS/2 (38 lines)
     From: Mike Organek <morganek@EROLS.COM>
   • Re: DB2 access through REXX and OS/2 (61 lines)
     From: Harald Wilhelm <Harald_Wilhelm@HAWI.DE>

10. ENQ information from REXX (MVS)
    • ENQ information from REXX (MVS) (60 lines)
      From: Doug Nadel <somebody@MINDSPRING.COM>
    • Re: ENQ information from REXX (MVS) (78 lines)
      From: Graham P Taylor <graham@DOCTORBOOTSNOSPAM.DEMON.CO.UK>

11. ENQ information from REXX (MVS) -Reply
    • ENQ information from REXX (MVS) -Reply (280 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>
    • ENQ information from REXX (MVS) -Reply (26 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>

12. Emails in REXXLIST and comp.lang.rexx as well
    • Emails in REXXLIST and comp.lang.rexx as well (25 lines)
      From: Vladimir Zabrodsky <zabro@SISBLANSKO.CZ>
    • Re: Emails in REXXLIST and comp.lang.rexx as well (41 lines)
      From: F. Scott Ophof <fsophof@MAIN.BLCLINKS.NET>

13. FW: Check existence of dsname with wildcards -Reply
    • FW: Check existence of dsname with wildcards -Reply (70 lines)
      From: David Seibert <Dave_Seibert@COMPUWARE.COM>

14. FW: Piping output of command into a shell variable
    • FW: Piping output of command into a shell variable (102 lines)
      From: Buck, Peter INS <PBUCK@ITP.EDS.COM>

15. Great Sex Site
    • Great Sex Site (9 lines)
      From: greatlinksite@MAIL.COM

16. HELP !! How to fileread into an array .
    • Re: HELP !! How to fileread into an array . (65 lines)
      From: Doug Rickman <doug@HOTROCKS.MSFC.NASA.GOV>

17. Internet Services
    • Internet Services (8 lines)
      From: hammer@COASTINTERNET.COM

18. Is there a compiler for REXX?
    • Is there a compiler for REXX? (14 lines)
      From: Peter <peter@HELPNET.COM.AU>
    • Re: Is there a compiler for REXX? (28 lines)
      From: Doug Rickman <doug@HOTROCKS.MSFC.NASA.GOV>

19. JCL needed for Cobol to call REXX
    • Re: JCL needed for Cobol to call REXX (31 lines)
      From: paulr <paulr@BIX.COM>

20. JCL needed for Cobol to call REXX -Reply
    • Re: JCL needed for Cobol to call REXX -Reply (43 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>
    • Re: JCL needed for Cobol to call REXX -Reply (34 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>

21. New REXX Code Formatter/2 release
    • New REXX Code Formatter/2 release (27 lines)
      From: Bob Eberle <rke_software@IBM.NET>

22. Newbie Question: How to Make REXX Submit JCL
    • Newbie Question: How to Make REXX Submit JCL (23 lines)
      From: Polanik, Joseph (Joseph)** CTR ** <jpolanik@LUCENT.COM>
    • Re: Newbie Question: How to Make REXX Submit JCL (34 lines)
      From: Metz, Seymour <smetz@NSF.GOV>

23. Newbie Question: How to Make REXX Submit JCL -Reply
    • Newbie Question: How to Make REXX Submit JCL -Reply (26 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>
    • Re: Newbie Question: How to Make REXX Submit JCL -Reply (24 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>

24. Pipe problem
    • Pipe problem (31 lines)
      From: John Beaulieu <jbeauli@IBM.NET>
    • Re: Pipe problem (31 lines)
      From: Reynolds Rupert <rupert.reynolds@HYDER.COM>

25. Piping into Rexxes--or not
    • Piping into Rexxes--or not (105 lines)
      From: Buck, Peter INS <PBUCK@ITP.EDS.COM>

26. Piping output of command into a shell variable
    • Re: Piping output of command into a shell variable (26 lines)
      From: dwp <info@BOOTSTRAP.CO.NZ>
    • Re: Piping output of command into a shell variable (40 lines)
      From: Metz, Seymour <smetz@NSF.GOV>
    • Piping output of command into a shell variable (40 lines)
      From: Tobias Ernst <tobi@BLAND.FIDO.DE>
    • Re: Piping output of command into a shell variable (74 lines)
      From: Buck, Peter INS <PBUCK@ITP.EDS.COM>

27. REXX Newbie Qn.
    • Re: REXX Newbie Qn. (33 lines)
      From: Ian Collier <imc@COMLAB.OX.AC.UK>
    • Re: REXX Newbie Qn. (32 lines)
      From: Mike Ruskai <thanny@SPAMBEGONE.HOME.COM>
    • Re: REXX Newbie Qn. (35 lines)
      From: Bob Rice <bob@REXXSHOP.COM>
    • Re: REXX Newbie Qn. (21 lines)
      From: Billl Fenlason <billfen@ULSTER.NET>

28. Regina/REXX Coding Examples
    • Regina/REXX Coding Examples (35 lines)
      From: Robert F. Brozewicz Jr. <Robert3085@AOL.COM>
    • Re: Regina/REXX Coding Examples (72 lines)
      From: F. Scott Ophof <fsophof@MAIN.BLCLINKS.NET>
    • Re: Regina/REXX Coding Examples (78 lines)
      From: Buck, Peter INS <PBUCK@ITP.EDS.COM>
    • Re: Regina/REXX Coding Examples (52 lines)
      From: Metz, Seymour <smetz@NSF.GOV>

29. RexxLA newsletter for December
    • RexxLA newsletter for December (35 lines)
      From: F. Scott Ophof <fsophof@MAIN.BLCLINKS.NET>

30. Symbols
    • Symbols (16 lines)
      From: John Beaulieu <jbeauli@IBM.NET>
    • Re: Symbols (25 lines)
      From: Bruce Roy <BRUCE@UCONNVM.UCONN.EDU>
    • Re: Symbols (22 lines)
      From: John Beaulieu <jbeauli@IBM.NET>

31. WANTED: REXX FOR WIN95
    • Re: WANTED: REXX FOR WIN95 (23 lines)
      From: Stawsh Murawski <Stawsh@WINREXX.COM>
    • Re: WANTED: REXX FOR WIN95 (15 lines)
      From: Albert A. Modderkolk <mdd@ADVWEBSYS.COM>

32. What is faster?
    • What is faster? (93 lines)
      From: Vladimir Zabrodsky <zabro@SISBLANSKO.CZ>

33. adding my load module as a tso command
    • adding my load module as a tso command (10 lines)
      From: Eyal Rond <eyal@ISG.CO.IL>
    • Re: adding my load module as a tso command (22 lines)
      From: Metz, Seymour <smetz@NSF.GOV>
    • Re: adding my load module as a tso command (30 lines)
      From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
    • Re: adding my load module as a tso command (21 lines)
      From: Doug Rickman <doug@HOTROCKS.MSFC.NASA.GOV>
    • Re: adding my load module as a tso command (26 lines)
      From: Binyamin Dissen <Binyamin_Dissen@THEOFFICE.NET>
    • Re: adding my load module as a tso command (21 lines)
      From: Frank Clarke <nisus@MINDSPRING.COM>
    • Re: adding my load module as a tso command (67 lines)
      From: Matt Bressler <Matt@SPCI.NET>

34. adding my load module as a tso command -Reply
    • Re: adding my load module as a tso command -Reply (39 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>
    • Re: adding my load module as a tso command -Reply (23 lines)
      From: Mike Hall <MJHall@US.FORTIS.COM>

35. baffled by a parse
    • Re: baffled by a parse (13 lines)
      From: Bob & Deb Levad <blevad@NETINS.NET>
    • baffled by a parse (26 lines)
      From: Roy Gardiner <gardiner@BTINTERNET.COM>
    • Re: baffled by a parse (36 lines)
      From: Buck, Peter INS <PBUCK@ITP.EDS.COM>
    • Re: baffled by a parse (46 lines)
      From: wcclalo@STATCAN.CA
    • Re: baffled by a parse (25 lines)
      From: wcclalo@STATCAN.CA
    • Re: baffled by a parse (26 lines)
      From: Reynolds Rupert <rupert.reynolds@HYDER.COM>
    • Re: baffled by a parse (36 lines)
      From: Metz, Seymour <smetz@NSF.GOV>
    • Re: baffled by a parse (40 lines)
      From: Metz, Seymour <smetz@NSF.GOV>
    • Re: baffled by a parse (34 lines)
      From: F. Scott Ophof <fsophof@MAIN.BLCLINKS.NET>
    • Re: baffled by a parse (45 lines)
      From: Metz, Seymour <smetz@NSF.GOV>

36. cms lines() bug?
    • cms lines() bug? (50 lines)
      From: Paul G. Barnett <Paul@BARNETT.DEMON.CO.UK>

37. lowercase
    • Re: lowercase (26 lines)
      From: Chris Barnabo <irish89@IBM.NET>
    • Re: lowercase (25 lines)
      From: Jack Snodgrass <jack.snodgrass@COMPAQ.COM>
    • Re: lowercase (25 lines)
      From: F. Scott Ophof <fsophof@MAIN.BLCLINKS.NET>

38. suppressing output buffering
    • Re: suppressing output buffering (39 lines)
      From: Mike Ruskai <thanny@SPAMBEGONE.HOME.COM>