Correct me if I am wrong, you are attempting to run a job on some agent where the script library does not contain the referenced user-defined statement? Right? At job run-time 24x7 only deploys the job cod to the agent. It doesn't attempt to deploy all referenced files, library entries, etc... You need to take care of that. For instance, if you want to deploy server side version of the library every time the job runs you can use RemoteCopySettings JAL statement with "SCRIPT LIBRARY" parameter. On the other hand, if you don't expect the code to change you can manually create the same user-defined statement on the agent and this way avoid getting "keyword not found" error and dealing with the settings replication issues. : I think I solved my issue, but I'm posting in case there is a better way to
: do
: this. I was trying to use a script that I had saved in the script library on
: my
: scheduling server in a job that runs remotely on my application server. I
: kept
: getting errors about a keyword not being found. : I found that if I logged into my application server and launched the 24x7
: GUI,
: I could then open the script library and create the script locally (even
: though
: 24x7 was still running as a Remote Agent and connected to the job database on
: the
: scheduling server). Once I did that I could run the job from the scheduling
: server normally. : Is this intentional or might there be a change in the future so that jobs
: will
: reference the Script Library in the job database that that the job is in?
|
