Q: We have begun work on automated operations and need a way to bring down QINTER in preparation for running a nightly batch job stream. How can I determine from a CL program when an ENDSBS *IMMED has completed and the subsystem is ended?
A: 10 illustrates a simple technique to determine if the subsystem has ended.
A: Figure 10 illustrates a simple technique to determine if the subsystem has ended.
Determining If a Subsystem Has Ended
Figure 10 Determining a Subsystem's Status
TEST: WRKSBSJOB SBS(QINTER) OUTPUT(*PRINT) MONMSG MSGID(CPF1003) EXEC(GOTO INACTIVE) /* qinter is still active -- wait & test again */ DLYJOB DLY(60) /* WAIT 1 MINUTE */ GOTO TEST INACTIVE: /* qinter is not active -- continue with batch processing */
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