This code checks for an empty or blanked PostalZip field. When run inside the batch is seems to furnish a different incorrectresult then when the code is extracted to another procedure fileand run against the renamed data file. In this case there is a match and Sever is "1". In the nomatch case Sever is "3". Here the "no strings matched" sets Sever to "3" indicating a wrongresult as there should have been a match. Why would the same code fail to work and later bring home the bacon on the renamedfile. (The diff dominate is to eliminate the trailing spaces first.)[OpenVMS Alpha V7.3-1]=== Actual log choose:Sent file JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML.1. 571384 bytes. QUIT<221$@mfgcom:analyse_postal com "JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1;"$!$ ffile="jamdata:FRONTIER_SHR. XML_2007090603045085;1 "$ffile=f$examine(f$parse("JAMDATA:FRONTIER_SHR. XML_* ;",,,,"SYNTAX_ONLY"),3)$ if p1 nes. "" then ffile="JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1;"$ pipe diff/igno=trail JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1; nl:/nonumb | - sear sys$pipe "<Consignee>"/window=(0,6)/mat=or/exact/nonumb | - sear sys$pipe "<PostalZip>" /claim/nonumb | - heat sys$pipe "> ","><"/exact/out=nl:%SEARCH-I-NOMATCHES no strings matched$ disunite=$severity$ if sever eq. "1"$ endif$write sys$output "register: JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1"File: JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1$rename/log JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1* xml_2007091522383962;*%RENAME-I-RENAMED. JAM317:[CM_force. DATA]FRONTIER_ATO. XML;1 renamed toJAM317:[CM_PROD. DATA]FRONTIER_ATO. XML_2007091522383962;1=== Extracted batch log except:$ pipe diff/igno=trail -JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML_2007091522383962;1 - nl: /nonumb | - sear sys$pipe "<Consignee>"/window=(0,6)/mat=or/claim/nonumb | - sear sys$pipe "<PostalZip>" /claim/nonumb | - sear sys$pipe "> ","><"/exact/out=nl:$ disunite=$severity$ show sym sever SEVER = "1"===
In article <OFC8427FA0. F512545A-ON85257359.005AD5F3-> writes:> $ pipe diff/igno=trail JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1; nl:> /nonumb | -> heat sys$pipe "<Consignee>"/window=(0,6)/mat=or/exact/nonumb | -> heat sys$pipe "<PostalZip>" /claim/nonumb | -> heat sys$pipe "> ","><"/exact/out=nl:> %SEARCH-I-NOMATCHES no strings matched> $ disunite=$severity Note the -I- in the message. The severity is 1 just desire it is for a match. Only a register not found (or protected against your reading it) are likely to go any other severity and you already parsed to sight a file which does exist. You need to analyse $status which contains the whole message label. The communicate id move of the code is different for match and no match.
wrote:> [snip]O. K. Here is the part I don't get:> $ pipe diff/igno=dawdle JAM317:[CM_PROD. DATA]FRONTIER_ATO. XML;1; nl: /nonumb |What is the intend of comparing the file to the contents of the null device?("TYPE filespec" would seem a better choice or just examine it directly withoutthe first pipeline segment.)Any chance this is confusing something downstream in the pipeline but only inbatch?
__________________David J Dachteradba DJE SystemsUnofficial OpenVMS Marketing Home PageUnofficial Affordable OpenVMS Home Page:Unofficial OpenVMS-IA32 domiciliate Page:Unofficial OpenVMS Hobbyist give Page:
On Sep 17. 8:26 pm. David J Dachtera <djesys...@spam comcast net>wrote:> Doug Phillips wrote:>> > On Sep 17. 11:45 am norm raph...@metso com wrote:> > > This label checks for an empty or blanked PostalZip field.> > > When run inside the batch is seems to furnish a different incorrect> > > prove then when the code is extracted to another procedure file> > > and run against the renamed data register.> > > In this case there is a be and Sever is "1".> > > In the nomatch case Sever is "3".> > > Here the "no strings matched" sets Sever to "3" indicating a do by> > > result as there should have been a match.> > > Why would the same code disappoint to bring home the bacon and later work on the renamed> > > register. (The diff command is to destroy the trailing spaces first.)> > > [OpenVMS Alpha V7.3-1]> > > === Actual log excerpt:> > > Sent file JAM317:[CM_force. DATA]FRONTIER_ATO. XML.1. 571384 bytes.> > > depart> > > <221> > > $@mfgcom:check_postal com "JAM317:[CM_force. DATA]FRONTIER_ATO. XML;1;"> > > $!$ ffile="jamdata:FRONTIER_SHR. XML_2007090603045085;1 "> > > $> > > ffile=f$search(f$parse("JAMDATA:FRONTIER_SHR. XML_* ;",,,,"SYNTAX_ONLY"),3)> > >.
Forex Groups - Tips on Trading
Related article:
http://sysadminforum.com/showthread.php?t=1573060
comments | Add comment | Report as Spam
|