: If you take out the first @ then it will attempt to replace @SCRIPT:file with
: the actual file name in the script where you call JobModify. What you want
: to get is to have @SCRIPT: in the script of the job being modifyed.
: The message you probably refer to, was about having a space between
: "@SCRIPT:" tag and a file name following that tag. Once they
: took out the space the script started to work.

: If you do everything correctly and refer to an existing file (no spelling
: errors) then when you open the target script in the debugger you should
: see the contents of the that file in place of the "@SCRIPT:[file name
: here]" line.

yep, if i put
@SCRIPT:d:\CognosData\CubePoint\automation.jal
in another job and debug it, the script inside the text file comes up as you say. However, when i put it in a jobmodify script like:
JobModify (428, "MSG_SCRIPT_CODE", "@SCRIPT:d:\CognosData\CubePoint\automation.jal")

then the "Line 0" error comes up.

That's why you need to use @@SCRIPT: there.

: yep, if i put
: @SCRIPT:d:\CognosData\CubePoint\automation.jal
: in another job and debug it, the script inside the text file comes up as you
: say. However, when i put it in a jobmodify script like: JobModify (428,
: "MSG_SCRIPT_CODE",
: "@SCRIPT:d:\CognosData\CubePoint\automation.jal")

: then the "Line 0" error comes up.

: That's why you need to use @@SCRIPT: there.

same error occurs when i use @@SCRIPT

: same error occurs when i use @@SCRIPT

my entire code in that job is:

----------------------------------------------
jobmodify (428, "MSG_SCRIPT", "Y")

jobmodify (428, "MSG_SCRIPT_TYPE", "JAL")
jobmodify (428, "MSG_START", "Y")
jobmodify (428, "MSG_FINISH", "Y")
jobmodify (428, "MSG_ACTIONS", "SS,FS")

JobModify (428, "MSG_SCRIPT_CODE", "@@SCRIPT:d:\CognosData\CubePoint\automation.jal")
----------------------------------------------

do you get the same error when you try this?

Yes, I get the same error because it attempts to replace @SCRIPT... tag with the file contents which in turn leads to a script syntax error.

Here is what you use as a workaround
1. Create new user defined statement using Tools/Script Library menu. Let's call it RunCube. It should have no parameters and no return value. In the code of this statement enter d:\\CognosData\\CubePoint\\automation.jal

2. In the code of the job running JobModify commands
Replace line JobModify (428, "MSG_SCRIPT_CODE", "@@SCRIPT: ....
with
JobModify (428, "MSG_SCRIPT_CODE", "RunCube()"

By the way, what are you trying to achieve? I am sure I can suggest a more efficient method if I only understand the goal. Please start a new message thread as this tread is already very long and as a result hard to read.

: my entire code in that job is: ----------------------------------------------
: jobmodify (428, "MSG_SCRIPT", "Y")

: jobmodify (428, "MSG_SCRIPT_TYPE", "JAL")
: jobmodify (428, "MSG_START", "Y")
: jobmodify (428, "MSG_FINISH", "Y")
: jobmodify (428, "MSG_ACTIONS", "SS,FS")

: JobModify (428, "MSG_SCRIPT_CODE",
: "@@SCRIPT:d:\CognosData\CubePoint\automation.jal")
: ----------------------------------------------

: do you get the same error when you try this?

I tried what you suggested. It now calls the contents of the script properly at job start and finsih.
however, it doesnt read the @V"event" macroparameter properly. When i try debugging this script in another job which calls the script libary job runCube() on its own.
the line in runCube(): ChooseCase "@V"event"", ENDCHOOSE
changes to CHooseCase "", ENDCHOOSE -- in the debugger.

And so the file runs and ends without doing anything because there was no match in the event.

: Yes, I get the same error because it attempts to replace @SCRIPT... tag with
: the file contents which in turn leads to a script syntax error.

: Here is what you use as a workaround
: 1. Create new user defined statement using Tools/Script Library menu. Let's
: call it RunCube. It should have no parameters and no return value. In the
: code of this statement enter d:\\CognosData\\CubePoint\\automation.jal

: 2. In the code of the job running JobModify commands
: Replace line JobModify (428, "MSG_SCRIPT_CODE", "@@SCRIPT:
: ....
: with
: JobModify (428, "MSG_SCRIPT_CODE", "RunCube()"

: By the way, what are you trying to achieve? I am sure I can suggest a more
: efficient method if I only understand the goal. Please start a new message
: thread as this tread is already very long and as a result hard to read.