SourceForge has been redesigned. Learn more.
Close

#110 SET REXXOUTPUT F confuses EXTRACT

closed-works-for-me
None
5
2007-12-13
2006-11-16
r corak
No

If I SET REXXOUTPUT F 10000000 and then invoke a macro in which I EXTRACT /SIZE/whatever/, what EXTRACT sets is the information for the trace file, not for the file under edit. For example,

12 *-* "command extract /fpath/filename/size/"
13 *-* msg fpath.1 filename.1 "size.1 =" size.1

gives

H:\ REXX.$$$ size.1 = 0

Discussion

  • Mark Hessling

    Mark Hessling - 2006-11-21
    • assigned_to: nobody --> rexx
     
  • Mark Hessling

    Mark Hessling - 2006-11-21

    Logged In: YES
    user_id=86185
    Originator: NO

    This only happens for me if the macro is started from the pseudo file where REXXOUTPUT is stored.
    eg:
    /**/
    "command extract /fpath/filename/size/"
    "msg" fpath.1 filename.1 "size.1 =" size.1

    run from any file will produce the correct results.

     
  • r corak

    r corak - 2006-11-21

    Logged In: YES
    user_id=1587066
    Originator: YES

    This happens for me when tracing a macro. I didn't mention, perhaps should have, that the macro's first statement is: trace ?i, after which comes the extract and all the rest.

     
  • r corak

    r corak - 2006-11-21

    Logged In: YES
    user_id=1587066
    Originator: YES

    This happens for me when tracing a macro. I didn't mention, perhaps should have, that the macro's first statement is: trace ?i, after which comes the extract and all the rest.

     
  • Mark Hessling

    Mark Hessling - 2007-12-06

    Logged In: YES
    user_id=86185
    Originator: NO

    The scenario is confusing. When a macro with EXTRACT /SIZE is run from within a "real" file, the size is returned correctly, but when the macro with EXTRACT /SIZE is run from the pseudo file created by REXXOUTPUT FILE, then the size is not the size of the edited file? What do you expect to be the edited file in this case? What if there are 3 real files in the ring, which one is the edited file? The EXTRACT /FILE is relevant to the current file, in the case you state that fails then this is the pseudo file produced by REXXOUTPUT FILE.
    I don't see an error with this.

     
  • Mark Hessling

    Mark Hessling - 2007-12-06
    • status: open --> open-invalid
     
  • r corak

    r corak - 2007-12-06

    Logged In: YES
    user_id=1587066
    Originator: YES

    Today I can't recreate this problem.
    My original description said that when I invoke the macro, implicitly against some arbitrary file, what I got was info about REXX.$$$, not about that arbitrary file. Today, EXTRACT tells be about that file, not about REXX.$$$.

    Forget it. I'll open a new report if it ever happens again.

     
  • r corak

    r corak - 2007-12-06

    Logged In: YES
    user_id=1587066
    Originator: YES

    Today I can't recreate this problem.
    My original description said that when I invoke the macro, implicitly against some arbitrary file, what I got was info about REXX.$$$, not about that arbitrary file. Today, EXTRACT tells be about that file, not about REXX.$$$.

    Forget it. I'll open a new report if it ever happens again.

     
  • Mark Hessling

    Mark Hessling - 2007-12-13
    • status: open-invalid --> closed-works-for-me
     

Log in to post a comment.