MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2010

Re: Problem solved, Re: Sorting DSPOBJD outfile by ascending date



fixed

Dennis,

I don't remember the details, but in v5r1, or so IBM did change an
existing outfile format...

Charles

On Thu, Jun 24, 2010 at 3:52 PM, Dennis Lovelady <iseries@xxxxxxxxxxxx> wrote:
Well, it's a pretty important allegation that IBM have historically changed
some (any) record format. Especially in the way you are describing
(repurposing or reformatting a field).  They have, many times, added to the
record layouts (QADSPOBJ - the output format for DSPOBJD has been through
many changes), but the kind of change you are describing is vastly different
from that.  And if you actually read those MTU I think you'll find that to
be the case.

As far as I know, IBM have maintained compatibility for all output files all
the way back to V1 (and indeed to the S/38).  So, I say again: what files
were changed and when?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"What the country needs are a few labor-making inventions."
       -- Arnold Glasow



I think it's a standard line in most Memo To Users about which output
file
formats got changed with a release.

Since I am constantly staying on the latest releases, and have multiple
partitions to support, not all partitions are immediately on the new
release.  (Gotta sleep sometime.)  Therefore the utilities that I use
which span releases cannot be dependent on formats in output files.
API's
are my approach.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:   "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
To:     "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date:   06/24/2010 02:16 PM
Subject:        RE: Problem solved, Re: Sorting DSPOBJD outfile by
ascending date
Sent by:        midrange-l-bounces@xxxxxxxxxxxx



This is interesting, Rob!  What and when?

 Has IBM changed output file
formats in the past?  Yes.

If we were all using APIs instead of DSPOBJD (as you say the vendors
who
do
it right are doing), this would be a non-issue, so why do we care?
Personally, I stopped using DSPOBJD except for Q&D CL back in V2R3.  I
thought everyone had.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Tried to play my shoehorn... all I got was footnotes!


Personally I don't care WHY it works that way.  Wish it were
different.
True date field would be best.  Second best would be YYYYMMDD.
Disruptive?  Yes.  If they changed it would customers have to change
code?
 Yes.  Do I care?  No.  Would vendors care?  Not those that do things
right and use list api's instead of outfiles.  Has IBM changed output
file
formats in the past?  Yes.

Have you submitted a DCR?  Has anyone else?  Have I (on this)?  No.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:   "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-
l@xxxxxxxxxxxx>
Date:   06/24/2010 12:33 PM
Subject:        Re: Problem solved, Re: Sorting DSPOBJD outfile by
ascending date
Sent by:        midrange-l-bounces@xxxxxxxxxxxx



Hi, James:

Ouch! I even tried CHGSYSVAL QDATFMT 'YMD' and then ran my DSPOBJD,
but
to no avail...

I thought that someone would have entered a PMR or DCR about this by
now
... And what about all the folks in countries where MDY is not the
popular choice for date format?  This seems to have been a very
strange
choice by IBM.

Does anyone know why this works this way?

Thanks,

Mark

 > On 6/24/2010 11:35 AM, James H. H. Lampert wrote:
Mark S. Waterbury wrote:

Just issue:
      CHGJOB JOB(*) DATFMT(*YMD)

Then run your DSPOBJD command.

That was the very first thing I tried. Only the "Display Date" is
in
job
date format.


--
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.


--
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.


--
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.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact