Q: We're currently running local and remote workstations in the same AS/400 subsystem. We seem to be getting uneven local and remote communications performance with this configuration. Any suggestions?
-Dale Figaro
A: Separate the local and remote devices into different subsystems. Because of the typically slow response times associated with remote devices, the subsystem may be delayed from promptly servicing requests for locally attached devices.
To separate your remote devices from your local ones, create a new subsystem for your remote devices and use your existing subsystem for your local devices. You'll then need to use the Add Work Station Entry (ADDWSE) command to identify the remote devices in the remote subsystem description and the local devices in the local subsystem description. You can use the WRKSTN parameter to identify the workstations by name or the WRKSTNTYPE parameter to identify them by type.
-Kris Neely
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online