B2H isn't leaving a file open? Active workunits can be a problem with pipes. In that case, a workaround could be that you open the output file with the DMSOPEN CSL call (that returns a token) and then you pass the token to the FILETOKEN stage. When the pipe ends, you can use FINIS to close B2H's file (if required); DMSCLOSE and maybe DMSCOMM (to commit changes). With this method, you can even have the SFS file written in another workunit than the default workunit (which is used by EXECIO & co in B2H).
2007/9/3, Colin Allinson <[EMAIL PROTECTED]>: > > Rob van der Heij <[EMAIL PROTECTED]> wrote :- > > > It appears something in your pipeline has the file open or locked, > > which prevents erasing the file (maybe somewhere in those REXX > > stages). I am not sure why it works anyway, but maybe your pipeline is > > actually creating the file twice or so? > > > Obviously you could erase or rename the file yourself before you start > > the pipeline, if you cannot make the topology such that opening the > > file is avoided. > > I could post the REXX stages but all they do is manipulate the input and > pass it to the output. The only thought I have is that B2H itself is doing > something however, I don't understand what if it works when the file does > not exist. > > Yes, I guess I could erase the output file (If it exists) first but not > sure of the best way when the eventual target directory will not be > accessed. Would writing a null output from a pipe do that? > > > Colin G Allinson > Technical Manager VM > Amadeus Data Processing GmbH > T +49 (0) 8122-43 49 75 > F +49 (0) 8122-43 32 60 > [EMAIL PROTECTED] > http://www.amadeus.com > > > Amadeus Data Processing GmbH > Geschäftsführer: Eberhard Haag > Sitz der Gesellschaft: Erding > HR München 48 199 > Berghamer Strasse 6 > 85435 Erding > Germany > -- Kris Buelens, IBM Belgium, VM customer support
