Lost link: Mac/Hp(Informix)

GSI Project - Handling of Adverts Preamble: 'Advert Handling' indicates a complete advert processing stage (creation, any amendments, filing in DB and recalling for insertion in any publication such as telephone directories, annuaries, etc.) Problem: Interruption on EtherShare Server HardWare: Server HP 9000/K400 with Informix DB Operating System: UX 10.01 PowerMac 8500 Client Operating System: MacOS 7.5.5 + Open Transport 1.1 OPI + shared disc Server/Client: EtherShare 2.20 (Helios) SoftWare: Client 1) WorkFlow (developed by ILTE) 2) Quark XPress 3.32 + XTension WorkFlowXT (developed by ILTE) Work cycle: an advert is recalled by Client from HP Server, via WorkFlow application and TCP/IP. The HP server, through an appropriate application, searches DB Informix for the requested advert and answers back via TCP/IP that it is either OK or KO, i.e. 1) KO if the advert cannot be processed 2) OK if the advert can be processed. In the latter case, prior to the answer, all files required to create/amend the advert are extracted from the Informix DB and stored in a folder of the shared EtherShare disc. According to the answer, the WorkFlow application reacts alternatively as follow: 1) KO permits the user to recall a new advert 2) OK prepares a data strcture (approx. 800 bytes) including: - advert size - advert type (alphabetical, yellow pages) - flag indicating whether it is a new advert or one to be modified - path of files relating to the advert (EtherShare disc) - name of the XPress document This structure is transferred to XPress via AppleEvent, which in turn starts XPress. Through AppleEvent and XTension WorkFlowXT, XPress reads the data structure transferred by WorkFlow, opens the old XPress document or creates automatically a new document corresponding to the values indicated in the structure, furthermore allowing the user to process the advert. At the end of the processing stage the user starts via menu the XTension WorkFlowXT wich in turn makes sure that: 1) the XPress document is saved on the shared EtherShare disc 2) creates the EPS file of the document on the shared EtherShare disc 3) starts the WorkFlow application via AppleEvent Upon receiving the information, the WorkFlow application via TCP/IP tells the HP Server that the files pertaining to the advert are ready to be saved on Informix DB. The user may the recall the next advert for processing. Problem: the problem is that the shared EtherShare disc on PowerMac Client is 'lost' during the advert processing. A "-1070" error (parameter error) and a "-1072" (session closed) error are reported. The shared disc disappears from the desk: the only way to re-use it is by re-starting the Client, wich involves an enormous waste of production time, if you consider that the problem occurs every second or third document and sometimes after a few days - (in one day up to 180/200 new documents are created on one Client). The problem usually occurs when a new document, or one to be modified are automatically opened via XTension WorkFlowXT. It does not depend on the type or size of the document, it is just occasional. The same inconvenience does not appear when WorkFlow and XTension WorkFlowXT are not used in processing a document with the shared EtherShare disc. The same production cycle (WorkFlow application + image retouching + shared EtherShare disc) is used to scan and retouch the advert images. The only difference there is no direct communication or data transfer via AppleEvent between the two applications. This may lead to assume that there may be an incorrect use of the AppleEvents or that the latter and EtherShare may be somehow incompatible. Attempts made: The WorkFlow application as well as XTension WorkFlowXT have been repeatedly controlled by different engineers, but no errors have been found. A special control panel has been used (AETracker v. 2.0 - C.K. Haun <TR> - RavenWare SoftWare - 22045 McClelland Rd. - Cupertino, CA 95014), which enabled us to check the AppleEvent activity and warned us about some imperfections when opening an XPress document (see enclosure) (are these 'normal' ??????). Nevertheless the problem is still standing. Macsbug has also been used without success. Request for HELP! At this stage, being short of clues, I ask the suppliers of the various system components and anybody else who may do it, to PLEASE HELP ME, in the hope that this type of accident may have occurred and have been solved already. Any ideas or suggestions regarding a special software such as AETracker that could be used are welcome. R. Giacomelli ---------------------------------------------------------------------- Enclosure: ---------------------------------------------------------------------- AETracker record Brought to you by C.K. Haun <TR> and RavenWare Software Tracking initiated in application:WorkFlow WorkFlow at TickCount: $0000CCB7 AECreateDesc Descriptor Type: sign The Data : $5850 5233 In ASCII : XPR3 Results returned.... Descriptor data; Descriptor Type: sign The Data : $5850 5233 In ASCII : XPR3 WorkFlow at TickCount: $0000CCB7 AECreateAppleEvent Creating Class: AVP* ID: Strc return ID: $FFFF transaction ID : $00000000 WorkFlow at TickCount: $0000CCB7 AEPutKeyPtr Descriptor Type: TEXT Key Type : ---- The Data : $0633 3632 3732 3100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 In ASCII : 362721