[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IFS processing problems



Just put our first ifs process into production a few weeks ago and have run into a little bit of a snag.

 

background:

3rd party vendor's print manager(PM) software residing on a x-card in the as/400 w/ an o/s of windows 2000

 

The PM receives sap gof printable files from SAP that contain a non-printable header data. The PM creates a temporary file then adds the data stream of this header data then sends the file to the ifs directory.

 

iseries: since the ifs doesn’t have a trigger I created an interface pgm w/ a delay wait of 3 seconds, opens the directory, reads/processes any files, closes the directory.

 

Problem: looks like to me that when the directory is being opened and closed it locks the directory. During that time PM may be sending a file, since the directory is locked the file is never added to the folder. PM only knows the file has been successfully sent not successfully created.

 

Tempory Solution: changed the delay wait to 30 seconds and haven't had the problem occur.

 

Tried:

1) Open the directory once, keeping the directory open and continually read/process the directory until *null value, delay wait 30 seconds then read the directory again. Can see files that files have been added but when reading the directory always returns a *null value

 

2) Open the directory once, keeping it open, when reading the directory for the first time save off the SP: value of the '.' file in the directory, if when reading the directory and a *null value is returned, delay wait 30 seconds then populate the SP: value with the '.' value and read the directory. This stil returns a *null even though there are files in the folder.

 

Thanks,

Joel