Re: CRTDUPOBJ - WRKOBJPDM vs WRKOBJ -- MIDRANGE-L

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.

That's exactly what I did many, many years ago.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, May 25, 2020 at 4:06 PM Peter Dow <petercdow@xxxxxxxxx> wrote:

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