Re: SQL Misbehaving -- MIDRANGE-L

OOPS - it was CHGATR - mea culpa (which is in Latin, so it sounds profound)

At 08:21 AM 3/22/02 -0500, you wrote:

>The command FIXATR does not exist on our V5R1machine.
>Vern, does DSPOBJD OBJ(FIXATR) OBJTYPE(*CMD) DETAIL(*FULL) show *IBM as the
>creator?
>
>Rob Berendt
>--
>"They that can give up essential liberty to obtain a little temporary
>safety deserve neither liberty nor safety."
>Benjamin Franklin
>
>
>
>                     Vernon Hamberg
>                     <vhamberg@attbi.com       To:     midrange-l@midrange.com
>                     >                         cc:
>                     Sent by:                  Fax to:
>                     midrange-l-admin@mi       Subject:     Re: SQL
> Misbehaving
>                     drange.com
>
>
>                     03/21/2002 07:07 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
>A command by this name exists on our v5r1 machine in QSYS, command
>processing program QP0LCCHA. You specify an IFS  path (generic is OK) and
>certain attributes. It does not look like the same thing.
>
>At 04:17 PM 3/21/02 -0500, you wrote:
> >I got the following from IBM:
> >
> >Info on the tool:
> >You can use this tool on a V4R3 or later system to change the attribute
> >information for objects.
> >
> >The library, FIXATR, contains the following objects:
> >- QLICHGAT     *PGM
> >- CHGATR        *CMD
> >
> >Program QLICHGAT is the program to process command CHGATR.
> >
> >You can use this command to change the attribute for a single object or a
> >group of objects.  You can change the attribute
> >to any character data.  The default on the command is *BLANK to set the
> >attributes to blank.
> >
> >This tool does not send many error messages.  If you specify an object
>name
> >that does not exist, you do not get an error
> >message.  You will get an error message if the library specified does not
> >exist.
> >
> >Please give me a call if you have questions.
> >Jim
> >
> >----- Original Message -----
> >From: "Vernon Hamberg" <vhamberg@attbi.com>
> >To: <midrange-l@midrange.com>
> >Sent: Thursday, March 21, 2002 12:38 PM
> >Subject: Re: SQL Misbehaving
> >
> >
> > > Yuk!! Maybe user profiles are corrupted. Something is clearly wrong,
>IMO.
> >A
> > > call to IBM is in order, I think.
> > >
> > > At 12:26 PM 3/21/02 -0500, you wrote:
> > > >I have values at V4R5M0
> > > >
> > > >----- Original Message -----
> > > >From: "Vernon Hamberg" <vhamberg@attbi.com>
> > > >To: <midrange-l@midrange.com>
> > > >Sent: Thursday, March 21, 2002 12:21 PM
> > > >Subject: Re: SQL Misbehaving
> > > >
> > > >
> > > > > What happens if you just do a DSPOBJD to the screen? The attribute
> >column
> > > > > is empty on the v5r1 system I'm on.
> > > > >
> > > > > At 12:17 PM 3/21/02 -0500, you wrote:
> > > > > >FYI, 45 of the 512 rcds are bad with data in ODOBAT
> > > > > >
> > > > > >----- Original Message -----
> > > > > >From: "Vernon Hamberg" <vhamberg@attbi.com>
> > > > > >To: <midrange-l@midrange.com>
> > > > > >Sent: Thursday, March 21, 2002 11:25 AM
> > > > > >Subject: RE: SQL Misbehaving
> > > > > >
> > > > > >
> > > > > > > Just tried all 3 flavors of DSPOBJD to outfile on a v5r1
>system.
> > > >ODOBAT
> > > > > > > field is all blanks.
> > > > > > >
> > > > > > > Is your outfile hand-built, or a dup of the system-provided
>one?
> >Maybe
> > > > > >from
> > > > > > > a previous release?
> > > > > > >
> > > > > > > At 11:12 AM 3/21/02 -0500, you wrote:
> > > > > > > >Dare,
> > > > > > > >
> > > > > > > >I remember the source of the file, my question was more
> >rhetorical
> > > >than
> > > > > > > >anything else.  My recollection is that user profiles (unlike
> >files
> > > >for
> > > > > > > >instance), don't really have attributes which would further
> > > >categorize
> > > > > > > >them.  I don't know what the system will do with that field
>and
> >don't
> > > > > > > >see a clear indication by looking at the data for the four
> >records
> > > >you
> > > > > > > >provided.  I don't have an AS/400 handy to do some testing,
>but
> >it
> > > > > > > >strikes me that your SQL session can't handle character data
> >which
> > > > > > > >doesn't translate into a displayable character.
> > > > > > > >
> > > > > > > >As to how it got there, it would seem to me that you're
>entering
> >PTF
> > > > > > > >territory or there is something weird with the file you
>created.
> >You
> > > > > > > >might try letting the command create it's own outfile and see
>if
> >you
> > > >get
> > > > > > > >the same result.
> > > > > > > >
> > > > > > > >Andy
> > > > > > > >
> > > > > > > > > Subject: Re: SQL Misbehaving
> > > > > > > > >
> > > > > > > > > All I did was DSPOBJD for type *usrprf to an outfile that I
> > > >created
> > > > > > > >prior
> > > > > > > > > to
> > > > > > > > > DSPOBJD.
> > > > > > > >
> > > > > > > >_______________________________________________
> > > > > > > >This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > > >mailing
> > > > > >list
> > > > > > > >To post a message email: MIDRANGE-L@midrange.com
> > > > > > > >To subscribe, unsubscribe, or change list options,
> > > > > > > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > > > >or email: MIDRANGE-L-request@midrange.com
> > > > > > > >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@midrange.com
> > > > > > > To subscribe, unsubscribe, or change list options,
> > > > > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > > > or email: MIDRANGE-L-request@midrange.com
> > > > > > > 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@midrange.com
> > > > > >To subscribe, unsubscribe, or change list options,
> > > > > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > >or email: MIDRANGE-L-request@midrange.com
> > > > > >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@midrange.com
> > > > > To subscribe, unsubscribe, or change list options,
> > > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > or email: MIDRANGE-L-request@midrange.com
> > > > > 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@midrange.com
> > > >To subscribe, unsubscribe, or change list options,
> > > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > >or email: MIDRANGE-L-request@midrange.com
> > > >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@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > 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@midrange.com
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> >or email: MIDRANGE-L-request@midrange.com
> >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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.