The job queue QBATCH keeps locking up with the error
Subsystem description QBATCH not changed, on one specific user
Where do I go to give him this right?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
here is the message, basically this happens as part of a job that runs after a file is updated.
I inherited this system and don't know how to grant him the ability to interact with the QBATCH job queue.
Error message from job thats stuck in the QBATCH queue
jltoops:
That message refers to message CPF1697 in a batch job. The joblog of the batch job will have the CPF1697 message; and, immediately before CPF1697, there will be another message that gives the particular reason that CPF1697 was issued.
That message will be a 'diagnostic' message. It will indicate what the problem is. I suspect that the message will be something like CPD1402 -- Not authorized to subsystem description. That's likely to show up if authority is the actual problem as you indicate.
However, it could also be from some other cause. It could be that program BATCHONE is trying to add a routing entry and there is already a routing entry with the same sequence number. Other possibilities exist.
Can you locate the CPF1697 message in the joblog of the failing job?
Authority could be granted, but it might not fix any problem.
Tom
jltoops:
Multiple paths will get you there. From the screen you supplied, you should be able to press <F9=Display message details>. Near the center of the resulting display, you should see the name of the job that caused the CPA0701 Inquiry message to appear.
The number, user and job values might look something like 199661, JLTOOPS and BATCHJOB.
At a command line, you would enter:
== > dspjoblog 199661/JLTOOPS/BATCHJOB
The joblog of that specific instance of the BATCHJOB job should display. Near the bottom of the joblog is where the original CPF1697 should be. Immediately preceding it, there should be one or more diagnostic messages.
Personally, I would perhaps use the WRKSBS command and enter option 8 against the QBATCH subsystem to see what job is in MSGW status. I'd drill into that job with <option 5=Work with> and then <option 10=Display job log.>
Numerous other ways exist. The DSPJOBLOG command is explicitly for this purpose.
Tom
Business Accounts
Answer for Membership
by: tliottaPosted on 2008-11-20 at 10:34:27ID: 23006643
jltoops:
Please provide the error message identifier. Normally, that error shouldn't happen. No user should be doing anything to 'change' the QBATCH subsystem. And anyone who should be able to change the QBATCH subsystem ought to be able also to tell you why they're doing it.
Where do you see the message? Pressing <F1> with the cursor on the message should display the message identifier.
Tom