A bad job dies a thousand deaths; a good job dies but one. Some jobs are difficult to end. Communication jobs that have gone awry are particularly prone to not ending, even when you've executed an End Job (ENDJOB) command with *IMMED specified for the OPTION parameter. The End Job Abnormal (ENDJOBABN) command can help kill those cowardly jobs.
ENDJOBABN is used to end a job that will not end through normal means. The parameters on this command are job name, user, and job number. The ENDJOBABN command requires that an ENDJOB OPTION(*IMMED) has already been run against the job you are trying to end. It also requires a lapse of 10 minutes for the ENDJOB command to have effect. Once those conditions are met, you can then run ENDJOBABN.
The only consideration for the ENDJOBABN command is that it makes your next IPL abnormal. So if you are testing the system value QABNORMSW in your IPL start-up program, it will be set to '1' at the next IPL. That isn't a problem, it just lets you know that clean-up processing was done during the IPL.
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