When you compare the System/36 JOBQ command with the AS/400 Submit Job (SBMJOB) command, you may be tempted to conclude that the AS/400 is a terribly complicated machine, and may even convince yourself that you will never master it. After all, the JOBQ command had only a few parameters (priority, library, procedure, and procedure parameters), whereas the SBMJOB has a couple dozen, all of which have weird names that do not mean much to you.
Fortunately, however, most parameters in the SBMJOB command have useful defaults that will make it work almost like the JOBQ command did on the S/36. If you still shy away from the SBMJOB command, perhaps you could use our Submit Command (SBMCMD) command, a simplified version of SBMJOB. Like all commands, SBMCMD has an associated processing program (CPP), which is named CMD002CL in this case. The command definition and the CPP are shown in Figures 1 and 2, respectively.
The SBMCMD command has three parameters only. Let's see what they are.
CMD: The command string you are submitting to batch processing. Notice that it has been specified with TYPE(*CMDSTR) command string with a maximum length of 3000 characters. Having MIN(1), the parameter is required.
JOBQ: The name of the job queue where the command will be placed. The default value is QBATCH, which is probably correct in most cases.
JOB: The name of the job you are submitting. It defaults to *CMD, which is interpreted as "give the job the same name as the command being submitted."
One feature worth mentioning is that when you prompt the SBMCMD command with the F4 key, you will get the CMD parameter as the first input field. Placing a command name in this field and pressing F4 again will display the prompt panel for the command you typed in. In other words, it is a prompt within a prompt. We really urge you to try it, as follows.
Type SBMCMD at the command line and press F4. Now type CRTLIB and press F4 a second time. The command prompter will show the CRTLIB prompt panel. Type TESTLIB, then press Enter. The command prompter will return to the SBMCMD prompt panel, showing the complete command string for the CRTLIB command: CRTLIB LIB(TESTLIB).
Now let's look at the command processing program, CMD002CL. First, it validates your input, making sure that the job queue you specified exists and that you are authorized to use it. Then it extracts from the &CMD (command line) variable the ten-character name of the command being submitted. Finally, it submits the job by calling QCMDEXC.
In case you are wondering why the SBMJOB command is not used, it is because SBMJOB does not accept input coming from a variable (such as &CMD) in its CMD parameter. The work-around solution presented here is to build a character string (&SBMJOB) having the entire SBMJOB command line. This character string is built by the previous CHGVAR command using several concatenation operations.
Midrange Computing
TechTalk: An Alternative to SBMJOB
Figure 1 Command SBMCMD
SBMCMD: CMD PROMPT('Submit Command to Batch') PARM KWD(CMD) TYPE(*CMDSTR) LEN(3000) MIN(1) + PROMPT('Command') PARM KWD(JOBQ) TYPE(*SNAME) LEN(10) DFT(QBATCH) + PROMPT('Job queue') PARM KWD(JOB) TYPE(*SNAME) LEN(10) DFT(*CMD) + SPCVAL((*CMD)) PROMPT('Job name')
TechTalk: An Alternative to SBMJOB
Figure 2 CL program CMD002CL
CMD002CL: + PGM PARM(&CMD &JOBQ &JOB) DCL VAR(&CMD) TYPE(*CHAR) LEN(3000) DCL VAR(&JOBQ) TYPE(*CHAR) LEN(10) DCL VAR(&JOB) TYPE(*CHAR) LEN(10) DCL VAR(&CMD_NAME) TYPE(*CHAR) LEN(10) DCL VAR(&VAR_POS) TYPE(*DEC) LEN(4 0) DCL VAR(&STR_POS) TYPE(*DEC) LEN(4 0) DCL VAR(&LENGTH) TYPE(*DEC) LEN(4 0) DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(80) DCL VAR(&SBMJOB) TYPE(*CHAR) LEN(3060) /* Validate input */ CHKOBJ OBJ(&JOBQ) OBJTYPE(*JOBQ) MONMSG MSGID(CPF9801) EXEC(DO) CHGVAR VAR(&MSGDTA) VALUE('Job queue' *BCAT &JOBQ *TCAT ' not + found') GOTO CMDLBL(ERROR) ENDDO CHKOBJ OBJ(&JOBQ) OBJTYPE(*JOBQ) AUT(*USE) MONMSG MSGID(CPF9802) EXEC(DO) CHGVAR VAR(&MSGDTA) VALUE('You are not authorized to use job + queue' *BCAT &JOBQ) GOTO CMDLBL(ERROR) ENDDO /* Extract from &CMD the name of the command being submitted */ CHGVAR VAR(&STR_POS) VALUE(1) CHGVAR VAR(&VAR_POS) VALUE(2) LOOP: + IF COND(%SST(&CMD &VAR_POS 1) *EQ '/') THEN(DO) CHGVAR VAR(&STR_POS) VALUE(&VAR_POS + 1) ENDDO IF COND(%SST(&CMD &VAR_POS 1) *EQ ' ') THEN(DO) CHGVAR VAR(&LENGTH) VALUE(&VAR_POS - &STR_POS) CHGVAR VAR(&CMD_NAME) VALUE(%SST(&CMD &STR_POS &LENGTH)) GOTO CMDLBL(LEAVE) ENDDO CHGVAR VAR(&VAR_POS) VALUE(&VAR_POS + 1) GOTO CMDLBL(LOOP) /* Reject attempts to submit either SBMCMD or SBMJOB to batch */ LEAVE: + IF COND(&CMD_NAME *EQ 'SBMCMD' *OR &CMD_NAME *EQ 'SBMJOB') THEN(DO) CHGVAR VAR(&MSGDTA) VALUE('Command' *BCAT &CMD_NAME *TCAT ' + cannot be submitted to batch.') GOTO CMDLBL(ERROR) ENDDO IF COND(&JOB *EQ '*CMD') THEN(DO) CHGVAR VAR(&JOB) VALUE(&CMD_NAME) ENDDO /* Submit command to batch */ CHGVAR VAR(&SBMJOB) VALUE('SBMJOB CMD(' *CAT &CMD *TCAT ') JOB(' + *CAT &JOB *TCAT ') JOBQ(' *CAT &JOBQ *TCAT ')') CALL PGM(QCMDEXC) PARM(&SBMJOB 3060) SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA('Command' *BCAT + &CMD_NAME *TCAT ' submitted to batch') MSGTYPE(*COMP) GOTO CMDLBL(ENDPGM) /* Send error messages */ ERROR: + SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA(&MSGDTA) + MSGTYPE(*DIAG) SNDPGMMSG MSGID(CPF0002) MSGF(QCPFMSG) MSGTYPE(*ESCAPE) /* End program */ ENDPGM: + ENDPGM
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
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