There have been numerous requests from programmers who want to access and manipulate with a job's QTEMP library. It is used for debugging and/or recovering from a job that has fallen over with a MSGW status. On occasion, the remedy would involve either investigating the contents in QTEMP or modifying the contents in it. Or the error may be also caused by an incorrect library list. The program may attempt to access objects that do not exist due to a missing library in the library list. Whichever the case, it is especially useful if we could remotely execute commands on a job as if it was the job itself that issued the command. Once the problem has been rectified, such as the missing library list scenario, then instead of answering "c" to cancel the request, you now answer "r" to retry the operation.
There have been earlier approaches to execute commands on another session that uses the message queue concept. It places the workstation message queue into *BREAK delivery mode and uses a break-handling program. When a message is received, the break handling program takes over and executes the command contained in the message. The problem with this approach is that it will not work with batch jobs. You cannot send messages to a batch job from another job. Moreover, the user profile also needs to be setup to run an initial program that will place the workstation message queue into break delivery mode. This approach is cumbersome and of limited use with only interactive jobs.
Finally there is a way to run commands on any job, batch or online and without any cumbersome pre-requisites. It consists of three parts, a command (RUNJOBCMD), a command processing program (SNDCMDCL) and an exit program (RCVCMDCL).
For this to work, you must have the f
To continue reading for free, register below or login
To read more you must become a member of Search400.com
ollowing:
1. *USE authority to the user profile where the command is intended to be executed.
2. *USE authority to STRSRVJOB, ENDSRVJOB and TRCJOB commands. These commands are normally shipped with *EXCLUDE authority.
3. Or have *SERVICE special authority in your user profile.
Code
This is the RUNJOBCMD command. It accepts two main parameters, the iSeries 400 job (where the command will be executed) and a command to be executed. Note: The command will be executed under the job that is being specified. It does not run under your current sign on session.
C This is the SNDCMDCL program which is the CPP for RUNJOBCMD. It will interrupt the iSeries 400 job by starting a service request. Then sends the command to be executed via data queues. When the command finishes executing, the messages (if any) are returned and displayed to the user.
This is the RCVCMDCL program. It is the exit program specified in the TRCJOB command. This program will run under the job being serviced. It accepts the commands to execute via data queues and returns the completion messages also through data queues.
Here I provide a hypothetical example of displaying the contents of QTEMP for a batch job named GLPOST, running under userid DAVIDONG and the job number is 123456.
RUNJOBCMD JOBNAME(GLPOST) JOBUSER(DAVIDONG) JOBNUMBER(123456) COMMAND('DSPOBJD OBJ(QTEMP/*ALL) OBJTYPE(*ALL) OUTPUT(*PRINT)')
Because the command runs under Davidong's user profile, then you will need to work with Davidong's spool files to view the report.
