×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
DSPSYSVAL QCTLSBSD
If QBASE then job queue QBATCH will be part of that subsystem. If QCTL then QBATCH will be it's own subsystem.
DSPS36 (see also CHGS36)
Make sure your libraries are the same.
IBM should give you a sample
// JOBQ #LIBRARY,RBC
DSPJOBLOG
F10
// JOBQ #LIBRARY,RBC
657315/ROB/RBC--this job has been placed on the jobq
DSPJOBLOG 657315/ROB/RBC
Message . . . . : Job 657315/ROB/RBC submitted.
Cause . . . . . : Job 657315/ROB/RBC submitted to job queue QBATCH in QGPL
RBC,#LIBRARY
// MENU RXMENU,RXLIBR
SYS1296 Options ( 3)
MENU statement not allowed from job queue.
I'm taking it that a serious jump in OS happened. Like something prior to V7R1. Either that or the old machine was too old to run an OS compatible with the new system. Thus this resulted in a "challenging" upgrade. You should probably get this cleaned up in a few months. Have fun.
According to:
http://ftpmirror.your.org/pub/misc/ftp.software.ibm.com/systems/power/docs/systemi/v5r4/fi_FI/sc414730.pdf
Job queue jobs
When you specify the Job Queue (JOBQ)
command or the // JOBQ OCL statement, the
system submits jobs to job queue QBATCH in
library QGPL.
Evoke jobs
When you specify the // EVOKE OCL statement, the system submits jobs to job queue
QS36EVOKE in library QGPL.
Note: Procedures placed on the
QS36EVOKE job queue by the // EVOKE OCL
statement will end abnormally if the job is held
on the job queue, an IPL is performed, and
the job is released after the IPL.
Rob Berendt
midrange.com
