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



Hi Paul

I may have said it already - but just because the command names are similar, it does not mean they should behave the same way - one is part of a large tool set (PDM) for programmers to use, the other is a more general-purpose command. Even the options in each are different - there are no authorization-related commands in PDM, but if you think the 2 are related as you seem to do, why doesn't PDM have the object authority options? I'd say, because it is not intended for general object maintenance, while WRKOBJ is.

2 different tools with different intended usage - hence, not too surprising that some options are different. I suggest that WRKOBJ is a system tool and that WRKOBJPDM is not. Should defaults be the same? Maybe, maybe not.

I did go looking for the documentations for PDM - I think the last manual came from 2000 - the link is http://publibfp.dhe.ibm.com/epubs/pdf/c0917710.pdf - and you can see if that works for you - I had to go through the Publications site and do a search and click on an "I agree..." window to get to it.

I think IBM have sunseted PDM and the other tools in ADTS - Application Development Toolset - we are supposed to use RDi.

There is another tool that allows editing CL, I think - it is meant for system administrators, IIRC.

I also just discovered that there is an exit that lets us restrict editing using the ADTS utilites - QIBM_QSU_ALW_EDIT. The page about it says 7.1 of the OS, don't know if it is still around.

Cheers
Vern

On 5/25/2020 3:12 PM, Paul Therrien wrote:
Understood.

It's just that option 3 on WRKOBJ gives a CRTDUPOBJ DATA(*NO)
While WRKOBJPDM gives a CRTDUPOBJ with a DATA(*YES).
If my default for the CRTDUPOBJ command is DATA(*NO), why would the CRTDUPOBJ from WRKOBJPDM default to DATA(*YES)?

We are on 7.3 - do others see this on their system?


Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Peter Dow
Sent: Monday, May 25, 2020 4:06 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: CRTDUPOBJ - WRKOBJPDM vs WRKOBJ

Hi Paul,

You may not be able to override it, but PDM gives us the ability to create our own options. Just create an option with F16, e.g. CO, and put in your own defaults for CRTDUPOBJ.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx> pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 5/25/2020 7:59 AM, Paul Therrien wrote:
Yeah, I've looked all over.

There doesn't appear to be a way to override the prepackaged PDM
options (like option 3 CRTDUPOBJ).


Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Tim Bronski
Sent: Monday, May 25, 2020 10:47 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CRTDUPOBJ - WRKOBJPDM vs WRKOBJ

Sorry, that's just the user defaults...

On 5/25/2020 4:06 PM, Paul Therrien wrote:
Vern,

Certainly I can override the DATA() parm in WRKOBJ or WRKOBJPDM -
what I am not understanding is where the DATA(*YES) in WRKOBJPDM gets
defined - how is the WRKOBJPDM CRTDUPOBJ DATA(*YES) override
specified? Is that something we would have done? Or does PDM
override that somehow? I don't see a place to configure this.



Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Vernon Hamberg
Sent: Monday, May 25, 2020 10:16 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CRTDUPOBJ - WRKOBJPDM vs WRKOBJ

Hi Paul

First, the 4 version of CRTDUPOBJ are there for compiling CL to
previous releases. The normal daily usage is the one in QSYS.

Second, WRKOBJ is a basic system command, while WRKOBJPDM is a
developer (and maybe system administrator) tool with some assumptions.
Perhaps the designers of PDM decided that normal use of CRTDUPOBJ
would be to include the data. It appears that WRKOBJ makes no choices
for values, instead, it simply uses the defaults. Note that WRKOBJPDM
doesn't give you a choice about replacing an object that already
exists,
while PDM typically does.
I am not on a system so I don't know - can you press F4 in WRKOBJ
when you take the 3 option? Or can you put the DATA(*YES) parameter
on the command line? The latter is a way to override default
parameters, as I
recall.
Regards
Vern

On 5/25/2020 8:42 AM, Paul Therrien wrote:
We are on IBM I V7R3.
I am confused about the following:
I run command WRKOBJPDM LIB(library) Obj(name*) to get a list of
name* objects. I execute option 3 with prompt to run CRTDUPOBJ
command on a physical file. The command pops up with parm
DATA(*YES). So when I copy the file, the data comes with it.
I run command WRKOBJ lib/name* to get the same list of files. I
execute an option 3 with prompt to run CRTDUPOBJ command. The
command pops up with parm DATA(*NO). So when I copy the file, the
data DOES NOT
come with it.
The default on the CRTDUPOBJ command is DATA(*NO).
I cannot figure out where the CRTDUPOBJ from the WRKOBJPDM display
is getting the DATA(*YES).
Can some one point me to where this would override behavior would be
defined?
There are 4 versions of CRTDUPOBJ on the system - but the only one I
would be accessing is in QSYS.
Object Type Library
CRTDUPOBJ *CMD QSYS
CRTDUPOBJ *CMD QSYSV6R1M0
CRTDUPOBJ *CMD QSYSV7R1M0
CRTDUPOBJ *CMD QSYS38
Incidentally, this discrepancy led me to make an EMPTY backup file
when I thought I was making a complete data backup.
Mea culpa for not being diligent.
Paul
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link:
https://amazon.midrange.com

--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com

--
This email has been checked for viruses by AVG.
https://www.avg.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.