ESPWSS900I ENDING QUOTE ASSUMED, 'AIX_JOB PORTALTST.%ESPAHH%ESPAMN%ESPASS
ESPWSS101W INVALID COMMAND, AGENT+
ESPWSS628W INVALID COMMAND NAME SYNTAX
ESPWSS101W INVALID COMMAND, ENDJOB')
# this is required for when the ESPmgr command is issued from the command line
# and not part of an existing ESP managed script
export ESPAGENTDIR ESPAPPLMGR
# user1 is set to the first arg. To TRACKING ID
# user2 is set to the second arg. To JOBNAME
# user3 is set to the third arg. To Rundate
# user4 is set to the forth arg. Time
# This is used to add a time stamp qualifier to the ESP WOB.
# This sets the job name to the clientid.
# Here the ESPmgr command is issued. The applname used is FTFAPPL. This man not
# be the final production appl. For the ESPmgr command to work the FTFAPPL must
# be opened on the ESP Queue.
/ESP_Agent/prod/ESPmgr "$JMFLINK.$QUAL/FTFAPPL.0/main ACTION INSERT Type(LINK) Process LateEnd('now plus 5 min') Statements(ESP TRIGGER $EVENT USER1('$USER1') USER2('$USER2') USER3('$USER3') USER4('$USER4') cs)"
Just to provide an update:We decided to pass the TRIGGER command instead of the APPLINS command when calling ESPLMI from powershell. Values for the job definition are passed to the USER fields and the corresponding event is triggered based on job type. Within the application there is a link workload object that uses the APPLINS command to insert the job definition in the latest generation of our ADHOCAPP application. See below example of the link workload object used for Unix job types:JOB ADHOCPTL LINK PROCESSRUN TODAYESP APPLINS APPL(ADHOCAPP.0)+STATEMENTS('UNIX_JOB %USER1..%ESPATIME;+AGENT %USER2;+SCRIPTNAME %USER3;+USER %USER4;+ENDJOB')ENDJOB