I have a VBScript job that when I exit and restart
changes to JALScript in the properties. I have uninstalled
and re-installed but same problem. If I run using Test Mode
it runs fine as VBScript (unless I restart) but if I
run using Normal my script runs up to Sub Main().

Is there a number of lines limit for VBScript. There are
1511 lines in my script.

Look if your VBScript job is set to run detached. I think when you run it in test mode you force it to run in the foreground in the same 24x7 instance and everything is working as expected. When it's run on schedule, it runs detached in a separate instance which doesn't have access to the main 24x7 instance (scheduling engine) and that's why you don't see it changing properties of another job. Detached mode is for shielding the scheduler from potentially unstable jobs such as VBScipt jobs that tend to loose system resources. You can control detached mode using detached job property.

: I have a VBScript job that when I exit and restart
: changes to JALScript in the properties. I have uninstalled
: and re-installed but same problem. If I run using Test Mode
: it runs fine as VBScript (unless I restart) but if I
: run using Normal my script runs up to Sub Main().

: Is there a number of lines limit for VBScript. There are
: 1511 lines in my script.

: Look if your VBScript job is set to run detached. I think when you run it in
: test mode you force it to run in the foreground in the same 24x7 instance
: and everything is working as expected. When it's run on schedule, it runs
: detached in a separate instance which doesn't have access to the main 24x7
: instance (scheduling engine) and that's why you don't see it changing
: properties of another job. Detached mode is for shielding the scheduler
: from potentially unstable jobs such as VBScipt jobs that tend to loose
: system resources. You can control detached mode using detached job
: property.

I think the real problem is that it changes from a VBscript
job to a JalScript job when the # of lines in myVBScript job
is greater than 1086. The job is VBScript (VBScript Icon showing)
but when I restart the scheduler the icon is now a JalScript job.

Is the script over 32000 characters long? Which version of the scheduler are you running?

In some old versions of 24x7 long scripts entered using copy & paste (at least partially) could spill over enternal storage size for the script field and override some other job properties. As a result other properties apears set to default after scheduler restart. That problem has been fixed in recent versions.

: I think the real problem is that it changes from a VBscript
: job to a JalScript job when the # of lines in myVBScript job
: is greater than 1086. The job is VBScript (VBScript Icon showing)
: but when I restart the scheduler the icon is now a JalScript job.

: Is the script over 32000 characters long? Which version of the scheduler are
: you running?

: In some old versions of 24x7 long scripts entered using copy & paste (at
: least partially) could spill over enternal storage size for the script
: field and override some other job properties. As a result other properties
: apears set to default after scheduler restart. That problem has been fixed
: in recent versions.

Yes. 33000+ without spaces and 44000+ with spaces. I was using
3.4.22 and now 3.4.24 and still have the same problem. I guess
even if i cut and paste 32000+ characters into 3.4.24 I
will experience the same problem?

Please consider splitting this script into 2 separate jobs each less then 32000 characters long or saving it as an external off-line file and using @SCRIPT tag in the job script to link to the off-line file in job run-time. After you change the job script make sure to reset other job properties or simply create a new job delete this one.
If you decide to split the job you can chain them using Run Another Job notification action.

: Yes. 33000+ without spaces and 44000+ with spaces. I was using
: 3.4.22 and now 3.4.24 and still have the same problem. I guess
: even if i cut and paste 32000+ characters into 3.4.24 I
: will experience the same problem?

: Please consider splitting this script into 2 separate jobs each less then
: 32000 characters long or saving it as an external off-line file and using
: @SCRIPT tag in the job script to link to the off-line file in job
: run-time. After you change the job script make sure to reset other job
: properties or simply create a new job delete this one.
: If you decide to split the job you can chain them using Run Another Job
: notification action.

Thank You. First I will try to clean up my code to reduce space and resources...
If that fails then I will split the job up.