Re: IFS authority problem when creating a PDF through a Infoprint printer.

oops, sorry...
Object . . . . . . . . . . . . : /testgem/
Type . . . . . . . . . . . . . : DIR
Owner . . . . . . . . . . . . : GMAGNUSON
Primary group . . . . . . . . : *NONE
Authorization list . . . . . . : *NONE

Type options, press Enter.
1=Add user 2=Change user authority 4=Remove user

Data --Object Authorities--
Opt User Authority Exist Mgt Alter Ref

*PUBLIC *RWX X X X X
GMAGNUSON *RWX X X X X

On Mon, Aug 22, 2016 at 5:25 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

What about *PUBLIC? Here's an example of what would help.. it's using
option 9 next to a directory:

Data --Object Authorities--
Opt User Authority Exist Mgt Alter Ref

*PUBLIC *RWX X X X X
QSYS *RWX X X X X
QDIRSRV *RWX X X X X
QTMHHTTP *RWX X X X X

On Mon, Aug 22, 2016 at 3:06 PM, Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx

wrote:

DATA *RWX object *ALL



On Mon, Aug 22, 2016 at 2:40 PM, Bradley Stone <bvstone@xxxxxxxxx>

wrote:

What's the authority for the directory the file is being stored in?


Brad
www.bvstools.com

On Mon, Aug 22, 2016 at 1:44 PM, Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx

wrote:

years ago I had created a printer and psfcfg object per this process:

https://www.youtube.com/watch?v=AGnQ0MnRtm0

well, I wanted to rename change where the output was stored, so I

removed

and
recreated the objects...

now, the resulting stream files are showing up as PUBLIC *EXCLUDE...
being owned by the spool file owner.

I have performed may different scenarios of CHGAUT, but that hasn't
helped...

this happens rarely, when a PDF file gets created in this process,

but

doesn't wind up where it needs to be, either attached to an email, or
placed in a different directory. the file used to be PUBLIC *ALL,

and

so

others could place it where it needed to go.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

list

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

list

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.