Our apps are supposed to handle the loss of any remote server. I'll check all dependent services before processing a request. If any service is unavailable, it delays and retries. If a service drops mid-request, an error is generated and the local service continues normal operation.
-----Original Message-----
From: Steinmetz, Paul [mailto:PSteinmetz@xxxxxxxxxx]
Sent: Thursday, October 19, 2017 12:41 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: Options for managing Windows and Linux updates on servers connecting to the i
Because of the Equifax security breach and other security issues, our remote server update policy has been changed from once a month to every 48 hours, automatic updates enabled.
This is causing some issues with those servers connecting to the i.
Most, not all, require a managed, controlled recycle process.
1) Stop service on the I
2) Stop service on remote server.
3) Apply updates/reboot remote server.
4) Start the service on the remote server.
5)Start the service on the i.
If the remote server is a Linux box, we have tools for steps 2,3,4 from the i.
For Windows servers, not as easily done.
Any thoughts from the group for various options on how to manage these processes?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
