× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'm not sure exactly why its this way either, but it has been that way
since I got here. Its where the Bossman wants it.  

Michael Smith
iSeries.mySeries.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Holden Tommy
Sent: Wednesday, July 12, 2006 10:39 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] OVRDBF problem or maybe it is early Alzheimer's


<rant>
This is one of my pet peeves....IMO QTEMP should ALWAYS reside at the
top of the library list... </rant> 

Why do people do that??? Jeez!!!

Thanks,
Tommy Holden


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Smith, Mike
Sent: Wednesday, July 12, 2006 8:33 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] OVRDBF problem or maybe it is early Alzheimer's

I seem to be having problems with OVRDBF.  
My original problem started with a CL running interactively.  I decided
to get down to the very basics and did the following scenario.  From
command line. 

Lib Qtemp- end of lib list
Lib Prodlib- middle of lib list

CRTDUPOBJ  OBJ(EMPMST) FROMLIB(Prodlib) OBJTYPE(*FILE)
             TOLIB(QTEMP) NEWOBJ(*OBJ)

OVRDBF     FILE(EMPMST) TOFILE(QTEMP/EMPMST)

DBU EMPMST 

File displayed is from Prodlib.   

Shouldn't this display the file in QTEMP?  


Michael Smith
iSeries.mySeries.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.