The output file is being created in the same place where the sql file is sitting
which is /sql/x.prt
In this case, I used SPOOL x.prt

i need the file to be created in /reports/x.prt

In this case,

I tried ....... SPOOL /../../../x.prt
also...
i tried ....... SPOOL '/../../../x.prt'
i tried ....... SPOOL "'/../../../x.prt'"
i tried ....... SPOOL "/../../../x.prt"

I even tried \..\..\..\x.prt

this is not an ANSI SQL question

which database system are you using? the thread will have to be moved to the appropriate forum

SQLPLUS question? on how to use SPOOL?

I've been to the Oracle forum... they've responded similar to you.

Never heard of it I'm afraid (as such, you will probably struggle to get much response from anyone).

Is it a server or desktop database?

pootle flump ur codings are working excelent.

they told you it wasn't an ANSI SQL question???

No, we told him/her it's neither a SQL nor an Oracle question, because it's essentially a Windows problem.

The path is totally messed up: it's not a valid Windows path (because of the forward slash), and it's logically wrong because the path denotes a directory one level up starting at the root directory...

Forward-slashes are fine on Windows. But that still doesn't make it an SQL question, of course.

In theory yes, but not for all applications (or built-in commands). Notepad can handle forward slashes, but e.g. Textpad or the DIR command cannot (as they use the forward slash for parameters).

SQL*Plus can deal with forward slashes in the SPOOL command, but not for "including" files (e.g. @/path/to/somescript.sql)

That makes sense. I usually use forward slashes only in code I write, and I don't care about Windows or not in this context. Fortunately, parameters are irrelevant in that case.