|
Really? In v4r4, this from the help text for DSPOBJD: >OUTFILE >Specifies the qualified name of the database file to >which the output of the display is directed. If the >OUTFILE does not exist, this command creates a data-base >file in the specified library. If the file is created, the >text is "output file for DSPOBJD". The public authority is >the same as the create authority specified for the library >in which the file is created. The database format >(QLIDOBJD) of the output file is the same as that used >in the IBM-supplied file database QADSPOBJ. If not, there's something clearly wrong, IMO. PTF time. At 11:40 AM 3/21/02 -0500, you wrote: >At V4R5M0, DSPOBJD does not have the ability to create the *OUTFILE. > > >----- 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.