From: Andrew Dekreon To: All
Does anyone have a suggestion about how to clean up extra device descriptions quickly and easily? Due to moving terminals around, switching to PC Support, and changing from twinax to token ring, we have quite a few obsolete device descriptions created by auto configuration (system value QAUTOCFG set to 1) cluttering up our system. Any shortcuts would be appreciated.
From: David Wallen To: Andrew Dekreon
You can use the Display Object Description (DSPOBJD) command to create an outfile containing all of your device descriptions.
DSPOBJD OBJ(QSYS/*ALL) + OBJTYPE(*DEVD) + OUTPUT(*OUTFILE) + OUTFILE(xxx/DEVDS)
The outfile contains a last used date field called ODUDAT that you can use to determine what devices may be candidates for deletion. You could read through the file and delete all those devices that have not been used in 30 days (or whatever limit you impose). One word of warning-I would avoid deleting any IBM device descriptions (e.g., those that start with Q).
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