Re: RUNSQLSTM Source File Record Length

Length for source file for RUNSQLSTM is 92 - just like most other source files on the iSeries have always been. There is no connection between RUNSQLSTM and QMQRY source = that has record length 91.

There is nothing in the help for RUNSQLSTM to tell you this, but the spooled file with the results of the run show the length of 80. The information we need is buried in the chapter on using the SQL Statement Processor in the SQL Programming manual - "If the record length of the source member is longer than 80, only the first 80 characters will be read."

That chapter will be well worth a read. There's stuff about commitment control and processing with errors, which can be helpful.

What is the origin of your statements? What is the app that gives you the statement? You're using SQL, you say, to insert into a source PF - how is the source statement generated in the first place? Just curious.

As to generating statements into a RUNSQLSTM source file on the iSeries, you can just substring and be happy. I just verified that additional blanks are not added at end of record - the statement can wrap in the middle of words with no problem. Not so readable and not as editable, but so it goes.

Then there is the iSeries Navigator SQL statement processor - that might be able to generate source of the right length. I don't have iSeries Access on my home machine to test this.

Just a gentle reminder - RTFM - if you can find the right one - heh!

HTH
Vern

At 06:19 AM 6/25/2007, you wrote:

I'm generating SQL statements to a source file in order to run that source
file member through RUNSQLSTM. The SQL statements are about 150 characters
long so I created a source physical file with a record length of 200
thinking that this would solve my problem. My SQL statements were now
complete but when I ran the source member through RUNSQLSTM it seemed to
ignore everything past character 79! What documentation I could find said
the same thing about QM QRY.

I'm using SQL to insert into the source physical file. Is there an easy way
to generate each SQL statement so that it runs over two lines without
resorting to another pass over the resulting member with another program?



Thanks,
Mike Pantzopoulos

_________________________________________________________________
Advertisement: Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=june07_endtext_salary&_m=EXT

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.