Q. I was very interested in Ernie Malaga's article, "Easy Software Distribution," which was printed in the February issue. When I tried to take advantage of the Load Run (LODRUN) command, however, I realized that I needed to let my QINST-
APP program know the name of the tape or diskette device specified in the LODRUN command. How is this done?
A. Your QINSTAPP program receives the device name in a 10-byte character parameter, which is the only parameter received by QINSTAPP. The program can then use this device name to perform restore operations from the tape or diskette supplied. For example, the QINSTAPP program listed in 7 restores a library called SOFTWARE.
A. Your QINSTAPP program receives the device name in a 10-byte character parameter, which is the only parameter received by QINSTAPP. The program can then use this device name to perform restore operations from the tape or diskette supplied. For example, the QINSTAPP program listed in Figure 7 restores a library called SOFTWARE.
When you mail a diskette with library SOFTWARE (and the QINST-APP program), the recipient runs the LODRUN command specifying the correct diskette device name for that system, and QINSTAPP will then be able to restore SOFTWARE.
TechTalk: The New LODRUN Command
Figure 7 Sample QINSTAPP program
Figure 7: Sample QINSTAPP Program QINSTAPP: PGM PARM(&DEV) DCL VAR(&DEV) TYPE(*CHAR) LEN(10) DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(80) DCL VAR(&MSGF) TYPE(*CHAR) LEN(10) DCL VAR(&MSGFLIB) TYPE(*CHAR) LEN(10) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ERROR)) RSTLIB LIB(SOFTWARE) DEV(&DEV) VOL(*MOUNTED) + ENDOPT(*UNLOAD) SNDPGMMSG MSGF('Library SOFTWARE restored + successfully.') MSGTYPE(*COMP) RETURN ERROR: RCVMSG MSGTYPE(*EXCP) MSGDTA(&MSGDTA) MSGID(&MSGID) + MSGF(&MSGF) MSGFLIB(&MSGFLIB) SNDPGMMSG MSGID(&MSGID) MSGF(&MSGFLIB/&MSGF) + MSGDTA(&MSGDTA) MSGTYPE(*ESCAPE) ENDPGM
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