Lucy,
Thanks so much for your patience with me. I still seem to be getting the same results. The "ESPlmi" program hits the sem-colon (;) after the first part of the External Dependency definition STATEMENTS('UNIX_JOB NZD_NZWBTAPADATE_ST1 EXTERNAL SCHEDULED('' 6:00 OCT 1 2014'') APPLID(NZDPADAT);RUN ANY;RELEASE ADD(C.R_ST1);ENDJOB') and chokes. I am actually executing a series of commands from a script. The series is:
/usr/local/ESP/Agent/ESPlmi -sespwss-dev.cols.ent.nwie.net:5301 -uwalteg5 -pMom#09Ka "-cvset INTEG_LEVEL 'GTW1' TABLE(NZDST1I)" > /beta/nfid/BetaFlows/log/LIFE_CycleDate20160123_NZDBTASD.esp.log
/usr/local/ESP/Agent/ESPlmi -sespwss-dev.cols.ent.nwie.net:5301 -uwalteg5 -pMom#09Ka "-ctrigger NZDST1.NZDBTASD AT(' 6:00 OCT 1 2014') ADD HOLD" >> /beta/nfid/BetaFlows/log/LIFE_CycleDate20160123_NZDBTASD.esp.log
/usr/local/ESP/Agent/ESPlmi -sespwss-dev.cols.ent.nwie.net:5301 -uwalteg5 -pMom#09Ka "-cAPPLINS APPL(NZDBTASD.0) STATEMENTS('UNIX_JOB NZD_NZWBTAPADATE_ST1 EXTERNAL SCHEDULED('' 6:00 OCT 1 2014'') APPLID(NZDPADAT);RUN ANY;RELEASE ADD(C.R_ST1);ENDJOB')" >> /beta/nfid/BetaFlows/log/LIFE_CycleDate20160123_NZDBTASD.esp.log
/usr/local/ESP/Agent/ESPlmi -sespwss-dev.cols.ent.nwie.net:5301 -uwalteg5 -pMom#09Ka "-cvset INTEG_LEVEL 'BETA' TABLE(NZDST1I)" >> /beta/nfid/BetaFlows/log/LIFE_CycleDate20160123_NZDBTASD.esp.log
All of the commands are working except the External Dependency. The "/beta/nfid/BetaFlows/log/LIFE_CycleDate20160123_NZDBTASD.esp.log" contains
-->vset INTEG_LEVEL 'GTW1' TABLE(NZDST1I)
-->trigger NZDST1.NZDBTASD AT(' 6:00 OCT 1 2014') ADD HOLD
ESPWSS2502I EVENT TRIGGERED
-->APPLINS APPL(NZDBTASD.0) STATEMENTS('UNIX_JOB NZD_NZWBTAPADATE_ST1 EXTERNAL SCHEDULED('' 6:00 OCT 1 2014'') APPLID(NZDPADAT)
ESPWSS900I ENDING QUOTE ASSUMED, 'UNIX_JOB NZD_NZWBTAPADATE_ST1 EXTERNAL SCHEDULED(' 6:00 OCT 1 2014') APPLID(NZDPADAT)
-->RUN ANY
ESPWSS101W INVALID COMMAND, RUN
-->RELEASE ADD(C.R_ST1)
ESPWSS171E INVALID EVENT ID, ADD(C.R_ST1)
-->ENDJOB')
ESPWSS101W INVALID COMMAND, ENDJOB')
-->vset INTEG_LEVEL 'BETA' TABLE(NZDST1I)
As you can see the External Dependency definition is fine up through the ". . .APPLID(NZDPADAT)". It appears to hit the semi-colon (;) and thinks it needs a closing quote, then errors the remainder of the commands. When I look at the APPL in the Execution Queue, the External Dependency is added, but is releasing the APPLEND instead of the C.R. Also, when I do an AJ command the External Dependency definition in the execution queue appears to be SCHEDULED properly, just releasing (SUCCESSOR) the wrong job.
The command sent to the server is: AJ NZD_NZWBTAPADATE_ST1 APPL(NZDBTASD.55)
Job=NZD_NZWBTAPADATE_ST1, Wob=UJ, PredWait, Hold=1
Expected completion ...... Not Available
External, ShortName=NZD_NZWB.~0000003
Predecessors:
Job=C.R_ST1, Wob=AS, Wait
Successors:
Job=APPLEND.NZDBTASD_ST1, Wob=AE, PredWait, Hold=2
Appl=NZDBTASD.55, Held
Scheduled ................ 2014/10/01 06:00
Built .................... 2014/12/01 12:22
DueOutPropagation, Event=NZDST1.NZDBTASD, TrigUser=WALTEG5
ESPWSS000 -->
I tried removing the semi-colon after the ". . .APPLID(NZDPADAT)" and got the same set of errors as above beginning with "ESPWSS900I ENDING QUOTE ASSUMED. . ." except it erred separately on the "RUN" and the "ANY" words. In the past, I have tried the command with no semi-colons, but still erred out all the commands after ". . .APPLID(NZDPADAT)".
I beginning to believe there is a bug in "ESPlmi". Not really sure where to go from here. Your insight is greatly appreciated.
Thanks,
George