|
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
Jason Hoskins
Joined: 12 Mar 2004 Posts: 68
|
|
|
|
Just create a job the has "24x7tower.com" or "24x7sc.com" in it and it should replace it. Within this job include a bunch of bogus lines ( I used 50 + in my test just now) and it cut it off with the JobModify command.
|
|
Mon Aug 18, 2008 1:50 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
|
|
Thanks, please give me some time to play with this.
|
|
Mon Aug 18, 2008 1:56 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
|
|
I'm able to reproduce this issue. Indeed there appears some limitation on the size of the value that can be passed using JobModify statement. I'm not sure about the exact place or cause of this limitation.
Here is a workaround that I found for this issue. It is possible to replace the JobModify with a user-defined statement using 24x7 DDE interface.
Create a new user-defined statement called SetJobScriptUsingDDE and taking 2 parameters: JobNo having numeric type and Script having string type.
In the code of the statement paste the following
|
|
Dim(channel, number)
DDEOpen("24x7 Scheduler", "JDL", channel)
Dim(what, string)
Concat( JobNo, "\tSCRIPT", what)
DDESetData(channel, what, Script)
DDEClose(channel) |
In the job script replace
JobModify( job_id, "SCRIPT", job_script )
with
SetJobScriptUsingDDE(job_id, job_script)
|
|
Tue Aug 19, 2008 12:42 am |
|
|
Jason Hoskins
Joined: 12 Mar 2004 Posts: 68
|
|
|
|
Why does the 'DDEClose(channel)' take so long? I have to wait 20 or so minutes.
|
|
Tue Aug 19, 2008 9:08 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
|
|
I don't have an answer for that. For me it takes about a minute which is also suspiciously long. Try running the job as a detached process so it can "talk" to the scheduler via DDE as a separate process, which might help.
Also, you can save time, by declare "channel" as a global variable and calling DDEOpen and DDEClose only once for all jobs
Last edited by SysOp on Tue Feb 08, 2011 8:12 pm; edited 1 time in total |
|
Tue Aug 19, 2008 10:13 am |
|
|
mpadilla
Joined: 02 Jul 2008 Posts: 33
|
|
|
|
Do you have any other work around for this issue?
I need to visit 300+ scripts to update them.
The DDE option takes too long (15-20 min per script)
|
|
Tue Feb 08, 2011 4:55 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7849
|
|
|
|
If you have a site license or a second license, you can use COM or Java APIs to perform the same operations. These APIs should be much faster, direct communications, no DDE timeouts, no script size limits, etc...
Another alternative is using a JAL script job to perform the required operation. Take a look at script examples provided in JobList and JobDescribe, JobModify topics in the on-line help. If you choose this method, make sure the job is run non-detached.
|
|
Tue Feb 08, 2011 8:21 pm |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|