Right I agree with Allen that you should maybe check whether the OPEN was successful. If it was NOT when the file SHOULD exist then you have some problem. Perhaps the file is not getting released by some process and so is not in an available state to be re-opened ? It might be a timing issue, even if you can't open it, you could encode a one-second sleep and try to re-open it again before failing. It's at least worth a try. Will Johnson Fast Forward Technologies
In a message dated 12/17/2004 3:09:23 PM Eastern Standard Time, "Allen E. Elwood" <[EMAIL PROTECTED]> writes: >As long as there is a valid file/id names. My point is that unless you are >checking OK_TO_CONTINUE you'll never know if maybe the filename is in a >write protected status or some other normally unforeseeable condition. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Kevin King >Sent: Friday, December 17, 2004 10:27 >To: [EMAIL PROTECTED] >Subject: RE: [U2] [UD]WRITESEQ quirkiness > > >Shouldn't really matter that he's not checking the variable. OPENSEQ >will create the item if it doesn't exist. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Allen E. >Elwood >Sent: Friday, December 17, 2004 11:58 AM >To: [EMAIL PROTECTED] >Subject: RE: [U2] [UD]WRITESEQ quirkiness > >Hi Dana, > >Well, you're setting OK_TO_CONTINUE but never checking it... > >Maybe something there..... > >Allen > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Dana Baron >Sent: Friday, December 17, 2004 10:11 >To: U2-Users (E-mail) >Subject: [U2] [UD]WRITESEQ quirkiness > > >Here's a puzzler: what is it that causes the ELSE clause to be >executed in a WRITESEQ block when the only apparent change is the >content of the data to be written. I've included a section of code >below followed by the output from two subsequent calls. In the first, >the code executes the THEN clause and prints SENDING... In the second, >the ELSE clause is executed producing the ERROR WRITING... results. >Any thoughts? Could it be that there is a limit to the size of the >data that wan be written using WRITESEQ? > >This code segment: > >****************** >SAVE_MESSAGE_FILE: > > UNIX_DIR = "/unidata/lodginglink/" > SAVE_DIR = "/unidata/lodginglink/save/" > DATE_PART = DATE() > TIME_PART = TIME() > MSG_PART = UHLL.ITEM<UHLL.TXN.ID.AMC> : >UHLL.ITEM<UHLL.SEQ.NUM.AMC> > FILE_NAME = DATE_PART:TIME_PART:MSG_PART:".out" > > OPENSEQ UNIX_DIR, FILE_NAME TO FILE_POINTER THEN > OK_TO_CONTINUE = TRUE. > END > PRINT "OPENSEQ STATUS IS " : > PRINT STATUS() > > MSG_HEX = OCONV(MSG_OUT,"MX") > WRITESEQ MSG_HEX ON FILE_POINTER THEN > IF TRACE.ON THEN > PRINT "SENDING: " : MSG_OUT > END > END ELSE > PRINT "ERROR WRITING" > PRINT "ASCII MESSAGE IS " : MSG_OUT > PRINT "HEX MESSAGE IS " : MSG_HEX > PRINT "FILE NAME IS " : FILE_NAME > END > CLOSESEQ FILE_POINTER > >SAVE_MESSAGE_FILE_EXIT: >RETURN >******* > >Produces this output: > >OPENSEQ STATUS IS 0 >SENDING: ^B451900000389999^C1 >OPENSEQ STATUS IS 0 >ERROR WRITING >ASCII MESSAGE IS ^B254440000369999008019DISHONGH, GEORGIA >L1060091*1163482144001015100101740043801175003SY11770010^C0 >HEX MESSAGE IS >02323534343430303030333639393939303038303139444953484F4E47482C2047454F >524749 >41204C313036303039312A313136333438323134343030313031353130303130313734 >303034 >33383031313735303033535931313737303031300330 >FILE NAME IS 135014589700369999.out > > >Dana Baron >System Manager >Smugglers' Notch Resort >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
