  Nested procedures and DCL SYS$INPUT? 
 The Question is:
 
Help Please,
 
I have included two .COM files, CEL and CEL1 along with the SET VER and
SET NOVER output from SUBMITting them to batch. These command files worked
until we upgraded to OpenVMS 7.2-1 from 7.1-2. Can you tell my why my
command procedure input is being read twice -- once as command procedure
input and once as erroneous command lines?  I am inputting data to the
command procedure exactly as it states in the OpenVMS Manual (16.2.2).
 
Please do not give the same response you gave to wiz_4810. You can see
from the output that my .COM files do in fact read the input but the commands
are still within the command stream. The exact same .COM files worked for
over a year until we upgraded to 7.2 last Friday. I have also included my
LOGIN.COM; so you can see there is nothing there which should cause this
command procedure input error
 
Thanks,
 
Chris Lewis
christopher.lewis@fredonia.edu
 
 
 
-----------------------------
LOGIN.COM:
 
$!
$! Login.Com for all AIS and STAFF
$!
$ WRITE SYS$OUTPUT "LOGIN.COM DONE"
 
 
 
-----------------------------
CEL.COM:
 
$ WRITE SYS$OUTPUT "CEL.COM STARTING"
$! SET VER
$ ASSIGN/NOLOG/USER_MODE SYS$COMMAND: SYS$INPUT
$ @cel1
UG
$ WRITE SYS$OUTPUT "CEL.COM DONE"
 
 
 
-----------------------------
CEL1.COM:
 
$ WRITE SYS$OUTPUT "CEL1.COM STARTING"
$ INQUIRE ZZ
$ WRITE SYS$OUTPUT "INPUT WAS: ''ZZ'"
$ WRITE SYS$OUTPUT "CEL1.COM DONE"
 
 
 
-----------------------------
CEL_SET_NOVER.LOG:
 
$ set noon
LOGIN.COM DONE
CEL.COM STARTING
CEL1.COM STARTING
INPUT WAS: UG
CEL1.COM DONE
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
 \UG\
CEL.COM DONE
  FINANCE      job terminated at 31-JAN-2001 09:30:22.04
 
  Accounting information:
  Buffered I/O count:                 53      Peak working set size:       1920
  Direct I/O count:                   28      Peak virtual size:         168208
  Page faults:                       146      Mounted volumes:                0
  Charged CPU time:        0 00:00:00.03      Elapsed time:       0 00:00:00.38
 
 
 
-----------------------------
CEL_SET_VER.LOG:
 
$ set noon
LOGIN.COM DONE
CEL.COM STARTING
$ ASSIGN/NOLOG/USER_MODE SYS$COMMAND: SYS$INPUT
$ @cel1
$ WRITE SYS$OUTPUT "CEL1.COM STARTING"
CEL1.COM STARTING
$ INQUIRE ZZ
UG
UG
$ WRITE SYS$OUTPUT "INPUT WAS: UG"
INPUT WAS: UG
$ WRITE SYS$OUTPUT "CEL1.COM DONE"
CEL1.COM DONE
UG
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
 \UG\
$ WRITE SYS$OUTPUT "CEL.COM DONE"
CEL.COM DONE
  FINANCE      job terminated at 31-JAN-2001 09:26:55.39
 
  Accounting information:
  Buffered I/O count:                 53      Peak working set size:       1936
  Direct I/O count:                   30      Peak virtual size:         168208
  Page faults:                       147      Mounted volumes:                0
  Charged CPU time:        0 00:00:00.03      Elapsed time:       0 00:00:00.19
 
 
 The Answer is:
 
  The OpenVMS Wizard would recommend against the use of this particular
  DCL construct -- reading from sys$input from within a set of nested
  command file is something the Wizard views as questionable -- though
  the Wizard is aware of an open problem report here.
 
