RE: [sqr-users] Fwd: Puzzling Input Argument File Error

["Knapp, Richard" <KnappR@umsystem.edu>]

SQRW is a windows application so it expects input files to have the
standard windows line terminators (CRLF).  Why are you trying to use a
unix file with unix line terminators (LF)in a windows application?
Transfer the file to the windows box with FTP and that will convert to
the destination OS line terminator or find some way to preserve the
crlfs. 

Richard Knapp
Database Programmer/Analyst
Institutional Research and Planning
University of Missouri System
573-882-8856
knappr@umsystem.edu


-----Original Message-----
From: sqr-users-bounces+knappr=umsystem.edu@sqrug.org
[mailto:sqr-users-bounces+knappr=umsystem.edu@sqrug.org] On Behalf Of
Jennifer Lee
Sent: Friday, October 08, 2004 1:42 PM
To: sqr-users@sqrug.org
Subject: [sqr-users] Fwd: Puzzling Input Argument File Error


>>> Jennifer Lee 10/6/2004 7:47:19 AM >>>
Hi,

I would like to seek advice from this group about an input argument
file error:

Q1) If an input argument file is to be up loaded into a Unix
environment, does it matter to SQRW whether or not each argument line
ends with '\r \n' (return followed by new-line) or simply '\n'?

Q2) If an argument line only contains '\n', will SQRW know that it
should take that as a 'null' value?

Q3) What happens after SQRW reads in a line with '\n'?  Will it assume
that there is no more input values or will it continue to read in values
from the argument file until end of the file?

Q4) Are there some watch-outs for using argument files for input
command?  What are the situations where 'Error getting INPUT' can
occur?

Some background info:
1) We are using SQR for PeopleSoft/8.20.  Sun's Solaris is our Unix
OS.

2)  I was able to run from my PC an sqr program with all input values
in an argument file.   

The command line looks like this: 
                sqrw.exe ...  @c:\csqr\umfac001.parm

3) There are five input statements in the program:
input $Parm1 'Enter Parm1 (Optional, Press ENTER to continue)'
input $Parm2 'Enter Parm2 (Optional, Press ENTER to continue)'
input $Parm3 maxlen=5 'Enter Parm3'
input $Parm4 maxlen=30 'Enter Parm4 (Optional, Press ENTER to
continue)'
input $Parm5 maxlen=10 'Enter Parm5'

4) The argument file used by the program looks like this (from a PC
text editor):
    Line 1:A blank space followed by a catridge return
    Line 2:A catridge return only
    Line 3:OSF followed by a catridge return
    Line 4:A catridge return only
    Line 5:2005 

5) Because we are trying to run this sqr program outside the Process
Scheduler but with a Unix script calling SQRW, we up loaded the program
and the argument file into our Unix environment.  Of course the @
argument has the proper Unix file path and file name.

6) When the same program was executed on Unix with a Unix script, the
program died right after 'Enter Parm3' is display in the log file.  

7) Here's what it was logged in the .err output file:
              Error on line 162:
              (SQR 2500) Error getting INPUT.
              SQR for PeopleSoft: Program Aborting.

Thanks in advance for your help!!


This e-mail and its attachments have been scanned for viruses.
EAS - Systems Support, OIT, University of Minnesota


_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users