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.