Apparently the website that I read (wherever it was) was incorrect about the
*secofr.
The piece I forgot about was CHGTCPSVR SVRSPCVAL(*SSHD) AUTOSTART(*YES).
After this, it auto-starts with the IPL.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
Taylor
Sent: Monday, February 4, 2019 9:02 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH
Can't you just autostart *SSHD?
I don't have *SECOFR and I can start *SSHD.
-----Original Message-----
From: smith5646midrange@xxxxxxxxx [mailto:smith5646midrange@xxxxxxxxx]
Sent: Saturday, February 02, 2019 11:24 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Calling a program on the i via OpenSSH
Since STRTCPSVR *SSHD has to be run by a secofr profile (unless I am reading
the internet incorrectly), I am looking for best practice for starting it
when the system IPLs. Is there a reason not to add it to QSTRUP and compile
it with a *secofr profile with adopt *owner auth? Is there some other
option that I am not finding during my research on automating it's startup?
--
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@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
