Larry,
The ";INFO=&" in the previous line causes the CI to try and append the
'commented' line as the argument of the infostring parameter. Thus it
expects to find a quote and not a #. Just switch the order of the two
'rename' lines and you should be fine.
Regards
Paul Christidis
I have a job that I added a pound sign (#) in the 2nd column, after the
exclamation point, see below:
!#*************************************************
!# Coldwater Creek Custom Code
!# Clean-up FTPERROR group from yesterday's aborts
!#*************************************************
! RUN MAIN.PUB.VESOFT,MPEX;INFO=&
!# "RENAME CW######(CREDATE=(TODAY-1)),CX######"
! "RENAME CW######(CREDATE=(TODAY-1)),./CX######.txt"
I made this change yesterday and now the job aborts on this modification,
see below:
:#*************************************************
:# Coldwater Creek Custom Code
:# Clean-up FTPERROR group from yesterday's aborts
:#*************************************************
: RUN MAIN.PUB.VESOFT,MPEX;INFO=&
:# "RENAME CW######(CREDATE=(TODAY-1)),CX######"
Expected ' or " to start string. (CIERR 682)
REMAINDER OF JOB FLUSHED.
CPU sec. = 2935. elapsed min. = 82. THU, JAN 10, 2002, 1:37 AM.
Why does the comment lines above this line work and the rename now aborts?
Thanks in advance,
Larry (confused) Barnes
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|