Identify error messages without printing back

[Luca Meyer]

Hello,

I often find myself to run long syntax and I would like to be able to easily
identify the location of the error within that syntax.

For instance, suppose at lines 5231-5232 of my syntax I have:

COMPUTE VAR1=VAR2+1.
EXE.

And when I run it at one point in my output windows (amongst tables and
graphs) I get:

>Error # 4285 in column 14.  Text: VAR2
>Incorrect variable name: either the name is more than 64 characters, or it
>is not defined by a previous command.
>This command not executed.

That error messagge does not tell me that the incorrect variable name is
written at line 5231. Is there anyway I can easily identify that position?

So far I have:

=> used SET PRINTBACK=ON and then searched in each output for "Error" and
"Warning" strings
=> with SET PRINTBACK=OFF inserted several ECHO with sequential numbers in
the syntax so that I could more or less find out the portion of syntax with
error
=> searched within the syntax for the "VAR2" string

This is just an example but sometimes I get errors far more complex to
locate in the syntax that this...

Thanks,

Luca

Luca MEYER
Ricerche di mercato, analisi di dati & altro
www.lucameyer.com <http://www.lucameyer.com/>  - Tel: [phone]

----------------------------------------------------------------------------
---------------------------------------------------
Il messaggio trasmesso e' rivolto esclusivamente alla persona o al soggetto
al quale e' indirizzato e potrebbe contenere informazioni riservate o
confidenziali. Ne sono proibiti qualunque modifica, inoltro o divulgazione a
terzi e qualunque altro uso. Chiunque riceva questa comunicazione per errore
e' pregato di contattare il mittente e distruggere il messaggio. Grazie.
----------------------------------------------------------------------------
---------------------------------------------------

[Melissa Ives]

Got to Edit-->Options and select the Viewer tab.  Check the button that
says 'Display commands in the log'.  Then when you have an error, it
will appear just following the syntax where the error occurs.

Melissa

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of
Luca Meyer
Sent: Tuesday, May 15, 2007 1:13 AM
To: [hidden email]
Subject: [SPSSX-L] Identify error messages without printing back

Hello,

I often find myself to run long syntax and I would like to be able to
easily identify the location of the error within that syntax.

For instance, suppose at lines 5231-5232 of my syntax I have:

COMPUTE VAR1=VAR2+1.
EXE.

And when I run it at one point in my output windows (amongst tables and
graphs) I get:

>Error # 4285 in column 14.  Text: VAR2
>Incorrect variable name: either the name is more than 64 characters, or

>it is not defined by a previous command.
>This command not executed.

That error messagge does not tell me that the incorrect variable name is
written at line 5231. Is there anyway I can easily identify that
position?

So far I have:

=> used SET PRINTBACK=ON and then searched in each output for "Error"
and "Warning" strings => with SET PRINTBACK=OFF inserted several ECHO
with sequential numbers in the syntax so that I could more or less find
out the portion of syntax with error => searched within the syntax for
the "VAR2" string

This is just an example but sometimes I get errors far more complex to
locate in the syntax that this...

Thanks,

Luca

Luca MEYER
Ricerche di mercato, analisi di dati & altro www.lucameyer.com
<http://www.lucameyer.com/>  - Tel: [phone]

------------------------------------------------------------------------
----
---------------------------------------------------
Il messaggio trasmesso e' rivolto esclusivamente alla persona o al
soggetto al quale e' indirizzato e potrebbe contenere informazioni
riservate o confidenziali. Ne sono proibiti qualunque modifica, inoltro
o divulgazione a terzi e qualunque altro uso. Chiunque riceva questa
comunicazione per errore e' pregato di contattare il mittente e
distruggere il messaggio. Grazie.
------------------------------------------------------------------------
----
---------------------------------------------------


PRIVILEGED AND CONFIDENTIAL INFORMATION
This transmittal and any attachments may contain PRIVILEGED AND
CONFIDENTIAL information and is intended only for the use of the
addressee. If you are not the designated recipient, or an employee
or agent authorized to deliver such transmittals to the designated
recipient, you are hereby notified that any dissemination,
copying or publication of this transmittal is strictly prohibited. If
you have received this transmittal in error, please notify us
immediately by replying to the sender and delete this copy from your
system. You may also call us at [phone] for assistance.

[Luca Meyer]

Hi Melissa,

Thanks for the suggestion. Following your suggestion in the output I find
the entire syntax, not just the erroneous part of it. That is the way I am
currently doing it, but what I would like is the program to output only
those parts of the syntax containing errors and/or warnings with indication
on where I can find them in the syntax.

Cheers,
Luca

-----Messaggio originale-----
Da: Melissa Ives [mailto:[hidden email]]
Inviato: martedì 15 maggio 2007 16.34
A: Luca Meyer; [hidden email]
Oggetto: RE: [SPSSX-L] Identify error messages without printing back

Got to Edit-->Options and select the Viewer tab.  Check the button that says
'Display commands in the log'.  Then when you have an error, it will appear
just following the syntax where the error occurs.

Melissa

-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of
Luca Meyer
Sent: Tuesday, May 15, 2007 1:13 AM
To: [hidden email]
Subject: [SPSSX-L] Identify error messages without printing back

Hello,

I often find myself to run long syntax and I would like to be able to easily
identify the location of the error within that syntax.

For instance, suppose at lines 5231-5232 of my syntax I have:

COMPUTE VAR1=VAR2+1.
EXE.

And when I run it at one point in my output windows (amongst tables and
graphs) I get:

>Error # 4285 in column 14.  Text: VAR2
>Incorrect variable name: either the name is more than 64 characters, or

>it is not defined by a previous command.
>This command not executed.

That error messagge does not tell me that the incorrect variable name is
written at line 5231. Is there anyway I can easily identify that position?

So far I have:

=> used SET PRINTBACK=ON and then searched in each output for "Error"
and "Warning" strings => with SET PRINTBACK=OFF inserted several ECHO with
sequential numbers in the syntax so that I could more or less find out the
portion of syntax with error => searched within the syntax for the "VAR2"
string

This is just an example but sometimes I get errors far more complex to
locate in the syntax that this...

Thanks,

Luca

Luca MEYER
Ricerche di mercato, analisi di dati & altro www.lucameyer.com
<http://www.lucameyer.com/>  - Tel: [phone]

------------------------------------------------------------------------
----
---------------------------------------------------
Il messaggio trasmesso e' rivolto esclusivamente alla persona o al soggetto
al quale e' indirizzato e potrebbe contenere informazioni riservate o
confidenziali. Ne sono proibiti qualunque modifica, inoltro o divulgazione a
terzi e qualunque altro uso. Chiunque riceva questa comunicazione per errore
e' pregato di contattare il mittente e distruggere il messaggio. Grazie.
------------------------------------------------------------------------
----
---------------------------------------------------


PRIVILEGED AND CONFIDENTIAL INFORMATION
This transmittal and any attachments may contain PRIVILEGED AND CONFIDENTIAL
information and is intended only for the use of the addressee. If you are
not the designated recipient, or an employee or agent authorized to deliver
such transmittals to the designated recipient, you are hereby notified that
any dissemination, copying or publication of this transmittal is strictly
prohibited. If you have received this transmittal in error, please notify us
immediately by replying to the sender and delete this copy from your system.
You may also call us at [phone] for assistance.