|
Try doing the DLTF QTEMP/USR first. If this file already exists in QTEMP the command will add records to the end. Thus you would still have the obscene records. Do not do a CLRPFM. Delete it and start from scratch. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Dare @ Work" <oludare To: <midrange-l@midrange.com> Sent by: cc: midrange-l-admin@mi Fax to: drange.com Subject: Re: SQL Misbehaving 03/21/2002 12:00 PM Please respond to midrange-l Could anyone on V4R5 try this: DSPOBJD OBJ(*ALL) OBJTYPE(*USRPRF) OUTPUT(*OUTFILE) OUTFILE(QTEMP/USR) OUTMBR(*FIRST *ADD) ----- 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.
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.