× 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.



Hmmm...  You may be right.

I'll flag this for follow-up thought...


| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of rob@dekko.com
| Sent: Thursday, December 13, 2001 8:39 AM
| To: midrange-l@midrange.com
| Subject: RE: CPY instead of CRTDUPOBJ ? (was: CD Burning software?)
|
|
|
| You would not have been happy how they would have had to modify WRKOBJ to
| get that flexibility.  Would you like having to key the following into the
| library parameter:  '/qsys.lib/mylib.lib'?  I think not.
| Modifying the object types would have been easier.  I hope you know that
| mylib.lib would have an object type of *LIB.  Then they could have added
| *EXE, *XLS, *DOC, etc.  Of course, for those really long
| extensions I would
| have been satisfied with *all.
| What about all those API's which claim to be just like WRKOBJ?  The field
| sizes would have all changed - probably to varying length.
|
| Nope - I think I prefer the separate commands than mongerfying WRKOBJ.
|
| Rob Berendt
|
| ==================
| "They that can give up essential liberty to obtain a little temporary
| safety deserve neither liberty nor safety."
| Benjamin Franklin
|
|
|
|                     "jt" <jt@ee.net>
|                     Sent by:                  To:
| <midrange-l@midrange.com>
|                     midrange-l-admin@mi       cc:
|                     drange.com                Fax to:
|                                               Subject:     RE:
| CPY instead of CRTDUPOBJ ? (was: CD Burning software?)
|
|                     12/12/2001 03:21 PM
|                     Please respond to
|                     midrange-l
|
|
|
|
|
|
| Rob,
|
| Sorry to have to disagree again.  I see your points and, while I
| don't know
| the IFS commands like I know the others, I have found some have more
| flexibility and/or new capabilities.
|
| However, I draw a different conclusion.  Why did we need a WRKLNK in the
| first place?  We already had WRKOBJ.
|
| I suspect because some wheel needed re-invented, rather than improving the
| original.  I have a serious problem with this viewpoint if it is, indeed,
| the case.
|
| I agree completely that there is no real need or value for having two
| versions of all these commands, however.  But if they wanted to "force" me
| to get exposed to the IFS, an easier way would have been to modify WRKOBJ
| **to include** that functionality, rather than force me to remember subtle
| differences between what are basically duplicate commands.
|
| JMHO.
|
| jt
|
| | -----Original Message-----
| | From: midrange-l-admin@midrange.com
| | [mailto:midrange-l-admin@midrange.com]On Behalf Of rob@dekko.com
| | Sent: Monday, December 10, 2001 4:01 PM
| | To: midrange-l@midrange.com
| | Subject: RE: CPY instead of CRTDUPOBJ ? (was: CD Burning software?)
| | Importance: High
| |
| |
| |
| | Once you get used to the IFS commands why remember ones which
| are so much
| | more restrictive?
| | I use CHGOWN, not CHGOBJOWN; and many other IFS commands.  They're more
| | flexible and once you have to start messing around with some of
| the newer
| | iSeries applications you pretty much have to get exposed to the
| IFS.  Got
| | an application.  To see what version you are running you
| display the text
| | on this one service program.  Command the vendor has you run - an IFS
| | command.  Let's say in the future they base something on the size and
| | change date on a file - why make people learn two ways of
| seeing this:  1
| | way with DSPOBJD, and another way with WRKLNK Option 8 - whatever that
| | command is.
| |
| | Rob Berendt
| |
| | ==================
| | "They that can give up essential liberty to obtain a little temporary
| | safety deserve neither liberty nor safety."
| | Benjamin Franklin
| |
| |
| |
| |                     "jt" <jt@ee.net>
| |                     Sent by:                  To:
| | <midrange-l@midrange.com>
| |                     midrange-l-admin@mi       cc:
| |                     drange.com                Fax to:
| |                                               Subject:     RE:
| | CPY instead of CRTDUPOBJ ? (was: CD Burning software?)
| |
| |                     12/08/2001 01:20 PM
| |                     Please respond to
| |                     midrange-l
| |
| |
| |
| |
| |
| |
| | 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.
| | |
| |
| | _______________________________________________
| | 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.
|
|
|
|
|
| _______________________________________________
| 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 thread ...

Replies:

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.