Re: CRTCSVF command and alternatives -- MIDRANGE-L

Martin

Perfect resolved my problem

Thanks again

John

message: 2
date: Wed, 30 May 2018 10:30:58 +0100
from: Martin Rowe <dbg400.net@xxxxxxxxx>
subject: Re: CRTCSVF command and alternatives

John

If you don't mind compiling from code there's my CRTCSVDTA routines -
http://www.dbg400.net/foswiki/bin/view/DBG400/CrtCsvDta There are
dependencies on the main DBG/400 package, but you can get to all the source
members from http://www.dbg400.net/foswiki/bin/view/DBG400/SourceCodeList

Regards, Martin

On 30 May 2018 at 10:12, Henrick, John <john.henrick@xxxxxxxxxxxxxxxx>
wrote:

Thanks All
The CPYTOIMPF still leaves a space with remove blank options *both as
stated anyone have access to crfcsvf or have another suggestion?. I need
the blanks fields to be NULL for import to another application.
Thanks

JH

martin@xxxxxxxxxx<mailto:martin@xxxxxxxxxx> http://www.dbg400.net
AS/400 | iSeries | System i Open Source/Free Software
Debian GNU/Linux - http://www.debian.org
Foswiki - The Free Open Source Wiki, http://foswiki.org/

------------------------------

message: 3
date: Wed, 30 May 2018 07:04:14 -0400
from: Rob Berendt <rob@xxxxxxxxx>
subject: Re: Issues with Adopted Authority

And that's the beauty of useadpaut (which I feel is properly named). It
uses the adopted authority of the chain. And our ERP is set up great as
it allows us to control the authority to run under.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 05/30/2018 04:45 AM
Subject: Re: Issues with Adopted Authority
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

??
USEADPAUT is poorly named...

In order for an application to "adopt authority", USRPRF must be *OWNER.

Your ERP system doesn't adopt authority, it uses whatever might alright
have been adopted by something outside the ERP.

USEADPAUT should have been named "Allow adopted authority (to propagate)"

With USRPRF(*OWNER), you can give JSMITH *USE to PGMXYZ and PGMXYZ adopts
the authority needed to change it's files. It doesn't matter how JSMITH
calls the program, rather than saying JSMITH must use this menu to call
PGMXYZ.

Carol's books get more into it, but here's an short article...
https://www.mcpressonline.com/security/ibm-i-os400-i5os/adopted-authority-friend-or-foe

"The default value for the User profile parameter is *USER, which means
that the program will not adopt authority. Changing it to *OWNER sets the
attribute so the program will adopt authority."
" I configure the application programs to adopt?typically all of them,
with
the exceptions such as ones previously described. "

Charles

On Tue, May 29, 2018 at 6:12 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Our ERP system comes shipped from the vendor with USEADPAUT(*YES) on all
programs so that you can set up an initial program and use "application
only access", if you want to.
And since IBM ships QCMDEXC and other programs this way I think this is
the way to go.

If you're going to use CHGPGM on all programs for *owner then why not do
it for useadpaut?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"

<midrange-l@xxxxxxxxxxxx>

Date: 05/29/2018 03:45 PM
Subject: Re: Issues with Adopted Authority
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

My personal preference is to compile (change) every program to
USRPRF(*OWNER) and have them all owned by the APPOWN user profile.

APPOWN

would have *CHG authority to the files/tables.

This way every program adopts the authority needed, rather than

depending

on some previously adopted authority from earlier in the call stack.

Charles

On Tue, May 29, 2018 at 1:24 PM, DrFranken <midrange@xxxxxxxxxxxx>

wrote:

If you are going down this path the routing program I think is the

right

direction.

- Larry "DrFranken" Bolhuis

www.Frankeni.com<http://www.Frankeni.com>
www.iDevCloud.com<http://www.iDevCloud.com> - Personal Development IBM i timeshare service.
www.iInTheCloud.com<http://www.iInTheCloud.com> - Commercial IBM i Cloud Hosting.

On 5/29/2018 3:03 PM, Marc Rauzier wrote:

Le 29/05/2018 ? 16:52, Joe Hatchell a ?crit :

The call stack is
lost and therefore they have no authority to the objects needed to

run

the
program.

I solved a similar issue by writing a program which is invoked in the
routing entry of the batch subsystem in place of QSYS/QCMD program.
The program I wrote does adopt owner authority. In fact, it is a bit

more

complex but this is the principle.

Marc

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

------------------------------

message: 4
date: Wed, 30 May 2018 07:07:40 -0400
from: Rob Berendt <rob@xxxxxxxxx>
subject: Re: Issues with Adopted Authority

I used to replace subsystem descriptions with my own. Then I realized
what a mess I made. I was always afraid that an upgrade might lose job
queues etc. We have a bazillion job queues. Then I discovered that it
would not. However I discovered it so late that it could no longer
migrate my subsystem descriptions because they were originally created
under some ancient release (perhaps even V2R1). I had to recreate them
from scratch and then all was right with the world.
Sometimes IBM adds some things to the subsystem descriptions it may need,
like some job queue for TCP for example.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 05/29/2018 10:13 PM
Subject: Re: Issues with Adopted Authority
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Joe,

The trick to avoiding issues with upgrades/PTFs is to copy the subsystem
descriptions to a user library (I use a combination of libraries at the
top of the system library list called PARTITION and SYSTEM) so during
those processes IBM will not touch them.

The basic partitions from IBM have not changed in many upgrades so they
are safe.

Jim Oberholtzer
Agile Technology Architects

On May 29, 2018, at 4:27 PM, Joe Hatchell <jhatchell@xxxxxxxxxxxxx>

wrote:

Thanks to all who responded to this. Rob Berendt is correct, the issue

not from QCMDEXC stopping the adoption string, it is from another issue.

That issue is the user doesn't have authority to the libraries in the
library list. SBMJOB defaults to INLLIBL(*CURRENT). When the sbmjob
runs, adoption is initially lost so the user reverts back to no

authority.

This causes issues with the SBMJOB because the user is not authorized to

those libraries.

The routing entry idea is very cool, I wish I had thought of that. I

may

choose to do this. I typically lean to solutions that can be embodied

code, as opposed to work management tweaks that are not obvious to less
experienced administrators and may be lost when an o/s upgrade replaces

subsystem description (QBATCH). I will weight the pros and cons.

I have figured out a way to solve the library list authority issue in my

approach, I pass the library list as a parameter in my command and set

the

library list when my program starts up in batch. It works.

Thank you all for your input.

Joe

From: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/29/2018 14:25
Subject: Re: Issues with Adopted Authority
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

If you are going down this path the routing program I think is the right

direction.

- Larry "DrFranken" Bolhuis

www.Frankeni.com<http://www.Frankeni.com>
www.iDevCloud.com<http://www.iDevCloud.com> - Personal Development IBM i timeshare service.
www.iInTheCloud.com<http://www.iInTheCloud.com> - Commercial IBM i Cloud Hosting.

On 5/29/2018 3:03 PM, Marc Rauzier wrote:

Le 29/05/2018 ? 16:52, Joe Hatchell a ?crit :
The call stack is
lost and therefore they have no authority to the objects needed to run

the
program.

I solved a similar issue by writing a program which is invoked in the
routing entry of the batch subsystem in place of QSYS/QCMD program.
The program I wrote does adopt owner authority. In fact, it is a bit
more complex but this is the principle.

Marc

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

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

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

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

------------------------------

Subject: Digest Footer

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

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

------------------------------

End of MIDRANGE-L Digest, Vol 17, Issue 1128
********************************************

This email was sent from outside the GKN Aerospace network.
Please ensure that you verify the source of the message is legitimate before taking action on it.
Suspicious emails can be sent to:report.phishing@xxxxxxx<mailto:report.phishing@xxxxxxx> or your IT Service Desk can provide further guidance.

GKN Aerospace Services
This e-mail and any attachments transmitted with it contain information which is confidential, intended solely for the addressee(s)
and which may also be privileged or exempt from disclosure under applicable law. If you are not the addressee(s), or have received
this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, print, disclose or use any
part of it or its attachments. Internet communications are not guaranteed to be secure or free of any virus. The GKN Group does not accept
liability for any loss or damage arising in any way from changes to this e-mail or its attachments which may occur in transmission
due to network, machine or software failure or manufacturer or operator error, or from unauthorised access or interference with internet
communications by any third party or from the transmission of any viruses. Any opinion or other information in this e-mail or its attachments
that does not relate to the business of the GKN Group or any part of it is personal to the sender and is not given or in any way endorsed by the
GKN Group or any part of it.

GKN Aerospace Services Limited is registered in England No. 355922
Registered office: Ipsley House, Ipsley Church Lane, Redditch, Worcestershire, B98 0TL

Reviewed 24th May 2018

-----------------------------------------------------------------------------------------------------------------------------------------
We are committed to using and managing personal information responsibly and ethically. Please see our privacy policy to find out more about how we will use your personal data. https://www.gkn.com/en/Utilities/privacy-policy/
This email message has been scanned & delivered safely by Mimecast, for more information please visit http://www.mimecast.co.uk
-----------------------------------------------------------------------------------------------------------------------------------------