With the embedded PIPE there wouldn't be any dependence of a REXX EXEC. It isn't even hard to code, let me know if you need help (and can wait a week).
-- Kris Buelens, IBM Belgium, VM customer support 2008/1/27, Fox Blue <[EMAIL PROTECTED]>: > Kris, > > Well it is a R/W minidisk. It is the 191 of the machine. > > Yesterday, I was also playing around with the LISTFILE command. It seems > that it retrieves the file names in the same unordered way. > > Regarding to your proposal, I wanted to program a CMS module that should > not > become dependent on external REXX EXEC(s). > > I think the documentation (CMS Application Development Guide SC24-6069-02 > ) > should reflect that the directory is not sorted. I was browsing through i > t > and could not find any hint on this issue. Also the CMS Callable Services > > Reference (SC24-6072-02) should contain a usage note referring to this. > > Thanks anyway for your proposal to overcome this problem. > > BR Fox. > > > On Sat, 26 Jan 2008 20:11:25 +0100, Kris Buelens <[EMAIL PROTECTED]> > wrote: > > >I have no experience with DMSGETDF... > >Is this a R/W minidisk? Only for R/O minidisks CMS keeps the FST's sort > ed. > > > >I would make the program call a REXX EXEC that in its turn executes a > >PIPE that contains a LISTFILE and SORT stage. The PIPE could pass the > >sorted list of files in the stack where your program retrieves them. > >Or, more elegant, your assembler program allocates a buffer large > >enough to store the result of the LISTFILE, prepares the PIPE command > >with the LISTFILE and SORT, the last stage would be a STORAGE stage to > >write the result in your program's buffer. > > > >Kris Buelens, > >IBM Belgium, VM customer support
