|
Hi, Folks:version.
We have a WRKSPLF workalike-plus-extras program, and it has been serving
our
needs fairly well. We found, though, that the output sequence of the
in-house command does not match the sequence presented in the IBM
Further, the sequence presented in the IBM version doesn't match theresult
of QUSLSPL for any particular user.in
We've known for years that SAV/HLD are shown last, and we thought that
within that list the files were presented in priority sequence and then
opened sequence (Created date/time). But when we do (IBM's) WRKSPLFis
username OUTPUT(*PRINT) we are unable to determine the sort order (this
on a V5R3 system).the
http://code.midrange.com/1e37238551.html shows the point of question.
This
is extracted from page 1 of WRKSPLF output for a certain user. Notice
create date/time of the last entry. I was tempted to think jobnumber/name
may come into play here, but one can see that there are two entries forlist
each
of two jobs, and the order is JOB1 JOB2 JOB2 JOB1.
So have any of you landed on an exact sort order that's used by this
command? Have any of you any idea why that output's sequence would be
different from QUSLSPL output?
Dennis E. Lovelady
AIM/Skype: delovelady MSN: fastcounter@xxxxxxxxxxxx
<http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --
"I either want less corruption, or more chance to participate in it."
- Ashleigh Brilliant
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.