Signing on and off is resource intensive on the AS/400. Consider what happens when you sign on.
o The subsystem monitor processes the signon request
o Job priority, timeslice, purge attribute and wait values are set
o The job is "hooked" to the user profile
o The PAG (Process Access Group) is created (contains working storage, file buffers, overrides and internal message queues)
o Initial library list is set up
o QTEMP library is created
o Initial program is called (as specified in user profile) or initial menu is displayed
When you sign off the system does the following for each invocation level:
o Close down files (data base, display, print, etc.)
o Collapse the PAG
Finally...
o Qtemp library is deleted
o Job log is processed and written
If you are nested deeply in many program invocations, SIGNOFF can take a very long time. If you are new to the AS/400, this probably seemed very unusual the first time you experienced it.
So signon and signoff activity "hurt" the system. What do you do about it?
1) Reduce the number of program invocations
2) Try and keep files open, e.g. OPNDBF TYPE(*PERM)
3) Have your users sign on and stay on until they leave for lunch or home
4) Have your users use the DSCJOB (Disconnect Job) command
DSCJOB is available on release 2.0 of OS/400. Entering DSCJOB immediately returns the user to a signon screen. When the user signs back on, they return to where they left, as if they never signed off.
DSCJOB works by workstation and user. For example, if I am at the WRKACTJOB display and enter DSCJOB, a signon screen is displayed.
o If I sign back on, I return to the WRKACTJOB display
o If I sign on another workstation, a new job is created and my initial menu is displayed
o If another user signs on the workstation where I entered DSCJOB, a new job is created for them and they see their initial menu
My job remains disconnected until I sign back on the workstation where DSCJOB was entered.
WRKUSRJOB *ALL *ACTIVE displays all active jobs including disconnected jobs.
WRKSBSJOB QINTER will display disconnected jobs too.
WRKACTJOB does not display disconnected jobs until you press F14 (Include).
Steven Kontos Patchogue, New York
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