Menu
▾
▴
oorexx-announce — Open Object Rexx announcements
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(2) |
Aug
(13) |
Sep
|
Oct
(7) |
Nov
(3) |
Dec
(2) |
| 2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(7) |
Oct
(12) |
Nov
(3) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(3) |
Apr
(4) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
(6) |
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(4) |
Mar
|
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
|
Dec
(2) |
| 2013 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
|
Jul
(27) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2014 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Sahananda S. <sah...@gm...> - 2022-12-24 07:37:04
|
The ooRexx (open object Rexx) team is pleased to release ooRexx 5.0.0 and make it generally available to the world via the web from <https://sourceforge.net/projects/oorexx/files/oorexx/5.0.0/> <https://sourceforge.net/projects/oorexx/files/oorexx/5.0.0/>. ooRexx is the object-oriented successor to IBM's famous Rexx language which remains easy to learn, easy to program in and easy to maintain, thanks to keeping up the "human centric" design principle. The "Rexx Language Association (RexxLA)" <https://www.rexxla.org/> <https://www.rexxla.org/> is the owner of the source code, originally donated by IBM in 2004 and improved considerably and continuously since then. Rexx programs can be run unchanged with ooRexx 5.0.0 and can be gradually augmented with the many beneficial new features ooRexx 5.0.0 brings to the table, like redirectable commands from and into running Rexx programs, new and helpful classes like the RexxInfo class, new ability to annotate programs (packages), routines, classes, methods and attributes, ability to easily define multiline strings (e.g. for SQL statements, boiler plate text, base64 encoded binary data ...) and many more. Among the notable improvements are numerous bug fixes compared to its predecessor ooRexx 4.2.0, noticeable speed improvements over ooRexx 4.2.0 and much more useful functionality. Please consult the file docs/CHANGES.txt for more information. After downloading ooRexx 5.0.0 and installing take a look into the samples directory which contains programs that demonstrate some of its capabilities. The Windows version has numerous examples that demonstrate how to interact with Microsoft Office, Apache Open Office/LibreOffice and many of the Windows infrastructures taking advantage of their OLE (Object Linking and Embedding) interfaces. To get more information and support you can use the ooRexx Sourceforge project's "Tickets" or "Mailing Lists" infrastructure. In addition you may consider joining the non-profit "Rexx Language Association (RexxLA)" for free at <https://www.rexxla.org/members/index.rsp?action=join> <https://www.rexxla.org/members/index.rsp?action=join> where Rexx experts of all kind of Rexx interpreters on all important operating systems are already members, including the language creators and implementers. So download the brand new ooRexx 5.0.0 and start to explore it! Have fun and enjoy! The ooRexx team, cyberspace, December 23rd, 2022 P.S.: Please, if you can, make all of your friends, all of your colleagues and the media you are interested in aware of this great event for ooRexx 5.0.0 (a short e-mail is quickly done)! |
|
From: Alexander S. <ale...@gm...> - 2020-05-19 21:24:44
|
Hello, I have created an update for ooRexxPlugin for IntelliJ IDEA. Your can download it here: https://sourceforge.net/projects/bsf4oorexx/files/Sandbox/aseik/ooRexxIDEA/GA/2.0.0/ The ooRexxPlugin for Intellij IDEA provides IDE support for ooRexx 5.0. A user can create ooRexx projects, write ooRexx programs with syntax highlighting and error reporting, and execute ooRexx programs within the IDE. Additionally, the user can also use various features of the IntelliJ platform e.g. version control, many editing/project management features, etc. IntelliJ IDEA is an integrated development environment (IDE) by JetBrains ( https://www.jetbrains.com/idea/). There is a community edition (free) and an ultimate edition (yearly subscription). The plugin works for both editions. What's new: - ooRexxDoc (auto generation of HTML-Documentation) is integrated into the plugin. It can be used within the plugin (right click on a file or directory -> Create 'ooRexxDoc' Documentation) - Supporting ooRexx 5.0 features - Various bug fixes - Update to newer IntelliJ IDEA platforms I would be happy to get feedback, request for enhancement (RFE), and bug reports here: https://sourceforge.net/p/bsf4oorexx/oorexxplugin/milestone/2.0/ ! Best Regards Alexander |
|
From: Mark M. <mie...@gm...> - 2014-03-05 14:35:02
|
I think you need to change your address yourself. Go to the mailing list page: https://sourceforge.net/p/oorexx/mailman/?source=navbar >From looking at it, you may have to subscribe with your new address and unsubscribe your old address. -- Mark Miesfeld |
|
From: Michael H. <MH...@at...> - 2014-03-05 13:18:38
|
Hello Rexx Team,
since I am retiring from IBM in the near future please change my EMail
from mh...@at... to mh...@ao...
Thx a lot, Michael
________________________________________________________
Mit freundlichen Grüßen ... best regards ...
Michael K. J. Heihs
Technical Solution Architect
Dpt.: 00-625 (GBS AS XIS)
( (+43-1) - 21145 / 4329
ITN: 4331 - 4329
. MH...@at...
IBM Österreich Internationale Büromaschinen Gesellschaft m.b.H.
Obere Donaustraße 95
1020 Vienna
Austria
Sitz: Wien, Firmenbuchgericht: Handelsgericht Wien, FN 80000
From: Mark Miesfeld <mie...@gm...>
To: Open Object Rexx Announcements
<oor...@li...>, ooRexx Dev List
<oor...@li...>, Open Object Rexx Users
<oor...@li...>, RexxLA Members mailing
list <rex...@re...>,
Date: 2014-02-24 05:19
Subject: [Oorexx-announce] Announce: The official release of ooRexx
4.2.0
The Open Object Rexx Project is happy to announce the official release of
oRexx 4.2.0. The installation packages are now available on SourceForge at:
https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0/
ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature
release in some time. There are a large number of new feature requests
that have been implemented in this release. In addition, many reported
bugs have been fixed. Please read the CHANGES document for a list of the
bug tracker items fixed and the feature request tracker items that have
been implemented.
--
The ooRexx Development Team
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-announce mailing list
Oor...@li...
https://lists.sourceforge.net/lists/listinfo/oorexx-announce
|
|
From: Mark M. <mie...@gm...> - 2014-02-24 04:19:25
|
The Open Object Rexx Project is happy to announce the official release of oRexx 4.2.0. The installation packages are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0/ ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. -- The ooRexx Development Team |
|
From: Mark M. <mie...@gm...> - 2014-02-15 22:55:45
|
A quick announcement that the ooTest-4.2.0-snapshot06 package has been updated and is now available for download from SourceForge: https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/? This snapshot represents the current state of the test suite used to test ooRexx 4.2.0. Due to user interest, some changes were made to the test suite and the snapshot was redone. The name of the package was not changed, the older snapshot was replaced by the one produced today. There is no real need to replace the older snapshot on your system unless you are interested in the changes listed below. * An -l option has been added to testOOrexx.rex to write the test results to a log file. An -L option was also added that will append the results to the named log file. By default the log file is overwritten. * An -x option has been added to testOORexx.rex. This option will exclude the test group files listed after the option, from execution. For example, the following command line invocation will exclude the RexxContext.testGroup from being executed: C:\rexx\ooTest-4.2.0-snapshot06>testOORexx.rex -x RexxContext * Some test case failures that were avoidable when run in an unexpected environment were fixed. * The ReadMe.first file has been slightly updated to include some information on some tests that are known to fail when the test suite is run in an unexpected environment. It has always been the hope of the ooRexx development team that users would help test ooRexx by running the test suite and participate in improving the test suite by writing test cases. Any and all questions regarding the test suite, or requests for help in writing test case, are welcome and will be addressed by one of the developers. Thank you, The ooRexx Project Team |
|
From: Mark M. <mie...@gm...> - 2014-02-08 20:36:46
|
A quick announcement that an ooTest-4.2.0-snapshot06 package is now available for download from SourcForge: https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/ This snapshot represents the current state of the test suite used to test ooRexx 4.2.0. There has been a lot of information written on how to use the test suite and that information is available in the ooTest-4.2.0-snapshot06 package. If, after reading that information, there are any questions regarding the test suite, please post a question on any of the lists where discussions concerning ooRexx take place. It has always been the hope of the ooRexx development team that users would help test ooRexx by running the test suite and participate in improving the test suite by writing test cases. Any and all questions regarding the test suite, or requests for help in writing test case, are welcome and will be addressed by one of the developers. Thank you, The ooRexx Project Team |
|
From: Mark M. <mie...@gm...> - 2014-01-31 15:12:11
|
The Open Object Rexx Project is happy to announce a release candidate for oRexx 4.2.0. The installation packages are available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%202%29/ A small number of bugs were discovered in the first release candidate. These have been fixed. All the installation packages have been rebuilt to produce a send release candidate. ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. Testing by the users of ooRexx has definitely contributed to producing a better 4.2.0 release. Continued testing of the release candidate will help ensure that 4.2.0 is a great release. The second release candidate may be your last chance to test that your ooRexx programs work well with the new version of ooRexx. Please test the second release candidate and report any issues uncovered on the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ All users of ooRexx are strongly urged to, at a minimum, run the Rexx programs they use under the release candidate code. All testing done by users of ooRexx is highly appreciated and of great help. This testing is one way for ooRexx users to contribute back to the project. Thank you, The ooRexx Project Team |
|
From: Mark M. <mie...@gm...> - 2014-01-20 17:01:57
|
The Open Object Rexx Project is happy to announce a release candidate for ooRexx 4.2.0. The installation packages are available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%29/ ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. Unless more bug reports are posted, It is anticipated that the official release of ooRexx 4.2.0 will be done in several weeks. This is your last chance to test that your ooRexx programs work well with the new version. Please test the beta and report any issues uncovered on the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ The users of ooRexx are strongly urged to, at a minimum, run the Rexx programs they use under the beta code. All testing done by users of ooRexx is highly appreciated and of great help. This testing is one way for ooRexx users to contribute back to the project. Thank you, The ooRexx Project Team |
|
From: Mark M. <mie...@gm...> - 2014-01-18 21:58:39
|
Installation packages for ooDialog version 4.2.3 are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3/ This is the official release of ooDialog 4.2.3. ooDialog 4.2.3 is a routine update with bug fixes and a few enhancements. The ReadMe file that displays on the SourceForge download page contains a list of the bug fixes and enhancements in 4.2.3. In addition the ooDialog reference manual, in chapter 1, Brief Overview, section 1.5 Current Release contains a complete discussion of the changes in ooDialog 4.2.3 from ooDialog 4.2.2. 4.2.3 has a few new features. It contains the implementations of Request For Enhancements that were submitted to the project on SourceForge. Users of ooDialog are encouraged to submit requests for features or enhancements they would like to see in ooDialog using the Request for Enhancement tracker at: https://sourceforge.net/p/oorexx/feature-requests/?source=navbar The new features in 4.2.3 include implementations of Vista Open File and Save File dialogs, along with a stand alone ooDialog executable. The executable can be used to display information about ooDialog, to run ooDialog programs with not visible console (similar to rexxhide but with a few enhancements,) as a drag-and-drop target for ooDialog programs, and to configure file associations for ooDialog programs. There are no known bugs in ooDialog at the time of this release. Anyone suspecting they have discovered a bug or other problem in ooDialog is encourage to report this using the ooRexx SourceForge tracker for bugs: https://sourceforge.net/p/oorexx/bugs/?source=navbar Beginning with the release of ooDialog 4.2.0, the installation of ooDialog has been decoupled from the interpreter. ooDialog 4.2.3 installs over the top of any ooRexx installation. It replaces the version of ooDialog in the ooRexx installation with ooDialog 4.2.3. This type of ooDialog installation is called an "independent" ooDialog installation to indicate the ooDialog installation is independent of an ooRexx installation and, to a degree, the version of ooRexx installed. ooDialog 4.2.3 requires a minimum ooRexx version of 4.1.0 to be installed on the target computer. Installation is simple, done through a typical Windows installer. Pick the installation package that matches the bitness of the ooRexx installation. I.e., a 32-bit package for a 32-bit ooRexx and a 64-bit package for a 64-bit ooRexx. Note that the bitness of the operating system is not relevant here. If you have installed a 32-bit ooRexx on a Windows 64-bit system, you must install a 32-bit ooDialog. The installer will detect the installed ooRexx, location, and version. If the ooRexx version is less than 4.1.0, or if there is no installed ooRexx, the installer will abort with a message explaining the problem. Otherwise the installer will replace the current ooDialog with ooDialog 4.2.3. -- Mark Miesfeld for the ooRexx Development Team |
|
From: Mark M. <mie...@gm...> - 2013-12-22 23:57:47
|
Installation packages for ooDialog 4.2.3, final release candidate, are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3%20%28release%20canidate%29/ The ooDialog 4.2.3 release is a routine update, providing some incremental improvements and a few bug fixes. ooDialog 4.2.3 can be installed to any ooRexx installation, 4.1.0 or later. 4.2.3 has been in beta now for over 3 weeks with only 1 minor bug reported and fixed. Unless some other bugs are reported in the next few days, it is anticipated that the official release version of ooDialog 4.2.3 will be done on Christmas day 2013. This may be your last chance to ensure your ooDialog applications run correctly before the official release. If problems are discovered please report them immediately using the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ -- The ooRexx Development Team |
|
From: Mark M. <mie...@gm...> - 2013-12-09 05:15:29
|
All - The Open Object Rexx Project is extremely happy to announce the first ooRexx 4.2.0 beta. The first beta installation packages are available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28beta%29/? Installer packages are available for a few operating systems now. Additional files will be added shortly, as they become available. ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. Please test the beta and report any issues uncovered on the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ Note that the development team is limited both in resources and numbers. Most members of the team run with the 4.2.0 code on their system every day and have been continually testing ooRexx 4.2.0 since the release of ooRexx 4.1.0. The bugs that the developers are likely to find, have been found and fixed. The bugs that currently exist in 4.2.0 need to be found by the users of ooRexx. The users of ooRexx are strongly urged to, at a minimum, run the Rexx programs they use under the beta code. Bugs discovered during the beta phase of ooRexx 4.2.0 will be fixed before the final release of 4.2.0. Bugs discovered the day after the final release will not make it into an official release of ooRexx for quite some time. Thank you, The ooRexx Project Team |
|
From: Mark M. <mie...@gm...> - 2013-12-02 04:09:38
|
Installation packages for ooDialog 4.2.3 beta are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3%20%28beta%29/ ooDialog 4.2.3 is an enhancement release, with a large number of new features. The Release Notes and the ReadMe file that displays on the SourceForge download page contain a list of the bug fixes, enhancements, and other changes in 4.2.3. Users of ooDialog should test the beta and report bugs or other problems through the ooRexx SourceForge tracker for bugs: https://sourceforge.net/p/oorexx/bugs/ Beginning with the release of ooDialog 4.2.0, the installation of ooDialog has been decoupled from the interpreter. ooDialog 4.2.3 installs over the top of any ooRexx installation. It replaces the version of ooDialog in the ooRexx installation with ooDialog 4.2.3. This type of ooDialog installation is called an "independent" ooDialog installation to indicate the ooDialog installation is independent of an ooRexx installation and, to a degree, the version of ooRexx installed. ooDialog 4.2.3 requires a minimum ooRexx version of 4.1.0 to be installed on the target computer. Installation is simple, done through a typical Windows installer. Pick the installation package that matches the bitness of the ooRexx installation. I.e., a 32-bit package for a 32-bit ooRexx and a 64-bit package for a 64-bit ooRexx. Note that the bitness of the operating system is not relevant here. If you have installed a 32-bit ooRexx on a Windows 64-bit system, you must install a 32-bit ooDialog. The installer will detect the installed ooRexx, location, and version. If the ooRexx version is less than 4.1.0, or if there is no installed ooRexx, the installer will abort with a message explaining the problem. Otherwise the installer will replace the current ooDialog with ooDialog 4.2.3. -- Mark Miesfeld for the ooRexx Development Team |
|
From: Mickey <mi...@co...> - 2013-07-15 02:04:48
|
No and No Trace I for intermediates Trace R for results only Trace R or I with a ? for interactive, which pauses after each command. The difference between I and R is as follows: A = B + C + D For Trace I, you will see the values for B and C, and the result of the addition, then the values for that and D and the result of that addition For Trace R, you will simple see the final result of the additions From: Wil...@jb... Sent: Wednesday, July 10, 2013 5:24 PM To: Open Object Rexx Announcements Cc: joh...@gm... Subject: Re: [Oorexx-announce] Failure I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... Does this help? William Lightner -------------------------------------------------------------------------------- ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk -------------------------------------------------------------------------------- _______________________________________________ Oorexx-announce mailing list Oor...@li... https://lists.sourceforge.net/lists/listinfo/oorexx-announce |
|
From: Don E K. <kal...@us...> - 2013-07-11 20:27:56
|
I am out of the office until 07/15/2013. TPF Operations Server issues should be opened with a problem management record (PMR) on retain. For TPF Operations Server questions, please contact my backup Lap Lau, be...@us.... For other questions needing immediate attention please contact my manager, Donna Strand, ds...@us.... Note: This is an automated response to your message "Re: [Oorexx-announce] Failure" sent on 07/11/2013 12:12:04. This is the only notification you will receive while this person is away. |
|
From: René J. <rvj...@xs...> - 2013-07-11 19:02:39
|
Glad that we solved this. The next time, can we please not use the announcements list for things other than announcements? I received several complaints from people who have the other lists on digest. Many thanks in advance, René Vincent Jansen On 11 jul. 2013, at 18:12, Wil...@jb... wrote: > You're undoubtedly right. I'm the one out of practice! > > > Thanks, > > > > > From: Rick McGuire <obj...@gm...> > To: Open Object Rexx Announcements <oor...@li...>, > Date: 07/10/2013 04:28 PM > Subject: Re: [Oorexx-announce] Failure > > > > No, the ? prefix has always been required for interactive debug, even on VM/CMS. > > Rick > > > On Wed, Jul 10, 2013 at 5:24 PM, <Wil...@jb...> wrote: > > I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. > > TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. > > On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... > > > Does this help? > > > William Lightner > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce |
|
From: <Wil...@jb...> - 2013-07-11 16:12:15
|
You're undoubtedly right. I'm the one out of practice! Thanks, From: Rick McGuire <obj...@gm...> To: Open Object Rexx Announcements <oor...@li...>, Date: 07/10/2013 04:28 PM Subject: Re: [Oorexx-announce] Failure No, the ? prefix has always been required for interactive debug, even on VM/CMS. Rick On Wed, Jul 10, 2013 at 5:24 PM, <Wil...@jb...> wrote: I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... Does this help? William Lightner ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-announce mailing list Oor...@li... https://lists.sourceforge.net/lists/listinfo/oorexx-announce ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-announce mailing list Oor...@li... https://lists.sourceforge.net/lists/listinfo/oorexx-announce |
|
From: Bob C. <bo...@mc...> - 2013-07-10 22:06:54
|
Yes! Too bad my eyes don't see the spelling errors! Bob ----- Original Message ----- From: William Lightner <Wil...@jb...> To: Open Object Rexx Announcements <oor...@li...> Cc: joh...@gm... Sent: Wed, 10 Jul 2013 16:24:11 -0500 (CDT) Subject: Re: [Oorexx-announce] Failure I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... Does this help? William Lightner |
|
From: Bob C. <bo...@mc...> - 2013-07-10 22:04:37
|
You are correct. Thanks. I try to learn something new every day! Bob ----- Original Message ----- From: Rick McGuire <obj...@gm...> To: Open Object Rexx Announcements <oor...@li...> Sent: Wed, 10 Jul 2013 16:27:48 -0500 (CDT) Subject: Re: [Oorexx-announce] Failure No, the ? prefix has always been required for interactive debug, even on VM/CMS. Rick On Wed, Jul 10, 2013 at 5:24 PM, <Wil...@jb...> wrote: > > I'm not particularly current in the OOREXX implementation, but I spent a > lot of years doing Rexx in VM/CMS. > > TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. > > On some other platforms (most DOS/Windows implementations I've seen) > there's also the '?' prefix, but I don't recall having it, let alone > needing it in VM/CMS. On the other hand, the last time I worked in that > environment was 1996.... > > > Does this help? > > > William Lightner > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > |
|
From: Harsen, M. F <Mark.Harsen@MissouriState.edu> - 2013-07-10 21:59:26
|
I've been programming REXX since the first versions on VM/CMS which replaced EXEC and EXEC2. The "I" stands for "Intermediates", not "Interactive". And yes, I concur that the "?" has always been required for an interactive trace from the birth of REXX. I can't say that some version somewhere didn't do this, but I would think it would violate the language standard. Best Regards, -Mark From: Rick McGuire [mailto:obj...@gm...] Sent: Wednesday, July 10, 2013 4:28 PM To: Open Object Rexx Announcements Subject: Re: [Oorexx-announce] Failure No, the ? prefix has always been required for interactive debug, even on VM/CMS. Rick On Wed, Jul 10, 2013 at 5:24 PM, <Wil...@jb...<mailto:Wil...@jb...>> wrote: I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... Does this help? William Lightner ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-announce mailing list Oor...@li...<mailto:Oor...@li...> https://lists.sourceforge.net/lists/listinfo/oorexx-announce |
|
From: Rick M. <obj...@gm...> - 2013-07-10 21:27:57
|
No, the ? prefix has always been required for interactive debug, even on VM/CMS. Rick On Wed, Jul 10, 2013 at 5:24 PM, <Wil...@jb...> wrote: > > I'm not particularly current in the OOREXX implementation, but I spent a > lot of years doing Rexx in VM/CMS. > > TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. > > On some other platforms (most DOS/Windows implementations I've seen) > there's also the '?' prefix, but I don't recall having it, let alone > needing it in VM/CMS. On the other hand, the last time I worked in that > environment was 1996.... > > > Does this help? > > > William Lightner > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > |
|
From: <Wil...@jb...> - 2013-07-10 21:24:22
|
I'm not particularly current in the OOREXX implementation, but I spent a lot of years doing Rexx in VM/CMS. TRACE I -- 'I' for 'Interactive'. Pauses after each instruction. On some other platforms (most DOS/Windows implementations I've seen) there's also the '?' prefix, but I don't recall having it, let alone needing it in VM/CMS. On the other hand, the last time I worked in that environment was 1996.... Does this help? William Lightner |
|
From: Rick M. <obj...@gm...> - 2013-07-10 21:04:53
|
And I was referring to section 14 in Mike's book. On Wed, Jul 10, 2013 at 4:59 PM, Bob Cox <bo...@mc...> wrote: > Must be my error. I'm using Mike Cowlishaw's book "The Rexx Language, A > Practical Approach to Programming". Its much easier to use his index and > TOC! > I don't do Java though I play chess with a Java program but have never > been able to edit it or make some useful changes to it. I prefer a simple > programming language if at all possible. > > Bob Cox > ----- Original Message ----- > From: Rick McGuire <obj...@gm...> > To: Open Object Rexx Announcements <oor...@li...> > Sent: Wed, 10 Jul 2013 15:19:21 -0500 (CDT) > Subject: Re: [Oorexx-announce] Failure > > See Section 14: Interactive Tracing. > > > On Wed, Jul 10, 2013 at 4:16 PM, Bob Cox <bo...@mc...> wrote: > > > I don't recall the use of a question mark with the Trace R command. I > > couldn't find it in Mike's book. > > Bob > > ----- Original Message ----- > > From: Rick McGuire <obj...@gm...> > > To: Open Object Rexx Announcements < > oor...@li...> > > Sent: Wed, 10 Jul 2013 12:16:55 -0500 (CDT) > > Subject: Re: [Oorexx-announce] Failure > > > > Either will cause a pause, but you also need to include the ? prefix > (i.e. > > "Trace ?r") > > > > Rick > > > > > > On Wed, Jul 10, 2013 at 12:00 PM, <Wil...@jb...> wrote: > > > > > As I recall, 'trace I' causes a pause. 'Trace R' does not; it just > gives > > > verbose output. In VM-370 the output pauses when the screen fills, > > waiting > > > for an ok to clear and go on. Trace I should pause after each > statement. > > > > > > > > > Thanks, > > > *William Lightner **| Sr Programming Specialist | Dual Data Center - > > > East * 4793617540 (O) | 479-619-6018 (C) > > > J.B. Hunt Transport, Inc. | What's your *next* move?™ Single Source | > > > Intermodal | Dedicated | Final Mile | Truckload | LTL | Refrigerated | > > > Flatbed > > > > > > > > > > > > > > > From: Bob Cox <bo...@mc...> > > > To: Open Object Rexx Announcements < > > > oor...@li...>, > > > Date: 07/09/2013 07:19 PM > > > Subject: Re: [Oorexx-announce] Failure > > > ------------------------------ > > > > > > > > > > > > #1: Tried putting the oIEF~Visible = .true statement in my code - - - > > > Still didn't work. > > > #2 Moved the Visible statement to just after the program definition > > > (procedure) statement - - - didn't work. > > > #3: Moved the Address Command to just before the Visible statement - - > - > > > didn't work. > > > > > > I'm still getting the flash presentation of the output screen but it is > > > only visible about 0.1 seconds or less. That's too short a time > interval > > > to see anything meaningful. > > > > > > When I have the Trace "R" statement the output should include all the > > > assignments in the stack. Under 370-VM the system would then stop and > > one > > > could enter another statement or correct the one displayed statement or > > an > > > enter key would proceed to the next statement in the script. If exit > was > > > entered the interpreter would stop. If trace "O" was entered the > tracing > > > function would stop and the script would be interpreted until either > the > > > end of the program or another Trace command was interpreted. It makes > > > debugging for a novice or old person prone to spelling errors much more > > > efficient. Syntax error merely indicates something is wrong but > doesn't > > > say what so one has to do more analysis to find the error. It is fine > > when > > > the programming is thought to be done and unexpected data values are > > > entered thus identifying the problem but particularly with complex > > logical > > > statements the trace function is invaluable. > > > Bob Cox > > > ----- Original Message ----- > > > From: Garry Smithwick <smi...@td...> > > > To: Open Object Rexx Announcements < > > oor...@li...> > > > Sent: Tue, 9 Jul 2013 15:13:48 -0500 (CDT) > > > Subject: Re: [Oorexx-announce] Failure > > > > > > oIE~Visible = .true sets the object value visible to true. The normal > > > Windows script uses oIE.visible, but for rexx we use "~" instead of "." > > > > > > It simply means internet explorer screen display (web site) will be > > > visible. > > > > > > Yes, trace works, but won't really tell you anymore than the syntax > > error. > > > > > > > > > Garry Smithwick > > > > > > Phone: 770-406-6010 > > > Mobile: 678-908-7319 > > > Email: smi...@td... > > > AIM ID: GarrySmithwick > > > FaceBook: www.facebook.com/garrysmithwick > > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > > > > > > > > > -----Original Message----- > > > From: Bob Cox > > > Sent: Tuesday, July 09, 2013 3:47 PM > > > To: Open Object Rexx Announcements > > > Subject: Re: [Oorexx-announce] Failure > > > > > > I don;t know or write Java. > > > Does the switch "oIE~Visible = .True" enable the output of any > > diagnostics > > > to be seen when the program is executed? Does the "Trace'R'" command > > work > > > with 64 bit ooRexx? > > > Bob cox > > > ----- Original Message ----- > > > From: Garry Smithwick <smi...@td...> > > > To: Open Object Rexx Announcements < > > oor...@li...> > > > Sent: Tue, 9 Jul 2013 13:05:56 -0500 (CDT) > > > Subject: [Oorexx-announce] Failure > > > > > > This fails with syntax error on “PageTitle = oIE~document~title” on the > > > new > > > release. > > > > > > Went back to 4.1.1 and it works. > > > > > > Several of my apps failed. Could not get the “document” object. > > > > > > I will open a report. > > > > > > > > > > > > > > > url = 'https://www.wireless.att.com/olam/dashboardAction.olamexecute' > > > > > > oIE = .OLEObject~New("InternetExplorer.Application") > > > oIE~Visible = .True > > > oIE~Top = 1 > > > oIE~Left = 1 > > > oIE~Width = 1000 > > > oIE~Height = 1000 > > > > > > oIE~navigate(url) > > > > > > Do 600 While oIE~readyState < 4 | oIE~busy = 1 > > > Call Syssleep 0.1 > > > End > > > > > > PageTitle = oIE~document~title > > > > > > Say Page PageTitle > > > > > > Garry Smithwick > > > > > > Phone: 770-406-6010 > > > Mobile: 678-908-7319 > > > Email: mailto:smi...@td... <smi...@td...> > > > AIM ID: GarrySmithwick > > > FaceBook: www.facebook.com/garrysmithwick > > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > > > > > > From: Mark Miesfeld > > > Sent: Monday, July 08, 2013 7:45 AM > > > To: Open Object Rexx Announcements ; Open Object Rexx Users ; ooRexx > Dev > > > List ; RexxLA > > > Subject: [Oorexx-announce] Correction,Re: Announce ooRexx 4.1.3 Is Now > > > Available > > > > > > The original post had incorrect links in it, sorry. > > > > > > This is the correct link to the ooRexx 4.1.3 download page: > > > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > > > > > > and this is the correct link to the docs for ooRexx 4.1.3: > > > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/ > > > > > > > > > -- > > > Mark Miesfeld > > > > > > > > > > > > On Sun, Jul 7, 2013 at 3:11 PM, Mark Miesfeld <mie...@gm...> > > wrote: > > > > > > The Open Object Rexx Development Team is proud to announce the > > > availability of ooRexx 4.1.3. This is a bug fix only release, with > about > > > 20 > > > bug fixes. > > > > > > Installation packages for ooRexx are available immediately on > > > SourceForge. > > > You can download ooRexx 4.1.3 from: > > > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > > > Complete documentation in PDF and HTML format can be downloaded from: > > > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/4.1.3/ > > > > > > Download the CHANGES document, in the ooRex files area, to see the > list > > > of > > > fixes. The _ReadMe.pdf or _ReadMe.html files contain additional > > > information > > > concerning the release. If you discover bugs please open a bug report > > at: > > > > > > http://sourceforge.net/p/oorexx/bugs/ > > > > > > -- > > > The ooRexx Development Team > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > > > > > > > ------------------------------------------------------------------------------ > > > This SF.net email is sponsored by Windows: > > > > > > Build for Windows Store. > > > > > > http://p.sf.net/sfu/windows-dev2dev > > > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > _______________________________________________ > > > Oorexx-announce mailing list > > > Oor...@li... > > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > See everything from the browser to the database with AppDynamics > > > Get end-to-end visibility with application monitoring from AppDynamics > > > Isolate bottlenecks and diagnose root cause in seconds. > > > Start your free trial of AppDynamics Pro today! > > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Oorexx-announce mailing list > > > Oor...@li... > > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > See everything from the browser to the database with AppDynamics > > > Get end-to-end visibility with application monitoring from AppDynamics > > > Isolate bottlenecks and diagnose root cause in seconds. > > > Start your free trial of AppDynamics Pro today! > > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Oorexx-announce mailing list > > > Oor...@li... > > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > See everything from the browser to the database with AppDynamics > > > Get end-to-end visibility with application monitoring from AppDynamics > > > Isolate bottlenecks and diagnose root cause in seconds. > > > Start your free trial of AppDynamics Pro today! > > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Oorexx-announce mailing list > > > Oor...@li... > > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > See everything from the browser to the database with AppDynamics > > > Get end-to-end visibility with application monitoring from AppDynamics > > > Isolate bottlenecks and diagnose root cause in seconds. > > > Start your free trial of AppDynamics Pro today! > > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Oorexx-announce mailing list > > > Oor...@li... > > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > |
|
From: Bob C. <bo...@mc...> - 2013-07-10 20:59:42
|
Must be my error. I'm using Mike Cowlishaw's book "The Rexx Language, A Practical Approach to Programming". Its much easier to use his index and TOC! I don't do Java though I play chess with a Java program but have never been able to edit it or make some useful changes to it. I prefer a simple programming language if at all possible. Bob Cox ----- Original Message ----- From: Rick McGuire <obj...@gm...> To: Open Object Rexx Announcements <oor...@li...> Sent: Wed, 10 Jul 2013 15:19:21 -0500 (CDT) Subject: Re: [Oorexx-announce] Failure See Section 14: Interactive Tracing. On Wed, Jul 10, 2013 at 4:16 PM, Bob Cox <bo...@mc...> wrote: > I don't recall the use of a question mark with the Trace R command. I > couldn't find it in Mike's book. > Bob > ----- Original Message ----- > From: Rick McGuire <obj...@gm...> > To: Open Object Rexx Announcements <oor...@li...> > Sent: Wed, 10 Jul 2013 12:16:55 -0500 (CDT) > Subject: Re: [Oorexx-announce] Failure > > Either will cause a pause, but you also need to include the ? prefix (i.e. > "Trace ?r") > > Rick > > > On Wed, Jul 10, 2013 at 12:00 PM, <Wil...@jb...> wrote: > > > As I recall, 'trace I' causes a pause. 'Trace R' does not; it just gives > > verbose output. In VM-370 the output pauses when the screen fills, > waiting > > for an ok to clear and go on. Trace I should pause after each statement. > > > > > > Thanks, > > *William Lightner **| Sr Programming Specialist | Dual Data Center - > > East * 4793617540 (O) | 479-619-6018 (C) > > J.B. Hunt Transport, Inc. | What's your *next* move?™ Single Source | > > Intermodal | Dedicated | Final Mile | Truckload | LTL | Refrigerated | > > Flatbed > > > > > > > > > > From: Bob Cox <bo...@mc...> > > To: Open Object Rexx Announcements < > > oor...@li...>, > > Date: 07/09/2013 07:19 PM > > Subject: Re: [Oorexx-announce] Failure > > ------------------------------ > > > > > > > > #1: Tried putting the oIEF~Visible = .true statement in my code - - - > > Still didn't work. > > #2 Moved the Visible statement to just after the program definition > > (procedure) statement - - - didn't work. > > #3: Moved the Address Command to just before the Visible statement - - - > > didn't work. > > > > I'm still getting the flash presentation of the output screen but it is > > only visible about 0.1 seconds or less. That's too short a time interval > > to see anything meaningful. > > > > When I have the Trace "R" statement the output should include all the > > assignments in the stack. Under 370-VM the system would then stop and > one > > could enter another statement or correct the one displayed statement or > an > > enter key would proceed to the next statement in the script. If exit was > > entered the interpreter would stop. If trace "O" was entered the tracing > > function would stop and the script would be interpreted until either the > > end of the program or another Trace command was interpreted. It makes > > debugging for a novice or old person prone to spelling errors much more > > efficient. Syntax error merely indicates something is wrong but doesn't > > say what so one has to do more analysis to find the error. It is fine > when > > the programming is thought to be done and unexpected data values are > > entered thus identifying the problem but particularly with complex > logical > > statements the trace function is invaluable. > > Bob Cox > > ----- Original Message ----- > > From: Garry Smithwick <smi...@td...> > > To: Open Object Rexx Announcements < > oor...@li...> > > Sent: Tue, 9 Jul 2013 15:13:48 -0500 (CDT) > > Subject: Re: [Oorexx-announce] Failure > > > > oIE~Visible = .true sets the object value visible to true. The normal > > Windows script uses oIE.visible, but for rexx we use "~" instead of "." > > > > It simply means internet explorer screen display (web site) will be > > visible. > > > > Yes, trace works, but won't really tell you anymore than the syntax > error. > > > > > > Garry Smithwick > > > > Phone: 770-406-6010 > > Mobile: 678-908-7319 > > Email: smi...@td... > > AIM ID: GarrySmithwick > > FaceBook: www.facebook.com/garrysmithwick > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > > > -----Original Message----- > > From: Bob Cox > > Sent: Tuesday, July 09, 2013 3:47 PM > > To: Open Object Rexx Announcements > > Subject: Re: [Oorexx-announce] Failure > > > > I don;t know or write Java. > > Does the switch "oIE~Visible = .True" enable the output of any > diagnostics > > to be seen when the program is executed? Does the "Trace'R'" command > work > > with 64 bit ooRexx? > > Bob cox > > ----- Original Message ----- > > From: Garry Smithwick <smi...@td...> > > To: Open Object Rexx Announcements < > oor...@li...> > > Sent: Tue, 9 Jul 2013 13:05:56 -0500 (CDT) > > Subject: [Oorexx-announce] Failure > > > > This fails with syntax error on “PageTitle = oIE~document~title” on the > > new > > release. > > > > Went back to 4.1.1 and it works. > > > > Several of my apps failed. Could not get the “document” object. > > > > I will open a report. > > > > > > > > > > url = 'https://www.wireless.att.com/olam/dashboardAction.olamexecute' > > > > oIE = .OLEObject~New("InternetExplorer.Application") > > oIE~Visible = .True > > oIE~Top = 1 > > oIE~Left = 1 > > oIE~Width = 1000 > > oIE~Height = 1000 > > > > oIE~navigate(url) > > > > Do 600 While oIE~readyState < 4 | oIE~busy = 1 > > Call Syssleep 0.1 > > End > > > > PageTitle = oIE~document~title > > > > Say Page PageTitle > > > > Garry Smithwick > > > > Phone: 770-406-6010 > > Mobile: 678-908-7319 > > Email: mailto:smi...@td... <smi...@td...> > > AIM ID: GarrySmithwick > > FaceBook: www.facebook.com/garrysmithwick > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > From: Mark Miesfeld > > Sent: Monday, July 08, 2013 7:45 AM > > To: Open Object Rexx Announcements ; Open Object Rexx Users ; ooRexx Dev > > List ; RexxLA > > Subject: [Oorexx-announce] Correction,Re: Announce ooRexx 4.1.3 Is Now > > Available > > > > The original post had incorrect links in it, sorry. > > > > This is the correct link to the ooRexx 4.1.3 download page: > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > > > and this is the correct link to the docs for ooRexx 4.1.3: > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/ > > > > > > -- > > Mark Miesfeld > > > > > > > > On Sun, Jul 7, 2013 at 3:11 PM, Mark Miesfeld <mie...@gm...> > wrote: > > > > The Open Object Rexx Development Team is proud to announce the > > availability of ooRexx 4.1.3. This is a bug fix only release, with about > > 20 > > bug fixes. > > > > Installation packages for ooRexx are available immediately on > > SourceForge. > > You can download ooRexx 4.1.3 from: > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > Complete documentation in PDF and HTML format can be downloaded from: > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/4.1.3/ > > > > Download the CHANGES document, in the ooRex files area, to see the list > > of > > fixes. The _ReadMe.pdf or _ReadMe.html files contain additional > > information > > concerning the release. If you discover bugs please open a bug report > at: > > > > http://sourceforge.net/p/oorexx/bugs/ > > > > -- > > The ooRexx Development Team > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by Windows: > > > > Build for Windows Store. > > > > http://p.sf.net/sfu/windows-dev2dev > > > > > > > > > -------------------------------------------------------------------------------- > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > |
|
From: Rick M. <obj...@gm...> - 2013-07-10 20:19:29
|
See Section 14: Interactive Tracing. On Wed, Jul 10, 2013 at 4:16 PM, Bob Cox <bo...@mc...> wrote: > I don't recall the use of a question mark with the Trace R command. I > couldn't find it in Mike's book. > Bob > ----- Original Message ----- > From: Rick McGuire <obj...@gm...> > To: Open Object Rexx Announcements <oor...@li...> > Sent: Wed, 10 Jul 2013 12:16:55 -0500 (CDT) > Subject: Re: [Oorexx-announce] Failure > > Either will cause a pause, but you also need to include the ? prefix (i.e. > "Trace ?r") > > Rick > > > On Wed, Jul 10, 2013 at 12:00 PM, <Wil...@jb...> wrote: > > > As I recall, 'trace I' causes a pause. 'Trace R' does not; it just gives > > verbose output. In VM-370 the output pauses when the screen fills, > waiting > > for an ok to clear and go on. Trace I should pause after each statement. > > > > > > Thanks, > > *William Lightner **| Sr Programming Specialist | Dual Data Center - > > East * 4793617540 (O) | 479-619-6018 (C) > > J.B. Hunt Transport, Inc. | What's your *next* move?™ Single Source | > > Intermodal | Dedicated | Final Mile | Truckload | LTL | Refrigerated | > > Flatbed > > > > > > > > > > From: Bob Cox <bo...@mc...> > > To: Open Object Rexx Announcements < > > oor...@li...>, > > Date: 07/09/2013 07:19 PM > > Subject: Re: [Oorexx-announce] Failure > > ------------------------------ > > > > > > > > #1: Tried putting the oIEF~Visible = .true statement in my code - - - > > Still didn't work. > > #2 Moved the Visible statement to just after the program definition > > (procedure) statement - - - didn't work. > > #3: Moved the Address Command to just before the Visible statement - - - > > didn't work. > > > > I'm still getting the flash presentation of the output screen but it is > > only visible about 0.1 seconds or less. That's too short a time interval > > to see anything meaningful. > > > > When I have the Trace "R" statement the output should include all the > > assignments in the stack. Under 370-VM the system would then stop and > one > > could enter another statement or correct the one displayed statement or > an > > enter key would proceed to the next statement in the script. If exit was > > entered the interpreter would stop. If trace "O" was entered the tracing > > function would stop and the script would be interpreted until either the > > end of the program or another Trace command was interpreted. It makes > > debugging for a novice or old person prone to spelling errors much more > > efficient. Syntax error merely indicates something is wrong but doesn't > > say what so one has to do more analysis to find the error. It is fine > when > > the programming is thought to be done and unexpected data values are > > entered thus identifying the problem but particularly with complex > logical > > statements the trace function is invaluable. > > Bob Cox > > ----- Original Message ----- > > From: Garry Smithwick <smi...@td...> > > To: Open Object Rexx Announcements < > oor...@li...> > > Sent: Tue, 9 Jul 2013 15:13:48 -0500 (CDT) > > Subject: Re: [Oorexx-announce] Failure > > > > oIE~Visible = .true sets the object value visible to true. The normal > > Windows script uses oIE.visible, but for rexx we use "~" instead of "." > > > > It simply means internet explorer screen display (web site) will be > > visible. > > > > Yes, trace works, but won't really tell you anymore than the syntax > error. > > > > > > Garry Smithwick > > > > Phone: 770-406-6010 > > Mobile: 678-908-7319 > > Email: smi...@td... > > AIM ID: GarrySmithwick > > FaceBook: www.facebook.com/garrysmithwick > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > > > -----Original Message----- > > From: Bob Cox > > Sent: Tuesday, July 09, 2013 3:47 PM > > To: Open Object Rexx Announcements > > Subject: Re: [Oorexx-announce] Failure > > > > I don;t know or write Java. > > Does the switch "oIE~Visible = .True" enable the output of any > diagnostics > > to be seen when the program is executed? Does the "Trace'R'" command > work > > with 64 bit ooRexx? > > Bob cox > > ----- Original Message ----- > > From: Garry Smithwick <smi...@td...> > > To: Open Object Rexx Announcements < > oor...@li...> > > Sent: Tue, 9 Jul 2013 13:05:56 -0500 (CDT) > > Subject: [Oorexx-announce] Failure > > > > This fails with syntax error on “PageTitle = oIE~document~title” on the > > new > > release. > > > > Went back to 4.1.1 and it works. > > > > Several of my apps failed. Could not get the “document” object. > > > > I will open a report. > > > > > > > > > > url = 'https://www.wireless.att.com/olam/dashboardAction.olamexecute' > > > > oIE = .OLEObject~New("InternetExplorer.Application") > > oIE~Visible = .True > > oIE~Top = 1 > > oIE~Left = 1 > > oIE~Width = 1000 > > oIE~Height = 1000 > > > > oIE~navigate(url) > > > > Do 600 While oIE~readyState < 4 | oIE~busy = 1 > > Call Syssleep 0.1 > > End > > > > PageTitle = oIE~document~title > > > > Say Page PageTitle > > > > Garry Smithwick > > > > Phone: 770-406-6010 > > Mobile: 678-908-7319 > > Email: mailto:smi...@td... <smi...@td...> > > AIM ID: GarrySmithwick > > FaceBook: www.facebook.com/garrysmithwick > > Home Page: personalpages.tds.net/~garrysmithwick > > > > > > > > > > From: Mark Miesfeld > > Sent: Monday, July 08, 2013 7:45 AM > > To: Open Object Rexx Announcements ; Open Object Rexx Users ; ooRexx Dev > > List ; RexxLA > > Subject: [Oorexx-announce] Correction,Re: Announce ooRexx 4.1.3 Is Now > > Available > > > > The original post had incorrect links in it, sorry. > > > > This is the correct link to the ooRexx 4.1.3 download page: > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > > > and this is the correct link to the docs for ooRexx 4.1.3: > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/ > > > > > > -- > > Mark Miesfeld > > > > > > > > On Sun, Jul 7, 2013 at 3:11 PM, Mark Miesfeld <mie...@gm...> > wrote: > > > > The Open Object Rexx Development Team is proud to announce the > > availability of ooRexx 4.1.3. This is a bug fix only release, with about > > 20 > > bug fixes. > > > > Installation packages for ooRexx are available immediately on > > SourceForge. > > You can download ooRexx 4.1.3 from: > > > > http://sourceforge.net/projects/oorexx/files/oorexx/4.1.3/ > > > > Complete documentation in PDF and HTML format can be downloaded from: > > > > http://sourceforge.net/projects/oorexx/files/oorexx-docs/4.1.3/ > > > > Download the CHANGES document, in the ooRex files area, to see the list > > of > > fixes. The _ReadMe.pdf or _ReadMe.html files contain additional > > information > > concerning the release. If you discover bugs please open a bug report > at: > > > > http://sourceforge.net/p/oorexx/bugs/ > > > > -- > > The ooRexx Development Team > > > > > > > > > > > > > -------------------------------------------------------------------------------- > > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by Windows: > > > > Build for Windows Store. > > > > http://p.sf.net/sfu/windows-dev2dev > > > > > > > > > -------------------------------------------------------------------------------- > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-announce mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > > > > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-announce mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-announce > |
16 messages has been excluded from this view by a project administrator.