I'm having some problems with a pipeline that process either STARMSG or
CONSOLE input.  When an SMSG is received it acts unexpectedly:

  "PIPE (endchar ?)",

      "   STARMSG *MSG",

      "|b:FIND 00000008"||,

        (process SCIF)
  "?b:",

      "|  FIND 00000004"||,

      "|  SPEC 9-* 1",

      "|l:LOOKUP W1 DETAIL",

      "|u:ZONE W2 ALL /QUIT/!/END/!/SHUT/!/STOP/",

      "|  PIPESTOP",

  "?u:",

      "|  SPEC /MSG/ 1 W1 NW /Unknown command '/ NW W2-* N /' entered./
N",
      "|  CP",

      "|  HOLE",

  "?",

      "   VAR !._ADMINS",

      "|  SPLIT AT BLANK",

      "|  STRIP",

      "|  l:",

  "?",

      "   CONSOLE",                                        
      "|z:ZONE W1 CASEI ALL /QUIT/!/END/!/SHUT/!/STOP/",   
      "|  PIPESTOP",                                       
  "?z:",                                                   
      "|  SPEC /Unknown command '/ 1 1-* N /' entered./ N",
      "|  CONSOLE"                                         

Without every after the "? CONSOLE", it works perfectly, with it a bad
command isn't send back and the pipe goes into a "VM READ".  When it
get's  into this situation, a bad CONSOLE command is displayed, but a
valid command seems to be ignored:

x                            
Unknown command 'x' entered. 
stop                       
                                        (VM READ)

Ideas?

Frank M. Ramaekers Jr.
Systems Programmer                   MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co.   Phone: (254)761-6649
1200 Wooded Acres Dr.                Fax:   (254)741-5777
Waco, Texas  76710
        

 



_____________________________________________________
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
[email protected].

Reply via email to