LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (November 1997)Back to main REXXLIST pageJoin or leave REXXLIST (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 31 Oct 1997 08:09:05 -0800
Reply-To:     REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
Sender:       REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
From:         Frank Merrow <fmerrow@QUALCOMM.COM>
Organization: QUALCOMM, Incorporated; San Diego, CA, USA
Subject:      Re: An Old Rexx hand is stumped by DIRECTORY()

>>I have been doing Rexx under OS/2 for a LONG time. Now I am trying to >>move a bunch of REXX scripts from OS/2 to WinNT using IBM's Object Rexx. >>Mostly, things are going Okay, but one item has me stumped. > >>DIRECTORY("gohere") > >>Doesn't seem to work. Well, it works, but ONLY for the Rexx script and >>not for the underlying DOS prompt. In fact, if I do a "dir" in the Rexx > > I think that's a known bug in Win Object Rexx. Drop by >http://www2.hursley.ibm.com/orexx

Thank you for the pointer to the update. I picked it up and installed it. However, while I do see some bugs associated with the DIRECTORY() command, none that seem to apply to my case. (Still I am very happy to have the update.)

The solution I came up with is a really old DOS trick. I wrap the REXX script in in a BAT file. The BAT file calls the REXX script and then calls a BAT file created by the REXX script. In short, I export the answer and then run it.

I suspect this is not a bug, but rather a "feature" caused by the fact that ObjRexx isn't integrated into the command shell like it is in the OS/2 World.

Frank


Back to: Top of message | Previous page | Main REXXLIST page