Академический Документы
Профессиональный Документы
Культура Документы
*CMD
*CLP (Command Validation program)
*CLP
Start Mqseries Monitor (STRMQQMON)
. . . . . . . . .
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
STRMQQCL
BOHMQQCL
BOHMQADMIN
RTVMQINFO
BOHMQQMON
BOHMQADMIN
RTVMQINFO
##
Character value
F12=Cancel
*CLP
*CBL
*CLP
*CBL
*CBL
*CLP
BOHMQQMON
STRMQBOHCL
BOHMQBOHCL
BOHMQBOH
BOHMQERR
*CLP
*CLP
*CBL
*CBL
The control of run priority and time slice of initiated job is in CL STRMQBOHCL. The
statement is shown in below.
SBMJOB JOB(&JOBNM) JOBD(&LVLEXC/&USER) JOBQ(QSYSNOMAX)
OUTQ(*JOBD) USER(&USER) RTGDTA(QSYSCLS20) RQSDTA(&CMD) +
INLLIBL(*JOBD) LOG(*JOBD *JOBD *MSG) MSGQ(&USER) ALWMLTTHD(*NO)
For parameter RTGDTA (routing data), the CL currently uses system defined
QSYSCLS20 class. For this class, the run priority is 20 and time slice is set to 2000
milliseconds. The above setting is equivalent to online job. However, you can change
it QSYSCLS30 for run priority 30. Please note that the different AS/400 system could
have different system defined class.
Special Notes for MQ Monitor: Add QMQM library into dataarea ELIBL into level xxxEXC. This step is to ensure the user
granted to level will have QMQM library in job description. This is crucial as all MQSeries
MQI is kept in QMQM library.
Use GRTLVLAUT or GRTRELAUT to create the job description for user and virtual
machine security officer. The MQ monitor job is run under VSMO id and requires VSMO
job description in that level.
To promote MQ Monitor Cobol Programs, delete MQSeries copybooks from SCLXPF file
via SQL as these copybooks are not registered in Smart/400 dictionary.
Starts MQ Monitor must be execute in the correct Smart/400 environment.
As MQ Monitor is executed under VMSO id, the user who starts it must have use
authority on VMSO profile. In other words, are able to use PAXSEC command.
The MQ Monitor job is submitted to job queue QSYSNOMAX that serves the subsystem
QSYWRK. The job-naming standard is MQDxxx where xxx is the level name.
The dump of the business object is found in user id from leader header spool file.
If secondary user id is used, the job initiated by multi thread MQ Monitor is executed
under VMSO id. For such situation, the datetime stamp will be under VMSO id.
The MQ monitor will only be down if it MQSeries return code is not OK. The job log will
show the reason code. Use MQSeries Message manual to find out whats wrong.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*INPLIB
*INPMBR
Character
Character
Character
Character
Character
Character
value
value
value
value
value
value
. . . . . . . . . .
Queue Manager
. . . . . . . . .
Bottom
F3=Exit
F4=Prompt
F24=More keys
TSTBOMQCL
TSTMQBOVAL
TSTBOMQ
F5=Refresh
*CLP
*CBL
*CBL
F12=Cancel
(Validation Pgm)
(Main Pgm)
(Assume input file with
1st line Session detail
2nd line Leader Header
3rd line onwards Request Data)