Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Automatically start STRHOSTSVR

47 views
Skip to first unread message

Paul Nicolay

unread,
Sep 23, 1997, 3:00:00 AM9/23/97
to

Hi Xavi,

Just give *USE authority for QPGMR to the command STRHOSTSVR.

In addition, make sure QSERVER is fully started before starting the host
servers. This is easily done by adding a DLYJOB of about 5-10 minutes
after STRSBS QSERVER.

Regards,
Paul
_________________
Xavier Caballé <xa...@caballe.com> wrote in article
<3427C602...@caballe.com>...
> I'm trying to add STRHOSTSVR command to my startup program, in order to
> execute it each time I start my system, but it fails because there's a
> rights problem.
>
> Specifically, I've get a CPD0032 message (You are not authorized to run
> STRHOSTSVR in the library *LIBL)
>
> So, to activate this command I must do it manually with a security user
> profile and with *IOSYSCFG rights.
>
> Can somebody help me?
>
>
> Xavi
>
>


The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, Merck & Co., Inc. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.

Xavier Caballé

unread,
Sep 23, 1997, 3:00:00 AM9/23/97
to

Jim Willsher

unread,
Sep 23, 1997, 3:00:00 AM9/23/97
to

The startup program (usually QSTRUP) should be compiled with authority
*OWNER, and should be owned by user QSYS.

We have STRHOSTSVR and STRTCP in our statup program with no problems.


Jim

Troy Napier

unread,
Sep 25, 1997, 3:00:00 AM9/25/97
to
Jim, the easiest way would be to compile the program while being signed
on as security officer. Prompt the submit and at the bottom, change the
default authority from user to owner. This will allow the program to use
the qsecofr authority.

David Pugh

unread,
Sep 29, 1997, 3:00:00 AM9/29/97
to

You need to grant QPGMR authority to run the STRHOSTSVR object.

Troy Napier <tna...@bellsouth.net> wrote in article
<342B17...@bellsouth.net>...

0 new messages