From: Ken Rokos
To: All
Under PC Support for DOS, our router uses a default user profile to sign on. We redirect a file containing the password for the user profile (startrtr < password.txt) to avoid manually entering the password. When we start the new Client Access for Windows, however, a window pops up that asks for the password. We haven't been able to figure out how to get around this, and IBM says there's no (official) way to do it. Have any of you figured a way around this?maybe with the Windows Macro Recorder, a Visual Basic program, or a .PIF or .INI file?
From: Lance Gillespie
To: Ken Rokos
If you're using the V3R1 native Windows router, you'll find a file in the c:windows directory called NSD.INI. This file can be changed with any ASCII editor. In this file, the section called [SIDEINFO] has an entry for every system you have configured the router to connect to (see 1).
If you're using the V3R1 native Windows router, you'll find a file in the c:windows directory called NSD.INI. This file can be changed with any ASCII editor. In this file, the section called [SIDEINFO] has an entry for every system you have configured the router to connect to (see Figure 1).
Just add the user profile and the password parameters to the appropriate entry, and the next time you start Client Access, the router will automatically sign on. The user still sees the dialog box, but does not have to do anything.
TechTalk: Password to Client Access for Windows
Figure 1: NSD.INI Client Access Router Entry
Format system = network-id.alias, mode, *, same, user-id, password, system, connection-order Example [SIDEINFO] MYSYS = APPN.MYSYS, QPCSUPP, *, SAME, GILLESPIE, ABC123, MYSYS, 1
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