• Subject: RUNQRY behavior
  • From: "Carl Galgano" <cgalgano@xxxxxxxxxxxxxxxxx>
  • Date: Sat, 27 Jan 2001 10:00:41 -0500
  • Importance: Normal

This may seem like a stupid newbie question (I've done work on the AS400
since 1988 and the S/38 before that), but I have noticed something about the
RUNQRY command that I can not figure out.

If I specify RUNQRY *N logicalfile/library, I would expect that the RUNQRY
command would display the file in the sequence specified by the logical
file, not the arrival sequence of the file, but that is not the case.  It
always seems to use the arrival sequence.  Is this correct?  Can it be
overridden to use the key sequence in the LF.  I know that I can create a
query over the file and just use the RUNQRY command to run the query
defn..... it just seems illogical how the RUNQRY command works.....

What do you guys (that's New York plural for all sexes) think?
Carl


Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw Avenue, Suite 800
Marietta, GA  30060
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:cgalgano@ediconsulting.com
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and
Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight

"You ain't gonna learn what you don't want to know" - rw

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].