Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OLQ BATCH from OLQ MENU

66 views
Skip to first unread message

Lancelot, Jim

unread,
May 30, 2000, 3:00:00 AM5/30/00
to
We're running 12.01 9607 in MVS. I've got one CV where the OLQ Batch option
from OLQ MENU mode works fine. In the other CV, it doesn't. I've compared
the OLQ entries in the SYSGENS, User definitions and Job Control Modules
(JCL) in the two IDD's, and don't see any differences. When entering BATch
from OLQ MENU the CV that doesn't work gives the following:

109008 Specified user not found.
132006 Default job control language module could not be found.

The user has no problem running OLQ MENU online, but when the Batch option
is selected it gives the errors and the Job Control Module field is blank.
Typing in the name of the Job Control Module eliminates the 132006 but
leaves the user not found message. Does someone know what needs to be done
beyond adding the Job Control Module and user to the dictionary for OLQ
Batch to be enabled from OLQ MENU? Our work around is to create a QFILE and
submit it from outside the CV in batch, but I would like to get it working
from OLQ MENU. I appreciate any help from the group.

Jim Lancelot
U. S. Department of Veterans Affairs
Database Support Services
(512) 326-6471
fax: (512) 326-6731
email: jim.la...@mail.va.gov <mailto:jim.la...@mail.va.gov>

John Dell

unread,
May 31, 2000, 3:00:00 AM5/31/00
to
Jim

Could this be a security problem ? You have defined the user in the same
dictionary as your JCL module, and presumably given him DISPLAY authority at
least on modules, but have you secured your dictionary (with DB security) in
such a way that he cannot read modules ? This is a list of RUNUNITs we found we
had to grant OLQ users in each dictionary they were using:
ADD RUNUNIT ???DICT.IDMSNWKA.IDBCAT
ADD RUNUNIT ???DICT.IDMSNWKA.JSSEV*
ADD RUNUNIT ???DICT.IDMSNWKA.OLQ*
ADD RUNUNIT ???DICT.IDMSNWKA.RHDCEV08
ADD RUNUNIT ???DICT.IDMSNWKA.RHDCEV58
In addition, for users to execute Clists, we grant:
ADD RUNUNIT ???DICT.IDMSNWK8
to PUBLIC.

OLQ has a nasty habit of lying about security problems - for example, if the
user has not been granted access to the quoted subschema, it says it cannot find
the subschema.

Hope this helps.

______________________________________________________________________
This email, together with any attachments, is for the exclusive and confidential
use of the addressee(s). Any other distribution, use or reproduction without
the sender's prior consent is unauthorised and strictly prohibited. If you have
received this message in error, please notify the sender by email immediately
and delete the message from your computer without making any copies.

Hugh Laderman

unread,
May 31, 2000, 3:00:00 AM5/31/00
to
Just as an aside to your response, for some who may not know, the "lying" is actually (and intended to be), in itself, a security measure, and has been used widely within IDMS.
 
Hugh Laderman
Laderman Associates
(215) 493-3460 voice
(215) 493-0573 fax
hu...@laderman.com
0 new messages