I looked at it, but I'm not sure if it'll help. In our case, it was the ADMIN4 job that caused the problem, but I would assume that any of them could do it. I'd need a way to force the port for all of them, and I don't see that wiki page going into that much detail.
-----Original Message-----
From: via MIDRANGE-L [mailto:midrange-l@xxxxxxxxxxxx]
Sent: Friday, May 16, 2014 1:21 PM
To: Midrange Systems Technical Discussion
Subject: RE: Navigator for i vrs. System i Navigator
Did you also see my post about "Listen" to bind specific? Not only did it have an IP address but it also had a port. Granted, it didn't cover all ports used by it...
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: Justin Taylor via MIDRANGE-L <midrange-l@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/16/2014 02:12 PM
Subject: RE: Navigator for i vrs. System i Navigator
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
IBM's work-around wasn't to not use Nav for I, just not to have it
auto-start with TCP. Once TCP is up we can start it manually since
(presumably) all the services running on dedicated ports are already
running.
midrange.com
