|
Let me re-phrase that: written by a reactionary gearhead. (The people that wrote the VB code may not even know *nix...) There is an OVERWHELMING view, in IBM, that turns a blind eye to the 400. They just DON'T WANT TO SEE that the 400 has a BETTER way, has had it for 20 YEARS, and that they actually having SOME CATCHING UP TO DO.. rather than the other way around. (Or rather that it works both ways.) That's my explanation for why some people prefer to do things the hard way: keeping coding practices using the *nix style, or the VB style... Long past where it makes sense, in some cases. (We all do that, of course, but some examples are pretty extreme, and I think this is one of 'em.) Again, JMNSHO... jt | -----Original Message----- | From: midrange-l-admin@midrange.com | [mailto:midrange-l-admin@midrange.com]On Behalf Of jt | Sent: Saturday, December 08, 2001 1:00 PM | To: midrange-l@midrange.com | Subject: RE: CPY instead of CRTDUPOBJ ? (was: CD Burning software?) | | | david, | | MNSHO: written by *nix gearhead... | | I've seen similar examples in CA OLE/DB sample code. I think they prefer | the generic commands and specifying objects in IFS notation. | Can't see the | sense of it myself, although I didn't look at this specific example code. | | jt | | | -----Original Message----- | | From: midrange-l-admin@midrange.com | | [mailto:midrange-l-admin@midrange.com]On Behalf Of David Gibbs | | Sent: Saturday, December 08, 2001 12:45 PM | | To: midrange-l@midrange.com | | Subject: CPY instead of CRTDUPOBJ ? (was: CD Burning software?) | | | | | | At 11:41 AM 12/8/2001, I wrote: | | >Found this | | >http://www-1.ibm.com/servers/eserver/iseries/optical/cdrom/lodrunlp.htm | | | | Ok, bit of confusion here ... on the above web page they | reference copying | | a program ... but they use IFS CPYcommand to do the copy instead | | of regular | | CRTDUPOBJ. | | | | Any ideas why? | | | | david | | | | -- | | | Internet: david@midrange.com | | | WWW: http://david.fallingrock.net | | | | | | Justice ... not vengeance | | | | _______________________________________________ | | 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.